Re: [osol-discuss] Re: Re: Re: Re: OpenSolaris - Why should I care?
OpenBSD also supports numerous crypto cards and the crypto instructions on VIA CPUs. And OpenBSD i sn't locked into 10 year old technology. New security features are being developed and integrated a ll the time. In Solaris 10 we've added the kernel crypto framework which allows us to plug in crypto hardware providers without making changes to all consumers. It is true that we do not (yet) provide modules for the VIA boards (But since I recently acquired one, that might change) I'm not sure what you mean by being locked into 10 year old technology? Solaris also supports many of the same security features that OpenBSD touts, but takes them to the next level. Zones is not just about making one server into many. Each zone is a walled off area that is independent of the others, it takes chroot jails to a whole new level. But services aren't zoned by default. OpenBSD privseps and jails as much as possible by default. Solaris does run quite a few daemons with as few privileges as possible and also separates the privileged and unpriivlege part from sshd. Casper ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: OpenSolaris - Why should I care? More questions.
1. What are the resource requirements for all this wonderful Solaris 10 software to work and perform reasonably well? Is it all available for x86 systems? Does it require a 64-bit dual or quad processor system, 4 GB of RAM and a 200 GB HDD? Or would it all work on a 1.8 GHz Intel Celeron single processor system with 512 MB of RAM? E.g. is the power of the zones technology fully available on such a low-powered desktop system? Yes. It's all fully available on low powered systems. (Even a VIA C3 CPU with 512 MB of ram works just fine, even as Sun RAY server; boot Solaris from flash too, if that's your thing) 2. And what about documentation? Are good tutorials available for Solaris newbies covering the unique aspects of Solaris 10, or do you have to be a long time, seasoned Solaris sys admin to catch on to these Solaris esoterica? I found the Sun Solaris 10 User's Guides and Sys Admin Guides to be pretty dense on these subjects. Much more accessible information can be found on blogs.sun.com; many engineers write accessible how-tos about the stuff they themselves build. 3. So far the discussion has only been about Solaris 10 or OpenSolaris. What about new distros such as Nexenta and BeleniX that retain only the Solaris kernel and core libraries? Pure Solaris is renowned for its stability; part of the reason presumably is the fact that Sun Q/A applies to every single aspect of the entire OS. Does this quality and stability necessarily carry over into a hybrid OS with Solaris kernel and GNU utilities, applications, etc.? Potentially such an OS could be incredibly buggy and unstable, completely negating the advantages of a very stable Solaris kernel, couldn't it? Can such a hybrid indeed be made as stable as Solaris itself? The GNU utilities carry both a stability and compatibility risk. Nothing in Solaris proper can fix that. Casper ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: OpenSolaris - Why should I care? More questions.
On Sun, 2005-11-27 at 11:11 +0100, [EMAIL PROTECTED] wrote: 3. So far the discussion has only been about Solaris 10 or OpenSolaris. What about new distros such as Nexenta and BeleniX that retain only the Solaris kernel and core libraries? Pure Solaris is renowned for its stability; part of the reason presumably is the fact that Sun Q/A applies to every single aspect of the entire OS. Does this quality and stability necessarily carry over into a hybrid OS with Solaris kernel and GNU utilities, applications, etc.? Potentially such an OS could be incredibly buggy and unstable, completely negating the advantages of a very stable Solaris kernel, couldn't it? Can such a hybrid indeed be made as stable as Solaris itself? The GNU utilities carry both a stability and compatibility risk. Nothing in Solaris proper can fix that. This statement true for any software in general, unless development is pretty much dead. :-) Solaris 8,9,10,11 are different, and therefore carry the same risk for end user's apps. Talking about Nexenta and Others: once distro reaches major release, i will be stabilized(i.e. no major changes) and supported for a longer periods of time. And in fact, GNU utilities rock stable and pretty compatible across the versions and platforms. So, I woudn't buy your statement.. Erast ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: OpenSolaris - Why should I care? More questions.
On Nov 27, 2005, at 11:11 AM, [EMAIL PROTECTED] wrote: 1. What are the resource requirements for all this wonderful Solaris 10 software to work and perform reasonably well? Is it all available for x86 systems? Does it require a 64-bit dual or quad processor system, 4 GB of RAM and a 200 GB HDD? Or would it all work on a 1.8 GHz Intel Celeron single processor system with 512 MB of RAM? E.g. is the power of the zones technology fully available on such a low-powered desktop system? Yes. It's all fully available on low powered systems. (Even a VIA C3 CPU with 512 MB of ram works just fine, even as Sun RAY server; boot Solaris from flash too, if that's your thing) Neat. Does it work on the PLE133 chipset? 2. And what about documentation? Are good tutorials available for Solaris newbies covering the unique aspects of Solaris 10, or do you have to be a long time, seasoned Solaris sys admin to catch on to these Solaris esoterica? I found the Sun Solaris 10 User's Guides and Sys Admin Guides to be pretty dense on these subjects. Much more accessible information can be found on blogs.sun.com; many engineers write accessible how-tos about the stuff they themselves build. IF you can find what you are looking for. It's hopeless to find the things you are looking for and the search facility doesn't help much. Example: there was mentioned an easy guide to live upgrade at someone's blog in this maillist, and I have accidently deleted that particular mail. I tried finding it via the search engine at Sun's blogsite, but gave up after checking at least 20 different blog entries (out of 296). How am I supposed to find what I'm looking for??? Kaiser Jasse -- Authorized Stealth Oracle The axioms of wisdom: 1. You can't outstubborn a cat 2. You can't conquer the universe without the knowledge of FORTRAN 3. In the Unix realm, 10% of work fixes 90% of the problems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: OpenSolaris - Why should I care? More questions.
The GNU utilities carry both a stability and compatibility risk. Nothing in Solaris proper can fix that. This statement true for any software in general, unless development is pretty much dead. :-) Perhaps I should have quantified that: when used as default in a Solaris environment.. The GNU utilities are not compatible with their Solaris equavalents and in some cases violate standards, best practices or have bugs which their authors refuse to fix. Solaris 8,9,10,11 are different, and therefore carry the same risk for end user's apps. No, they do not, certainly not to the same extend as OpenSolaris + GNU utilities does when compared to standard Solaris. Talking about Nexenta and Others: once distro reaches major release, i will be stabilized(i.e. no major changes) and supported for a longer periods of time. And in fact, GNU utilities rock stable and pretty compatible across the versions and platforms. So, I woudn't buy your statement.. Except for GNU find and GNU tar which are buggy and are known to be buggy to the point that we can only assume that their maintainers have no interest in fixing them. Casper ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Fwd: Re: OpenSolaris - Why should I care? More questions.
James Dickens [EMAIL PROTECTED] wrote: Solaris Express is the beta version of the next release of Solaris Solaris Express Community build is the absolute latest public release, current draw to this version is that it has ZFS in it. Source Only: ( has to be installed on top of Solaris Express) OpenSolaris is the opensource version of Solaris Express Community build. The last statement is a myth. Check out SchilliX (first version came out 3 days after the first OpenSolaris release) to verify that you don't need Solaris Express. 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: Re: Re: OpenSolaris - Why should I care?
Jake Maciejewski [EMAIL PROTECTED] wrote: But you already claimed OpenBSD has unacceptable limitations for the desktop that Solaris doesn''t have. BTW Solaris has roots in a 30 year old technology not 10. Having said this Solaris is far more modern than that in just about everything, and with OpenSolaris now, is Solaris locked into technology any more than OpenBSD ? I'm not advocating OpenBSD for the desktop. And if you want to talk about roots, OpenBSD has its roots in NetBSD which has its roots in BSD. Solaris from what I know has its roots in the merging of BSD derived SunOS with SVR4 because SVR4 was more advanced at the time. Whereas Solaris got refreshed with the more advanced codebase, OpenBSD enjoys the benefits of a complete security audit to eliminate vulnerabilities from the old BSD days when security wasn't much of a concern. I admit that Solaris is more scalable (OpenBSD often performs worse with SMP enabled, for example) and possibly more stable, but that's because the developers care more about security. Looks like you forgot that Svr4 was derived from SunOS and SVr3... 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: OpenSolaris - Why should I care? More questions.
Erast Benson [EMAIL PROTECTED] wrote: And in fact, GNU utilities rock stable and pretty compatible across the versions and platforms. So, I woudn't buy your statement.. Internal staibility isn't worh anything as long as programs like e.g. GNU tar exist that cause major compatibility issues because they did ignore standards until very recently. 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: OpenSolaris - Why should I care? More questions.
[EMAIL PROTECTED] wrote: And in fact, GNU utilities rock stable and pretty compatible across the versions and platforms. So, I woudn't buy your statement.. Except for GNU find and GNU tar which are buggy and are known to be buggy to the point that we can only assume that their maintainers have no interest in fixing them. Add GNU rm it includes an option that allows you to unlink non-empty directories as root. This is a feature that POSIX did put with care into a separate utility called unlink. So GNU rm includes an unneeded security risk if you make a typo. 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: OpenSolaris - Why should I care? More questions.
Yes. It's all fully available on low powered systems. (Even a VIA C3 CPU with 512 MB of ram works just fine, even as Sun RAY server; boot Solaris from flash too, if that's your thing) Neat. Does it work on the PLE133 chipset? I think I actually have an old ASUS PC with a similar chipset which works fine (CUV4X). I don't see any reason why it would not work. The board I have is a CLE266, though (USB, audio, integrated graphics are all supported but the latter better in Xorg 6.9 which will be in build 28, I think; build 28 will be later because of thanks giving. IF you can find what you are looking for. It's hopeless to find the things you are looking for and the search facility doesn't help much. Unfortunately, that is often the case. Example: there was mentioned an easy guide to live upgrade at someone's blog in this maillist, and I have accidently deleted that particular mail. I tried finding it via the search engine at Sun's blogsite, but gave up after checking at least 20 different blog entries (out of 296). How am I supposed to find what I'm looking for??? Well, if you can't find it you can always ask. Casper ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Re: Re: Re: Is 'forking' inevitable here too?
True, although to be fair one might say that the fact that the automounter make home directories appear in /home is an implementation detail. Don't get me wrong: I think that disabling the automounter and using /home directly (rathen than automounting $NFS_SERVER:/export/home) is wrong in all but the smallest of environments. I know, I know... well, you and I have almost always seen eye to eye on these issues. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Re: Re: Is 'forking' inevitable here too?
Is worshiping unix required for using solaris? Absolutely. As a bonus, you get to really enjoy it. What [b]exactly[/b] is wrong with having users in /home? It seems you're angry that Linux is more used, isn't it? Oh, I'm absolutely, positively, and without a doubt angry that I have to deal with total and complete amateurs every day who think that they know how things should be done, and who think that Linux, a severly broken, UNIX wannabe hack is the way to go. You don't even want to get me started on that, so let's drop that part of the discussion and move right along. As for /home, that's the mount point onto which the AutoMounter mounts users' home directories. You see, in any environment where you have more than one PC-bucket, you'll probably want to implement a central file server, usually with some sort of a big RAID, that, among other things, will serve up your users' home directories. Sun, as the inventor of NFS, has defined /export/home/ as a point from which resources are exported. So instead of trying to figure out which server to mount to and where, with the AutoMounter it's a uniform location, namely /home. This in turn makes it consistent across multiple systems and your files are always remotely mounted on the same mount point (/home). It was designed this way to abstract the physical location. Point in case: if you set up the AutoMounter on the very system that your home directory is on, the AutoMounter will simply NFS loopback-mount /export/home under /home (in a somewhat complex way, but this is abstracted from you as the user). Now, going back to what is wrong, the fact of life is that most Linux users have one or two disparate systems at home, and usually maintain either dual boot, or separate home accounts on each server. Most don't even know there is such a thing as the AutoMounter facility, so to these people it would appear that the logical place to put their home directories is, in fact, /home. This is of course misleading, but you go and try to explain that to someone with an almost religious fervor toward Linux. I think you'd get angry too. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: OpenSolaris - Why should I care? More questions.
On 11/27/05, Joerg Schilling [EMAIL PROTECTED] wrote: Add GNU rm it includes an option that allows you to unlink non-empty directories as root. This is a feature that POSIX did put with care into a separate utility called unlink. So GNU rm includes an unneeded security risk if you make a typo. Why would someone want to unlink a non-empty directory? -- Eric Enright ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: OpenSolaris - Why should I care? More questions.
Eric Enright [EMAIL PROTECTED] wrote: On 11/27/05, Joerg Schilling [EMAIL PROTECTED] wrote: Add GNU rm it includes an option that allows you to unlink non-empty directories as root. This is a feature that POSIX did put with care into a separate utility called unlink. So GNU rm includes an unneeded security risk if you make a typo. Why would someone want to unlink a non-empty directory? One reason may be to remove a hard link to another existing directory. 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: OpenSolaris - Why should I care? More questions.
On Sun, 27 Nov 2005, Erast Benson wrote: Solaris 8,9,10,11 are different, and therefore carry the same risk for end user's apps. You're forgetting a rather important detail: Sun places a big emphasis on backwards compatibility, so migrating to newer versions of Solaris carries much less risk than migrating to a new version of Linux. Linus has specifically stated that not only is backwards compatibilty not a requirement for him, but that he (and the other Linux developers) will deliberately break compatibility with previous releases to discourage binary-only software. Because of this policy, how long do you think it will be before companies like Nvidia take a look at their Linux vs Solaris maintenance costs, and decide to srop support for the former as a cost saving measure? -- Rich Teer, SCNA, SCSA, OpenSolaris CAB member President, Rite Online Inc. Voice: +1 (250) 979-1638 URL: http://www.rite-group.com/rich ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: OpenSolaris - Why should I care? More questions.
...and Solaris has had multi-threaded applications running for years. If it is not fast enough, add more CPUs! Solaris scales and by respecting APIs (thanks for mentioning that Rich) developers save time ...as time goes by. RB :-) On Nov 27, 2005, at 1:10 PM, Rich Teer wrote: On Sun, 27 Nov 2005, Erast Benson wrote: Solaris 8,9,10,11 are different, and therefore carry the same risk for end user's apps. You're forgetting a rather important detail: Sun places a big emphasis on backwards compatibility, so migrating to newer versions of Solaris carries much less risk than migrating to a new version of Linux. Linus has specifically stated that not only is backwards compatibilty not a requirement for him, but that he (and the other Linux developers) will deliberately break compatibility with previous releases to discourage binary-only software. Because of this policy, how long do you think it will be before companies like Nvidia take a look at their Linux vs Solaris maintenance costs, and decide to srop support for the former as a cost saving measure? -- Rich Teer, SCNA, SCSA, OpenSolaris CAB member President, Rite Online Inc. Voice: +1 (250) 979-1638 URL: http://www.rite-group.com/rich ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: OpenSolaris - Why should I care? More questions.
On Sun, 2005-11-27 at 12:44 +0100, [EMAIL PROTECTED] wrote: The GNU utilities carry both a stability and compatibility risk. Nothing in Solaris proper can fix that. This statement true for any software in general, unless development is pretty much dead. :-) Perhaps I should have quantified that: when used as default in a Solaris environment.. The GNU utilities are not compatible with their Solaris equavalent and in some cases violate standards, best practices or have bugs which their authors refuse to fix. don't you agree that any software has some bugs anyways? I'd say this is part of software industry. violate standards sounds very funny to me. Microsoft violates standards all over, still everybody using it. But my point is: GNU tools are slightly incompatible with SUN tools. But because GNU tools has x1000 times wider usage, I think, this is SUN tools which are violates GNU standards. :-) Guys, this GNU vs. SUN tools discussion leading to nowhere. Decent OpenSolaris-based distro must support both. One way or another. Erast ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: OpenSolaris - Why should I care? More questions.
On Sun, 2005-11-27 at 11:10 -0800, Rich Teer wrote: On Sun, 27 Nov 2005, Erast Benson wrote: Solaris 8,9,10,11 are different, and therefore carry the same risk for end user's apps. You're forgetting a rather important detail: Sun places a big emphasis on backwards compatibility, so migrating to newer versions of Solaris carries much less risk than migrating to a new version of Linux. Linus has specifically stated that not only is backwards compatibilty not a requirement for him, but that he (and the other Linux developers) will deliberately break compatibility with previous releases to discourage binary-only software. Because of this policy, how long do you think it will be before companies like Nvidia take a look at their Linux vs Solaris maintenance costs, and decide to srop support for the former as a cost saving measure? Hey, I do not disagree. :-) This is the reason why we started Nexenta OS development after all. And btw, Nexenta OS is as stable at its core as Solaris. Nexenta OS as compatible (core userland and kernel) with Solaris as SchiliX. Moreover, we are working on the solution which will allow users to switch personalities dynamically. So, if someone wants pure Solaris-like behavior, it is going to be very easy possible. Erast ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Re: Re: Is 'forking' inevitable here too?
As for /home, that's the mount point onto which the AutoMounter mounts users' home directories. You see, in any environment where you have more than one PC-bucket, you'll probably want to implement a central file server, usually with some sort of a big RAID, that, among other things, will serve up your users' home directories. Sun, as the inventor of NFS, has defined /export/ and /export/home/ as the points from which resources are shared (exported). So instead of trying to figure out which server to mount to and where, with the AutoMounter it's a uniform location, namely /home. This in turn makes it consistent across multiple systems and your files are always remotely mounted on the same mount point (/home). It was designed this way to abstract the physical location. Point in case: if you set up the AutoMounter on the very system that your home directory is on, the AutoMounter will simply NFS loopback-mount /export/home under /home (in a somewhat complex way, but this is abstracted from you as the user). I understand that. What I don't understand is why have loopback-mounted directories when you login directly to computer and when you're using shared /home, why not export /home directly. Anyway, let's say it's a tradition. There is no need to argue about it. Did you happen to read my previous post with a recount of the /proc classic? I'll take a look. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: Is it able to write self-defined data to VFS's vnode or UFS's inode?
I want to make a kernel module to do something. In this module, I will redirect syscalls. After my open syscall, I want to add some self-defined data to some files. User programs know nothing about this. What shall I do? I have read information about openat(2), but I do not know what can I learn from openat(2). Would you show me some details? Thank you very much! This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Is it able to write self-defined data to VFS's vnode or UFS's inode?
On Sun, 2005-11-27 at 20:12, nice wrote: I want to make a kernel module to do something. In this module, I will redirect syscalls. After my open syscall, I want to add some self-defined data to some files. User programs know nothing about this. What shall I do? Ask Sony. I hear they've learned a few things about rootkits lately. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How to create /var/sadm/* info for OpenSolaris
On Thu, Nov 24, 2005 at 02:23:35PM +, Darren J Moffat wrote: On Wed, 2005-11-23 at 12:39, Joerg Schilling wrote: Hi, if I like to create a SchilliX that is able to deal with Blastwave packages, I would need to populate the SUNW* related package database for a SchilliX installation. Is there a simple way to do this without really running pkgadd? Or is there a way to create complete SUNW* packages from the ON sourcetree and then run pkgadd -R root-path for the SchilliX template directory? The -p flag to nightly(1) creates package for everything in the ON gate that is shipped - NOTE what ends up in the proto area and what gets bfu'd on to your machine is a superset of that. The package definition files are in $SRC/pkgdefs, you should be able to run make install in subdirs in there to build specific packages. That's not quite correct; the BFU archives and the packages contain the *same* subset of the proto area. You do get more than in a full installation, though, since some of the packages aren't delivered into Solaris. (That's one of the side-effects of cpiotranslate, which fixes up the owner/group data to match the packages -- it also removes files that aren't in any package) Cheers, - jonathan -- Jonathan Adams, Solaris Kernel Development ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Issues when upgrade from Solaris 8 to 9
Can someone please help me on this . Issue 1: As per the Live Upgrade documentation, the -s option with - allows the alternate boot environment to be created without being cloned from another system. The use of this option is for a flash archive installation (which is what we use). Unfortunately this option does not work. After the lucreate is complete the new BE is not marked as complete, as such many follow on commands will not work. For instance, issuing an lustatus for the new BE results in a failure; however issuing an lustatus without any BEs specified works fine. Also attempting to luupgrade the new BE with the flash archive fails. The logs are as below: $ /usr/sbin/lucreate -s - -m /:/dev/dsk/c2t0d0s0:ufs -m /opt:/dev/dsk/c2t0d0s1:ufs -m /var:/dev/dsk/c2t0d0s3:ufs -m /opt/LC/dfms:/dev/dsk/c2t0d0s4:ufs -m /opt/oracle:/dev/dsk/c2t0d0s5:ufs -m /opt/oracle/backup:/dev/dsk/c2t0d0s6:ufs -m -:/dev/dsk/c2t0d0s7:swap -n Side1 Please wait while your system configuration is determined. Determining what file systems should be in the new BE. Searching /dev for possible BE filesystem devices Please wait while the configuration files are updated. Creation of Boot Environment Side1 successful. $ lustatus BE_name Complete Active ActiveOnReboot CopyStatus Side2 yes yes yes - Side1 nono no ACTIVE $ lustatus Side1 ERROR: The Boot Environment Side1 is not Complete. ERROR: Unable to retrieve configuration of boot environment Side1. USAGE: lustatus [-l error_log] [-o outfile] ( [-n] BE_name ) WARNING: The BE_name should be enclosed in double quotes. $ lustatus ?Side1? ERROR: The Boot Environment Side1 is not Complete. ERROR: Unable to retrieve configuration of boot environment Side1. USAGE: lustatus [-l error_log] [-o outfile] ( [-n] BE_name ) WARNING: The BE_name should be enclosed in double quotes. $ /usr/sbin/lufslist Side1 ERROR: The Boot Environment Side1 is not Complete. ERROR: Unable to retrieve configuration of boot environment Side1. USAGE: lufslist [-l error_log] [-o outfile] ( [-n] BE_name ) WARNING: The BE_name should be enclosed in double quotes. $ cat /etc/lutab 1:Side2:C:0 1:/:/dev/dsk/c2t1d0s0:1 2:Side1:NC:0 2:/:/dev/dsk/c2t0d0s0:1 Note that Side1 is not complete (i.e. NC) according to /etc/lutab. $ /usr/sbin/luupgrade -f -n Side1 -s /deploy/jumpstart/OS/Solaris_9_2005-09/ -a /deploy/jumpstart/FlashArchives/system.flar INFORMATION: Removing invalid lock file. Validating the contents of the media /deploy/jumpstart/OS/Solaris_9_2005-09/. The media is a standard Solaris media. Validating the contents of the miniroot /deploy/jumpstart/OS/Solaris_9_2005-09//Solaris_9/Tools/Boot. Constructing flash profile template to use. Locating the flash install program. Checking for existence of previously scheduled Live Upgrade requests. Creating flash profile for BE Side1. Performing the operating system flash install of the BE Side1. CAUTION: Interrupting this process may leave the boot environment unstable or unbootable. The operating system flash install completed. Making the ABE bootable. Updating ABE's /etc/vfstab file. ludo: WARNING: Merged filesystem /deploy and Merge point / have different options - and logging. The update of the vfstab file on the ABE succeeded. Updating ABE's /etc/mnttab file. The update of the mnttab file on the ABE succeeded. Updating ABE's /etc/dumpadm.conf file. The update of the dumpadm.conf file on the ABE succeeded. Updating partition ID tag on boot environment Side1 device /dev/rdsk/c2t0d0s2 to be root slice. Updating boot loader for SUNW,UltraAX-i2 on boot environment Side1 device /dev/dsk/c2t0d0s0 to match OS release. Making the ABE Side1 bootable succeeded. The Live Flash Install of the BE Side1 completed. $ lustatus Side1 BE_name Complete Active ActiveOnReboot CopyStatus Side1 yes no no - $ lufslist Side1 BE name: Side1 Filesystemfstype size(Mb) Mounted on -- /dev/dsk/c2t0d0s7 swap 2500.00 - /dev/dsk/c2t0d0s0 ufs 6000.00 / /dev/dsk/c2t0d0s1 ufs 8000.00 /opt /dev/dsk/c2t0d0s4 ufs 1.00 /opt/LC/dfms /dev/dsk/c2t0d0s5 ufs 14000.00 /opt/oracle /dev/dsk/c2t0d0s6 ufs 13000.00 /opt/oracle/backup /dev/dsk/c2t0d0s3 ufs 16000.00 /var $ cat ICF.2 Side1:-:/dev/dsk/c2t0d0s7:swap:512 Side1:/:/dev/dsk/c2t0d0s0:ufs:12288000 Side1:/opt:/dev/dsk/c2t0d0s1:ufs:16384000 Side1:/opt/LC/dfms:/dev/dsk/c2t0d0s4:ufs:2048
