I see Sarah provided some answers, but a few things to add: Jonathan Edwards wrote: > On Mar 13, 2008, at 10:36 AM, Dave Miner wrote: >> Jonathan Edwards wrote: >>> hacking around the the livemedia kit i'm noticing that >>> mkbootcd.files.minimal seems to be woefully out of date from the >>> most recent sxde (nv79) or nevada (nv84/nv85) .. am in the process >>> of cleaning this up, but i'm wondering on some of the rhyme or >>> reason behind some of the files that are determined to be >>> minimal .. is this being tracked by caiman or kept somewhere >>> centrally so that we can all reference minimal requirements to >>> keep boot images small? >> It's not been maintained the past 6 months because we've turned our >> attention to the Distribution Constructor work that's part of >> Caiman. It does similar things, but in a different way. As you've >> seen, maintaining that list is way too much work for a product. > > okay - the caiman distro constructor appears to be based on the new > and fancy IPS package infrastructure .. but how are these packages > maintained (pkg.opensolaris.org i see), and how do they map to the > SUNWC metaclusters in the clustertocs on the various distributions? >
They don't map. The metaclusters used in Solaris are a particular combination of packages, most of which appear in OpenSolaris, but some of which don't, because they don't meet the criteria for inclusion in the OpenSolaris distro. > in other words - if i wanted to build a live distribution based off a > particular nevada build - who tracks the minimal required packages for > an install .. in the past we'd use SUNWCreq and add metaclusters on > top .. has somebody taken on an SVR4 -> IPS translator yet? > Yes, there's a translator for packages which Sarah pointed you two, but again, it's not based on the Solaris metaclusters, which are a construct of that distribution. Instead it's based on how we've defined the live CD and repository contents for the OpenSolaris distribution. > fwiw - i just took to hacking up build_live_dvd to have proc_toc.pl > process multiple metaclusters before it tsorts them, and redid most of > the microroot creation for a project i'm working on .. in the distro > constructor it looks like we've got a new microroot defined and are > now creating compressed images for /etc /var as well as /opt and /usr > which is nice .. how do we plan to deal with /lib /kernel and / > platform? and how are we tracking necessary files for the microroot > across distributions? That part is still being designed as part of the Distribution Constructor and Slim Install work. Dave
