[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: simple buildinstall question
- From: Matilainen Panu <panu matilainen nokia com>
- To: kickstart list <kickstart-list redhat com>
- Subject: Re: simple buildinstall question
- Date: Tue, 27 Nov 2001 00:50:03 +0200 (EET)
On Mon, 26 Nov 2001, ext rpjday wrote:
> 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?
That's right - all the buildinstall generated stuff is install-time only,
with the exception of rescue.img. So only if you want to change anaconda,
the boot-time kernel, XFree version used in the install or so you need to
run it.
- Panu -
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]