Having built a few hundred kernels over the past 6-7 years, perhaps
I can offer a few tips. (Sounds like it would be a good Chapter meeting
topic, however!).
One way of working around the module directory problem would be to
rename the currently working directory temporarily, just before doing
the kernel build. The modules are installed in a kernel-version-number-specific
directory in /lib/modules, e.g., /lib/modules/2.2.16. If you're
building a new kernel that is also based on 2.2.16, rename the current
directory to something like "/lib/modules/2.2.16.working". That way,
you can go ahead and build your kernel. I usually do:
make xconfig # and use the Tcl/Tk applet to configure my kernel
make dep; make clean # same old, same old
make bzdisk # put the new kernel on a bootable floppy
make modules; make modules_install # if and only if 'make bzdisk' worked
(Yes, I realize that I could write a bash script to 'automate' all
this, but I prefer a hands-on approach, since I typically work with
the bleeding-edge kernels. This also avoids tinkering with the LILO
settings and the stuff in /boot until I get a really stable kernel
that I KNOW will boot properly and consistently).
Note that you need to have X11 (in whatever incarnation you prefer,
with whatever Window Manager and KDE/Gnome/whatever) in order to use
'make xconfig'. Otherwise, from a command line, I think the command
is 'make config' - haven't used it in years...
Note that if you succeed in building all this stuff, you may get a
number of error messages when booting Red Hat 6.x based systems because
the System.map file of the newly booted kernel doesn't match what's
in /boot/System.map. However, these messages are generally benign
enough for initial check-out that you can ignore them. Then, once you're
satisfied with the stability and correctness of the new kernel, you
can finish setting up LILO and /boot/System.map and /boot/vmlinux, etc.
HTH,
Bayard
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
