On 3 Aug 00, at 4:10, Charles Galpin wrote:
> On Wed, 2 Aug 2000, Pete Lancashire wrote:
> > Should I copy/rename the file /usr/src/....arch/i386/boot/bzImage
> > to /boot/vmlinuz-2.2.16-5 ?
>
> yes. see the /usr/src/linux/README
>
> > The links kernel.h, System.map, module-info point to actual
> > files named with the version suffix, is there a script that gets
> > them there ?
>
> not sure about these, sorry
I haven't found info on that last point (not that I've looked
*that* hard) so I just manually update the System.map-XXXX (and
leave the original one there so I can boot the install kernel) and
change the symlink. The module.info seems to be static, and the
kernel.h file is new to RH 6.2, and claims to be automatically
generated at boot time on a freshly installed system (ie, no custom
kernel yet).
You can check the readme and other docs in the kernel source, and
there's a small kernel upgrade HOWTO on the RedHat site.
On the first point above, I copy the new bzImage kernel file over
to /boot/test, and leave the original kernel there. Just add
another stanza to lilo.conf that points to the image under
/boot/test (you can call the file anything you want). Here's the
sequence (replace X.X with your version number):
make sure the kernel source *and* the kernel headers are installed
(along with gcc, glibc, all the basic devel stuff)
cd /usr/src/linux
make [x|menu]config
('make config' is a PITA, so do menuconfig at the console, or
xconfig in X) Start off by changing as little as possible, except
for obvious things like turning off ISDN (unless of course, you
have ISDN). save your config to another place.
make dep
make clean
make bzImage
make modules
mv /lib/modules/X.X.XX /lib/modules/X.X.XX-old
make modules_install
depmod -a
cp /usr/src/linux...bzImage /boot/test/vmlinuz-X.X.XX
cp /usr/src/linux/System.map /boot/System.map-X.X.XX
Add something like this to lilo.conf:
image=/boot/test/vmlinuz-2.0.36
label=test
root=/dev/sda1
read-only
don't forget to run lilo
Now you get to do the modules thing. The install conf.modules only
has your required modules detected/setup during the install, eg:
alias scsi_hostadapter BusLogic
alias parport_lowlevel parport_pc
alias eth0 3c509
All is well (usually) with the install setup, and all module
dependencies should be resolved (ie, no module symbol error
messages at boot). However, after you boot a custom kernel all
bets are off (well, sometimes it seems that way anyway ;)
After you're finished with the above, backup the original
conf.modules file. You can then do:
modprobe -c>/etc/conf.modules
You should probably remove all the path stuff (down to where the
aliases start) so it will have a better chance of finding
everything. RedHat 6.2 fixes the manual tweaking that was
previously required, so modprobe "should" generate a correct conf
file for you. Certain hardware configurations (eg, 2 parallel
ports) or devices still need manual tweaking, but...
If you compiled certain drivers as modules (eg, a SCSI controller
connected to the boot drive) you will need to run mkinitrd and add
that to the lilo stuff above. See 'man mkinitrd'.
That's about it. And that was more than you asked, wasn't it?
Someone must have hit the verbose switch...
Steve
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
