|
well, i'm unwilling to read through that mess, but here's what i do:
1) get the source, put it wherever (doesn't have to be in /usr/src/, but that's canonical) and untar it.
2) issue "#make mrproper && make menuconfig" from the untarred source directory. then i choose the relevant kernel options
3) once that's all done (make sure to save your kernel config!), then issue "#make dep && make clean && make bzImage && make modules && make modules_install"
(double and signs say "if the step before occurs without errors, then do the next". it's good for multiple commands here)
4) move the old kernel image (vmlinuz, etc.) and the old system.map to a safe spot (i make the directory /boot/old and move them there).
5) in compiled source directory, issue the following "cp System.map /boot/System.map && cat arch/i386/boot/bzImage > /boot/vmlinuz" to move the system.map and the kernel image to the /boot directory
6) edit the text in /etc/lilo.conf to allow for 2 entries as follows:
you start with this
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda1
label = Linux
read-only
# Linux bootable partition config ends
change it to the following
image = /boot/vmlinuz
root = /dev/hda1
label = fresh.slack
read-only
# Linux bootable partition config begins
image = /boot/old/vmlinuz
root = /dev/hda1
label = old.slack
read-only
# Linux bootable partition config ends
this way, your old kernel can still boot from lilo (no disks).
7) issue "#lilo" to update your lilo boot list (this is the command in slackware, don't know about other distros)
8) reboot and choose "fresh.slack" at the lilo prompt
i've gotten kernel panic a couple times, but only when i didn't finish configuring the system and had to turn things off mid-install. it may have something to do with your configuration you've chosen.
in a pinch, get out the slackware iso cd or bootdisk and boot from that and then fix everything as listed above. if problems persist, post your config file.
HTH,
y-p
|
