[101081] in RedHat Linux List
Custom kernel questions
daemon@ATHENA.MIT.EDU (Sven N. Thommesen)
Tue Nov 24 14:52:26 1998
Date: Tue, 24 Nov 1998 13:49:59 -0600
To: redhat-list@redhat.com
From: "Sven N. Thommesen" <sthomme@aub.mindspring.com>
Resent-From: redhat-list@redhat.com
Reply-To: redhat-list@redhat.com
Compiling custom versions of 2.0.36-1 on Apollo, the following questions
came up:
(a) the usual instructions say to do
# rm -rf /lib/modules/<ver>-old
# mv /lib/modules/<ver> /lib/modules/<ver>-old
before doing
# make modules_install
Question: if I want to have say 3 custom kernels, each with a different
selection of modules (vs. compiled-in functionality), then no matter which
version of the /lib/modules/<ver> directory is the final one, the other two
kernels may not find all the modules they need. Is there a solution to this?
[I can think of one: make one kernel answering 'm' to every place possible
during 'make config', then leave the resulting /lib/modules/<ver> directory
in place, since it'll contain all possible modules. Would this work?]
(b) When I install the new kernel using rpm, there are two files added to
/boot, namely 'System.map-<ver>' and 'module-info-<ver>'. When I compile a
custom kernel, no such files are created.
Question: Are these files informational only, or necessary? Do they vary
between custom kernels? If so, how do I generate new versions?
Thanks!
Sven Thommesen
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com http://archive.redhat.com
To unsubscribe: mail redhat-list-request@redhat.com with
"unsubscribe" as the Subject.
