Is using buildinstall appropriate if you are planning to change what modules are available at install time? So if I had a generic NIC card that had a linux driver, but it wasn't part of the install set, I could change the install set to include it? Mike From: rpjday <rpjday@xxxxxxxxxxxxxx> To: kickstart list <kickstart-list@xxxxxxxxxx> Subject: Re: simple buildinstall question Send reply to: kickstart-list@xxxxxxxxxx <mailto:kickstart-list-request@xxxxxxxxxx?subject=subscribe> <mailto:kickstart-list-request@xxxxxxxxxx?subject=unsubscribe> Date sent: Mon, 26 Nov 2001 16:20:23 -0500 (EST) > On Mon, 26 Nov 2001, Matilainen Panu wrote: > > > On Mon, 26 Nov 2001, ext rpjday wrote: > > > > > > > > now that i'm going to figure out how buildinstall works, one > > > really > > > trivial question -- what's it for? i've already figured out what > > > splitdistro is all about, but what's the purpose of buildinstall, > > > in ten words or less? thanks. this is getting more complicated > > > by the minute. > > > > Buildinstall builds the installer :) You point it to the distro's > > RPM directory and from the various packages in there (anaconda, X, > > kernel-BOOT...) it creates all the disk and *std.img images the > > installer uses. > > i suspected as much, as i've been poking around in the code, amusing > myself. this leads to another question -- even if i change the set of > RPMS under RedHat/RPMS, and come up with an updated comps file, and > run "genhdlist" to rebuild the hdlist and hdlist2 files, is it > necessary to run buildinstall to rebuild the .img files? > > it would seem that the .img files under RedHat/base are built solely > to support the install process. as long as you're not changing > anything related to the install itself, is there any reason not to > stick with the original .img files that are already there? > > rday > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/kickstart-list Michael Barsalou barjunk@xxxxxxxxxxxxx
