Re: [osol-discuss] Compile errors during onnv-gate
S h i v wrote: > On 8/6/07, James Carlson <[EMAIL PROTECTED]> wrote: >> It does seem puzzling. >> The reason is that: >> >> - SXDE (and in particular the "developer install" feature) was >> supposed to be aimed at developers who are writing software to run >> _on_ Solaris, and not those who are just compiling OpenSolaris >> itself. The former can make good use of having the freshest >> possible set of tools. >> > > If this is the case then GNU build tools must be included in SXDE. A > huge part of open source world use this ! Most of them already are - gcc, gmake, gdb, autoconf, etc. - what are you missing? -- -Alan Coopersmith- [EMAIL PROTECTED] Sun Microsystems, Inc. - X Window System Engineering ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] File Events Notification API - PSARC/2007/027
Kaiwai Gardiner wrote: > On Mon, 2007-08-06 at 20:09 +0200, Milan Jurik wrote: >> And I don't know why File Events Notification API - PSARC/2007/027 is >> not public. You can see who made the putback - ask him, maybe he is not >> reading this list. > > Its very hard to know when there is no name attached to the put back as > far as I see. The onnv-notify mail about the putback lists the committers name: http://mail.opensolaris.org/pipermail/onnv-notify/2007-July/012243.html -- -Alan Coopersmith- [EMAIL PROTECTED] Sun Microsystems, Inc. - X Window System Engineering ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] File Events Notification API - PSARC/2007/027
Hi Matthew, Kaiwai Gardiner pÃÅ¡e v út 07. 08. 2007 v 15:36 +1200: > On Mon, 2007-08-06 at 20:09 +0200, Milan Jurik wrote: > > Hi Matthew, > > > > I know I'm not right man who should answer you, as I'm from Sun... But > > look at it from another perspective: > > > > V po, 06. 08. 2007 v 19:18, Kaiwai Gardiner pÃÅ¡e: > > > Agreed, but at the same driver - are drivers *truely* that secret? I > > > mean, wpi for 3945 was developed in 'secret' - why? what possible loss > > > of competitive advantage would it yield? looking at it from my angle, > > > all I see are positives by way of consumers actually seeing and knowing > > > that Sun are making/porting drivers to Solaris. > > > > > > > Are you sure that Sun employees had access to 3945 development except > > the developer of it? The most of them didn't know about it. And it is > > way how distributed development happens - somebody (or some team) is > > working on something till point it is "compilable" or "usable" or just > > "publicable". The level of this point is on the developer decision, as > > usual in open source world. Some developers are publishing all their > > steps, some are publishing something usefull for users. You had the > > access to source code of wpi at the same time as the most of Sun > > employees. Today you can find on bugs.opensolaris.org the responsible > > engineer for all accepted RFEs, why not to contact him if you want to > > help with development and/or testing of some particular RFE? > > BUt at the same time - if the 'community' knew that wpi was being worked > on - Sun might have actually found people helping port it to Solaris :-) > > A small hear-ye hear-ye would have been on order. > But this happend, the responsible engineer took related RFE and you could see that on bugs.opensolaris.org. I agree with one thing - bugster is very good tool, but its public interface is not very useful in case that you want to monitor some CR. > > > I mean, if they're going to worry about 'competitive advantage' then why > > > announce to the world support for a product that doesn't yet exist in > > > the marketplace/still in development? > > > > > > > I don't think that in wpi case it was about competitive advantage. It > > was just way how the most of drivers in open source are developed - by > > some small team (typically with just one member), which is publishing > > their results when they are ready for public, per their decision. You > > can go and ask for source codes earlier if you want. And maybe the team > > will do it for you. > > But the driver is opensource and ported by Sun - I know about the > existance of wpi, what I didn't know about was Sun porting it to > Solaris. > Because you didn't monitor the RFE probably. Otherwise you would see that something happend and one man started to work on it. I know, not very simple these days. But still possible. > > And I don't know why File Events Notification API - PSARC/2007/027 is > > not public. You can see who made the putback - ask him, maybe he is not > > reading this list. > > Its very hard to know when there is no name attached to the put back as > far as I see. > http://mail.opensolaris.org/pipermail/onnv-notify/2007-April/007227.html -> 6381975 solaris need centrino ipw3945 wifi support http://bugs.opensolaris.org/view_bug.do?bug_id=6381975 -> now you know ;-) And I think that Brian is very active even in community to help people with this driver :-) He just worked hard to release something and even at that time he was ready to communicate with those who wrote e-mail to him (I know it :-) ). > > > Things should be merged into the public tree, just like they're merged > > > inside the company. Everything that occurs inside Sun should occur at > > > the same time on the other side - if a case log as been updated, then it > > > should be accessible to the public. > > > > > > > But wpi wasn't merged to Sun tree significantly sooner (it tooks few > > minutes, that sync between ON gate inside and outside). The developer > > worked on his source code in his own workspace. As usual. > > Would it be better to put documentation out there before the code? > That's typically PSARC and sometimes updates in Bugster. E.g. manpage is written after driver completition. Which docu? > > > Its all about transparency in the development process; and if it means > > > that developers think out aloud on ideas - I'd sooner see Sun > > > programmers conduct regular brain farts on a blog and know there is some > > > cranium activity about future Solaris development than just sitting on > > > the side lines praying something is occurring in the deep crypt of Sun. > > > > > > > Did you look at RFEs? Did you look at PSARCs? Did you look at projects > > on opensolaris.org? And can you show me some really big project where > > all developers are informing community about their actual work and > > future plans? > > > > Please, leave the decision about their openness on develop
Re: [osol-discuss] Compile errors during onnv-gate
On 8/6/07, James Carlson <[EMAIL PROTECTED]> wrote: > It does seem puzzling. > The reason is that: > > - SXDE (and in particular the "developer install" feature) was > supposed to be aimed at developers who are writing software to run > _on_ Solaris, and not those who are just compiling OpenSolaris > itself. The former can make good use of having the freshest > possible set of tools. > If this is the case then GNU build tools must be included in SXDE. A huge part of open source world use this ! (The mandatory packages of JDS_CBE - CBEfoo.pkg's can be included with SXDE) ~Shiv ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Can't install Open Solaris
On Tuesday 07 August 2007 02:45, Harvey Green wrote: > Hello People. > I thought I would like to try OpenSolaris but it won't install! when I > boot from the CD into Solaris Express or any other option it runs for a > while then say's can't find windowing system, and that's as far as it goes. I had the same with one VIA motherboard, though I actually used an NVidia graphics card. Never wasted time in searching "why", though. I just chose text mode installation and completed it. Then, when I first booted, my card was identified with no problem, window manager worked OK. Try text mode installation! (Later I changed the motherboard for an Intel *965 based one and never had that problem again.) > I run a home built PC with AMD AthlonXP 2800+ on a gigabyte GA-7N400 Pro2 > MB with NVIDIA FX200 Graphics & onboard GigaRaid IT8212F chipset. Now I > think that may be the problem, although Solaris 10 installs OK on the spare > drive albeit with no NIC driver or Sound Driver for my cards "ViaRhine" & > "Emu10k1" so can some one help me Please? For ViaRhine NIC drivers for Solaris(and possibly Emu10k1) search the web. I just don't remember now where, but I found the drivers. OSS sound drivers are now included in Solaris Express(some of them). > > > This message posted from opensolaris.org > ___ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org Sincerely yours, Berger Kostya pgp1m11zKc3iw.pgp Description: PGP signature ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] User defined functions call from Dtrace...!
HI Ravi, If you want to find memory leaks, you may try to see the difference between number of mallocs and number of frees. However you may find libumem/dbx more handy, atleast to begin with in finding memory leaks and memory corruption issues. Towards the end of the following article http://java.sun.com/javase/6/webnotes/trouble/TSG-VM/html/memleaks.html you will find some details. As for finding the best time, you can use aggregation function to find the max/min of all the time spent values. Look for aggregation function section on the following link. http://partneradvantage.sun.com/protected/solaris10/adoptionkit/tech/dtrace/usage.html If you want to find real time spent, probably vtimestamp may be useful. I haven't used it myself but you can try exploring that. Thanks Suraj rps wrote: > Hi, > May be my question looks silly but I wanna get clarified with experts. > I have written several D language scripts which generated lots of output > to all my programs. > the question is, how does this output helps me to debug my programs. what > I mean is, how do I find memory leaks in the program, how do I know how much > time control struct in a function(I used "self->ts[probefunc]=timestamp" > statement. the result is in nano seconds. but how do I know what is the idle > time/best time for that particular function execution). > I have written a simple C program which allocates memory by calling "malloc" > function as: > > char *p1; char *p2; > p1=(char*)malloc(1024); > p2=(char*)malloc(1024); > > I ran Dtrace for the same, the output shown as "malloc called 22 times..." > how does this output helps me to debug my prog... > > can someone help me on the proper usage of dtrace. > > > This message posted from opensolaris.org > ___ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org > ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Fwd: Sun Device Detection Tool 1.2 is released
> > Hi James, > > The grey out means that the Solaris installed on your system is not an > official release. It's just a build of Solaris. ah ha ... I was getting confused about that. also .. that button does not even exist when you run this on Sparc but that may be just a trivial point. Dennis ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] File Events Notification API - PSARC/2007/027
Sending it again.. my reply got lost... I am the person working on this feature. Briefly, the File Events Notification(FEN) facility provides means to monitor a file or directory for changes. The API is based on the event ports(the event notification framework) that was introduced in Solaris 10. The FEN facility will be added as an event source to the event notification framework. It is similar to FAM(SGI)/Gamin. But from what I know, FAM & Gamin, are user land implementations as a file monitoring services. They in turn use kernel file monitoring mechanisms like 'kqueues'(BSD), 'inotify'(on Linux) and 'imon'(SGI). On systems where such kernel mechanisms are not present it just polls. The FEN facility being added to Solaris is a kernel mechanism. Using these interfaces, applications can register files and directories to be monitored for changes and receive an event notification, via an event port, when change occurs. In that sense, it is similar to 'kqueues', 'inotify', 'imon', file monitoring mechanisms. There has been discussion regarding File Event Notification on the performance community forum ' [EMAIL PROTECTED]'. With regards to why is this case not public - You may have noticed, not all cases are discussed in public. We are still transitioning into the open development model. More and more cases are being discussed in public. I can certainly try and find out if we can make the case materials for this case public. -Prakash. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] File Events Notification API - PSARC/2007/027
On Mon, 2007-08-06 at 20:09 +0200, Milan Jurik wrote: > Hi Matthew, > > I know I'm not right man who should answer you, as I'm from Sun... But > look at it from another perspective: > > V po, 06. 08. 2007 v 19:18, Kaiwai Gardiner pÃÅ¡e: > > Agreed, but at the same driver - are drivers *truely* that secret? I > > mean, wpi for 3945 was developed in 'secret' - why? what possible loss > > of competitive advantage would it yield? looking at it from my angle, > > all I see are positives by way of consumers actually seeing and knowing > > that Sun are making/porting drivers to Solaris. > > > > Are you sure that Sun employees had access to 3945 development except > the developer of it? The most of them didn't know about it. And it is > way how distributed development happens - somebody (or some team) is > working on something till point it is "compilable" or "usable" or just > "publicable". The level of this point is on the developer decision, as > usual in open source world. Some developers are publishing all their > steps, some are publishing something usefull for users. You had the > access to source code of wpi at the same time as the most of Sun > employees. Today you can find on bugs.opensolaris.org the responsible > engineer for all accepted RFEs, why not to contact him if you want to > help with development and/or testing of some particular RFE? BUt at the same time - if the 'community' knew that wpi was being worked on - Sun might have actually found people helping port it to Solaris :-) A small hear-ye hear-ye would have been on order. > > I mean, if they're going to worry about 'competitive advantage' then why > > announce to the world support for a product that doesn't yet exist in > > the marketplace/still in development? > > > > I don't think that in wpi case it was about competitive advantage. It > was just way how the most of drivers in open source are developed - by > some small team (typically with just one member), which is publishing > their results when they are ready for public, per their decision. You > can go and ask for source codes earlier if you want. And maybe the team > will do it for you. But the driver is opensource and ported by Sun - I know about the existance of wpi, what I didn't know about was Sun porting it to Solaris. > And I don't know why File Events Notification API - PSARC/2007/027 is > not public. You can see who made the putback - ask him, maybe he is not > reading this list. Its very hard to know when there is no name attached to the put back as far as I see. > > Things should be merged into the public tree, just like they're merged > > inside the company. Everything that occurs inside Sun should occur at > > the same time on the other side - if a case log as been updated, then it > > should be accessible to the public. > > > > But wpi wasn't merged to Sun tree significantly sooner (it tooks few > minutes, that sync between ON gate inside and outside). The developer > worked on his source code in his own workspace. As usual. Would it be better to put documentation out there before the code? > > Its all about transparency in the development process; and if it means > > that developers think out aloud on ideas - I'd sooner see Sun > > programmers conduct regular brain farts on a blog and know there is some > > cranium activity about future Solaris development than just sitting on > > the side lines praying something is occurring in the deep crypt of Sun. > > > > Did you look at RFEs? Did you look at PSARCs? Did you look at projects > on opensolaris.org? And can you show me some really big project where > all developers are informing community about their actual work and > future plans? > > Please, leave the decision about their openness on developers. Some > prefer public development (lots of Sun employee), some are working in > their own workspaces (lots of Sun employee). > > You want just big amount of paperwork from us ;-) I hope the community > is not my second manager asking for weekly reports... Its about communication - I'm generally not a person who likes to communicate anything with anyone - I generally speaking keep people on a 'need to know' basis - but at the same time, there is a need to inform the community on what is happening. Tell the community what they're working on - and shock horror, they might actually find that a few of the great unwashed might actually be interested in contributing. Matthew ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Test post.
Oh my. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] File Events Notification API - PSARC/2007/027
I am the person working on this feature. Briefly, the File Events Notification(FEN) facility provides means to monitor a file or directory for changes. The API is based on the event ports(the event notification framework) that was introduced in Solaris 10. The FEN facility will be added as an event source to the event notification framework. It is similar to FAM(SGI)/Gamin. But from what I know, FAM & Gamin, are user land implementations as a file monitoring services. They in turn use kernel file monitoring mechanisms like 'kqueues'(BSD), 'inotify'(on Linux) and 'imon'(SGI). On systems where such kernel mechanisms are not present it just polls. The FEN facility being added to Solaris is a kernel mechanism. Use these interfaces applications can register files and directories to be monitored for changes and receive an event notification on an event port when change occurs. In that sense, it is similar to 'kqueues', 'inotify', 'imon', file monitoring mechanisms. There has been discussion regarding File Event Notification on the performance community forum ' [EMAIL PROTECTED]'. With regards to why is this case not public - You may have noticed, not all cases are discussed in public. We are still transitioning into the open development model. More and more cases are being discussed in public. I can certainly try and find out if we can make the case materials for this case public. -Prakash. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Fwd: Sun Device Detection Tool 1.2 is released
Hi Andrew, The submission is only available on official release of Solaris 10 and Solaris Express Developer Edition. It will be grey out on Solaris build, which is not an offical release. While it will be invisible on other OS, such as Windows and Linux. Thanks, Richard > >> I have tried this both ways on different revs of Solaris and >> sometimes I get >> the submission button and sometimes I don't. >> >> and .. I don't know why either. > > Is there any chance that the submission only appears when you are > running on Solaris 10 11/06 or Developer 5/07 releases. > > This seems to be the case for me. > > > Andrew ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Fwd: Sun Device Detection Tool 1.2 is released
Hi James, The grey out means that the Solaris installed on your system is not an official release. It's just a build of Solaris. Thanks, Richard > Ming Richard Wu - New Solaris/BJ writes: > >> Choose the 'Advanced' will lead you to the 'Settings', choose 'Java >> Console' and set it as 'Show console', then next time, Java Console will >> show with log, when you run Sun Device Detection Tool next time. >> >> Click the 'General' will lead you to "Network Settings', press the >> 'Network Setting' button, in the 'Network Setting' window, choose >> 'Direct Connection'. >> >> You probably can submit report if you set the 'Direct Connection' in >> Java Control Panel and your host has a hostname. However, if you still >> can not submit the report, please send me the log in the Java Console. >> > > I do all that, and I see nothing in the console window, and the > "HCL Submission" button is greyed out. > > Could this be because I use javaws rather than attempting to run it > inside a browser? > > ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] User defined functions call from Dtrace...!
Hi, May be my question looks silly but I wanna get clarified with experts. I have written several D language scripts which generated lots of output to all my programs. the question is, how does this output helps me to debug my programs. what I mean is, how do I find memory leaks in the program, how do I know how much time control struct in a function(I used "self->ts[probefunc]=timestamp" statement. the result is in nano seconds. but how do I know what is the idle time/best time for that particular function execution). I have written a simple C program which allocates memory by calling "malloc" function as: char *p1; char *p2; p1=(char*)malloc(1024); p2=(char*)malloc(1024); I ran Dtrace for the same, the output shown as "malloc called 22 times..." how does this output helps me to debug my prog... can someone help me on the proper usage of dtrace. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Can't install Open Solaris
Hello People. I thought I would like to try OpenSolaris but it won't install! when I boot from the CD into Solaris Express or any other option it runs for a while then say's can't find windowing system, and that's as far as it goes. I run a home built PC with AMD AthlonXP 2800+ on a gigabyte GA-7N400 Pro2 MB with NVIDIA FX200 Graphics & onboard GigaRaid IT8212F chipset. Now I think that may be the problem, although Solaris 10 installs OK on the spare drive albeit with no NIC driver or Sound Driver for my cards "ViaRhine" & "Emu10k1" so can some one help me Please? This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] File Events Notification API - PSARC/2007/027
Hi Cyril, > Hi Milan, > > On 8/6/07, Milan Jurik <[EMAIL PROTECTED]> wrote: > > > Did you look at RFEs? Did you look at PSARCs? Did you look at projects > > on opensolaris.org? And can you show me some really big project where > > all developers are informing community about their actual work and > > future plans? > > Umm, Linux ? Are you sure about this? I spent lots of time in lkml... Lots of patches (even bigger) are comming "from sky". > In fact in the open source world it is a matter of etiquette. Why? Why should he publish all his steps? He can go and develop something himself, because he prefers to spend some time just with "his code". Not all are "exhibicionists" (please, read this word in positive way, or just say that I'm Czech who doesn't know English very well :-) ). > Working privately is one's choice, of course. However, it would demonstrate > a disrespect to the rest of the community. Why ? Because at the end of the > work one will, essentially, throw the code over the wall. > Disrespect? Because you want to publish something really working, not just some skeleton? Are you publishing all your "everyday" changes? Could you respect that some developers prefer to "work in bigger steps" and not consulting their everyday steps with others? It is normal even in companies. > > Please, leave the decision about their openness on developers. Some > > prefer public development (lots of Sun employee), some are working in > > their own workspaces (lots of Sun employee). > > We (community) cannot decide for Sun employees how to do their > work for Sun. Nonetheless we can create rules for work integrated > into OpenSolaris. I think it is fair. > Of course. Could you specify one example of rule which will prohibit the integration that somebody is working in his own workspace and going to public just before integration or ARC, please? It is his decision to do it in this way. And potentially very dangerous, because: a) his work must not be accepted by others, as he implemented something in "unpopular" way b) somebody will implement it quicker c-d-e-f-...) add your own points here Is his contribution worse because he decided to not communicate frequently? > > You want just big amount of paperwork from us ;-) I hope the community > > is not my second manager asking for weekly reports... > > That strange conclusion. How did you get to it ? > And what are you asking for in "wpi cases"? And btw. I added some "hints" how to receive FEM API to my previous e-mail, the main topic of this thread. Why are you complaining here? What are you expecting? That our CEO will go and push us in some way? Are you sure that this will make Sun engineers happy members of opensolaris community? We are just people, people with e-mail addresses ;-) Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] [indiana-discuss] CDE Update?
Yuriy Y. Yermilov wrote: > Anyone know if CDE will still be around for Indiana release? It's not likely to be included due to the licensing issues - it's already starting to be removed from Nevada/Solaris Express anyway. (sdtimage is gone now.) > If so do you think it will be updated to 2.1 or something greater than 1.7? You're mixing version numbers there. The OpenGroup released CDE 1.0 & 2.1. Sun's CDE has always been based on OpenGroup CDE 1.0, but incremented the version number for each Solaris release, so Sun CDE 1.7 is still based on OpenGroup CDE 1.0. Since the only work Sun is putting into CDE now is removing it from Solaris, there is no chance of updating to a new OpenGroup version. > Also is there a way to update solaris 10 CDE from 1.6.3 to 1.7_64? I don't think the Nevada (CDE 1.7) packages will run on Solaris 10, but have never tried it. -- -Alan Coopersmith- [EMAIL PROTECTED] Sun Microsystems, Inc. - X Window System Engineering ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] CDE Update?
Anyone know if CDE will still be around for Indiana release? If so do you think it will be updated to 2.1 or something greater than 1.7? Also is there a way to update solaris 10 CDE from 1.6.3 to 1.7_64? I just really like CDE (personal choice) gnome is nice too. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Fwd: Sun Device Detection Tool 1.2 is released
Andrew Watkins writes: > > > I have tried this both ways on different revs of Solaris and sometimes I get > > the submission button and sometimes I don't. > > > > and .. I don't know why either. > > Is there any chance that the submission only appears when you are > running on Solaris 10 11/06 or Developer 5/07 releases. > > This seems to be the case for me. Ah, ok. That's what I'm seeing. I couldn't figure it out. For me, a user interface that greys things out might as well just be dumping core. I get zero information from greyed-out selections -- it makes me think that I *should* be able to do that, but that the system is just being ornery. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Fwd: Solaris "thinks" that my standalone desktop is a huge network....
On 8/4/07, Sivasubramanian Muthusamy <[EMAIL PROTECTED]> wrote: > On 8/4/07, Kaiwai Gardiner <[EMAIL PROTECTED]> wrote: > > On Fri, 2007-08-03 at 23:08 -0700, Sivasubramanian Muthusamy wrote: > > > My post was in a certain manner of expression. On rapid reading, > > > ux-admin and other readers thought that i did not understand the > > > basics of how elaborate the O/S is or that I did not understand the > > > purpose for built in measures such as the time taken to shut down the > > > system. > > > > > > The post was on the task of taking Solaris to the home segment as more > > > elaborately addressed in > > > http://www.opensolaris.org/jive/thread.jspa?threadID=36522&tstart=0 > > > > > > What I wrote here was written wearing a non-technical user's shoes, so > > > my post was to present, DELIBERATELY, uneducated questions to the > > > experts in the forum. > > > > > > ux-admin wrote about the user also having to be the root in a single > > > board computer, I am planning to sell Solaris to a user who would > > > blink if the terminal screen pops up. No, he does not want to be the > > > root, and he becomes the root, he would do something like run an fsck > > > and say yes when he has to say, and say no when he has to say yes and > > > end up wiping out the hard disk for a trivial problem. I don't want > > > the standalone user to get anywhere near the terminal, but he needs to > > > have access to the functionality of all ( and only those ) > > > applications that he needs. > > > > > > You went on to say that UNIX is a multi user system etc.. Yes I know > > > how elaborate Solaris is, I know that each function and limitation has > > > a purpose and that Solaris is amazing in the context of a multiuser > > > system. I wouldn't make a multiuser system any easier, nor would I > > > relax the controls in any manner, in fact I would still harden Solaris > > > in a multi user, mission critical setting. > > > > > > Again the post is that of a non-technical, completely non-technical, > > > user thinking aloud. > > > > And if he or she is a 'completely non-technical person' he or she > > wouldn't even be talking about what operating system is being used. He > > or she wouldn't even be contemplating purchasing a Solaris machine. > > > > > > If you wish to use Solaris effectively, you will have to do some > > > reading. > > > > > > No, the user that I have in mind doesn't care to read. > > > > And if that is the case, that said user wouldn't even be considering > > moving from Windows. They would be ignorantly content with what they > > have. > > > > > >Do you even care to understand? > > > > > > No, the user doesn't care to understand. He wants it to be easy, he > > > wants it to work. He is that uncooperative, and he is that irrational, > > > and he is the Boss. > > > > So why even try to sell to a customer who will cost more than the money > > he will actually bring in, in regards to profits? > > > > > >For a thing so powerful, complexity is inherent; and while some > > > things can be simplified, some level of understanding will be > > > required. > > > > > > Waynel, I have answered you as well. Thank you for the commands to > > > shut down immediately. I will go ahead and make a little button and > > > put in the launch menu, or modify the log in button in the user's > > > interface to say include shut down. I knew that such possibilities > > > exist within Solaris, the post is about bringing such ease to the > > > fore, in order to come up with a single user's computer for someone > > > "who doesn't care to understand, who wouldn't read" > > > > > > Ian, I am more talking about Solaris 10, Version 11/06, but I have > > > also been exposed to more advanced developer versions. The shut down > > > feature is not the only difficulty that I am talking about. I am > > > talking about identifying such "irritants" for the common man, who is > > > the Master by virtue of the fact that he has bought a $500 machine > > > with Solaris. > > > > Why would you be even selling a desktop aimed at a user with Solaris 10 > > 11/06? why don't you want till Indiana, which is actually geared to that > > market along with support infrastructure by way of telephone and > > software updates. > > No, I have not decided on Solaris 10 11/16. I have also been exposed > to the most recent developer editions. Indiana sounds promising. > > > > > Che, the reference to the user phoning up the admin to shut down the > > > system, is just an expression, a manner of expressing how > > > non-technical he could be. In a single user environment, there is no > > > system administrator, so the question of the system admin being > > > comptent or incompetent does not arise. It should be decided at the > > > installation level, before the computer reaches his home. > > > > > > That is where the challenge is. If GM wanted you to master the complex > > > aspects of the valve dynamics and transmission mechanism before it > > > qualified you to buy a car,
Re: [osol-discuss] Solaris "thinks" that my standalone desktop is a huge network....
Dear Ian Collins, > This isn't the place to discuss the shortcomings of Solaris 10, many of > these have been addressed in Solaris Express and other OpenSolaris based > distributions. Let the past rest and look to the future. I have seen looked at developer editions, some of the most recent versions of it, some of the shortcomings that I had specifically mentioned might have been resolved, but the essence of what I am talking about is better understood by actually using Mac or Windows Vista. ( this is with a PURPOSE, use windows or mac, suspending all your technical background, imagine that you are dumb and use Windows or Mac ) > > I have been trialling Solaris Express with an uncommon woman, a far more > fickle user than your common man. The only thing preventing her > adopting Solaris as her exclusive desktop is some windows only > software. The main reason she and a number of other in bunt terms, > computer illiterate, users want to to use an alternative desktop is the > volume of malware directed at windows. They don't really care what > their PC runs, they just want something reliable and safe to read their > mail, pay their bills and write the occasional letter. That is very very interesting. But is she finding it easy to upgrade a browser ? Does she like the idea of downloading the update and following the command line routine of pkgadd etc. ? No, I am not so much comfortable with Solaris 10,. I might go along with Indiana. Sivasubramanian. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] So... when is Sun going to start offering SXCE/SXDE support contracts?
Bart, Thanks - that sounds perfect. Do I understand then that Sun would offer a structured (whatever that means) support mechanism for specific "stops" on the release train? On 8/2/07, Bart Smaalders <[EMAIL PROTECTED]> wrote: > > Glen Wiley wrote: > > Bart, > > > > You or Tim had mentioned the idea of being able to support > > "checkpoints" of some kind which would let more rigid environments > > take advantage of some of the more useful features with reduced risk. > > Do you see motion in that direction? > > > > With the new packaging/software repository, we'll be able to update the > software on a machine by downloading the difference between where the > target machine and the desired end state. Using ZFS root, this will be > completely reversible. Once the new packaging system is part of > our mainline development environment, it would be possible to offer > a release train containing periodic large scale change, interspersed > with small scale critical fixes. > > - Bart > > > -- > Bart Smaalders Solaris Kernel Performance > [EMAIL PROTECTED] http://blogs.sun.com/barts > -- Glen Wiley "But our citizenship is in heaven, and from it we await a Savior, the Lord Jesus Christ," Phil 3:20 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] File Events Notification API - PSARC/2007/027
Hi Milan, On 8/6/07, Milan Jurik <[EMAIL PROTECTED]> wrote: > Did you look at RFEs? Did you look at PSARCs? Did you look at projects > on opensolaris.org? And can you show me some really big project where > all developers are informing community about their actual work and > future plans? Umm, Linux ? In fact in the open source world it is a matter of etiquette. Working privately is one's choice, of course. However, it would demonstrate a disrespect to the rest of the community. Why ? Because at the end of the work one will, essentially, throw the code over the wall. > Please, leave the decision about their openness on developers. Some > prefer public development (lots of Sun employee), some are working in > their own workspaces (lots of Sun employee). We (community) cannot decide for Sun employees how to do their work for Sun. Nonetheless we can create rules for work integrated into OpenSolaris. I think it is fair. > You want just big amount of paperwork from us ;-) I hope the community > is not my second manager asking for weekly reports... That strange conclusion. How did you get to it ? -- Regards, Cyril ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] OSS integration status? was Re: Sound Blaster Live! in ONNV
[...] > The one thing I'd ask about here is whether the > project team is aware > of the OSS integration project (that will likely be > obsoleting the old > SADA bits), and if this project conflicts with or is > obsoleted by that > one. If so, then coordinating with them would be > helpful. [...] What's the status of the OSS integration? On SPARC, last I tried, it was still not very useful (compatibility interface didn't work, simple Logitech USB headset had audible glitches (but was fine under Sun driver), SB Audigy NX USB didn't work, no support for builtin audio devices (audiocs in my case)). Not to mention that until it is the one true solution, the uninstall leaves enough of a mess that backing up devlink.tab driver_classes name_to_major driver_aliases minor_perm path_to_inst (and maybe others?) before installing is advisable, so as to be able to restore them after uninstalling. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] User defined functions call from Dtrace...!
Thanx suraj, it really helped me to debug my programs... This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Solaris "thinks" that my standalone desktop is a huge network....
James Carlson wrote: > UNIX admin writes: > Do you even care to understand? >>> I don't think it's helpful at all to chase away >>> people who want to use >>> an OpenSolaris-based distribution in an unexpected or >>> novel way. We >>> actually do _want_ new users. >>> >> Did you find that question offensive? >> > [...] > > To stretch the analogy a great deal further, it's possible to operate > some pretty complex devices (including radios, TVs, and recording > machines) without having to learn how they operate internally. That > wasn't always true (particularly so in the pre-superhet days), but it > should be so if you're going to capture more ordinary users. > > Whether a simplified usage model is an install choice, a per-user > login option, or a completely separate distribution, I don't care. I > do think it'd be a worthwhile goal, though, and that the original > poster was not wrong for asking about it. > Agree wholeheartedly. Why should an user have to learn Unix in order to use a Word Processor. Maybe that person is writing a novel and wants to concentrate on the characters, plot, storyline rather than fumbling with ls flags. A developer/cs student/hacker however, by all means, learn Unix, work with the CLI etc. Regards, Moinak. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] File Events Notification API - PSARC/2007/027
Hi Matthew, I know I'm not right man who should answer you, as I'm from Sun... But look at it from another perspective: V po, 06. 08. 2007 v 19:18, Kaiwai Gardiner píše: > Agreed, but at the same driver - are drivers *truely* that secret? I > mean, wpi for 3945 was developed in 'secret' - why? what possible loss > of competitive advantage would it yield? looking at it from my angle, > all I see are positives by way of consumers actually seeing and knowing > that Sun are making/porting drivers to Solaris. > Are you sure that Sun employees had access to 3945 development except the developer of it? The most of them didn't know about it. And it is way how distributed development happens - somebody (or some team) is working on something till point it is "compilable" or "usable" or just "publicable". The level of this point is on the developer decision, as usual in open source world. Some developers are publishing all their steps, some are publishing something usefull for users. You had the access to source code of wpi at the same time as the most of Sun employees. Today you can find on bugs.opensolaris.org the responsible engineer for all accepted RFEs, why not to contact him if you want to help with development and/or testing of some particular RFE? > I mean, if they're going to worry about 'competitive advantage' then why > announce to the world support for a product that doesn't yet exist in > the marketplace/still in development? > I don't think that in wpi case it was about competitive advantage. It was just way how the most of drivers in open source are developed - by some small team (typically with just one member), which is publishing their results when they are ready for public, per their decision. You can go and ask for source codes earlier if you want. And maybe the team will do it for you. And I don't know why File Events Notification API - PSARC/2007/027 is not public. You can see who made the putback - ask him, maybe he is not reading this list. > Things should be merged into the public tree, just like they're merged > inside the company. Everything that occurs inside Sun should occur at > the same time on the other side - if a case log as been updated, then it > should be accessible to the public. > But wpi wasn't merged to Sun tree significantly sooner (it tooks few minutes, that sync between ON gate inside and outside). The developer worked on his source code in his own workspace. As usual. > Its all about transparency in the development process; and if it means > that developers think out aloud on ideas - I'd sooner see Sun > programmers conduct regular brain farts on a blog and know there is some > cranium activity about future Solaris development than just sitting on > the side lines praying something is occurring in the deep crypt of Sun. > Did you look at RFEs? Did you look at PSARCs? Did you look at projects on opensolaris.org? And can you show me some really big project where all developers are informing community about their actual work and future plans? Please, leave the decision about their openness on developers. Some prefer public development (lots of Sun employee), some are working in their own workspaces (lots of Sun employee). You want just big amount of paperwork from us ;-) I hope the community is not my second manager asking for weekly reports... Best regards, Milan (not opensolaris developer, "only" Solaris sustainer) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] IBM ServeRAID 4 installation
Hi all. Is it possible using open solaris IBM ServeRAID 4 driver on a fresh Solaris 10 install ? and if yes, how ? Thanks, Noam Segal This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] An Open Letter to the Solaris Community.
On Mon, 2007-08-06 at 17:23 +0200, Joerg Schilling wrote: > Brandorr <[EMAIL PROTECTED]> wrote: > > > On 8/6/07, Mario Goebbels <[EMAIL PROTECTED]> wrote: > > > > > > Well, I've taken a look and the development of a Linux reader has pretty > > > much stagnated the same time the Solaris SPARC, AIX and HP-UX builds have. > > > All are stuck at 7.0.9, so I suppose Adobe simply just doesn't believe in > > > *nix. > > > > > > Unless you don't count Mac OS X as Unix. > > Before continuing this discussion, I would be really interested to know how > Apple did pass the POSIX compliance tests on Mac OS X. > > Jörg > They must have done some major changes in Leopard given it is UNIX 2003 compliant. Matthew ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] File Events Notification API - PSARC/2007/027
On Mon, 2007-08-06 at 18:03 +0100, Robert Milkowski wrote: > Hello Kaiwai, > > Monday, August 6, 2007, 11:58:32 AM, you wrote: > > KG> On Mon, 2007-08-06 at 10:37 +0100, Robert Milkowski wrote: > >> Hello Kaiwai, > >> > >> Saturday, August 4, 2007, 4:13:52 AM, you wrote: > >> > >> KG> On Fri, 2007-08-03 at 19:42 +0100, Robert Milkowski wrote: > >> >> Hello opensolaris-discuss, > >> >> > >> >> Can anyone shed some light on it? Maybe PSARC materials can be made > >> >> publicly available? > >> >> > >> > >> KG> The way I interpete it, it is something like FAM which allows things > >> KG> like nautilus to know when something has been change in the file system > >> KG> so that it automatically is shown in the file manager window. > >> > >> I had the same thought still that information should more openly > >> available, more in a spirit of open source > >> > > KG> Unfortunately development by Sun isn't occuring in the public, which > KG> kinda sucks - someone needs to remind Sun what opensource actually > KG> means. > > Some does some not - we should give them credit for all what has been > done so far - it's a huge changeover. > > I can understand that some projects will be developed 'secretely' and > only then integrated - after all Sun is competing in a market. > > However what is a reasoning for not publishing arc case like in that > example with file event notification API? I guess there's none - just > old habits... Agreed, but at the same driver - are drivers *truely* that secret? I mean, wpi for 3945 was developed in 'secret' - why? what possible loss of competitive advantage would it yield? looking at it from my angle, all I see are positives by way of consumers actually seeing and knowing that Sun are making/porting drivers to Solaris. I mean, if they're going to worry about 'competitive advantage' then why announce to the world support for a product that doesn't yet exist in the marketplace/still in development? Things should be merged into the public tree, just like they're merged inside the company. Everything that occurs inside Sun should occur at the same time on the other side - if a case log as been updated, then it should be accessible to the public. Its all about transparency in the development process; and if it means that developers think out aloud on ideas - I'd sooner see Sun programmers conduct regular brain farts on a blog and know there is some cranium activity about future Solaris development than just sitting on the side lines praying something is occurring in the deep crypt of Sun. Matthew ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] File Events Notification API - PSARC/2007/027
Hello Kaiwai, Monday, August 6, 2007, 11:58:32 AM, you wrote: KG> On Mon, 2007-08-06 at 10:37 +0100, Robert Milkowski wrote: >> Hello Kaiwai, >> >> Saturday, August 4, 2007, 4:13:52 AM, you wrote: >> >> KG> On Fri, 2007-08-03 at 19:42 +0100, Robert Milkowski wrote: >> >> Hello opensolaris-discuss, >> >> >> >> Can anyone shed some light on it? Maybe PSARC materials can be made >> >> publicly available? >> >> >> >> KG> The way I interpete it, it is something like FAM which allows things >> KG> like nautilus to know when something has been change in the file system >> KG> so that it automatically is shown in the file manager window. >> >> I had the same thought still that information should more openly >> available, more in a spirit of open source >> KG> Unfortunately development by Sun isn't occuring in the public, which KG> kinda sucks - someone needs to remind Sun what opensource actually KG> means. Some does some not - we should give them credit for all what has been done so far - it's a huge changeover. I can understand that some projects will be developed 'secretely' and only then integrated - after all Sun is competing in a market. However what is a reasoning for not publishing arc case like in that example with file event notification API? I guess there's none - just old habits... -- Best regards, Robert Milkowski mailto:[EMAIL PROTECTED] http://milek.blogspot.com ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] An Open Letter to the Solaris Community.
On 8/6/07, Joerg Schilling <[EMAIL PROTECTED]> wrote: > > Brandorr <[EMAIL PROTECTED]> wrote: > > > On 8/6/07, Mario Goebbels <[EMAIL PROTECTED]> wrote: > > > > > > Well, I've taken a look and the development of a Linux reader has > pretty > > > much stagnated the same time the Solaris SPARC, AIX and HP-UX builds > have. > > > All are stuck at 7.0.9, so I suppose Adobe simply just doesn't believe > in > > > *nix. > > > > > > Unless you don't count Mac OS X as Unix. > > Before continuing this discussion, I would be really interested to know > how > Apple did pass the POSIX compliance tests on Mac OS X. http://arstechnica.com/journals/apple.ars/2007/08/01/mac-os-x-leopard-receives-unix-03-certification This isn't the current release. It is for the upcoming release, Leopard, that happens to also include ZFS. (Also it's only the x86 build.) I guess the question is, why wouldn't they pass the certification? -Brian ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Fwd: Sun Device Detection Tool 1.2 is released
> I have tried this both ways on different revs of Solaris and sometimes I get > the submission button and sometimes I don't. > > and .. I don't know why either. Is there any chance that the submission only appears when you are running on Solaris 10 11/06 or Developer 5/07 releases. This seems to be the case for me. Andrew ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Fwd: Sun Device Detection Tool 1.2 is released
> Ming Richard Wu - New Solaris/BJ writes: >> Choose the 'Advanced' will lead you to the 'Settings', choose 'Java >> Console' and set it as 'Show console', then next time, Java Console will >> show with log, when you run Sun Device Detection Tool next time. >> >> Click the 'General' will lead you to "Network Settings', press the >> 'Network Setting' button, in the 'Network Setting' window, choose >> 'Direct Connection'. >> >> You probably can submit report if you set the 'Direct Connection' in >> Java Control Panel and your host has a hostname. However, if you still >> can not submit the report, please send me the log in the Java Console. > > I do all that, and I see nothing in the console window, and the > "HCL Submission" button is greyed out. > > Could this be because I use javaws rather than attempting to run it > inside a browser? I have tried this both ways on different revs of Solaris and sometimes I get the submission button and sometimes I don't. and .. I don't know why either. Dennis ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Fwd: Sun Device Detection Tool 1.2 is released
> > Hi Dennis, > > Yes, I need you copy and paste the log in the Java Console if you still > can not submit the report. One possibility that you can not see the > Java Console may be caused by the different of Java. What different Java ? This is a Solaris 10 Update 2 machine fully patched up to date. When I run the javaws binary with the sddt 1.2 jnlp file as the parameter I eventually get the same results over and over : http://www.blastwave.org/dclarke/blog/images/SDDT_JavaConsole_005.png or just : http://www.blastwave.org/dclarke/blog/images/SDDT_1.2_006.png but in any case I did run snoop to watch the packet flow and not one packet ever goes out the door. It is a mystery. > So, if you run /usr/java/jre/bin/ControlPanel to set the Java Control > Panel, then you should try /usr/java/jre/javaws to start the download > jnlp file. Yes, I did that. > On the Sun Download center web page you click the link and > choose save file then start the jnlp by running /usr/java/jre/javaws > sddtool_12.jnlp. That is precisely what I have been doing since version 1.0. You can see the command in the xterm in this screenshot : http://www.blastwave.org/dclarke/blog/images/SDDT_JavaConsole_003.png Dennis ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] An Open Letter to the Solaris Community.
Brandorr <[EMAIL PROTECTED]> wrote: > On 8/6/07, Mario Goebbels <[EMAIL PROTECTED]> wrote: > > > > Well, I've taken a look and the development of a Linux reader has pretty > > much stagnated the same time the Solaris SPARC, AIX and HP-UX builds have. > > All are stuck at 7.0.9, so I suppose Adobe simply just doesn't believe in > > *nix. > > > Unless you don't count Mac OS X as Unix. Before continuing this discussion, I would be really interested to know how Apple did pass the POSIX compliance tests on Mac OS X. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] An Open Letter to the Solaris Community.
On Mon, 2007-08-06 at 10:36 -0400, Brandorr wrote: > On 8/6/07, Mario Goebbels <[EMAIL PROTECTED]> wrote: > Well, I've taken a look and the development of a Linux reader > has pretty much stagnated the same time the Solaris SPARC, AIX > and HP-UX builds have. All are stuck at 7.0.9, so I suppose > Adobe simply just doesn't believe in *nix. > > Unless you don't count Mac OS X as Unix. > ___ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org Unfortunately it is for ever wedded to Apple hardware, thus makes it a non-viable alternative to Windows. Matthew ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] An Open Letter to the Solaris Community.
On Mon, 2007-08-06 at 07:32 -0700, Mario Goebbels wrote: > Well, I've taken a look and the development of a Linux reader has > pretty much stagnated the same time the Solaris SPARC, AIX and HP-UX > builds have. All are stuck at 7.0.9, so I suppose Adobe simply just > doesn't believe in *nix. True - it would be great to see Adobe contribute to Evince since they're not willing to maintain an uptodate version of adobe acrobate for *NIX. matthew > > -mg > > > Flash was supplied via an agreement with Macromedia - > > Adobe merely held > > up the original agreement. I doubt very much that > > Adobe would have > > created a Flashplayer for Solaris given Adobes > > refusal to provide > > Acrobat for Solaris - even after Sun offered to pay > > for the porting of > > it to Solaris x86. > > > This message posted from opensolaris.org > ___ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] So... when is Sun going to start offering SXCE/SXDE support contracts?
It sounds as though Sun is heading in the right direction. I am most interested in how we can take advantage of Open Solaris for production systems that serve very narrow, but very high visibility functions and that must meet strict service levels. These sort of systems are typically designed so that catastrophic failures on a set of platforms do not degrade service, via design points such as logical and geographic load balancing and diverse platforms. This permits us some latitude. In a case where OpenSolaris provides a feature that addresses a specific problem (one sufficiently important) I would like to have the option of using it rather than waiting for the feature to make it into the GA Solaris release. it is easier for me to make the management team comfortable if we can expect only slightly elevated risks of defects and the confidence that Sun is prepared to help solve the problem via some "active" support mechanism. I would like to be able to call Sun and say "build 123 has this specific problem" and know that an engineer will be assigned by Sun to bring the problem to a resolution within a week or so. Since there is often significant investment in QA cycles for a platform that includes interoperability between the HW/OS/APP/Network by our own internal teams this should not include a pat response of "are you using the LATEST build?". This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Sound Blaster Live! in ONNV
Vladimir Kotal writes: > Now, how to handle the following issues: >- integration process itself (assuming PSARC is needed, open source > review, code review) You'll need to work out the license issues with legal. I would _assume_ that part would be trivial, but I'm not a lawyer, and it sounds like you need one. As for PSARC, the "yet another instance of a known thing" case isn't all that architecturally interesting. This looks like just yet another audio driver, and should conform to all the expectations for audio drivers on Solaris. Unless the C-team demands an ARC case as a reference, I see no need for extra review. The one thing I'd ask about here is whether the project team is aware of the OSS integration project (that will likely be obsoleting the old SADA bits), and if this project conflicts with or is obsoleted by that one. If so, then coordinating with them would be helpful. >- support model for the driver once integrated Support and testing for contributed drivers seems like a pretty confusing area. Contact the ON C-team for help. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] An Open Letter to the Solaris Community.
On 8/6/07, Mario Goebbels <[EMAIL PROTECTED]> wrote: > > Well, I've taken a look and the development of a Linux reader has pretty > much stagnated the same time the Solaris SPARC, AIX and HP-UX builds have. > All are stuck at 7.0.9, so I suppose Adobe simply just doesn't believe in > *nix. Unless you don't count Mac OS X as Unix. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] An Open Letter to the Solaris Community.
Well, I've taken a look and the development of a Linux reader has pretty much stagnated the same time the Solaris SPARC, AIX and HP-UX builds have. All are stuck at 7.0.9, so I suppose Adobe simply just doesn't believe in *nix. -mg > Flash was supplied via an agreement with Macromedia - > Adobe merely held > up the original agreement. I doubt very much that > Adobe would have > created a Flashplayer for Solaris given Adobes > refusal to provide > Acrobat for Solaris - even after Sun offered to pay > for the porting of > it to Solaris x86. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Sound Blaster Live! in ONNV
Hi all, First, sorry for cross-posting but this is also related to how OpenSolaris handles external contributions. I am trying to find a way how to incorporate 'audioemu' driver for Sound Blaster Live! (EMU10K based) into ONNV. The driver in question was written by Juergen Keil (Cc'ed) and is covered by BSD license (AFAIK both original code from NetBSD and the glue needed for Solaris). The driver itself works (I've been using it for months w/out a problem) and I've blogged about it here: http://blogs.sun.com/vlad/entry/sound_blaster_live_on_solaris Now, how to handle the following issues: - integration process itself (assuming PSARC is needed, open source review, code review) - my knowledge of drivers is very limited, just want to help to integrate it - support model for the driver once integrated - this could be generic question for every new external driver integrated v. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Fwd: Sun Device Detection Tool 1.2 is released
Ming Richard Wu - New Solaris/BJ writes: > Choose the 'Advanced' will lead you to the 'Settings', choose 'Java > Console' and set it as 'Show console', then next time, Java Console will > show with log, when you run Sun Device Detection Tool next time. > > Click the 'General' will lead you to "Network Settings', press the > 'Network Setting' button, in the 'Network Setting' window, choose > 'Direct Connection'. > > You probably can submit report if you set the 'Direct Connection' in > Java Control Panel and your host has a hostname. However, if you still > can not submit the report, please send me the log in the Java Console. I do all that, and I see nothing in the console window, and the "HCL Submission" button is greyed out. Could this be because I use javaws rather than attempting to run it inside a browser? -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Compile errors during onnv-gate
Patrick Ale writes: > Maybe an ignorant question but.. why ship SS12 with SXCE and SXDE when > 11 is what you're recommending? It does seem puzzling. The reason is that: - SXDE (and in particular the "developer install" feature) was supposed to be aimed at developers who are writing software to run _on_ Solaris, and not those who are just compiling OpenSolaris itself. The former can make good use of having the freshest possible set of tools. - The two groups (ON and compiler) are separate. - Each consolidation actually picks a Common Build Environment (CBE) independently -- ON isn't the only consolidation. The synchronization for a switch is somewhat involved. I agree that it's annoying. It's even arguably "broken" in some contexts (particularly so for OpenSolaris). I hope it's just temporary and a side-effect of showing incremental progress rather than distinct releases. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Solaris "thinks" that my standalone desktop is a huge network....
UNIX admin writes: > > > Do you even care to understand? > > > > I don't think it's helpful at all to chase away > > people who want to use > > an OpenSolaris-based distribution in an unexpected or > > novel way. We > > actually do _want_ new users. > > Did you find that question offensive? Amazingly so, yes. The user had an application that was itself completely valid -- treating the operating system as a mere appliance in service of some larger job. You proceeded to tell him that, not only does he need to spend his time learning the innermost details of the operating system in order to use it at all effectively, details that are irrelevant to the reason he bought the machine, but hinted that it was foolish to wish otherwise. I think it'd be perfectly reasonable to have the option to use Solaris without having to learn the details. It's almost certainly true that in order to do this, you'll need to give something else up. Perhaps you won't be tweaking fdisk cylinder boundaries or frobbing about with IP interface flags. But for users who have needs that are a bit more modest, I think the "it just works" philosophy is fine. As I said in the portion of my posting that you trimmed away, Mac OS X has shown quite nicely that it's possible to have something that's both a Unix-based system and something that's easy for novices to use and maintain over time. You may disagree that this is a "good" thing -- that those users are sacrificing some sort of purity-of-essence by refusing to learn anything about POSIX or other Unix-related bits -- but it turns out that, for their usage, it just doesn't matter. To stretch the analogy a great deal further, it's possible to operate some pretty complex devices (including radios, TVs, and recording machines) without having to learn how they operate internally. That wasn't always true (particularly so in the pre-superhet days), but it should be so if you're going to capture more ordinary users. Whether a simplified usage model is an install choice, a per-user login option, or a completely separate distribution, I don't care. I do think it'd be a worthwhile goal, though, and that the original poster was not wrong for asking about it. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] DL385 hangs after 90 minutes with B66
Hi, On 08/06/07 13:04, Chris Linton-Ford wrote: Apologies for the delay in replying - our fileserver died a grisly death on Friday afternoon. Could you do the following for me, please: 0) In your BIOS options look for an option to remap/reclaim the dram hole, and if it is offering a choice of "software" vs "hardware" remapping select hardware. If that was not already selected reboot with that setting and see if the hang occurs. Set the following in /etc/system to increase the scrub rate we apply so (if we're guilty) you won't have to wait 90 minutes each time: set cpu\.AuthenticAMD\.15:ao_scrub_rate_dram=1 No option exists in the BIOS Setup Utility to remap the dram hole, as far as I could see. OK. It appears you do not have the hole remapped either way, anyway. Adding the above line to /etc/system did indeed reduce the time to crash - so much so that it didn't get as far as the login prompt :( Hence, as I didn't have the nous or time to roll the Smart Array drivers into a Live CD or the failsafe boot environment, I reinstalled. Sorry, I should have listed a few ways out of that hole. My bad. 1) Regardless of the results of 0, in mdb dump out the memory controller nvlist info and then the full memory controller structure: mdb -k < The output is pretty long: instead of attaching it I've put it here: http://chrislf.freeshell.org/mdb.out Thanks for this. You have revision E cpus in two socket 940 sockets (Opteron). On each node there are 4 dimms, each dimm being single-rank and each being 512M in size. On each chip the dimms are arranged into two 1G chip-selects of 128-bit width. There is no node interleaving, and the chip-selects of each node are configured in a two-way chip-select interleave. On both nodes the dram hole size refelected in the dram hole register is zero, so there is no hardware hole reclaim. The chip-selects are interleaved so there is no possibility of discontiguous chip-selects (erratum #99 does not apply). Indeed with 2G per node there is nothing to reclaim - it's only when the installed memory on a node approaches 4G that you overlap with the MMIO area and lose access to that dram that overlaps MMIO. What stands out here, as it did in the Sun-internal case I had a look at, is that "bank swizzling" is enabled on this system. I believe there is no BIOS option to disable it. Bank swizzling is an AMD mode in which some row bits are interchanged with SDRAM internal bank-select bits to change the physical order in which sdram bits are traversed as physical addresses increase (this can be a performance win for some access patterns). That stands out only because I have never seen that enabled in any lab system, and the only two systems I've seen it enabled on are these two (yours + internally reported) systems reporting hangs involving the dram scrubber. This leads me to suspect that there may be an issue involving the dram scrubber in the presence of bank swizzling. The last I heard from the internal case the HP BIOS team were going to experiment. I've just asked for an update. Could you try one more experiment, please. Leave the Solaris /etc/system setting below to stop us enabling the scrubber, but look for the BIOS option (if any) to enable dram scrubbing. Note what it is set to before changing it, and then try enabling the scrubber from there and see if the OS will run. The BIOS option to enable dram scrubbing sometimes hides within an option named something like "ECC protection" which you can set from "none" to "good" "better" etc - higher levels enable the scrubbers at higher rates. If Solaris runs ok with the dram scrubber enabled via BIOS (I think the hang will likely still occur) then this may be a case of starting the scrubber incorrectly from Solaris. Actually all we do is set it going at the node dram base address, so there is little to get wrong! 2) If 0 did not take care of it, rename the two AMD cpu modules and reboot: # mv /platform/i86pc/kernel/cpu/cpu.AuthenticAMD.15 \ /platform/i86pc/kernel/cpu/cpu.AuthenticAMD.15- # mv /platform/i86pc/kernel/cpu/amd64/cpu.AuthenticAMD.15 \ /platform/i86pc/kernel/cpu/amd64/cpu.AuthenticAMD.15- # init 6 This worked. OK. That's a bit heavy-handed since it eliminates all the config operations we perform and not just the scrubber stuff. We will fallback to the dumb generic support. 3) If 2) appears to let you survive longer than 90 minutes you can add the following to /etc/system as a workaround: set cpu\.AuthenticAMD\.15:ao_scrub_policy=1 set cpu\.AuthenticAMD\.15:ao_scrub_rate_dram=0 which will stop us enabling the dram scrubber. If you set the dram scrub rate in 0) above to 1 be sure to replace that line with the 0 setting above. This also worked fine! Let me know if you would like further details of my hardware setup. So for now I'd suggest running with the cpu.AuthenticAMD.15 modules in place, and with
Re: [osol-discuss] Compile errors during onnv-gate
On 8/5/07, Patrick Ale <[EMAIL PROTECTED]> wrote: > Hi all, > > And now for something completely different. > > I pulled the ONNV source from the mercurial (spelling) repository. > I get the following errors in the mail_msg: http://pastebin.com/m776bbbf0 > > The end result after 8 hour compilation is... SILK! ACK! I don't see > any cpio archives in the archives directory, and I think it's cause of > the error shown in the mail_msg. > > Can someone give me a guide line as of what I am doing wrong or how I > can fix it? > > I am trying to compile on an Athlon 2400XP+ with Sun Studio Pro 12, > which is shipped by default with Nevada 69. Building ON using Studio 12 is not supported yet. IF you want to use Studio 12 try export __SSNEXT= export CW_NO_SHADOW=1 dmake setup dmake install Irek ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Compile errors during onnv-gate
On 8/6/07, Jürgen Keil <[EMAIL PROTECTED]> wrote: Hi all, doing an 'rm -rf usr' and 'bunzip2 -c on-src.tar.bz2 | tar xvf -' solved my problem. I'll install Sun Studio 11 to more or less increase my chances of not running into problems. Maybe an ignorant question but.. why ship SS12 with SXCE and SXDE when 11 is what you're recommending? Take care and thanks for the answers, Patrick Ale WickedWicky ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] fdisk partition does not show up
> The rule of thumb is to install Windows first, and > let the rest of the disc be unpartitioned. Then you > install Solaris. (I left the rest be unpartitioned > and boot windows and make a big zfs partition of it) > > (Windows wants to be the one, true OS on your > computer) > > > Here is my description of how I did with Windows, and > how I formated a partition to zfs: > http://www.paleodiet.nu/forum/viewtopic.php?t=1233 Well I found a blog entry saying that you can not create a partition table on the second solaris fdisk partition so I just ran: zpool create local c1d0p3 and it took it. ZFS rocks. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Problem regarding network configuration on Solaris 10
I have an via rhine 2 network card too. I downloaded the driver and followed its instructions. Still I couldnt get it to work. Therefore I tried "sys-unconfig" which resets the computer and asks you about info: what is hostname, do you want dhcp, do you want ipv6, etc. I had to try several times, but at last network is functioning now correct. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] fdisk partition does not show up
The rule of thumb is to install Windows first, and let the rest of the disc be unpartitioned. Then you install Solaris. (I left the rest be unpartitioned and boot windows and make a big zfs partition of it) (Windows wants to be the one, true OS on your computer) Here is my description of how I did with Windows, and how I formated a partition to zfs: http://www.paleodiet.nu/forum/viewtopic.php?t=1233 This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Project proposal for SCSI SAM File system
On 7/19/07, Richard L. Hamilton <[EMAIL PROTECTED]> wrote: > There are simply too many ways poorly written scripts can be tricked into > doing horribly wrong things; which is why I tend to overuse quoting and > curly braces and such; better to put them somewhere they're not needed > than to leave them off of somewhere that might result in someone > sneaking something in via an untrusted arg or environment variable. You could use a modern shell like bash or ksh93 and set IFS to an empty string and use set -o noglob. Without field separators variables may contain spaces without breaking out of their cage and disabling file name globbing will prevent holes created by file name expansion. Irek ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] DL385 hangs after 90 minutes with B66
Apologies for the delay in replying - our fileserver died a grisly death on Friday afternoon. > Could you do the following for me, please: > > 0) In your BIOS options look for an option to remap/reclaim > the dram hole, and if it is offering a choice of "software" > vs "hardware" remapping select hardware. If that was > not already selected reboot with that setting and see > if the hang occurs. Set the following in /etc/system > to increase the scrub rate we apply so (if we're guilty) > you won't have to wait 90 minutes each time: > > set cpu\.AuthenticAMD\.15:ao_scrub_rate_dram=1 > No option exists in the BIOS Setup Utility to remap the dram hole, as far as I could see. Adding the above line to /etc/system did indeed reduce the time to crash - so much so that it didn't get as far as the login prompt :( Hence, as I didn't have the nous or time to roll the Smart Array drivers into a Live CD or the failsafe boot environment, I reinstalled. > 1) Regardless of the results of 0, in mdb dump out the memory > controller nvlist info and then the full memory controller structure: > > mdb -k < *mc_list::list mc_t mc_next | ::print mc_t mc_nvl | ::nvlist > *mc_list::list mc_t mc_next | ::print mc_t > EOM > The output is pretty long: instead of attaching it I've put it here: http://chrislf.freeshell.org/mdb.out > 2) If 0 did not take care of it, rename the two AMD cpu modules and reboot: > > # mv /platform/i86pc/kernel/cpu/cpu.AuthenticAMD.15 \ > /platform/i86pc/kernel/cpu/cpu.AuthenticAMD.15- > > # mv /platform/i86pc/kernel/cpu/amd64/cpu.AuthenticAMD.15 \ > /platform/i86pc/kernel/cpu/amd64/cpu.AuthenticAMD.15- > > # init 6 This worked. > > That's a bit heavy-handed since it eliminates all the config > operations we perform and not just the scrubber stuff. We will > fallback to the dumb generic support. > > 3) If 2) appears to let you survive longer than 90 minutes you can > add the following to /etc/system as a workaround: > > set cpu\.AuthenticAMD\.15:ao_scrub_policy=1 > set cpu\.AuthenticAMD\.15:ao_scrub_rate_dram=0 > > which will stop us enabling the dram scrubber. If you > set the dram scrub rate in 0) above to 1 be sure to replace > that line with the 0 setting above. This also worked fine! Let me know if you would like further details of my hardware setup. Cheers, Chris ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] File Events Notification API - PSARC/2007/027
> On Mon, 2007-08-06 at 03:14 -0700, Doug Scott wrote: > > > On Fri, 2007-08-03 at 19:42 +0100, Robert > Milkowski > > > wrote: > > > > Hello opensolaris-discuss, > > > > > > > > Can anyone shed some light on it? Maybe PSARC > > > materials can be made > > > > publicly available? > > > > > > > > > > The way I interpete it, it is something like FAM > > > which allows things > > > like nautilus to know when something has been > change > > > in the file system > > > so that it automatically is shown in the file > manager > > > window. > > > > Close :) libgaim (FAM clone) can be use by > nautilus/gnome-vfs to > > monitor file/directory updates. The FEN API will be > used by libgamin > > to monitor file events within the kernel. Currently > on Solaris > > libgamin is only able to monitor via polling in > userland. To enable > > this you can build libgamin using SUNWgamin.spec > which currently in > > the spec-files-extra repository on sourceforge. > Once you have > > libgamin, you then need to rebuild SUNWgnome-vfs > and re-login to > > Gnome. (it also works with Xfce). > > > > Doug > > > > > https://pkgbuild.svn.sourceforge.net/svnroot/pkgbuild/ > spec-files-extra/trunk/SUNWgamin.spec > > > https://pkgbuild.svn.sourceforge.net/svnroot/pkgbuild/ > spec-files-extra/trunk/base-specs/gamin.spec > > So I'd assume that with GNOME no longer polling it > should result in > better performance as well. JDS is not linked with gamin at all at the moment. Thats why you have to do a refresh within nautilus to see file changes. Without gamin I think only the desktop is monitored. I originally did the Solaris gamin port for Xfce as you needed to logout and log back in to see things added and removed from the desktop. Currently a Sun Engineer is adding FEN support to gamin. Once it and FEN are completed gamin will be added to JDS. As for performance, from good to bad it probably goes nothing->FEN->polling. Having used both Xfce and Gnome with polling, I can say that the performance hit is very minimal. If you are looking for ways to speed up Gnome. This is not one of them :) Doug This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] fdisk partition does not show up
> Mike DeMarco wrote: > > During installation I split my disk into three > partitions. One for Solaris, one for Windows and one > for solaris to use as zfs. After the install is > complete format can not see any device other than its > own. > > How can I get it to see the device that I want to > present to zfs? > > > > > Keep everything Solaris is going to use in the > Solaris FDISK partition. > > Ian I wanted to avoid giving my solaris boot disk all the space and using a slice for my zpool. This would force me into a total reconstruction rather then splitting my fdisk partitions. Any way to get another fdisk slice to be seen from the Solaris install? This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] File Events Notification API - PSARC/2007/027
On Mon, 2007-08-06 at 03:14 -0700, Doug Scott wrote: > > On Fri, 2007-08-03 at 19:42 +0100, Robert Milkowski > > wrote: > > > Hello opensolaris-discuss, > > > > > > Can anyone shed some light on it? Maybe PSARC > > materials can be made > > > publicly available? > > > > > > > The way I interpete it, it is something like FAM > > which allows things > > like nautilus to know when something has been change > > in the file system > > so that it automatically is shown in the file manager > > window. > > Close :) libgaim (FAM clone) can be use by nautilus/gnome-vfs to > monitor file/directory updates. The FEN API will be used by libgamin > to monitor file events within the kernel. Currently on Solaris > libgamin is only able to monitor via polling in userland. To enable > this you can build libgamin using SUNWgamin.spec which currently in > the spec-files-extra repository on sourceforge. Once you have > libgamin, you then need to rebuild SUNWgnome-vfs and re-login to > Gnome. (it also works with Xfce). > > Doug > > https://pkgbuild.svn.sourceforge.net/svnroot/pkgbuild/spec-files-extra/trunk/SUNWgamin.spec > https://pkgbuild.svn.sourceforge.net/svnroot/pkgbuild/spec-files-extra/trunk/base-specs/gamin.spec So I'd assume that with GNOME no longer polling it should result in better performance as well. Matthew ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] File Events Notification API - PSARC/2007/027
On Mon, 2007-08-06 at 10:37 +0100, Robert Milkowski wrote: > Hello Kaiwai, > > Saturday, August 4, 2007, 4:13:52 AM, you wrote: > > KG> On Fri, 2007-08-03 at 19:42 +0100, Robert Milkowski wrote: > >> Hello opensolaris-discuss, > >> > >> Can anyone shed some light on it? Maybe PSARC materials can be made > >> publicly available? > >> > > KG> The way I interpete it, it is something like FAM which allows things > KG> like nautilus to know when something has been change in the file system > KG> so that it automatically is shown in the file manager window. > > I had the same thought still that information should more openly > available, more in a spirit of open source > Unfortunately development by Sun isn't occuring in the public, which kinda sucks - someone needs to remind Sun what opensource actually means. Matthew ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Compile errors during onnv-gate
> I pulled the ONNV source from the mercurial (spelling) repository. > I get the following errors in the mail_msg: http://pastebin.com/m776bbbf0 > > The end result after 8 hour compilation is... SILK! ACK! I don't see > any cpio archives in the archives directory, and I think it's cause of > the error shown in the mail_msg. > > Can someone give me a guide line as of what I am doing wrong or how I > can fix it? > > I am trying to compile on an Athlon 2400XP+ with Sun Studio Pro 12, > which is shipped by default with Nevada 69. Quote from the ON download page: ( http://www.opensolaris.org/os/downloads/on/ ) » You will then need to download the compilers specific to your platform. Choose either: * The Sun Studio Compilers (Recommended). NOTE: Sun Studio 11 [*] is required for building Build 45 and higher. Builds prior to Build 45 use Sun Studio 10. Please note that the compiler that comes with the Solaris Developer Express release is Studio 12, and there may be some problems using it to build ON. If you use Studio 12, please do report problems, particularly if the problem goes away when you use Studio 11. « [*] http://www.opensolaris.org/os/community/tools/sun_studio_tools/sun_studio_11_tools/ This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Compile errors during onnv-gate
Patrick Ale wrote: > Hi all, > > And now for something completely different. > > I pulled the ONNV source from the mercurial (spelling) repository. > I get the following errors in the mail_msg: http://pastebin.com/m776bbbf0 > > The end result after 8 hour compilation is... SILK! ACK! I don't see > any cpio archives in the archives directory, and I think it's cause of > the error shown in the mail_msg. > > Can someone give me a guide line as of what I am doing wrong or how I > can fix it? > > I am trying to compile on an Athlon 2400XP+ with Sun Studio Pro 12, > which is shipped by default with Nevada 69. You MUST use Studio 11 at this time. Use of Studio 12 is not known to produce working and usable output from the build. -- Darren J Moffat ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] File Events Notification API - PSARC/2007/027
> On Fri, 2007-08-03 at 19:42 +0100, Robert Milkowski > wrote: > > Hello opensolaris-discuss, > > > > Can anyone shed some light on it? Maybe PSARC > materials can be made > > publicly available? > > > > The way I interpete it, it is something like FAM > which allows things > like nautilus to know when something has been change > in the file system > so that it automatically is shown in the file manager > window. Close :) libgaim (FAM clone) can be use by nautilus/gnome-vfs to monitor file/directory updates. The FEN API will be used by libgamin to monitor file events within the kernel. Currently on Solaris libgamin is only able to monitor via polling in userland. To enable this you can build libgamin using SUNWgamin.spec which currently in the spec-files-extra repository on sourceforge. Once you have libgamin, you then need to rebuild SUNWgnome-vfs and re-login to Gnome. (it also works with Xfce). Doug https://pkgbuild.svn.sourceforge.net/svnroot/pkgbuild/spec-files-extra/trunk/SUNWgamin.spec https://pkgbuild.svn.sourceforge.net/svnroot/pkgbuild/spec-files-extra/trunk/base-specs/gamin.spec This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] fdisk partition does not show up
Mike DeMarco wrote: > During installation I split my disk into three partitions. One for Solaris, > one for Windows and one for solaris to use as zfs. After the install is > complete format can not see any device other than its own. > How can I get it to see the device that I want to present to zfs? > > Keep everything Solaris is going to use in the Solaris FDISK partition. Ian ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] fdisk partition does not show up
During installation I split my disk into three partitions. One for Solaris, one for Windows and one for solaris to use as zfs. After the install is complete format can not see any device other than its own. How can I get it to see the device that I want to present to zfs? This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] File Events Notification API - PSARC/2007/027
Hello Kaiwai, Saturday, August 4, 2007, 4:13:52 AM, you wrote: KG> On Fri, 2007-08-03 at 19:42 +0100, Robert Milkowski wrote: >> Hello opensolaris-discuss, >> >> Can anyone shed some light on it? Maybe PSARC materials can be made >> publicly available? >> KG> The way I interpete it, it is something like FAM which allows things KG> like nautilus to know when something has been change in the file system KG> so that it automatically is shown in the file manager window. I had the same thought still that information should more openly available, more in a spirit of open source -- Best regards, Robertmailto:[EMAIL PROTECTED] http://milek.blogspot.com ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Solaris "thinks" that my standalone desktop is a huge network....
> These were the difficulties that limited sale of > computers to less than a hundred thousand units when > the world's population was 4 billion. What is the > statistics today ? GUI made it possible to get the > computer across to a quarter of the population of the > world. Improve the GUI, my maid servant will buy > one. Actually, the Commodore 64 sold 15 million units, Amiga sold at least another 8. and Atari 800, the XL and Atari ST must've sold another 15-20 million units combined. There there was Apple, also having sold several million units, and the fledgling IBM PC XT and AT models. This was still at the end of '89 - '90 of the past century, so your point about "less than a hundred thousand units" does not stand. This was in times when almost nobody knew what a computer is when compared to today's state of affairs, yet units sold in tens of millons and people were proficient in using them. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
