I think they use 'pungi' to spin the iso images if memory serves. Cool tool. Didn't know about the package-cleanup script, thanks. My manual procedure is relatively similar except I do it in VMware making liberal use of snapshots in case I get a bit aggressive carving it to pieces. Basic hand-carving procedure has been posted to the web and some Linux mags in a variety of forms over the years: - remove locale, i18n, zoneinfo, gconv - remove man, doc, info and the like - remove extra kernel modules - remove the rpmdb - disable selinux then remove its policy data - leave just a minimal terminfo - strip --strip-debug all libs In years past I could easily get rh9 into an initrd that was about 45MB in size in ramdisk when running even with lots of extra stuff in there. I seem to remember taking rh72 down to 27MB or so way back when for a firewall/router type box. My current FC4 (not bare minimum, about 150 rpms) is ballpark 150MB footprint. So far I have FC6 at about 210 MB on disk hand-stripped ala above, but I have lots of rpms to go. I'll take Jesse's rpm list, build something with the FC6 versions, and then hand-strip it down just to see how small it can gets before+after for comparison. Thanks for the pointers. ------ vince.skahan@xxxxxxxxxx ------ -----Original Message----- From: seth vidal [mailto:skvidal@xxxxxxxxxxxxxx] Sent: Monday, July 30, 2007 3:49 PM To: ross.cameron@xxxxxxxxxxxxxx; Yellowdog Updater,Modified Subject: Re: RE: yum compatibility backward with rpm On Tue, 2007-07-31 at 00:53 +0200, Ross Cameron wrote: > I think half the problem is,... YUM was designed to do exactly the > things you're asking it not to do. > > Whilst its always possible to extend YUM to do what you want,... the > question needs to be raised is,... is all the additional maintenance > etc. going to be carried on once someone writes the addon? > Its a feature set completely contrary to the design and global > implimentation of the program. And not impossible to be removed at a > later day leaving you high and dry again,... > > How do the guys at the Fedora project knock out their 500-odd MB > server version I think is more the Q,... cause Im sure they must run > into these same issues. Here's how I do it. Install a box via kickstart that does not have anything in %packages boot it. install yum-utils - specifically for the package-cleanup script run: package-cleanup --leaves --all that's a list of all the packages upon which nothing else depends. - sift that list and remove all the stuff you don't think you need - run it again - sift it again - run it again - sift it again yum list installed see how many pkgs are there and make sure there's nothing in there (that something else may depend on) that you know you don't need. This is what Jesse Keating got Fedora7/Rawhide down to: http://jkeating.fedorapeople.org/107rpms -sv _______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxxxxx https://lists.dulug.duke.edu/mailman/listinfo/yum _______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxxxxx https://lists.dulug.duke.edu/mailman/listinfo/yum
