[osol-discuss] Re: joining Sun
[i]There are some interesting connections to Linux here as well. If you think about it, what do people want when they say they want Linux? The Linux kernel? Or the Linux distribution (i.e., GNU)? Could Solaris become a better Linux than Linux by following that line of thinking? And if you following that line of thinking, where does that lead the company in terms of Linux strategy? Some interesting parallels open up with the way Sun masterfully embraced x86 a few years ago...[/i] Please, no entrenched GNOME or gcc. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Project proposal: NTP
Yes, but at this point there hasn't been much discussion. We expect to have bits to test in a short period of time, so I expect things to pick up soon. Boyd Adamson wrote: Sorry to revive an old thread, but did anything ever come of this? The project pages exist, but only minimally. On 5/11/06, Rainer Orth [EMAIL PROTECTED] wrote: We propose the creation of an NTP project on OpenSolaris.ORG, affiliated with the Nevada and Device Driver communities. While historially SunOS 4 and Solaris have been platforms of choice for NTP timekeeping and leading-edge development, Solaris has fallen behind other platforms (notably FreeBSD) in recent years. This is due to a couple of issues: * The NTP daemon and utilities have seen much development in preparation for the upcoming NTPv4 standard. Unfortunately, Solaris still ships the ancient xntp (NTPv3) daemon. * The NTP kernel support has evolved beyond the code currently in Solaris, but those enhancements have not been picked up. * There's a multi-vendor API for reference clocks that provide a pulse-per-second signal (PPS API, RFC 2783). While Solaris has some support for PPS devices, it failed to implement the PPS API specification. * Recent serial interface chips have seriously degraded NTP performance due to extended on-chip buffering, so current systems have become considerably worse for attaching serial reference clocks. * The PPS serial support in the kernel is a private interface that was not published in the DDI, so only onboard serial ports are supported. * The TOD synchronizaton model is fundamentally broken in Solaris and has resulted in unstable system clocks and wasted thousands of dollars in support calls and needlessly replaced hardware. * The adjtime system call slews the clock in a way that can disrupt NTP time networks. This project seems to remedy those problems and again turn Solaris into a primary NTP deployment and development platform. Project leaders will be Brian Utterback and myself. Rainer - Rainer Orth, Faculty of Technology, Bielefeld University ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org -- blu Remember 'A Thousand Points of Light'? With a network, we now have a thousand points of failure. -- Brian Utterback - Solaris RPE, Sun Microsystems, Inc. Ph:877-259-7345, Em:brian.utterback-at-ess-you-enn-dot-kom ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] ZFS, Pkg Update Questions
1. After I installed Solaris do I need to create ZFS ? I've read some info and watched a video about ZFS it seems to be a good filesystem. Why doesn't it come as a default FS then ? 2. How can I update a package or a program like firefox for instance ? P.S. I did install pkg-get but it installs the second instance of firefox into a different directory. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] ZFS, Pkg Update Questions
Horvath wrote: 1. After I installed Solaris do I need to create ZFS ? I've read some info and watched a video about ZFS it seems to be a good filesystem. Why doesn't it come as a default FS then ? Because there's an awful lot of work involved to make it the default. This work covers multiple consolidations, and affects just about everything you might want to consider when it comes to system admin. It's not something which can happen overnight - even with immense efforts by the engineers involved it still takes time. 2. How can I update a package or a program like firefox for instance ? If you're using Solaris Express then pretty much each new build (eg, snv_60) will contain an updated firefox. Otherwise you can go to mozilla.org or a mirror site to download the package. In order to get started with Solaris packages you should read through the Solaris System Administration Guide at docs.sun.com. You can also ask questions on the #opensolaris channel on the freenode irc network. cheers, James C. McPherson -- Solaris kernel software engineer, system admin and troubleshooter http://www.jmcp.homeunix.com/blog Find me on LinkedIn @ http://www.linkedin.com/in/jamescmcpherson ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: ZFS, Pkg Update Questions
1. So we'll see ZFS as a default FS in the future ? 2. How can I convert my current FS (I assume it's UFS that comes as default) to ZFS? 3. I upgraded my snv_59 to snv_60 and Firefox is still 2.0.1 I wonder why. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: [n00b] Solaris Install Help (No, it's not in the manual!)
I got the ISO from the Solaris website.I burn it.I follow and follow the install steps until it asks me from what do I wish to install Solaris 10 from.I select CD\DVD.It gets to 5% then it says something like Solaris instalation was not found on the selected medium.Then what the f... did it boot from?! A floppy?! (:-) It looks like two possible scenarios: 1. did you verify / do a MD5 checksum on all the ISO / pieces of it and compare the results with what was listed on the download page? 2. sometimes, when the disk doesn't yet have a Solaris VTOC, the installer complains; if you can boot to single user mode (add -s in the GRUB menu) and run `fdisk /dev/rdsk/c#d#p0` (like: `fdisk /dev/rdsk/c0d0p0`), then you'll be able to write a VTOC on the disk. WARNING: should you choose step 2., you should be extremely careful, because it is extremely easy to wipe the existing partitions on the disk and/or make the existing operating systems on the disk unbootable. You must read the fdisk documentation on docs.sun.com, and you must understand what you are doing. In particular, you must comprehend the difference between BIOS partitions and Solaris slices, which are written inside of one of BIOS partitions on the i86pc platform. In any case, step 1. is highly recommended before attempting step 2. (if at all). This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: ZFS, Pkg Update Questions
Horvath wrote: 1. So we'll see ZFS as a default FS in the future ? yes 2. How can I convert my current FS (I assume it's UFS that comes as default) to ZFS? Short answer - you need more disks, so that you can create the zpool and zfs, then copy your files across. At the moment there is no way of doing this in-place that I am aware of. 3. I upgraded my snv_59 to snv_60 and Firefox is still 2.0.1 I wonder why. Probably because the desktop team didn't integrate any new build of Firefox. Is it really a deal-breaker if you don't have the latest bleeding-edge version of firefox? James C. McPherson -- Solaris kernel software engineer, system admin and troubleshooter http://www.jmcp.homeunix.com/blog Find me on LinkedIn @ http://www.linkedin.com/in/jamescmcpherson ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Re: ZFS, Pkg Update Questions
2. Is there a way to reinstall Solaris with ZFS instead of UFS? 3. No it's not a matter of having a bleeding-edge tools. My question was about any pkg in Solaris, how can I update a pkg in Solaris to be short? This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: Re: Fire!! core dumped!
eric wang writes:
How did you think it's calling pthread_mutex_lock(NULL), but no other e.g.
pthread_mutex_lock(invalid address, e.g. 0xf)?
I think the NULL pointer into pthread_mutex_lock is not accordant with signal
SEGV (access to address exceeded protections).
What do you mean by accordant?
SIGSEGV is exactly what you get if you try to touch storage via a NULL
(zero) pointer. This can be shown fairly easily:
% echo 'void main(void) { *(char *)0 = 1; }' foo.c
% cc -o foo foo.c
% ./foo
Segmentation fault (core dumped)
% echo ::status | sudo mdb core
debugging core file of foo (32-bit) from phorcys
initial argv: ./foo
threading model: native threads
status: process terminated by SIGSEGV (Segmentation Fault)
%
--
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] Re: Re: ZFS, Pkg Update Questions
Horvath writes: 2. Is there a way to reinstall Solaris with ZFS instead of UFS? No, because the boot system cannot yet boot from ZFS. 3. No it's not a matter of having a bleeding-edge tools. My question was about any pkg in Solaris, how can I update a pkg in Solaris to be short? For Solaris Express (or whatever it's being called these days), you upgrade a package by upgrading to the next build. There's a new build available every two weeks. (And LU is your friend.) There's no way to upgrade just one package alone, though. It's possible that a new package from a new build will run on an older build, but there's simply no way to guarantee it, and we don't. Attempting to upgrade just one package is probably a mistake. For official Solaris releases (such as Solaris 10), you get individual changes as patches. These are smaller sets of changes that replace individual binaries from multiple packages at once, and typically deliver a finer-grained update. However, there are *NO* patches generated for marketing releases that are still under development. Solaris Nevada (the base of Solaris Express) is still under development. I think you might be confused about blastwave's pkg-get. That doesn't update Solaris packages; it has nothing to do with Solaris itself. Instead, it intentionally installs into a separate place on the system (/opt/csw) and provides an _alternative_ set of packaged software you can choose to use. You almost certainly do not want to attempt to copy binaries from blastwave atop Solaris-delivered binaries. You'll end up with chaos. -- 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] Re: Update to B60 ?
MC writes: Horvath writes: How to update to Nevada b60 ? Your best option is LU. It allows you to continue to use the system normally during the upgrade process, then you can quickly switch over after the upgrade is done (and back if you find problems). *raises hand* Is an online live upgrade feature on the way? ie, it downloads and installs automatically. That is what I expected LU to be. Downloading those files and typing those 50 characters sounds like a good candidate for automation. I know some guys like pain, but I'd rather click Yes to upgrade :) Part of it is automated (see the liveupgrade20 tool in Solaris_*/Tools/Installers), but the download part is not. I suspect that automating the download part would be annoying given the current download process. This discussion is almost certainly more appropriate for the [EMAIL PROTECTED] list, rather than the general opensolaris-discuss list. -- 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] Re: joining Sun
On Thu, 22 Mar 2007, Shawn Walker wrote: That is a matter of preference. I always hated the -- options GNU utilities use since they were so much more to type. I will admit You and me both! Add me to that list. --switch is not the UNIX(R) way. It's inconsistent with the -[a-zA-Z] phylosophy, and consistency is one of the most important benefits and perks UNIX has to offer. In other words, GNU phylosophy *detracts* from user's efficiency at the expense of readability and choice. I argue however, that breaking consistency is far worse. It's like walking around the corner only to get one's face smashed full force by someone's fist. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: joining Sun
I will admit GNU/Linux systems get you used to typing cmd --help instead of man cmd which I think is a bad habit. I think most people got used to doing this since documentation is something that was usually completely overlooked on most GNU/Linux distributions... ...Or in plain English: people were too lazy to crank out man pages, i.e. when quantity (just release it, it works for me) matters over quality (either do it right and completely, or don't do it at all). This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Getting Opensolaris build notification
HI, How can I get an email notification about new opensolaris build being available? Also I would like to get a ChangeLog notification for build/putbacks as well. Regards, -Atul ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: [ug-bosug] Getting Opensolaris build notification
Looks like I'm a little out of date! The changelogs are now over here: http://dlc.sun.com/osol/on/downloads/ Venky. On Mon, Mar 26, 2007 at 07:54:55PM +0530, Venky wrote: Don't know of an email notification setup, but you could have a look at the ON community page for details of the builds and changelogs: http://opensolaris.org/os/community/on/onnv_putback_logs/ Venky. On Mon, Mar 26, 2007 at 07:33:16PM +0530, Atul Vidwansa wrote: HI, How can I get an email notification about new opensolaris build being available? Also I would like to get a ChangeLog notification for build/putbacks as well. Regards, -Atul ___ ug-bosug mailing list List-Unsubscribe: mailto:[EMAIL PROTECTED] List-Owner: mailto:[EMAIL PROTECTED] List-Archives: http://www.opensolaris.org/jive/forum.jspa?forumID=54 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: [ug-bosug] Getting Opensolaris build notification
Don't know of an email notification setup, but you could have a look at the ON community page for details of the builds and changelogs: http://opensolaris.org/os/community/on/onnv_putback_logs/ Venky. On Mon, Mar 26, 2007 at 07:33:16PM +0530, Atul Vidwansa wrote: HI, How can I get an email notification about new opensolaris build being available? Also I would like to get a ChangeLog notification for build/putbacks as well. Regards, -Atul ___ ug-bosug mailing list List-Unsubscribe: mailto:[EMAIL PROTECTED] List-Owner: mailto:[EMAIL PROTECTED] List-Archives: http://www.opensolaris.org/jive/forum.jspa?forumID=54 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Getting Opensolaris build notification
Atul Vidwansa wrote: HI, How can I get an email notification about new opensolaris build being available? Also I would like to get a ChangeLog notification for build/putbacks as well. Regards, -Atul ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org Are you subscribed to the opensolaris-announce mailing list? Most of the build deliveries notifications are sent there. cheers, steve -- stephen lau // [EMAIL PROTECTED] | 650.786.0845 | http://whacked.net opensolaris // solaris kernel development ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: [n00b] Solaris Install Help (No, it's not in the manual!)
uzy31 wrote: Solaris instalation was not found on the selected medium My system is composed of the following : AMD Athlon 2600+ CPU @ 1.91GHz,Asus A7V600 X motherboard,Ati Radeon X1550 AGP 8x video card,Western Digital 120GB WD1200JB SATA HDD,Nec 3540A DVD RW drive,LG CD RW drive As you have one DVD/RW and one CDROM/RWin you system . Maybe the installer tries to load the OS from the CD drive instead of the DVD drive it booted from ? motherboards with interesting combinations of IDE and SATA buses are, well interesting. You dont have a SATA DVD and an IDE CD/RW do you ? Pull the cables from the CD/RW drive and try again. //Lars This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: joining Sun
On Mon, 26 Mar 2007, UNIX admin wrote: Add me to that list. --switch is not the UNIX(R) way. It's inconsistent with the -[a-zA-Z] phylosophy, and consistency is one of the most important benefits and perks UNIX has to offer. Another thing that I find almost annoying is the use of -switch (find(1) and dd(1M) are the most obvious examples that come to mind). Should that be read as -switch or -s -w -i -t -c -h? POSIX (and I) say the latter. -- Rich Teer, SCSA, SCNA, SCSECA, OpenSolaris CAB member CEO, My Online Home Inventory Voice: +1 (250) 979-1638 URLs: http://www.rite-group.com/rich http://www.myonlinehomeinventory.com ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Re: joining Sun
Another thing that I find almost annoying is the use of -switch (find(1) and dd(1M) are the most obvious examples that come to mind). Should that be read as -switch or -s -w -i -t -c -h? POSIX (and I) say the latter. And I would agree with both you and POSIX. -switch would be -s -w -i -t -c -h to me. As in: df -hF zfs This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: joining Sun
On 26/03/07, Christopher Chan [EMAIL PROTECTED] wrote: [i]There are some interesting connections to Linux here as well. If you think about it, what do people want when they say they want Linux? The Linux kernel? Or the Linux distribution (i.e., GNU)? Could Solaris become a better Linux than Linux by following that line of thinking? And if you following that line of thinking, where does that lead the company in terms of Linux strategy? Some interesting parallels open up with the way Sun masterfully embraced x86 a few years ago...[/i] Please, no entrenched GNOME or gcc. What does that mean? -- Less is only more where more is no good. --Frank Lloyd Wright Shawn Walker, Software and Systems Analyst [EMAIL PROTECTED] - http://binarycrusader.blogspot.com/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Using isaexec approach
Hi Folks, We were recently developing a Cluster solution for our product. And we are planning on using the isaexec approach. http://docs.sun.com/app/docs/doc/816-5138/6mba6ua5n?a=view Create Hardlinks to various executables and following the isaexec approach of getexecname() and executing the appropriate binary isaexec does a (void) execve(mybinary, argv, envp); to execute the actual binary. But how do I get the return value of the binary, I know that exec family of functions won't return any value ?. Is there any way i can get the return value of mybinary after it executes ?. Say if mybinary returns 1 ( failure ) 2 ( success ) 4 ( some thing else ).. _Thanks much D This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Using isaexec approach
On Mon, 2007-03-26 at 11:09 -0700, Durga Deep Tirunagari wrote: But how do I get the return value of the binary, I know that exec family of functions won't return any value ?. Is there any way i can get the return value of mybinary after it executes ?. Say if mybinary returns 1 ( failure ) 2 ( success ) 4 ( some thing else ).. The *function* doesn't return any value, because a proper exec*() doesn't return at all. From the manpage: Each of the functions in the exec family replaces the current process image with a new process image. Once isaexec does the execve(), it's gone. The new binary is executing in its place, just as if you'd run it in the first place. I assume you're after the value returned by exit(), right? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Using isaexec approach
* Durga Deep Tirunagari [EMAIL PROTECTED] [2007-03-26 11:09]: Hi Folks, We were recently developing a Cluster solution for our product. And we are planning on using the isaexec approach. http://docs.sun.com/app/docs/doc/816-5138/6mba6ua5n?a=view Create Hardlinks to various executables and following the isaexec approach of getexecname() and executing the appropriate binary isaexec does a (void) execve(mybinary, argv, envp); to execute the actual binary. But how do I get the return value of the binary, I know that exec family of functions won't return any value ?. Is there any way i can get the return value of mybinary after it executes ?. Say if mybinary returns 1 ( failure ) 2 ( success ) 4 ( some thing else ).. exec(2) replaces the running process image with a new image. So when mybinary calls exit(2), the exit status will be available to the parent via waitid(2). In your example, the parent would be the parent of the process which is calling isaexec(3C). - Stephen -- Stephen Hahn, PhD Solaris Kernel Development, Sun Microsystems [EMAIL PROTECTED] http://blogs.sun.com/sch/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: [n00b] Solaris Install Help (No, it's not in the manual!)
So,MD5 checks aren't just possibilities? I mean,I did say I burnt the ISO on two different DVDs.I don't know what MD5 is or what a has is but I assure you that I will do my wiki before the next post. I'm gonna try your options guys!Thanks a lot! LovePeace! This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] joining Sun
On 3/21/07, Alan DuBoff [EMAIL PROTECTED] wrote: Seriously, I hope to see Ian active with the OpenSolaris community.;-) Absolutely. My latency may be terrible though, particularly in the beginning (as you've no doubt already noticed :-). Sorry about that. -ian -- Ian Murdock 650-331-9324 http://ianmurdock.com/ Don't look back--something might be gaining on you. --Satchel Paige ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Developer Conference slides added to Talks Presentations page
Hey All, Just to you know, I've added the talks presentations from the recent OpenSolaris Developer Conference to the page at: http://www.opensolaris.org/os/community/os_user_groups/os-presentations/ - I'd like to say a *big thanks* to Dirk Wetter for sending me these links in an easy-to-digest format (to the extent that I just needed to copy/paste them onto the page!) We now have 133 presentations on that page, which I think is pretty good going - if you've got anything to add to the page, please let me know! cheers, tim -- Tim Foster, Sun Microsystems Inc, Solaris Engineering Ops http://blogs.sun.com/timf ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Using isaexec approach
I assume you're after the value returned by exit(), right? Thats exactly correct, the Cluster framework need to have an exit code. Based on the exit code it will take the appropriate action _D This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] SUN_SSH_1.1 vs openSSH
Hello, Does anyone know from which openSSH version that SUN_SSH_.1.1 was developed from? I need this info to complete the IA (Information Assurance) certification for Solaris 10 on x86 platform. Thanks Quyen This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: ZFS, Pkg Update Questions
No, AFAIK there is no such option. But there is a easy way to convert your home directory from UFS to ZFS. This is from a German Sun Blog http://blogs.sun.com/solarium/ : I did it that way, slightly diffrent mkdir /space ufsdump -0f /space/home.dump /export/home Remove /export/home from vfstab Reboot and login as root zpool create -m /export/home home c0t0d0s7 (if your home directory is on that partition) cd /export/home ufsrestore rvf /space/home.dump Delete /space You can also convert the /opt directory to ZFS: http://www.opensolaris.org/jive/thread.jspa?messageID=97061 All other directorys must be UFS This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: Update to B60 ?
Stephen Lau wrote: On Sun, Mar 25, 2007 at 04:55:29AM -0700, Andrew Pattison wrote: Incorrect. The site just sometimes doesn't update properly for some reason. Latest is always here: http://opensolaris.org/sxce_dvd Why is this magic URL up-to-date, yet the one on the download page (http://www.opensolaris.org/os/downloads/sol_ex_dvd/) still points to build 59? I believe that one is manually updated by Derek. The one at http://opensolaris.org/sxce_dvd periodically polls the SDLC to see if a new build has been released and auto-updates accordingly. Sorry everybody. The mail that updates me got sent to the wrong folder so I missed it. I'll add Eric B to the update list as backup so we don't miss it again. Derek -steve -- Derek Cicero Program Manager Solaris Kernel Group, Software Division ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] SXCE Build 60 available
Please find the links to SXCE Build 60 at http://www.opensolaris.org/os/downloads/on/. - Derek -- Derek Cicero Program Manager Solaris Kernel Group, Software Division ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: SXCE Build 60 available
Where? This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: SXCE Build 60 available
Ron Halstead wrote: Where? Under the Quick Download Links: http://www.opensolaris.org/os/downloads/sol_ex_dvd/ http://www.opensolaris.org/os/downloads/sol_ex_cd This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org -- Derek Cicero Program Manager Solaris Kernel Group, Software Division ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: Update to B60 ?
Stephen Lau wrote: On Sun, Mar 25, 2007 at 04:55:29AM -0700, Andrew Pattison wrote: Incorrect. The site just sometimes doesn't update properly for some reason. Latest is always here: http://opensolaris.org/sxce_dvd Why is this magic URL up-to-date, yet the one on the download page (http://www.opensolaris.org/os/downloads/sol_ex_dvd/) still points to build 59? I believe that one is manually updated by Derek. OK, I set up: http://www.opensolaris.org/os/downloads/sol_ex_dvd/ to use http://opensolaris.org/sxce_dvd So anyone using that first URL will get the most recent version. Derek The one at http://opensolaris.org/sxce_dvd periodically polls the SDLC to see if a new build has been released and auto-updates accordingly. -steve -- Derek Cicero Program Manager Solaris Kernel Group, Software Division ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Using isaexec approach
Thanks very much stephen and Hume _D This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] E_SEC_SHELL_WARN ( running lint )
Folks, we were running LINT against our code and it spewed out the following warning: warning: avoid using system() as it invokes the shell (E_SEC_SHELL_WARN) Here is the code snippet: sprintf (start_command,%s, /opt/SUNWdsee/start-slapd); (void) system(start_command); Any suggestions on getting rid of this warning ? _Durga This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] E_SEC_SHELL_WARN ( running lint )
On 3/26/07, Durga Deep Tirunagari [EMAIL PROTECTED] wrote: Folks, we were running LINT against our code and it spewed out the following warning: warning: avoid using system() as it invokes the shell (E_SEC_SHELL_WARN) Here is the code snippet: sprintf (start_command,%s, /opt/SUNWdsee/start-slapd); (void) system(start_command); Any suggestions on getting rid of this warning ? not using system() ? :) nacho ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Re: Re: Update to B60 ?
This thread is a beautiful microcosm OpenSolaris. An analogy of the growth happening throughout the community. Mister Sun and Mister Joe working hand in hand for the common good. :) This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] E_SEC_SHELL_WARN ( running lint )
On 3/26/07, Ignacio Marambio Catán [EMAIL PROTECTED] wrote: On 3/26/07, Durga Deep Tirunagari [EMAIL PROTECTED] wrote: Folks, we were running LINT against our code and it spewed out the following warning: warning: avoid using system() as it invokes the shell (E_SEC_SHELL_WARN) Here is the code snippet: sprintf (start_command,%s, /opt/SUNWdsee/start-slapd); (void) system(start_command); Any suggestions on getting rid of this warning ? not using system() ? :) nacho ok, now seriously speaking, system() is not thread safe, it does weird things with the signal handlers, specially if you call system() in parallel. you should replace it with the safer popen(), read both man pages for a better explanation nacho ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] E_SEC_SHELL_WARN ( running lint )
Durga Deep Tirunagari wrote: Folks, we were running LINT against our code and it spewed out the following warning: warning: avoid using system() as it invokes the shell (E_SEC_SHELL_WARN) Here is the code snippet: sprintf (start_command,%s, /opt/SUNWdsee/start-slapd); (void) system(start_command); In addition to the other reply, you shouldn't have to use the ghastly (void)system() just to silence lint warnings. Ian ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SXCE Build 60 available
Hello Derek, That's great! While we're at it - maybe it would be possible to prepare short What's New with each build - something like DP used to publish on his blog some time ago. I belive it would be greatly appreciated by many. ps. no, on-changes is not enough as SXCE is not only ON -- Best regards, Robertmailto:[EMAIL PROTECTED] http://milek.blogspot.com ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Project Proposal: NWS (Network Storage)
Thanks, John. You have seconds. I'll contact you offline to get you set up. On Fri, 23 Mar 2007, John Forte wrote: The NWS project consists of drivers, libraries and utilities in support of storage interconnect technologies including both Fibre Channel and iSCSI. The NWS project source code has been available since 2/06, however, the project does not have its own project page but rather exists as part of the Storage Community. This proposal provides for NWS to be treated as a real project within OpenSolaris. Initially, it will be endorsed by the Storage Community. The NWS project currently includes: o iSCSI (software initiator) o Fibre Channel Transport o Interfaces for Fibre Channel HBA drivers o Storage Management APIs o Storage Management Utilities The initial leaders for this project would be: - Charles Baker - Aaron Dailey - John Forte - Stephen Salbato 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] joining Sun
On Monday 26 March 2007 11:56 am, Ian Murdock wrote: On 3/21/07, Alan DuBoff [EMAIL PROTECTED] wrote: Seriously, I hope to see Ian active with the OpenSolaris community.;-) Absolutely. My latency may be terrible though, particularly in the beginning (as you've no doubt already noticed :-). Sorry about that. Understood, and please do participate whenever you have time. I saw you at MPK17 today, and was walking in just as you were heading up the stairs. I was going to say hi, but your cell phone rang.;-) -- Alan DuBoff - Solaris x86 Engineering - IHV/OEM Group Advocate of Insourcing at Sun, hire people that care about our company! ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] setting TTYB characteristics
Hi i am working on Network Element. I connect to that NE on TTYB port. From the command line if I tried to send ascii character like [b]À[/b], it get dropped at serial port. By dropping at serial port mean it is not going to network element. I am wondering if I need to set the characteristics of TTYB port. help me Thanks Vineet This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Proposal: new project for improving ON build times
I would like to propose a project aimed to improve ON build times. This can live either under tools or under performance or under some other community. There was some discussion about it a while ago in the context of Google summer of code: http://www.opensolaris.org/jive/message.jspa?messageID=33951 It may be a part of ONNV project, or something else if you think that some other project/community is more suitable. The goal of the project is to make our ON builds faster. This includes, but is not limited to: - Developing and running observability tools to understand existing problems and find some low-hanging fruits - Increasing build parallelism - Taking advantage of new OpenSOlaris technologies like DTrace and ZFS. - Cleaning up Makefiles (at least some major Makefile issues) - Exploring some aggressive tricks and techniques to radically improve build times - Exploring various caching approaches. The goal is to make builds fast enough for developers to be productive. This is, probably, going to be an open-ended project. -- Alex Kolbasov ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: joining Sun
As a Linux user who has recently started working with the OpenSolaris kernel for a project, I have been thinking about this as well. What I personally find important in Linux is: - the user experience, mostly embodied by the KDE desktop environment. I don't like Gnome, so I don't like the default Solaris desktop environment. I heard that there is a KDE project for OpenSolaris, so that is great. If most of the GUI programs would run on OpenSolaris as well, then the biggest challenge has been overwon I think. I sort of agree on that - KDE is certainly easier to get into quickly. Although GNOME may have more potential in some ways, it seems slow to get lean, and get a settled set of apps that do what people want; I know I'd rather have one app that did a whole job (email, say) well, than two that each did 2/3 of what I wanted them to. - then there are the command line programs. There might be a good reason for this, but I feel that some of the Solaris-shipped tools are inferior to the GNU tools. For example, I don't see a reason why a simple recursive grep with 'grep -R' does not work on Solaris. Why there are two greps is something I do not understand either. The commands in /usr/bin, /usr/xpg4/bin, and so on are the way they are because compatibility is more important than doing what you (or I, or everybody put together) want them to. That way, existing end-user scripts and apps just keep working. Even adding features in a supposedly compatible way can sometimes break things. That doesn't mean that all your fave GNU tools can't be in some other directory, nor even that a particular site might not choose to create user accounts so that they saw the GNU version of tools in preference to other versions, so as long as you don't hard-code pathnames, it shouldn't matter much. If you think that's over the top, think again. Most places that have been around that long have scripts and apps that haven't been touched in years if not decades; nobody can proactively maintain them anymore, and yet they're part of earning the income that keeps the place open, so breaking them just to fix or replace them is not a desirable option. Mainframes are even worse; they're likely to have programs on them that are just about unchanged since the late 60's. Again, that doesn't preclude new functionality, it just means one doesn't usually get that as first choice out of the box. Of course, even if Sun's Solaris distro won't go there, there's nothing preventing other OpenSolaris distros from having various goodies favored out of the box. I hear Nexenta is like that. I do not get the way man works either. On Linux, you would just do man cat or man vi, and it would just give you the correct man page. Even 'man man' doesn't work here. (I'm beginning to wonder whether this may be because the man pages are not installed... could this be? man man should work, right?) The man command works fine if you have it and the pages installed. You do have to build the indexes if you want to do man -k keyword but that's about it. Oh, and if you want to specify a section of the manual (like when there are pages by the same name in different sections), the syntax is man -s section page unlike some other systems, where you don't need the -s. I agree that a lot of this frustration is more because it is unknown and different than what I am used to. But I think this will be the case for a lot of users which come from Linux, and if Solaris wants to make these people change OS, this should be taken into account. Ok. And I think that, even if not quite out of the box, that can actually be done now. I mean, it's not like you get an install option to please make this look as much like Linux as possible, but it doesn't take a whole lot of work to accomplish that, and may well take less in the future. I'd probably be in a similar position on Linux - trying to figure out how to make it look more like Solaris, or at least an SVR4 derivative, except that unlike you, the kernel _does_ matter to me because I've worked with Unix since the PDP-11 days, and don't draw a line between GUI, application innards, and kernel when I've got a problem; I just keep digging. But I know I'm not normal in that regard... - the actual kernel is not very important from a user point of view I think. What is important is the hardware support, and I am not sure to what extent OpenSolaris is good at this. For example, I have an Acer laptop with an embedded webcam. For Linux, there was reasonably quickly a driver (gspca) available. I don't know if this would have been the case with OpenSolaris. Of course, this also depends on the size of the developer community and I think that's were Linux has a plus. I think a 1394 (Firewire) webcam should usually work fine; I've got one hooked up to my SPARC, no problem. Someone (both inside Sun and outside, although I think they were sharing info later on) is working
Re: [osol-discuss] Proposal: new project for improving ON build times
Alexander Kolbasov wrote: I would like to propose a project aimed to improve ON build times. This can live either under tools or under performance or under some other community. There was some discussion about it a while ago in the context of Google summer of code: http://www.opensolaris.org/jive/message.jspa?messageID=33951 [...] The goal is to make builds fast enough for developers to be productive. This is, probably, going to be an open-ended project. -- Alex Kolbasov +1 (FYI: Even my fastest SPARC, a Sun Blade 2000 / Dual x7017a 1056 MHz / 8GB memory / FC-AL drives, needs about 4 hours currently [for a nightly non-debug build using Studio11 as primary compiler and using dmake] / even if the whole workspace sits in physical mem in /tmp/foo plus when not doing anything else) GCC shadow compilation added noticable costs: http://www.opensolaris.org/os/community/tools/gcc/shadow/ One may of course disable it in-house - for one or another personal build - (Note: I'm very happy, ON can be built with gcc and I understand that shadow compilation is a good means to keep ON gcc-clean.) ~m ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [perf-discuss] [osol-discuss] Proposal: new project for improving ON build times
Alexander Kolbasov wrote: I would like to propose a project aimed to improve ON build times. This can live either under tools or under performance or under some other community. There was some discussion about it a while ago in the context of Google summer of code: http://www.opensolaris.org/jive/message.jspa?messageID=33951 It may be a part of ONNV project, or something else if you think that some other project/community is more suitable. The goal of the project is to make our ON builds faster. This includes, but is not limited to: - Developing and running observability tools to understand existing problems and find some low-hanging fruits - Increasing build parallelism - Taking advantage of new OpenSOlaris technologies like DTrace and ZFS. - Cleaning up Makefiles (at least some major Makefile issues) - Exploring some aggressive tricks and techniques to radically improve build times - Exploring various caching approaches. The goal is to make builds fast enough for developers to be productive. This is, probably, going to be an open-ended project. +1 -Eric ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [perf-discuss] [osol-discuss] Proposal: new project for improving ON build times
Very interesting and useful too. I gave up and aborted the build after ON build kept running for 5 hrs on Solaris on VMWare. If you a create a separate project, please post it so that we can join the efforts. Cheers, -Atul On 3/27/07, Eric Saxe [EMAIL PROTECTED] wrote: Alexander Kolbasov wrote: I would like to propose a project aimed to improve ON build times. This can live either under tools or under performance or under some other community. There was some discussion about it a while ago in the context of Google summer of code: http://www.opensolaris.org/jive/message.jspa?messageID=33951 It may be a part of ONNV project, or something else if you think that some other project/community is more suitable. The goal of the project is to make our ON builds faster. This includes, but is not limited to: - Developing and running observability tools to understand existing problems and find some low-hanging fruits - Increasing build parallelism - Taking advantage of new OpenSOlaris technologies like DTrace and ZFS. - Cleaning up Makefiles (at least some major Makefile issues) - Exploring some aggressive tricks and techniques to radically improve build times - Exploring various caching approaches. The goal is to make builds fast enough for developers to be productive. This is, probably, going to be an open-ended project. +1 -Eric ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
