Re: More adding network driver to custom cd

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

 



That's correct except for a few files which if present in the root of
the build tree will override the ones in the rpms.  These are mkimages,
mkimages.i386 (or other archs) and upd-instroot.  Drop these in at the
same level that the RedHat directory lives.  Add a 'set -x' at the top
of each if you want to see alot of debug info.


You really only need the architecture specific one.  Find the line for
NETWORKMODULES and modify to suit.  If you are adding a new module, then
you have to 
1) place the rpm in RedHat/RPMS 
2) patch the anaconda and kudzu packages so pcitable and modules-info is
correct
3) replace the anaconda and kudzu packages in RedHat/RPMS with your new
ones.
4) regen the pkglist file
5) run buildinstall, then mount the .img files and make sure your
modules are included.
6) install :-)

If you are enabling a module that is already in the pcitable/modules-info, 
then you just have to edit NETWORKMODULES and run buildinstall

You can also do stuff like hack out the support for other languages,
create other .img files, etc.

Harder to learn than stuffing things in .img files, but ultimately
(IMHO), much more satisfying.


On Thu, 4 Sep 2003, Glenn MacGregor wrote:

> Jim,
> 
> Not sure I follow you. I have been looking at the buildinstall script for
> most of the day, having trouble following it in spots.
> AS far as I can tell buildinstall creates all the img and initrd files for
> the install based on what is in the RPMS directory, correct? What do I need
> to add to the rpms directory to have the isolinux/initrd.img and stage2.img
> (and maybe the hdsgt1.img) created with the correct modules.cgz, pcitable,
> module-info, etc?
> 
>     Thanks
> 
>             Glenn
> 
> ----- Original Message -----
> From: "Jim Wildman" <jim@xxxxxxxxxxxxx>
> To: <kickstart-list@xxxxxxxxxx>
> Sent: Thursday, September 04, 2003 3:06 PM
> Subject: Re: More adding network driver to custom cd
> 
> 
> > To do it cleanly, check out the 'buildinstall' script which is part of
> > the Anaconda-runtime package.  In short, copy mkimage.i386 to the root
> > of your CD build tree, regen the package indexes, then run buildinstall.
> > Presto, all new install images with stuff in the right places..
> >
> > On Thu, 4 Sep 2003, Glenn MacGregor wrote:
> >
> > > Thanks for all the responses to my original question!
> > >
> > > I am still having some issues. Let me explain my situation a bit better
> this time. I need to make a cd which installs a modified (some of my own
> rpms get installed) redhat linux 8.0 on a server with no interaction from
> the user (server has no keyboard,mouse or monitor). This did work fine when
> Dell shipped there 1u series servers with Intel network cards, now they ship
> them with Broadcom networks cards.
> >
> > ------------------------------------------------------------------------
> > Jim Wildman, CISSP, RHCE                                jim@xxxxxxxxxxxxx
> > http://www.rossberry.com
> >
> >
> > _______________________________________________
> > Kickstart-list mailing list
> > Kickstart-list@xxxxxxxxxx
> > https://www.redhat.com/mailman/listinfo/kickstart-list
> >
> 
> 
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/kickstart-list
> 

------------------------------------------------------------------------
Jim Wildman, CISSP, RHCE                                jim@xxxxxxxxxxxxx
http://www.rossberry.com




[Index of Archives]     [Red Hat General]     [CentOS Users]     [Fedora Users]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux