Yeah, that was one of the possibilities, but one I was hoping to
avoid. Worst case that's how we'll go.
I was kind of hoping someone from RedHat was listening and might be
able to suggest what they do to customize the kernel to deal with
using "/modules/modules.cgz" in the search path...
Incidentally, the generic boot kernel has a lot of stuff enabled that
is a total waste (like "parallel port" support, which is hardly useful
at kickstart time).
- Matt
Lynn, Michael (IDS DM&DS) wrote:
I experienced this issue and had to resort to keeping custom bootnet.img images based on the hardware architecture of the client being built - this is accomplished using a webform/cgi that prompts the
user for information about the client being built... eg:
[ ] Server with GigE card
[ ] Server with e100 card
etc.
Then based on the user's selection, I source the bootnet.img with the proper set - pop in the ks.cfg and present it to the user for download.
-----Original Message-----
From: Matt Fahrner [mailto:Matt.Fahrner@xxxxxxxx]
Sent: Friday, March 28, 2003 1:49 PM
To: kickstart-list@xxxxxxxxxx
Subject: Re: Shrinking the kickstart image
Thanks, but that's not possible because I can't get the modules loaded
for the ethernet adapters to do networking. That's the whole problem
really. We need 3 different ethernet modules that aren't by default
supplied on the boot floppy...
Thanks,
- Matt
Johnston, Christopher (IDS DM&DS) wrote:
Use grub with a tftp session..
-----Original Message-----
From: Matt Fahrner [mailto:Matt.Fahrner@xxxxxxxx]
Sent: Friday, March 28, 2003 12:31 PM
To: kickstart-list@xxxxxxxxxx
Subject: Shrinking the kickstart image
We have building our own "initrd.img" files with added modules for our
kickstart floppy. Unfortunately under "rawhide" (aka: 8.1, soon to be
9.0) the kernel plus our modules no longer fit on a 1.4 meg floppy.
My answer was to chop out any bogus modules and build own BOOT kernel
deconfiging extra stuff not needed.
The problem I've found is that now this new kernel doesn't find the
modules we've placed in out "initrd.img" (no, there are no versioning
issues). In fact if I slim our "initrd.img" down (by leaving out some
of the modules we usually want) and just use the generic kernel you
come out with from using the "kernel-2.4.20-i386-BOOT.config" file, it
doesn't find the modules either. The same slimmed "initrd.img" works
fine with the kernel found in "bootdisk.img" (ie: it does find the
modules - in particular an "e1000.o" we've added).
The issue as far as I can tell appears that the "bootdisk.img" kernel
looks in "/modules/modules.cgz" and the built kernel does not. Maybe
I'm wrong though.
So, does anyone have a guess what I need to do here? Is there
something I'm not setting in the kernel build to set the module search
path?
Any help would be appreciated.
- Matt
--
---------------------------------------------------------------------
Matt Fahrner 2 South Park St.
Manager of Networking Willis House
Burlington Coat Factory Warehouse Lebanon, N.H. 03766
TEL: (603) 448-4100 xt 5150 USA
FAX: (603) 443-6190 Matt.Fahrner@xxxxxxxx
---------------------------------------------------------------------
