Hi Jonathan,
> 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? > > If you take a look at the ips repo, hg.opensolaris.org/hg/onnv/onnv-gate, under src/util/distro-import/common. What you will see in this directory are the ips pkg definitions that are used when creating an ips repo. They are pretty self explanatory in that they import a SVR4 package, or parts of an SVR4 package or multiple packages to complete the ips definition of a pkg. > 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, if you use this code it will do the import of the SVR in to IPS for the builds listed in the gate/src/util/distro-import directory. > 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? > > Right now we are only creating x86 images so we aren't tracking the files per platform. As for how we might do this I will leave this to the DC team to respond. Regards, sarah **** > --- > .je > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss > >
