[osol-discuss] OpenSolaris rsync
What are our prospects of making OpenSolaris distributables avalible to mirrors via Rsync? Right now the reason Genunix updates are taking so long is because of the time involved; due to the monster URLs used by SDC I'm having to download each file manually via a browser, then upload to genunix and update the HTML. I'd like to be able to automate the process. Rsync would make mirroring way easier and facilitate additional mirrors in the future. Any chances on this one? benr. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] OpenSolaris rsync
On Tue, 2005-10-25 at 02:37 -0700, Ben Rockwood wrote: What are our prospects of making OpenSolaris distributables avalible to mirrors via Rsync? Right now the reason Genunix updates are taking so long is because of the time involved; due to the monster URLs used by SDC I'm having to download each file manually via a browser, then upload to genunix and update the HTML. I'd like to be able to automate the process. Rsync would make mirroring way easier and facilitate additional mirrors in the future. Ben, I am using wget to download sources directly to svn.genunix.org At 20Mb/s average it works remarkably well. +1 to rsync, though. Cyril Any chances on this one? benr. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] A 42-in-1 flash card reader project
ken mays [EMAIL PROTECTED] wrote: For innovative college students looking for the next big thing in software engineering: Coming to an OpenSolaris project near you: http://www.xpcgear.com/42i1cardreader.html Why is there a need for a project? This kind of devices work since Solaris 9 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] OpenSolaris rsync
We've gotten approval to use opensolaris.org as a download site, so we should be able to bypass SDLC in the future. I'm not sure what the timeframe is for providing downloads directly off of opensolaris.org though. But that would certainly make it easier to automatically sync up with genunix. Derek? Do you have any idea when we'll be able to do this? In the meantime, maybe we can find an interm solution. What if I have my delivery scripts scp it directly onto genunix once I have them ready? cheers, steve Ben Rockwood wrote: What are our prospects of making OpenSolaris distributables avalible to mirrors via Rsync? Right now the reason Genunix updates are taking so long is because of the time involved; due to the monster URLs used by SDC I'm having to download each file manually via a browser, then upload to genunix and update the HTML. I'd like to be able to automate the process. Rsync would make mirroring way easier and facilitate additional mirrors in the future. Any chances on this one? benr. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org -- stephen lau // [EMAIL PROTECTED] | 650.786.0845 | http://whacked.net opensolaris // solaris kernel development ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: SchilliX-0.2 ready, but SchilliX (the project) needs help
[EMAIL PROTECTED] wrote: Jake Maciejewski [EMAIL PROTECTED] wrote: Let us face reality... Belenix has been developped by starting with SchilliX and modifying it. Um ... I'd strongly object to this statement! It is correct that 2 ideas were taken from the earlier discussions on this list: * Using the math library from FreeBSD * Using the aperture driver as a replacement for xsvc Well, Belenix has just too much in common with SchilliX that is completely different to what Sun does on Sun Solaris to believe you. - The way to do the overall split of / and /usr - The fact that the CD-ROM is mounted on /.cdrom - The fact that subdirectories from /.cdrom are mounted to e.g. /usr via lofs. and some other minor stuff. It is most unlikely that you did never have a look at SchilliX and we all know, that knowing that/how something works makes things a lot easier for people who do it the second time and are not forced to develop everything from scratch as I did. 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] Re: Re: SchilliX-0.2 ready, but SchilliX (the project) needs help
Does it matter? One of the great features of open source is being able to save time and derive from other people's work, whether it be implicitly or explicitly. Our nascent community should be helping and supporting each other - not arguing silly debates. cheers, steve Joerg Schilling wrote: [EMAIL PROTECTED] wrote: Jake Maciejewski [EMAIL PROTECTED] wrote: Let us face reality... Belenix has been developped by starting with SchilliX and modifying it. Um ... I'd strongly object to this statement! It is correct that 2 ideas were taken from the earlier discussions on this list: * Using the math library from FreeBSD * Using the aperture driver as a replacement for xsvc Well, Belenix has just too much in common with SchilliX that is completely different to what Sun does on Sun Solaris to believe you. - The way to do the overall split of / and /usr - The fact that the CD-ROM is mounted on /.cdrom - The fact that subdirectories from /.cdrom are mounted to e.g. /usr via lofs. and some other minor stuff. It is most unlikely that you did never have a look at SchilliX and we all know, that knowing that/how something works makes things a lot easier for people who do it the second time and are not forced to develop everything from scratch as I did. Jörg -- stephen lau // [EMAIL PROTECTED] | 650.786.0845 | http://whacked.net opensolaris // solaris kernel development ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: SchilliX-0.2 ready, but SchilliX (the project) needs help
Erast Benson [EMAIL PROTECTED] wrote: let me clarify a little bit on what GNU/Solaris distro is. Thank you! The idea behind it is simple: do not re-invent the wheel and try to re-use existing 17000 high quality Debian packages, Debian infrastracture(read Dpkg, APT repositories, Debootstraps, installation program, utilities, developer's policy and so on) and Debian developer's if you will. It depends on how we define re-invent the wheel I try to avoid to re-invent the wheel for SchilliX by not using a different package system than the one used by Solaris and I don't try to replace standard UNIX tools by GNU clones. As a result of the missing pkg system, I need to wait and to create a simple intermediate method for packaging. In addition, I look at the quality of the debian packages and I see that Debian publishes a version of cdrtools that is broken because of the patches that are applied by Debian. For this reason, I believe that it may be similar with other tools and the only way to have guaranteed quality is to create your own compile environment for the free software you linke or need to package together with OpenSolaris. GNU/Solaris distribution uses OpenSolaris kernel and runtime(libc). So, it runs any existing Solaris software without modifications. In addition to that(and this is what differes it from SchiliX and BeliniX), it greatly simplifies porting effort for pure Linux applications and packages, since it provides real Debian environment. And how do you include these Debian packages? If you put them into /usr/bin, you will overwrite existing standard UNIX tools and then you will not be able to benefit from e.g. smf because you are forced to use the init process that Debian uses on Linux. If you would like to get guest password and participate in further development you could send me a request e-mail. If you are willing to participate in further SchilliX development, I would be happy to help your project too. 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] /usr/lib/lu/lucreatezone
Hi, A while ago, Andy Tucker did write that /usr/lib/lu/lucreatezone has been a shell script during the development of zones ahd that: Perhaps David or Dan could dig out some version of those scripts. I would like to add zone support to SchilliX and it would be nice if there was a way to make them work on OpenSolaris as well as on Sun Solaris. 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] Re: Re: SchilliX-0.2 ready, but SchilliX (the project) needs help
Stephen Lau [EMAIL PROTECTED] wrote: Does it matter? One of the great features of open source is being able to save time and derive from other people's work, whether it be implicitly or explicitly. Our nascent community should be helping and supporting each other - not arguing silly debates. Well sayd! I am still waiting for more people who contribute to SchilliX 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] Re: Re: Re: SchilliX-0.2 ready, but SchilliX (the project) needs help
Jake Maciejewski [EMAIL PROTECTED] wrote: Thank you for the clarification. GNU/Solaris sounds like it will be the ideal OpenSolaris desktop. It would help people coming from the Linux corner. It would most likely not fit my wishes. ... let us wait and see what it really is, once it is available. 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] community proposal: OpenSolaris storage
James C. McPherson wrote: Aaron Dailey wrote: I'd like to propose a community dedicated to the storage software in Open Solaris. This would include drivers below the filesystems/volume managers, and related utilities. For example, this would be: -target drivers such as sd, st, ses -SCSA framework -FibreChannel stack, various parallel SCSI HBA drivers, ATA/IDE drivers, the iSCSI initiator -The storage specific portions of USB and Firewire -Related utilities, such as fcinfo, format, luxadm, cfgadm plugin, etc I see a couple reasons to do this: -Generally the storage stack is a distinct part of OpenSolaris, and it's interesting, at least to some of us :-) -More specifically, the division of Sun I work in will soon be releasing source for FibreChannel and the iSCSI initiator, as well as other bits, and this community would be a good place for any discussion to occur. Moreover, there's a lot of code already released that deals with storage, which this community would include. I second this proposal, especially since I'm in the same group as Aaron :) +1 -- Chris Gerhard. __o __o __o PTS in Europe _`\,`\,`\,_ Sun Microsystems Limited (*)/---/---/ (*) Phone: +44 (0) 1252 426033 (ext 26033) --- http://blogs.sun.com/chrisg --- NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. smime.p7s Description: S/MIME Cryptographic Signature ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: SchilliX-0.2 ready, but SchilliX (the project) needs help
Jörg, I have the kit and Schillix-0.2 so just need time to review. If someone already has X built for you then just tar up the binaries/libs and post them on the mirrors. I have tarballs of X 6.8.2 (CVS) compiled as well as in Solaris package formats. Take your pick. if you have a natively built one already then let us get it our there so we can test it and move on. If rebuilding Schillix with X included appeals, then better do it now with the new patches and files than wait. Schillix 0.2.1 ?!?! I beleive it should really be that simple with any of these distros. Anyhow, I'm looking about 4,000 GNU packages that can work universally with either Schillix and other distros. Possible? Mainly, to evaluate Sun Studio 10 in various build situations. So, once the debating is over... can we review the autobuild systems and how we can use Schillix to meet that goal?? ;o ~Ken Mays --- Joerg Schilling [EMAIL PROTECTED] wrote: ken mays [EMAIL PROTECTED] wrote: I have X.org 6.8.2 libraries, binaries, and header packages built for Solaris 8/9/10 (x86/SPARC) over at Blastwave. Could these work for you?!? I am not sure. The Blastwave packages itself do not work at all because the pkg* tools are missing on OpenSolaris and because most */reloc/* files do not have the right permissions in the archive. In addition, symlinks are often missing. This was e.g. a big problem when I tried to install the java compiler on Schillix (which is needed to compile OpenSolaris but which is not available as tar archive for OpenSolaris). If you like to unserstand how SchilliX is created from packages, please have a look at the SchilliX ISO kit. 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 __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: Re: SchilliX-0.2 ready, but SchilliX (the project) needs help
Jake Maciejewski [EMAIL PROTECTED] wrote: SchilliX won't be able to compete with GNU/Solaris as a desktop. In the Linux and BSD world, distributions need to find a niche to remain popular. For SchilliX, this might be servers and the authentic Solaris experience. You've done a great job packaging OpenSolaris in a usable form, but others have now managed to do the same. You won't be without competition for much longer, and Xorg without applications isn't the answer to the upcoming dilemma. Xorg is the start for the upcomming enhancements for SchilliX. I never did believe that SchilliX would stay without competition. It did even happen later then I believed. 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] Re: Re: Re: SchilliX-0.2 ready, but SchilliX (the
TJ Yang [EMAIL PROTECTED] wrote: Good short and insight comment about SchilliX distribution. The bigger problem is funding issue. I don't know solution for opensolaris funding issue. blastware was in trouble and now Schillix project. Sun has a good bussiness model by supporting Solaris, but where is the bussiness model for OpenSolaris ? can people make a living out of opensolaris work ? I am not sure if a general business model for OpenSolaris would help SchilliX. Since Spring 2005 I am working on SchilliX during my office hours at Fokus. This may be forced to end soon unless we find a way to fund the project. If I don't have my employed student anymore and if I need to share my free time with working on star, cdrecord, SchilliX and other free software, I will be much slower than I am today. Once release in early Novemenber, I am interested to translate the livecd process into one of the modulesin opensolaris-20050909.sb at http://en.wikibooks.org/wiki/OpenSolaris/Developer The SchilliX Kit is available since yesterday, so you could start to document it. ftp://ftp.berlios.de/pub/schillix/schillix-0.2-kit.tar Do you think will we end up like Linux to have 300+ distribution ? I was in hope that we could have a unified corporate aproach for a Life CD or distribution as it is done by e.g. the FreeBSD people. It seems that people who are interested in OpenSolaris don't like the corporate aproach but all try to run their own business which results in being less effective than possible. It is worng do discouge innovation but we should avoid unafforable variations to drain the limited and free-time resources. I WISH we have one OpenSolaris LIVE CD, one embeded OpenSolaris, one OpenSolaris Sparc and one OpenSoarlis i386/AMD64, that is it. I would cuncur but I doubt that it will be this way. The track switches are already set and you cannot turn the clock back. I am even sure that there are people who would prefer a Gnusolaris distribution. I personally prefer an OS that behaves like UNIX. 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] Re: Re: SchilliX-0.2 ready, but SchilliX (the project) needs help
ken mays [EMAIL PROTECTED] wrote: Jörg, I have the kit and Schillix-0.2 so just need time to review. If someone already has X built for you then just tar up the binaries/libs and post them on the mirrors. I have tarballs of X 6.8.2 (CVS) compiled as well as in Solaris package formats. Take your pick. if you have a natively built one already then let us get it our there so we can test it and move on. If rebuilding Schillix with X included appeals, then better do it now with the new patches and files than wait. X should compile on SchilliX-0.2 as I did pot some effort in libm and math.h Schillix 0.2.1 ?!?! I am currently compiling Build 25 and I expect SchilliX-0.2.1 to be ready soon :-) I beleive it should really be that simple with any of these distros. Anyhow, I'm looking about 4,000 GNU packages that can work universally with either Schillix and other distros. Possible? Mainly, to evaluate Sun Studio 10 in various build situations. As Studio 10 is fully C-99, it is easier to deal with various sources that use .member = val in struct init statements. So, once the debating is over... can we review the autobuild systems and how we can use Schillix to meet that goal?? ;o I did start the sps system as a wrapper for sources and did use it already for all the packages that are currently part of SchilliX. 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] Re: Re: SchilliX-0.2 ready, but SchilliX (the project) needs help
[EMAIL PROTECTED] wrote: Let us face reality... Belenix has been developped by starting with SchilliX and modifying it. Um ... I'd strongly object to this statement! It is correct that 2 ideas were taken from the earlier discussions on this list: * Using the math library from FreeBSD * Using the aperture driver as a replacement for xsvc Well, Belenix has just too much in common with SchilliX that is completely different to what Sun does on Sun Solaris to believe you. - The way to do the overall split of / and /usr - The fact that the CD-ROM is mounted on /.cdrom - The fact that subdirectories from /.cdrom are mounted to e.g. /usr via lofs. and some other minor stuff. It is most unlikely that you did never have a look at SchilliX and we all know, that knowing that/how something works makes things a lot easier for people who do it the second time and are not forced to develop everything from scratch as I did. True. But these are just the ideas that you also get by by looking at any of the Linux LiveCDs from a high level. Translating from these ideas into a working self-hosting distro is the real challenge: * Just looking at a disro does not tell you how the Solaris New Boot works. One needs to understand this in order to create an OpenSolaris distro. How does one figure out the key to getting a rootfs on the ramdisk without knowing Newboot - the fact that ?bootpath? should be absent. * How do you find out the cd device node that contains the LiveCD early in the boot when devfsadm has not yet executed ? It took me two iterations to arrive at an optimal solution. First solution was suboptimal till I wrote a small utility using libdevinfo to list the cd nodes and then use fstyp on them to get the volume id. * How do you handle the Math library requirements ? I ported and enhanced the FreeBSD math libary which was more than a week's effort for me. SchilliX did not make the Math library sources available. * What files do you include in the miniroot ? Optimise space. * What are the correct options to pass to mkisofs to get the desired bootable cd ? * How do you handle the inetd failures ? Inetd has a dependency on ksh and it took me several days of hacking to identify that the same functionality exists in /usr/xpg4/bin/sh * I had to write the missing sysidtool service manifests and renamed them to sysonfigure. * I had to preconfigure additional open-source drivers like network drivers from Masayuki. Which files should you change to add the drivers by hand ? * One can easily configure dhcp on a interface but it is quite involved to write a proper /etc/dhcp/eventhook script that auto-configures DNS and NIS based on whichever is available. * I have actually picked ideas from KnoppiX like: - Giving user option to select the keyboard layout and subsequently using it for setting XKBLayout in Xorg as well. - Scanning all block devices and mounting any supported filesystems - recovery feature - Using physical swap if a Solaris partition is present on the harddisk How to identify the swap slice ? * Knowing the boot sequence in SMF using Dan Price and Eric Schrock's bootchart. * Fixing shutdown issues * Configuring many things in /etc to get a clean boot * Vold throws out the cdrom occasionally so I had to disable the cdrom module in vold. * Which files do you need to modify in OpenSolaris source to get the BeleniX name instead of Solaris ? I had to tackle all these and many more smaller issues too numerous to mention here. Obviously I had seen the SchilliX 0.1 in action and got a few ides from there. But there is a big difference in getting an idea and it's implementation. Building an entire distro from source code is a real challenge - I built everything in BeleniX from source code. I have written build and package metadata generation scripts. Nothing apart from the SchilliX iso was available when I started. Now that you have made the ISO kit available, it will be easy to create SchilliX derivatives. People can look at your scripts and quickly know how things are done. So I object to the term: Belenix has been developped by starting with SchilliX and modifying it. I did not modify SchilliX. I just picked a few ideas from it as I picked from KnoppiX and built everything else on my own. That effort should not be underestimated. Having said that it is also pertinent to point out that your challenge was greater than mine since you are the pioneer, and started from a clean slate. Also as Stephen pointed out in another email, lets end the debate right now. This is how open-source works by sharing ideas and code. I came out with a distro because I had my own reasons and ideas. I do not think there is anything wrong with that. It will be great for OpenSolaris in
Re: [osol-discuss] Re: Re: SchilliX-0.2 ready, but SchilliX (the project) needs help
[EMAIL PROTECTED] wrote: Let us face reality... Belenix has been developped by starting with SchilliX and modifying it. Um ... I'd strongly object to this statement! It is correct that 2 ideas were taken from the earlier discussions on this list: * Using the math library from FreeBSD * Using the aperture driver as a replacement for xsvc Well, Belenix has just too much in common with SchilliX that is completely different to what Sun does on Sun Solaris to believe you. - The way to do the overall split of / and /usr - The fact that the CD-ROM is mounted on /.cdrom - The fact that subdirectories from /.cdrom are mounted to e.g. /usr via lofs. and some other minor stuff. It is most unlikely that you did never have a look at SchilliX and we all know, that knowing that/how something works makes things a lot easier for people who do it the second time and are not forced to develop everything from scratch as I did. True. But these are just the ideas that you also get by by looking at any of the Linux LiveCDs from a high level. Translating from these ideas into a working self-hosting distro is the real challenge: * Just looking at a disro does not tell you how the Solaris New Boot works. One needs to understand this in order to create an OpenSolaris distro. How does one figure out the key to getting a rootfs on the ramdisk without knowing Newboot - the fact that ?bootpath? should be absent. * How do you find out the cd device node that contains the LiveCD early in the boot when devfsadm has not yet executed ? It took me two iterations to arrive at an optimal solution. First solution was suboptimal till I wrote a small utility using libdevinfo to list the cd nodes and then use fstyp on them to get the volume id. * How do you handle the Math library requirements ? I ported and enhanced the FreeBSD math libary which was more than a week's effort for me. SchilliX did not make the Math library sources available. * What files do you include in the miniroot ? Optimise space. * What are the correct options to pass to mkisofs to get the desired bootable cd ? * How do you handle the inetd failures ? Inetd has a dependency on ksh and it took me several days of hacking to identify that the same functionality exists in /usr/xpg4/bin/sh * I had to write the missing sysidtool service manifests and renamed them to sysonfigure. * I had to preconfigure additional open-source drivers like network drivers from Masayuki. Which files should you change to add the drivers by hand ? * One can easily configure dhcp on a interface but it is quite involved to write a proper /etc/dhcp/eventhook script that auto-configures DNS and NIS based on whichever is available. * I have actually picked ideas from KnoppiX like: - Giving user option to select the keyboard layout and subsequently using it for setting XKBLayout in Xorg as well. - Scanning all block devices and mounting any supported filesystems - recovery feature - Using physical swap if a Solaris partition is present on the harddisk How to identify the swap slice ? * Knowing the boot sequence in SMF using Dan Price and Eric Schrock's bootchart. * Fixing shutdown issues * Configuring many things in /etc to get a clean boot * Vold throws out the cdrom occasionally so I had to disable the cdrom module in vold. * Which files do you need to modify in OpenSolaris source to get the BeleniX name instead of Solaris ? I had to tackle all these and many more smaller issues too numerous to mention here. Obviously I had seen the SchilliX 0.1 in action and got a few ides from there. But there is a big difference in getting an idea and it's implementation. Building an entire distro from source code is a real challenge - I built everything in BeleniX from source code. I have written build and package metadata generation scripts. Nothing apart from the SchilliX iso was available when I started. Now that you have made the ISO kit available, it will be easy to create SchilliX derivatives. People can look at your scripts and quickly know how things are done. So I object to the term: Belenix has been developped by starting with SchilliX and modifying it. I did not modify SchilliX. I just picked a few ideas from it as I picked from KnoppiX and built everything else on my own. That effort should not be underestimated. Having said that it is also pertinent to point out that your challenge was greater than mine since you are the pioneer, and started from a clean slate. Also as Stephen pointed out in another email, lets end the debate right now. This is how open-source works by sharing ideas and code. I came out with a distro because I had my own reasons and ideas. I do not think there is anything wrong with that. It will be great for OpenSolaris in
Re: [osol-discuss] Re: Re: SchilliX-0.2 ready, but SchilliX (the project) needs help
On Tue, 2005-10-25 at 15:20 +0200, Joerg Schilling wrote: Erast Benson [EMAIL PROTECTED] wrote: let me clarify a little bit on what GNU/Solaris distro is. Thank you! The idea behind it is simple: do not re-invent the wheel and try to re-use existing 17000 high quality Debian packages, Debian infrastracture(read Dpkg, APT repositories, Debootstraps, installation program, utilities, developer's policy and so on) and Debian developer's if you will. It depends on how we define re-invent the wheel I try to avoid to re-invent the wheel for SchilliX by not using a different package system than the one used by Solaris and I don't try to replace standard UNIX tools by GNU clones. Well, this is the idea behind of GNU/Solaris: to be as much GNU centric as possible, but do not break sunw* core. GNU/Solaris trying to find gold middle and trying to do it right. As a result of the missing pkg system, I need to wait and to create a simple intermediate method for packaging. In addition, I look at the quality of the debian packages and I see that Debian publishes a version of cdrtools that is broken because of the patches that are applied by Debian. For this reason, I believe that it may be similar with other tools and the only way to have guaranteed quality is to create your own compile environment for the free software you linke or need to package together with OpenSolaris. GNU/Solaris distribution uses OpenSolaris kernel and runtime(libc). So, it runs any existing Solaris software without modifications. In addition to that(and this is what differes it from SchiliX and BeliniX), it greatly simplifies porting effort for pure Linux applications and packages, since it provides real Debian environment. And how do you include these Debian packages? If you put them into /usr/bin, you will overwrite existing standard UNIX tools and then you will not be able to benefit from e.g. smf because you are forced to use the init process that Debian uses on Linux. If you would like to get guest password and participate in further development you could send me a request e-mail. If you are willing to participate in further SchilliX development, I would be happy to help your project too. virtually, all our distros based on the same core bits - sunw*. We are planning quite a bit of work there. So, all these beginnings, (i.e. SchiliX, BeliniX) are very good for overall progress. After all, thanks to GPL/CDDL. It forces/stimulates developers to exchange patches between the projects. We will launch pilot GNU/Solaris developer's program by the end of this week. So, if you didn't get invitation yet, send e-mail to me, and hold your breath a little longer. Thank you. Erast ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: SchilliX-0.2 ready, but SchilliX (the project) needs help
1. XFCE 4.2.2 ? 2. Xorg 6.9 RC1 (CVS) - is this with the latest DRI drivers as well ? If so this, this is great! ~Ken M. --- [EMAIL PROTECTED] wrote: BTW BeleniX 0.2 is due out shortly and boots into a full Graphical XFce4 desktop on Xorg 6.9 RC1 (CVS). It has preliminary auto-configuration support that augments X -configure. Regards, Moinak. 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 __ Start your day with Yahoo! - Make it your home page! http://www.yahoo.com/r/hs ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: SchilliX-0.2 ready, but SchilliX (the project) needs help
Erast Benson and Joerg Schilling were discussing GNU/Solaris: GNU/Solaris distribution uses OpenSolaris kernel and runtime(libc). So, it runs any existing Solaris software without modifications. If you put them into /usr/bin, you will overwrite existing standard UNIX tools This points out some large differences in people's perceptions of what is a Solaris app? One perspective is a minimalist one, concerned with syscalls in libc; another is broader and takes into account the utilities and other commands that are part of the system. Still others focus on middle ware and libraries, Java, web services, etc... That is, runs any existing Solaris Software without modifications is more difficult to do than it is to say. It is safe to say that the ARC process at Sun spends much of its time ensuring that changes to the system don't negatively impact this area. The Solaris Binary Compatibility effort (see appcert(1)) grapples with this issue as well. Going forward with OpenSolaris distros, a simple expectation might be If it runs on Solaris AND it passes appcert(1), then it should also run on any Solaris Compatible system. (Noting that appcert focuses on shared libraries and does not address system()'d or exec()'d utilities...) -John ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: Re: SchilliX-0.2 ready, but SchilliX (the
TJ Yang [EMAIL PROTECTED] wrote: [snipped...] It is worng do discouge innovation but we should avoid unafforable variations to drain the limited and free-time resources. I WISH we have one OpenSolaris LIVE CD, one embeded OpenSolaris, one OpenSolaris Sparc and one OpenSoarlis i386/AMD64, that is it. I would cuncur but I doubt that it will be this way. The track switches are already set and you cannot turn the clock back. I am even sure that there are people who would prefer a Gnusolaris distribution. I personally prefer an OS that behaves like UNIX. That's the point. There are diferent user communities who would expect different things from a distro. There cannot be the ONE distro that satifies everybody. In my personal experience I have seen a Big user community exists who would be inerested in a GNU/Solaris distro. This community is pretty BIG in India. And there is also a user community who would want a UNIX distro, not a clone. IMHO the presence of multiple distros helps the popularity of GNU/Linux. Even though too many distros creates problems there has to be 1 distro to cater to differnt user groups with conflicting requirements. Regards, Moinak. 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 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: SchilliX-0.2 ready, but SchilliX (the project) needs help
1. XFCE 4.2.2 ? XFce 4.2.0 . 2. Xorg 6.9 RC1 (CVS) - is this with the latest DRI drivers as well ? Yes. I did a cvs update of the tree several hours back. I have also included Firefox 1.5/ Thunderbird 1.5 Beta2, Gaim, XMMS, some of the libraries from Gnome 2.12 with Cairo support, Vim 6.4 etc. All of these built on BeleniX 0.2 using gcc 3.4. In fact I am sending this email from Firefox 1.5 running on BeleniX 0.2 which is running on my AMD laptop :) Regards, Moinak. If so this, this is great! ~Ken M. --- [EMAIL PROTECTED] wrote: BTW BeleniX 0.2 is due out shortly and boots into a full Graphical XFce4 desktop on Xorg 6.9 RC1 (CVS). It has preliminary auto-configuration support that augments X -configure. Regards, Moinak. 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 __ Start your day with Yahoo! - Make it your home page! http://www.yahoo.com/r/hs ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] b24 and b25 panic on UltraAXe
I got panics booting from the b24 and b25 CDs on my UltraAXe. It gets as far as the banner and the little spinning line and then barfs on the screen. I haven't had a chance yet to do it over a serial console to capture the data, but wanted to check if anyone else had a UltraAXe that was working correctly. This system was previously running Solaris 9 with no problems. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: SchilliX-0.2 ready, but SchilliX (the project) needs help
Very valid point. Would be nice if all opensolaris-based distros could guarantee to run unmodified C binaries. There are quite a few ways to achive that. Erast On Tue, 2005-10-25 at 11:22 -0700, John Plocher wrote: Erast Benson and Joerg Schilling were discussing GNU/Solaris: GNU/Solaris distribution uses OpenSolaris kernel and runtime(libc). So, it runs any existing Solaris software without modifications. If you put them into /usr/bin, you will overwrite existing standard UNIX tools This points out some large differences in people's perceptions of what is a Solaris app? One perspective is a minimalist one, concerned with syscalls in libc; another is broader and takes into account the utilities and other commands that are part of the system. Still others focus on middle ware and libraries, Java, web services, etc... That is, runs any existing Solaris Software without modifications is more difficult to do than it is to say. It is safe to say that the ARC process at Sun spends much of its time ensuring that changes to the system don't negatively impact this area. The Solaris Binary Compatibility effort (see appcert(1)) grapples with this issue as well. Going forward with OpenSolaris distros, a simple expectation might be If it runs on Solaris AND it passes appcert(1), then it should also run on any Solaris Compatible system. (Noting that appcert focuses on shared libraries and does not address system()'d or exec()'d utilities...) -John ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: nForce3 NIC-where the heck is it?
Ok, So after the install of last week's Solaris Express, I see that I now have the SUNWnge driver package installed. 'update_drv -a -i pci10de,df nge' now proceeds without error, and the interface can be plumbed and used. However, the configuration does not persist across reboots-I have to manually pull the 'nge pci10de,df' entry from /etc/driver_aliases, and re-add it with update_drv after every reboot. I am most likely missing something obvious and important. On a related note, what is the SolarisX86 equivalent of typing boot -r at the ok prompt on a SPARC system? Thanks for all the good advice, everyone! -GBA This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: SchilliX-0.2 ready, but SchilliX (the project) needs help
[EMAIL PROTECTED] wrote: and some other minor stuff. It is most unlikely that you did never have a look at SchilliX and we all know, that knowing that/how something works makes things a lot easier for people who do it the second time and are not forced to develop everything from scratch as I did. True. But these are just the ideas that you also get by by looking at any of the Linux LiveCDs from a high level. Translating from these ideas into a working self-hosting distro is the real challenge: From a short look at Belenix, it seems that SchilliX is much closer to a self hosting enviroment than Belenix. Everythig provided by SchilliX-0.1 (except the Sun OpenSolaris sources itself) has been compiled on SchilliX-0.1 and even Xorg compiles on SchilliX-0.2. The binaries found on Belenix have been compiled on Solaris 10 instead. * Just looking at a disro does not tell you how the Solaris New Boot works. One needs to understand this in order to create an OpenSolaris distro. How does one figure out the key to getting a rootfs on the ramdisk without knowing Newboot - the fact that ?bootpath? should be absent. The related facts have been discussed with a lot of details on the opensolaris mailing list and it was absolutely no problem for me to set up the boot environment for SchilliX. * How do you find out the cd device node that contains the LiveCD early in the boot when devfsadm has not yet executed ? It took me two iterations to arrive at an optimal solution. First solution was suboptimal till I wrote a small utility using libdevinfo to list the cd nodes and then use fstyp on them to get the volume id. SchilliX provides code to 'search' for the right CD, why didn't you ask? * How do you handle the Math library requirements ? I ported and enhanced the FreeBSD math libary which was more than a week's effort for me. SchilliX did not make the Math library sources available. Having a short look at the (probable) current state of your port of libm shows that you seem to be at approx. the same state as I have been after the first week. The libm you find on SchilliX-0.2 got one month's effort from me. Why did you start your unneeded enterprize? * What files do you include in the miniroot ? Optimise space. It is simple to find out whatyou need for a minimal version, it should not take more than 3 iterations. * What are the correct options to pass to mkisofs to get the desired bootable cd ? As the needed options are documented in detail in the mkisofs man page and the included README's and as even the GRUB documentation includes a chapter on mkisofs it should not take more than 30 minutes to find this out. * How do you handle the inetd failures ? Inetd has a dependency on ksh and it took me several days of hacking to identify that the same functionality exists in /usr/xpg4/bin/sh As I did write many mails on this problem in this mailing list in August, it was easier for you than for me. You had the advantage of not being on vacation after I did the introducing work on the bug. After I did recover from the 4600 mails in my mailbox after I did return from vacation, it took me 2 days to find the problem - you did not send any information on it meanwhile :-( * I had to write the missing sysidtool service manifests and renamed them to sysonfigure. I did the same in May, so you have not been forced to do this. * I had to preconfigure additional open-source drivers like network drivers from Masayuki. Which files should you change to add the drivers by hand ? See SchilliX ;-) SchilliX-0.1 includes all drivers except the one that has been created by Masayuki _after_ I found that SchilliX-0.1 did not work on some emulators and asked him for help. * One can easily configure dhcp on a interface but it is quite involved to write a proper /etc/dhcp/eventhook script that auto-configures DNS and NIS based on whichever is available. Schillix does not yet support this due to lack of time. SchilliX uses a statix intermediate solution that works too. * I have actually picked ideas from KnoppiX like: - Giving user option to select the keyboard layout and subsequently using it for setting XKBLayout in Xorg as well. As the Sun keyboard layout setup is broken, you only have two opportunities: - fix the Sun keyboard setup bugs (as I did) - or implement this select service. - Scanning all block devices and mounting any supported filesystems - recovery feature I am not sure if this is a good idea in special as Belenix does this without asking. I prefer to a boot method that does not touch the hard disk at all. - Using physical swap if a Solaris partition is present on the harddisk How to identify the swap slice ? See above. I don't like this being done without asking me.
Re: [osol-discuss] Re: Re: SchilliX-0.2 ready, but SchilliX (the project) needs help
John Plocher [EMAIL PROTECTED] wrote: If you put them into /usr/bin, you will overwrite existing standard UNIX tools This points out some large differences in people's perceptions of what is a Solaris app? One perspective is a minimalist one, concerned with syscalls in libc; another is broader and takes into account the utilities and other commands that are part of the system. Still others focus on middle ware and libraries, Java, web services, etc... The biggest compatibility problem of OpenSolaris (compared to Sun Solaris) is the fact that libm is not part of OpenSolaris. In case you don't know, it took me a full month already to work on FreeBSD's libm in order to be halfway compatible with Sun Solaris and I am not even shure about the effort that would be needed for a mostly 100% compatibility. I am definitely interested in a UNIX centric OpenSolaris distro. Do not expect people who work on Linux centric Open Solaris distros to put a similar amount of work into compatibility issues. That is, runs any existing Solaris Software without modifications is more difficult to do than it is to say. It is safe to say that the ARC process at Sun spends much of its time ensuring that changes to the system don't negatively impact this area. The Solaris Binary Compatibility effort (see appcert(1)) grapples with this issue as well. I am not sure whether appcert(1) is sufficient to check for the compatibility ussies we will see on typcal OpenSolaris dustros. Going forward with OpenSolaris distros, a simple expectation might be If it runs on Solaris AND it passes appcert(1), then it should also run on any Solaris Compatible system. (Noting that appcert focuses on shared libraries and does not address system()'d or exec()'d utilities...) So judging from above, do you consider libc to be unstable as it calls system()'d or exec()'d utilities to support basic Solaris features like smf? 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] Re: Re: SchilliX-0.2 ready, but SchilliX (the project) needs help
On Tue, 2005-10-25 at 23:10 +0200, Joerg Schilling wrote: John Plocher [EMAIL PROTECTED] wrote: If you put them into /usr/bin, you will overwrite existing standard UNIX tools This points out some large differences in people's perceptions of what is a Solaris app? One perspective is a minimalist one, concerned with syscalls in libc; another is broader and takes into account the utilities and other commands that are part of the system. Still others focus on middle ware and libraries, Java, web services, etc... The biggest compatibility problem of OpenSolaris (compared to Sun Solaris) is the fact that libm is not part of OpenSolaris. In case you don't know, it took me a full month already to work on FreeBSD's libm in order to be halfway compatible with Sun Solaris and I am not even shure about the effort that would be needed for a mostly 100% compatibility. I am definitely interested in a UNIX centric OpenSolaris distro. Do not expect people who work on Linux centric Open Solaris distros to put a similar amount of work into compatibility issues. They will. Simply becase not everything in this world is open-source... Also I do not see big advantages of creating yet another copy of Solaris Express. SchiliX and BeliniX over time will offer thier own features. This will create incompatabilities anyways. We should not expect fully 100% compatability between distros. Compatability to some extent ... yes. This we could achive. We probably might need to create some sort of Solaris Distributions Foundation(SDF) which will control the spec similar to LSB. Erast ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: remote installation of service
ug maaa wawa bop! This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: SchilliX-0.2 ready, but SchilliX (the project) needs help
Erast Benson [EMAIL PROTECTED] wrote: The biggest compatibility problem of OpenSolaris (compared to Sun Solaris) is the fact that libm is not part of OpenSolaris. In case you don't know, it took me a full month already to work on FreeBSD's libm in order to be halfway compatible with Sun Solaris and I am not even shure about the effort that would be needed for a mostly 100% compatibility. I am definitely interested in a UNIX centric OpenSolaris distro. Do not expect people who work on Linux centric Open Solaris distros to put a similar amount of work into compatibility issues. They will. Simply becase not everything in this world is open-source... Then it seems that you have a different background than a typial Debian maintainer. Also I do not see big advantages of creating yet another copy of Solaris Express. SchiliX and BeliniX over time will offer thier own features. This will create incompatabilities anyways. SchilliX does not like to be another Solaris Express. Even now, there is the advantage that SchilliX is freely redistributable. Currently, SchilliX needs to add basic features, later I expect that SchilliX may even include new dirvers and software before Sun Solaris will do it. With respect to Ethernet drivers this is already true thanks to Masayuki Murayama. We should not expect fully 100% compatability between distros. Compatability to some extent ... yes. This we could achive. What we need to define is a basic compatibility set. What Sun People may not yet know is that there cannot be 100% compatibility with Sun Solaris as long as Sun Solaris is not 100% OpenSource. We probably might need to create some sort of Solaris Distributions Foundation(SDF) which will control the spec similar to LSB. We need to define a basic compatibility set and we need to define a way of dealing with incompatibilities that are caused by missing source availability. It seems that we are at the same place as we have been a year agio when I did write my postulates on OpenSolaris that did end with the creation of the CAB. 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] Any progress on non-DEBUG builds?
The news hasn't changed much, I'm afraid. Alan Hargreaves has some changes to support non-debug builds. I haven't had time to finish reviewing them. It's currently #8 on my Todo list, but a couple of the things above it are pretty big, so I don't know when I'll get to it. mike ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Any progress on non-DEBUG builds?
Mike, The news hasn't changed much, I'm afraid. Alan Hargreaves has some changes to support non-debug builds. I haven't had time to finish reviewing them. It's currently #8 on my Todo list, but a couple of the things above it are pretty big, so I don't know when I'll get to it. No worries. Many thanks for the update. Regards... Sean. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: SchilliX-0.2 ready, but SchilliX (the project) needs help
The biggest compatibility problem of OpenSolaris (compared to Sun Solaris) is the fact that libm is not part of OpenSolaris. I agree. And now, there are (at least) two separate attempts to develop a replacement: one by you and one by Moinak for BeleniX. Do you think it makes sense to start a project for this and pool efforts? We could host the development repository on sourceforge. It'd have potential to become the de-facto libm for any OpenSolaris distribution and cut down some of the potential incompatibilities we'll eventually have to grapple with. Venky. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: SchilliX-0.2 ready, but SchilliX (the project) needs help
The roadmap hasn't been updated (I'll look into that), but libm is coming. Source is targeted for January, and in the interim, we hope to get binaries posted this week or next. Hope that helps. Bonnie Venky wrote On 10/25/05 16:40,: The biggest compatibility problem of OpenSolaris (compared to Sun Solaris) is the fact that libm is not part of OpenSolaris. I agree. And now, there are (at least) two separate attempts to develop a replacement: one by you and one by Moinak for BeleniX. Do you think it makes sense to start a project for this and pool efforts? We could host the development repository on sourceforge. It'd have potential to become the de-facto libm for any OpenSolaris distribution and cut down some of the potential incompatibilities we'll eventually have to grapple with. Venky. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: SchilliX-0.2 ready, but SchilliX (the project) needs help
Bonnie Corwin [EMAIL PROTECTED] wrote: The roadmap hasn't been updated (I'll look into that), but libm is coming. Source is targeted for January, and in the interim, we hope to get binaries posted this week or next. I was planning to pubish my libm source soon also (after I had the time for some cleanup ;-) 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] Re: Re: SchilliX-0.2 ready, but SchilliX (the project) needs help
Source is targeted for January, and in the interim, we hope to get binaries posted this week or next. Great! Now that's one less issue to fight about! :) Venky. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] OpenSolaris on Dell OptiPlex GX520?
Heya, On Tue, 2005-10-25 at 18:36 -0700, Philip Machanick wrote: Does anyone have experience of installing and running on a GX520? I have a GX280 handy as well I've found that one mentioned a few times which looks promising, but I would have to move my Linux installation off it and so would prefer to put OpenSolaris on the new machine if I can. My GX280 works like a charm. I'm currently running Solaris 10 FCS on it, and apart from needing to download the external broadcom driver, I didn't have any other problems with it. Obviously don't know about the GX520 though, sorry. Glynn ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: b24 and b25 panic on UltraAXe
Ok, here's a copy of the panic: UltraAXe(UltraSPARC-IIi 300MHz), PS/2 Keyboard OpenBoot 3.14.1 ME , 256 MB memory installed, Serial #16280317. Ethernet address 8:0:20:f8:6a:fd, Host ID: 80f86afd. Unrecognized magic number in media label Can't open disk label package Unrecognized magic number in media label Can't open disk label package Boot device: net File and args: Evaluating: boot Can't open boot device ok boot cdrom Boot device: /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL PROTECTED],0:f File and args: SunOS Release 5.11 Version snv_25 64-bit Copyright 1983-2005 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. WARNING: Failed to process interrupt for kb_ps20 due to down-rev nexus driver 80 420 panic[cpu0]/thread=180e000: kb_ps2[0], kd_attach(): failed ddi_add_intr() 0180b030 kb_ps2:kd_attach+428 (34ac1f8, 7be03c00, 0, 70056400, 0, 7b e05000) %l0-3: 030ea3f0 70057000 018adc00 %l4-7: 018a8400 0026 0025 0009 0180b110 genunix:devi_attach+ac (34ac1f8, 0, 0, 69a0, 0, 7be02fb8) %l0-3: 0185f1d8 01853160 0001 0185f000 %l4-7: 01853000 0820 70056628 0001 0180b1e0 genunix:attach_node+9c (34ac1f8, 1, 0, 34ac260, 1853400 , 4) %l0-3: 0001 0001 03074f80 03074f30 %l4-7: 8ffa8000 7be013b8 0180b290 genunix:i_ndi_config_node+100 (34ac1f8, 10bba80, 10, 10bb80 0, 0, 3) %l0-3: 0001 0006 01853420 %l4-7: 01853400 0004 0110 0180b340 genunix:i_ddi_attachchild+48 (34ac1f8, , 0, 34ac5c8, 0, 0) %l0-3: 0180b3e8 0180b3e0 %l4-7: 03a3b000 0100 030ea400 0180b400 genunix:devi_attach_node+88 (34ac1f8, 4080, 30e8c47, 30 0004ac260, 4080, 0) %l0-3: 034ac630 %l4-7: 0183cb28 0100 0180b4b0 genunix:devi_config_one+234 (34ac5c8, 40, 180b6e8, fffd, 0, 34ac1f8) %l0-3: 4080 034ac71c %l4-7: 034ac630 0030 030e8c47 030e8c47 0180b580 genunix:ndi_devi_config_one+c8 (34ac5c8, 30e8c40, 180b6 e8, , 30e9048, 11d6c00) %l0-3: 01004000 4080 000c %l4-7: 70055dc0 70055ea0 0004 0180b630 genunix:resolve_pathname+158 (4080, 0, 180b7d8, 0, 0, 100) %l0-3: 030e8c40 0180b6f0 034ac5c8 030e9040 %l4-7: 4000 0180b6e8 0180b718 0180b720 genunix:ddi_pathname_to_dev_t+10 (1820b68, 13f7000, 0, 3a67 b80, 13f7000, 13f7000) %l0-3: 013f7400 7c00 7400 01853160 %l4-7: 01853000 0185f1d8 013f7400 013fe1a4 0180b7e0 consconfig_dacf:consconfig_load_drivers+14 (30c9888, 180e00 0, 18ab000, 7400, 7000, 7000) %l0-3: 018b0400 7000 018a4800 01857000 %l4-7: 01857000 013f7400 0180b890 consconfig_dacf:dynamic_console_config+6c (18a4800, 5ada64, 300 000c9888, 1857000, 1857000, 1857000) %l0-3: 0013 037228c8 018ab400 %l4-7: 018ab000 018ab400 018ab000 018ab000 0180b940 unix:stubs_common_code+70 (183c9a6d42, 5ada64, 35576c6c, 0, bf3 00, 0) %l0-3: 0180b209 0180b2e1 1f00 %l4-7: 01817150 018aac00 018adc00 0180ba10 genunix:main+12c (2, 1013000, 1835cc0, 18aba10, 18ab800, 1813c0 0) %l0-3: 01819400 70002000 01813c00 018aac00 %l4-7: 018aac00 0180c000 0180c000 018aac00 syncing file systems... done skipping system dump - no dump device configured rebooting... Resetting ... On 10/25/05, Jason W [EMAIL PROTECTED] wrote: I got panics booting from the b24 and b25 CDs on my UltraAXe. It gets as far as the banner and the little spinning line and then barfs on the screen. I haven't had a chance yet to do it over a serial console to capture the data, but wanted to check if anyone else had a UltraAXe that was working correctly. This system was previously running Solaris 9 with no problems. UltraAXe(UltraSPARC-IIi
