[ale] Kernel-rebuild loose ends

[Fulton Green]

I use the DOS-based LoadLin in lieu of lilo (don't LOL), but here's a stab at
what I do know:

The System.map file should appear in your /usr/src/linux build directory
after the kernel image has been produced. Copy it to /boot/System.map-2.2.16 .
The /etc/rc.d/rc.sysinit script is looking for a .rhkmvtag file. You may need
to comment out this section of the script unless you can figure out how to
emulate it.  You may also need to generate the modules.dep file for the
modules subdir by doing a
    depmod -aei -F /boot/System.map-2.2.16 2.2.16

Unless someone knows otherwise, the module-info file appears to be a Red Hat-
specific file that doesn't seem to be mentioned anywhere in the vanilla
kernel source. Just create a softlink of /boot/modules-conf-2.2.16 to point
to the 2.2.14 one and be done w/it.

On Thu, Jun 08, 2000 at 02:29:27PM -0400, John M. Mills wrote:
> I have a RH6.1 system with the 'out-of-the-box' linux-2.2.12-20 kernel, so
> today it seemed a good moment to install 2.2.16. (Thanks, Bob.) I
> configured and installed the kernel and modules, and it appears to boot
> and run OK. My questions:
> 
> 1) How should the file '/boot/System.map' and '/boot/map' be produced? I
> tried directing Lilo to create a '/boot/System.map-2.2.16', but I get
> error reports that it is not parseable. '/boot/map' is presumably the
> mapfile named in /etc/lilo.conf, but my first try (without mentioning a
> mapfile) generated complaints of an incorrect (old) kernel version.
> 
> 2) How should the file module-info-<version> be produced? I thought it
> would result from 'make modules_install', but it didn't.
> 
> These must be documented somewhere, but I didn't find them, so direction
> to the "Right Fine Manual" would be welcome.
--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.