[osol-discuss] Re: [osol-announce] OpenGrok, the OpenSolaris.org source browsing tool, is now available for download
On Tue 15 Nov 2005 at 08:45PM, Derek Cicero wrote: OpenGrok, the open source source browsing tool developed by Chandan B.N and used on OpenSolaris.org is now available for download. OpenGrok is a fast and usable source code search and cross reference engine. It helps you search, cross-reference and navigate your source tree. It can understand various program file formats and version control histories like SCCS, RCS and CVS. In other words it lets you grok (profoundly understand) the open source, hence it is called OpenGrok. More information, source and downloads are available on: http://www.opensolaris.org/os/project/opengrok/ [Please set the reply-to for -announce postings to -discuss] Guys, this is a HUGE contribution to the world. Chandan, you have my undying gratitude, as, I think, will hundreds of thousands of developers. Please make a freshmeat.net announcement :) I'm wicked happy. -dp -- Daniel Price - Solaris Kernel Engineering - [EMAIL PROTECTED] - blogs.sun.com/dp ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Is 'forking' inevitable here too?
On Tue, 2005-11-15 at 19:47, Joerg Schilling wrote: GNU The youngest set of tools (starting around 1986). My current idea is to put them into /usr/sps/* as Linux users may expect them in the same hierarchy as the rest of free software. It may be a good idea to create a second location (e.g. /usr/gnu/bin) with symlinks to /usr/sps/bin/gnu-tool to document the origin and to allow to use PATH to set up a specific precedence order. Obviously you can do what you like for your distro but on Solaris /usr/sps isn't likely to be the chosen location it is much more likely to be /usr/gnu where /usr/gnu is strictly for the GNU utils that conflict with stuff in /usr/bin as traditional Solaris stuff or /usr/xpg?/bin as XPG compliant versions where they differ incompatibly from Solaris. /usr/gnu should not be used for any old thing that happens to be under a GPL or LPGL license because it isn't /usr/gpl it is /usr/gnu/ What if anything do you intend to do in SchilliX for XPG compliance where there is a difference between XPG4, XPG5 and XPG6 ? - Put all BSD tools into /usr/bsd/* Are there really that many of them are different from the /usr/bin versions or /usr/ucb versions ? Ie they are actually conflicts rather than commands that don't exist in /usr/bin on Solaris today ? BTW this isn't the best forum for this discussion. This is an architecture discussion and is probably best moved to [EMAIL PROTECTED], it is the ARC forum where we have traditionally had discussions like this at Sun. Best to join that alias and start a fresh thread there rather than continuing as a sub topic on the forking thread. -- Darren J Moffat ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] milestone none really means nothing running at all really
On Wed, 2005-11-16 at 03:52, Dennis Clarke wrote: The boot -m milestone=none resulted in this : Booting to milestone none. Requesting System Maintenance Mode (See /lib/svc/share/README for more information.) Console login service(s) cannot run Root password for system maintenance (control-d to bypass): single-user privilege assigned to /dev/console. Entering System Maintenance Mode Nov 16 03:48:07 su: 'su root' succeeded for root on /dev/console -sh: /bin/i386: not found -sh: /usr/sbin/quota: not found -sh: /bin/cat: not found -sh: /bin/mail: not found # # df -ak df: not found # ls ls: not found # pwd /root That looks like you have split / and /usr, right ? In milestone none only the root filesystem is mounted read only. IMO this is REAL single user mode not that mamby pamby thing with all the local filesystems mounted and some basic networking running :-) -- Darren J Moffat ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] milestone none really means nothing running at all really
-sh: /bin/i386: not found -sh: /usr/sbin/quota: not found -sh: /bin/cat: not found -sh: /bin/mail: not found # # df -ak df: not found # ls ls: not found # pwd /root That looks like you have split / and /usr, right ? And we've long said you shouldn't be doign that :-) Not sure install follows that lead Casper ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Build 27a community release hits SDLC - Has ZFS!
Hi all, Build 27a has hit the SDLC and it carries ZFS URL: http://javashoplm.sun.com/ECom/docs/Welcome.jsp?StoreId=7PartDetailId=Sol-Express_b27-x86-SP-G-BTransactionId=try enjoy!!! This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: milestone none really means nothing running at all really
Booting to milestone none. Requesting System Maintenance Mode (See /lib/svc/share/README for more information.) Console login service(s) cannot run ... # df -ak df: not found # ls ls: not found # pwd /root okay .. really not much here at all. I may have to leave some bins in a /root/bin directory in order to do anything at all. Like run ps or even ls. Or mount the separate /usr filesystem, before trying to use programs stored on that filesystem? (You do have a separate /usr filesystem, do you?) This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: fsck seems to have a few new features in build 26
Well, the ability to boot so single user mode and then run fsck on the current root slice seems to be something that I have done for a long long time. Well, it wasnt just explicitely pointed out as with the fsck re-write now, however fsck_ufs(1M) warns you since ages: snip WARNINGS The operating system buffers file system data. Running fsck on a mounted file system can cause the operating system's buffers to become out of date with respect to the disk. For this reason, the file system should be unmounted when fsck is used. If this is not possible, care should be taken that the system is quiescent and that it is rebooted immediately after fsck is run. Quite often, however, this will not be sufficient. A panic will probably occur if running fsck on a file system modifies the file system. snip end --- frankB This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Build 27a community release hits SDLC - Has ZFS!
Super. This is something I am anxious to try. Kudos to all involved. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: fsck seems to have a few new features in build 26
On 11/16/05, Frank Batschulat [EMAIL PROTECTED] wrote: Well, the ability to boot so single user mode and then run fsck on the current root slice seems to be something that I have done for a long long time. Well, it wasnt just explicitely pointed out as with the fsck re-write now, however fsck_ufs(1M) warns you since ages: snip WARNINGS The operating system buffers file system data. Running fsck on a mounted file system can cause the operating system's buffers to become out of date with respect to the disk. For this reason, the file system should be unmounted when fsck is used. If this is not possible, care should be taken that the system is quiescent and that it is rebooted immediately after fsck is run. Quite often, however, this will not be sufficient. A panic will probably occur if running fsck on a file system modifies the file system. snip end Must be some rare circumstances that would cause that to happen. I have run fsck on the / slice as well as /var and /usr for years while in single user mode and never seen a problem. Sure its common sense to try to boot from some other place before running fsck on the root filesystem. If possible. Dennis ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: milestone none really means nothing running at all really
On 11/16/05, Jürgen Keil [EMAIL PROTECTED] wrote: Booting to milestone none. Requesting System Maintenance Mode (See /lib/svc/share/README for more information.) Console login service(s) cannot run ... # df -ak df: not found # ls ls: not found # pwd /root okay .. really not much here at all. I may have to leave some bins in a /root/bin directory in order to do anything at all. Like run ps or even ls. Or mount the separate /usr filesystem, before trying to use programs stored on that filesystem? (You do have a separate /usr filesystem, do you?) This message posted from opensolaris.org Well /sbin/mount -F ufs -o ro /dev/dsk/c0t0d0s6 /usr works fine. Dennis Dennis ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] milestone none really means nothing running at all really
On Wed, 2005-11-16 at 15:01, [EMAIL PROTECTED] wrote: But I'm certain our best practices now are something like: / /var- for servers only /export - separate the users/data from the rest. I'd agree with that completely. In fact I'd actually say that on general purpose servers even having /var separate isn't useful. On a Kerberos KDC I've have /var/krb5 seperate but the rest of /var just part of /, similarly on a mail server using /var/mail that would be separate etc etc. I also tend to have /var/core and /var/crash separate as well but thats because I don't actually want live upgrade to copy the core and crash files over to the new boot environment, because they aren't relevant. Sometimes I just use dumpadm and coreadm to send them to a filesystem shared between all BEs. -- Darren J Moffat ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] milestone none really means nothing running at all really
[EMAIL PROTECTED] writes: - you run out of space more quickly because you dividing line will not be correct - hard recoverability issues become impossible with net/cdrom boot - the gain in stability is fairly minimal (a read-only /usr mount mostly increases maintenance costs. There's also the path of least resistance issue. The default installs don't include a separate /usr, which means that fewer people do this, and subtle bugs related to it are less likely to be caught. (I'm certainly not saying that our software isn't well-tested. Just that there's no good substitute for having large numbers of people using the system that way.) -- James Carlson, KISS Network[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] milestone none really means nothing running at all really
Darren J Moffat [EMAIL PROTECTED] writes: On Wed, 2005-11-16 at 15:01, [EMAIL PROTECTED] wrote: But I'm certain our best practices now are something like: / /var- for servers only /export - separate the users/data from the rest. I'd agree with that completely. In fact I'd actually say that on general purpose servers even having /var separate isn't useful. I separate / and /var because you can't mount / (incl. /usr) nosuid, but /var is fine with this option. You can even mount / nodevices nowadays, since device special files live in devfs as of S10 (and nosuid has been separated into nosetuid,nodevices; and old RFE of mine). Rainer -- - Rainer Orth, Faculty of Technology, Bielefeld University ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] App porting forum?
Alfredo Peña [EMAIL PROTECTED] wrote: Erast, Thanks for your offer, but I'm trying to target Sun Solaris distro. Probably for most software developing in Nexenta is the same than developing in Solaris, but for something like xine that is very dependent on the specific versions of various libs (gnome, Xorg, libjpeg/tiff/etc...) that are not part of OpenSolaris yet, I assume that using Nexenta would be very different than using Solaris. Please correct me if I'm wrong. There is a big difference between developing on Nexenta and doing the same on Sun Solaris or SchilliX. On the latter, you get full compatibility even for the build system. On Nexenta, it may be that you will get into trouble while compiling because there are no UNIX tools in /usr/bin but GNU tools. So be careful with assumptions on compatibility. For a software dveloper, SchilliX is currently the best platform because it gives better compatibility to Sun Solaris and because the developer tools, libraries and include files are more complete. 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] milestone none really means nothing running at all really
DJM == Darren J Moffat Darren writes: DJM I also tend to have /var/core and /var/crash separate as well but DJM thats because I don't actually want live upgrade to copy the core and DJM crash files over to the new boot environment, because they aren't DJM relevant. DJM Sometimes I just use dumpadm and coreadm to send them to a filesystem DJM shared between all BEs. You can also symlink them off somewhere else. Matt -- Matt Simmons - [EMAIL PROTECTED] | Solaris Kernel - New York Ever consider what they must think of us? I mean, here we come back from a grocery store with the most amazing haul -- chicken, pork, half a cow. They must think we're the greatest hunters on earth! -- Anne Tyler ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] fd limit on 32bit solaris i386 box
It would be simple to add a (maybe hidden) flag to the FILE * data structures that tell stdio that the calling program is aware of the new interface because it has been compiled with the new include files. There's always an issue with old libraries and such and FILE *'s being passed around to such libraries. This needs to apply to _endopen() which does the real work for fopen() and friends. Of course, stdin/stdout/stderr need to be patched too.. Then old binaries would see the old behaviro and new binaries (not using fileno() as macro) would be able to use more than 256 FILE * streams. The outline of the proposed implementation is something like this: - the ability to mark a file descriptors 3 = fd = 255 bad in the kernel (attempts to dup2() to it will fail and the kernel will never return it. close(badfd) fails with EBADF Any other operations will either fail with EBADF or will cause the kernel to send a pre determined signal. - FILE's can either use an ordinary fd = 255 or they can use a shadow fd; in the later case a flag is set in the FILE structure and the fp-_file is set to badfd. - the default behaviour still limits to 256 fds. - applications can request the behaviour by doing a specific call. - libraries can request no bounds FDs without affecting the behaviour for other programs (this means that badfd is not created under those circumstances); that part of the interface will likely not be supported (i.e., not a documented interface, only for use in Sun's libraries which now duplicate part of stdio just to get around the restriction. Casper ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] milestone none really means nothing running at all really
On Wed, 2005-11-16 at 16:21, Matthew Simmons wrote: DJM == Darren J Moffat Darren writes: DJM I also tend to have /var/core and /var/crash separate as well but DJM thats because I don't actually want live upgrade to copy the core and DJM crash files over to the new boot environment, because they aren't DJM relevant. DJM Sometimes I just use dumpadm and coreadm to send them to a filesystem DJM shared between all BEs. You can also symlink them off somewhere else. I use to do that but if using dumpadm and coreadm to actually put them else where seemed like a better solution to me - mainly because they have the functionality built in so why not use it. -- Darren J Moffat ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] milestone none really means nothing running at all really
DJM == Darren J Moffat Darren writes: DJM I use to do that but if using dumpadm and coreadm to actually put them DJM else where seemed like a better solution to me - mainly because they DJM have the functionality built in so why not use it. On the other hand, /var/crash is a well-known location, so there's some value in leaving something there that lets you get to the right place automagically. To each his own. DJM -- Darren J Moffat -- Matt Simmons - [EMAIL PROTECTED] | Solaris Kernel - New York The NASDAQ, properly understood, is nothing more than bingo for yuppies. - Rex Murphy, in an editorial on the CBC National News ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Build 27a community release hits SDLC - Has ZFS!
Sean Sprague wrote: Build 27a has hit the SDLC and it carries ZFS URL: http://javashoplm.sun.com/ECom/docs/Welcome.jsp?StoreId=7PartDetailId=Sol-Express_b27-x86-SP-G-BTransactionId=try Just when I finished installing and configuring b23 on my Thinkpad R50 (including the perfectly working wireless drivers)! Are changelogs available for Solaris Express releases? Or do I have to wait for someone from Sun to blog about it? ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] milestone none really means nothing running at all really
On Wed, 2005-11-16 at 16:43, Matthew Simmons wrote: DJM == Darren J Moffat Darren writes: DJM I use to do that but if using dumpadm and coreadm to actually put them DJM else where seemed like a better solution to me - mainly because they DJM have the functionality built in so why not use it. On the other hand, /var/crash is a well-known location, so there's some value in leaving something there that lets you get to the right place automagically. To each his own. True. Which brings me to very minor grip about the default config of Solaris, it is /var/crash/hostname at the first time you booted which when using DHCP in the default Solaris config can change. Sure I can find out what it is from dumpadm. Why do we still have it as /var/crash/hostname rather than just /var/crash as the default given that dumpadm can be used to change it ? Is this something tied with how we built diskless clients on SunOS ? -- Darren J Moffat ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] milestone none really means nothing running at all really
DJM == Darren J Moffat Darren writes: DJM Which brings me to very minor grip about the default config of DJM Solaris, it is /var/crash/hostname at the first time you booted DJM which when using DHCP in the default Solaris config can change. Sure DJM I can find out what it is from dumpadm. DJM Why do we still have it as /var/crash/hostname rather than just DJM /var/crash as the default given that dumpadm can be used to change it? DJM Is this something tied with how we built diskless clients on SunOS ? I think it's historical. It *might* be tied to diskless clients. They've all got their own /var, but an admin could conceivably replace their /var/crash directories with symlinks to the mothership, but they could make the symlink hostname-specific just as easily. For the specific case you mentioned wrt DHCP, I believe there's an RFE open to add macro support to dumpadm (i.e. /var/crash/$HOST), but I don't have the ID handy. Matt -- Matt Simmons - [EMAIL PROTECTED] | Solaris Kernel - New York A report says the number of train derailments is up. What's the brand new slogan of Amtrak? We love to fly and it shows. - Alan Ray ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] ZFS fun
Hi there, Just got my hands on a copy of Nevada b27 and have started playing with zfs and zpool, and already have run myself into a corner. Is it possible to remove storage from a storage pool without using zpool destroy? Let's say I want to migrate from one storage type to another online, for example a mirrored volume to a raidz volume. If I create the volume with zpool create testpool mirror c1t5d0 c1t6d0 for example, I know that I can add the raidz volume with something like zpool add -f testpool raidz c1t2d0 c1t3d0 c1t4d0 is it possible then to remove the original mirror pair? Or maybe replace one of the mirror components with a raidz set? I was hoping that this flexibility was available to make migration from one type of storage array to another [u]really[/u] easy, something like start with old array and storage layout then zpool add ( new and shiny ) and zpool drop ( old and busted ) wait for i/o to complete and disconnect. Perhaps I am being a little greedy here :) First impressions are that ZFS is excellent and I am looking forward to trying more and more of the features later on, congratulations to everyone involved! All the best, Alan This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Build 27a community release hits SDLC - Has ZFS!
Josip Gracin wrote: Are changelogs available for Solaris Express releases? Not in full. ON X currently publish changelogs for those bits, but I don't know of any other consolidations that do so yet. See: http://opensolaris.org/os/community/onnv/onnv_putback_logs/ http://opensolaris.org/os/community/x_win/changelogs/ -- -Alan Coopersmith- [EMAIL PROTECTED] Sun Microsystems, Inc. - X Window System Engineering ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] ZFS fun
On Wed, Nov 16, 2005 at 09:06:03AM -0800, Alan Romeril wrote: Hi there, Just got my hands on a copy of Nevada b27 and have started playing with zfs and zpool, and already have run myself into a corner. Is it possible to remove storage from a storage pool without using zpool destroy? Currently, no; I just put up a blog entry about my experience with this: https://blogs.sun.com/roller/page/jwadams?entry=an_initial_encounter_with_zfs Let's say I want to migrate from one storage type to another online, for example a mirrored volume to a raidz volume. If I create the volume with zpool create testpool mirror c1t5d0 c1t6d0 for example, I know that I can add the raidz volume with something like zpool add -f testpool raidz c1t2d0 c1t3d0 c1t4d0 is it possible then to remove the original mirror pair? Or maybe replace one of the mirror components with a raidz set? This is not yet possible; it is being worked on, but I'm not sure of the timeframe; I'll let one of the ZFS folk answer this. I was hoping that this flexibility was available to make migration from one type of storage array to another [u]really[/u] easy, something like start with old array and storage layout then zpool add ( new and shiny ) and zpool drop ( old and busted ) wait for i/o to complete and disconnect. Perhaps I am being a little greedy here :) My understanding is that that is the desired end functionality; currently, you can't do it. Cheers, - jonathan -- Jonathan Adams, Solaris Kernel Development ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] ZFS fun
(CCing zfs-discuss, since it is the better forum) On Wed, Nov 16, 2005 at 09:06:03AM -0800, Alan Romeril wrote: Hi there, Just got my hands on a copy of Nevada b27 and have started playing with zfs and zpool, and already have run myself into a corner. Is it possible to remove storage from a storage pool without using zpool destroy? Currently, no; I just put up a blog entry about my experience with this: https://blogs.sun.com/roller/page/jwadams?entry=an_initial_encounter_with_zfs Let's say I want to migrate from one storage type to another online, for example a mirrored volume to a raidz volume. If I create the volume with zpool create testpool mirror c1t5d0 c1t6d0 for example, I know that I can add the raidz volume with something like zpool add -f testpool raidz c1t2d0 c1t3d0 c1t4d0 is it possible then to remove the original mirror pair? Or maybe replace one of the mirror components with a raidz set? This is not yet possible; it is being worked on, but I'm not sure of the timeframe; I'll let one of the ZFS folk answer this. I was hoping that this flexibility was available to make migration from one type of storage array to another [u]really[/u] easy, something like start with old array and storage layout then zpool add ( new and shiny ) and zpool drop ( old and busted ) wait for i/o to complete and disconnect. Perhaps I am being a little greedy here :) My understanding is that that is the desired end functionality; currently, you can't do it. First impressions are that ZFS is excellent and I am looking forward to trying more and more of the features later on, congratulations to everyone involved! Cheers, - jonathan -- Jonathan Adams, Solaris Kernel Development ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Build 27a community release hits SDLC - Has ZFS!
Josip Gracin writes: Are changelogs available for Solaris Express releases? Or do I have to wait for someone from Sun to blog about it? The only open changelogs I know about are in Dan Price's blog. -- James Carlson, KISS Network[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] Is 'forking' inevitable here too?
Erast Benson [EMAIL PROTECTED] wrote: very true. dpkg's alternatives is a good thing. Also there are other ways to achive that, i.e. playing with execv() for instance. Did you hack libc to do this? 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] Is 'forking' inevitable here too?
On Wed, 2005-11-16 at 18:36 +0100, Joerg Schilling wrote: Erast Benson [EMAIL PROTECTED] wrote: very true. dpkg's alternatives is a good thing. Also there are other ways to achive that, i.e. playing with execv() for instance. Did you hack libc to do this? No. not yet. But at least we've discussed it a lot back in July. There was some other solutions, like sunsh wrapper with LD_LIBRARY_PATH tricks and so on. Erast ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] App porting forum?
On Wed, 2005-11-16 at 17:09 +0100, Joerg Schilling wrote: Alfredo Peña [EMAIL PROTECTED] wrote: Erast, Thanks for your offer, but I'm trying to target Sun Solaris distro. Probably for most software developing in Nexenta is the same than developing in Solaris, but for something like xine that is very dependent on the specific versions of various libs (gnome, Xorg, libjpeg/tiff/etc...) that are not part of OpenSolaris yet, I assume that using Nexenta would be very different than using Solaris. Please correct me if I'm wrong. There is a big difference between developing on Nexenta and doing the same on Sun Solaris or SchilliX. On the latter, you get full compatibility even for the build system. On Nexenta, it may be that you will get into trouble while compiling because there are no UNIX tools in /usr/bin but GNU tools. So be careful with assumptions on compatibility. For a software dveloper, SchilliX is currently the best platform because it gives better compatibility to Sun Solaris and because the developer tools, libraries and include files are more complete. Actually regarding xine and alike, Nexenta would be a better option for developers because of availability of libraries which does not exists on Solaris or blastwave.org. I'm talking about various plugins, language bindings and so on. All these extra libraries are part of Nexenta core. So, whether SchiliX or Nexenta better for developers is all pretty much depends on developers and their tasks. And just to notice, I think compilation of OpenSolaris on Nexenta is very possible, and will be available in Alpha 2 time frame. Erast ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] App porting forum?
Erast Benson [EMAIL PROTECTED] wrote: And just to notice, I think compilation of OpenSolaris on Nexenta is very possible, and will be available in Alpha 2 time frame. If you believe this, you did obviously never actually try it out.. Of course, if you delay Alpha 2 for several weeks you may be right ;-) 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
[osol-discuss] Re: newb help
thanks michelle. i am not really looking for how to write the code, i just want to know the basics of how it works. does anyone happen to know where i can find the solaris 10 zfs file system limitations are? i cant really seem to find it on the sun site. thanks This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] App porting forum?
On Wed, 2005-11-16 at 19:59 +0100, Joerg Schilling wrote: Erast Benson [EMAIL PROTECTED] wrote: And just to notice, I think compilation of OpenSolaris on Nexenta is very possible, and will be available in Alpha 2 time frame. If you believe this, you did obviously never actually try it out.. I think Mac tried it out. There was many issues all over... But all this is doable. Of course, if you delay Alpha 2 for several weeks you may be right ;-) Right. :-) No rush. After all, some bits are not even available yet. Erast ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] fsck seems to have a few new features in build 26
Jonathan Adams schrieb: On Tue, Nov 15, 2005 at 08:06:06PM -0500, Dennis Clarke wrote: Hold on .. do you mean from the ok prompt ? ok boot -m milestone=none as opposed to ok boot -sv hmmm fascinating ... let me try that right now. Yes; it's a completely minimal boot, with nothing but init(1M), svc.startd(1M), svc.configd(1M), and sulogin(1M) running. Finally we have an official replacement for the undocumented boot -b flag in earlier Solaris releases. Daniel ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: [osol-announce] OpenGrok, the OpenSolaris.org source browsing tool, is now available for download
On 11/15/05, Derek Cicero [EMAIL PROTECTED] wrote: OpenGrok, the open source source browsing tool developed by Chandan B.N and used on OpenSolaris.org is now available for download. Very cool - this will be a great way to bridge communities (since it's useful to all developers, not just those working on operating systems or using Solaris/OpenSolaris). Is this going to get its own discussion list? I already have a couple of (minor) bugs to report, plus some comments and questions. opensolaris-discuss doesn't seem like the right place for these. Andy ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] OpenGrok, the OpenSolaris.org source browsing tool, is now available for download
On Wed, 2005-11-16 at 12:13, Andy Tucker wrote: or using Solaris/OpenSolaris). Is this going to get its own discussion list? I already have a couple of (minor) bugs to report, plus some comments and questions. Derek is working on getting project support as per roadmap http://www.opensolaris.org/os/about/roadmap/ (I guess that might mean having project specific mailing lists, issue tracking etc., For now, send bugs, feedback or ideas to [EMAIL PROTECTED] Thanks, -Chandan -- https://blogs.sun.com/chandan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Build 27 available at www.genunix.org
URL:http://www.genunix.org/mirror/index.html Many congrats to team ZFS! Al Hopper Logical Approach Inc, Plano, TX. [EMAIL PROTECTED] Voice: 972.379.2133 Fax: 972.379.2134 Timezone: US CDT OpenSolaris.Org Community Advisory Board (CAB) Member - Apr 2005 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: build 27a on x86 : panic at boot
how did you install it? was it an upgrade or a clean install? i have had a similar problem with b24 http://www.opensolaris.org/jive/thread.jspa?threadID=2745tstart=0 This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] build 27a on x86 : panic at boot
Dennis Clarke wrote: diskread: reading beyond end of ramdisk start = 0x2000, size = 0x2000 failed to read superblock diskread: reading beyond end of ramdisk start = 0x8000, size = 0x800 failed to read superblock panic: cannot mount boot archive Press any key to reboot I don't think that is what I was expecting ... :-( Me neither, my test system (dual Athlon MP) give a panic in the bootloader. The previous BE (b25) still boots OK. Ian ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
