[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Kickstart with updated images



> There were some problems with the initial RedHat 6.0 boot images
> that were fixed in an update.  I'm not sure if and how to use the
> "supp" and "modules" disks from that when using kickstart.

I had the same problem some time ago and found the solution:
When installing through nfs (which we do through kickstart),
some bin and libs are used from the server:
(...)RedHat/instimage/...

There is no update in redhat for that part, although I asked
for it some times ago.
So I took what was in rawhide/i386/RedHat/instimage
and replaced it in my nfs distribution.
I did it in the beginning of june and it worked.
Today, I see new versions of install2, etc. I should
probably try this.

Having a mirror of updates for RedHat/instimage would really help
to be conherent between .img files and nfs installation.

Anyway, with the instimage of rawhide you don't need
any other disket than the one for the installation.

> The announcement (on redhat-watch-list) said
> 
> > Three disks are needed for Intel based computers: "boot.img" or
> > "bootnet.img", "supp.img", and "modules.img".  Choose "boot.img" for
> > local installs (CD-Rom, hard drive) or "bootnet.img" for network
> > installs (NFS, FTP, HTTP).  Copy the three images to 1.44 MB floopy
> > disks using "dd if=file.img of=/dev/fd0 bs=72k" under Linux or
> > "rawrite.exe" under DOS or Windows.
> > 
> > After preparing the disk images, insert the appropriate boot disk and
> > boot the computer.  At the boot prompt type "linux supp" and press
> > Enter.  This tells the installer to load changes from the supplimental
> > and modules disks.  The installer will prompt the user to insert the
> > supplemental disk and modules disk during the installation process.
> 
> I'm using kickstart, and all I've had to do before is to put a
> bootnet.img floppy in and type "linux ks" to get everything up
> and running.  If I do a "linux supp" it goes into the "normal"
> installation, which I don't want.  When I try to do as before, but
> with the new bootnet.img (not using the supp or modules disks)
> the one thing that was fixed on the new version that I need still
> doesn't work.
> 
> Has anyone gotten this to work?
> -- 
> Per Starback <starback ling uu se> <http://stp.ling.uu.se/~starback/me.html>
-- 

                    Anne Possoz
                    http://slsun2.epfl.ch/possoz.html
                    Service Informatique Central
                    Ecole Polytechnique Federale de Lausanne
                    1015 Lausanne (Switzerland)
                    Tel : (41/21) 693.22.49




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]