On Sun, 2006-06-25 at 11:26 +0000, Glynn Foster wrote: > Hey, > > Shawn Walker wrote: > > <i>What you can do, though, and this is how we build JDS, is > > using a chroot environment. It also makes the build environment > > more controlled and easy to reinstall.</i> > > > > Couldn't a zone be used instead of a chroot environment, or am I dreaming? > > > > Is there documentation somewhere on how this chroot environment is setup, > > and exactly how JDS builds are performed using this chroot environment? > > Better still, there's some scripts - > > http://mail.opensolaris.org/pipermail/desktop-discuss/2006-March/000625.html
Not the most user friendly or the best documented scripts on this planet, but replacement scripts are 85% done. The new scripts use smf to mount the loopback directories on system boot and has config files, interactive installation, etc... Just need to finish the remaining 15%... I had spent some time investigating whether we could use zones, but I don't think we can. First of all, this RFE would have to be fixed: 4963323 RFE: zonecfg/zoneadm should support a way to exclude packages Otherwise your global zone cannot have any of the JDS packages installed. Which is pretty difficult when JDS needs newer libxml2 than what's in Nevada (not the case right now). Another issue is that procedural scripts behave differently in zones. Damien has been working with WOS RE on fixing a postinstall script since Sept 2005. The script creates a couple of symlinks. The original script was 10 lines long, the most recent one is 335 and may still have issues. Laca
