Is is possible (and straightforward) to keep two versions of the kernel around selecting which to actually boot in LILO? I need 2.2.14 (actually >= 2.2.9) to play quake, but my there are problems using my Seagate IDE tape drive. The tape drive behaves fine under 2.2.7. Until I get the tape problems solved I need to switch back and forth. Thanks, Jeffrey -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Sun, 04 Jun 2000, muskrat@texas.net wrote:
Is is possible (and straightforward) to keep two versions of the kernel around
It's possible and very straight forward. Actually I'd suggest people should keep at least one extra kernel lying around. This way when you upgrade the kernel the old one is there to fall back to. Nick -- Nick Zentena "The Linux issue," Wladawsky-Berger explained, "is whether this is a fundamentally disruptive technology, like the microprocessor and the Internet? We're betting that it is." -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
* muskrat@texas.net (muskrat@texas.net) [20000605 17:54]:
Is is possible (and straightforward) to keep two versions of the kernel around selecting which to actually boot in LILO?
Yes on both accounts ;-) Just rename one of the kernels (and System.map
accordingly) and add an entry in /etc/lilo.conf. Here's what my lilo.conf at
home looks like:
image = /boot/vmlinuz-2.4.0-test1-ac7
root = /dev/hda6
append ="video=matrox:1280x1024@75,mtrr,sgram"
label = linux
#
image = /boot/vmlinuz-2.3.99-pre9
root = /dev/hda6
append ="video=matrox:1280x1024@75,mtrr,sgram"
label = lxpre9
#
image = /boot/vmlinuz-2.3.99-pre8
root = /dev/hda6
append ="video=matrox:1280x1024@75,mtrr,sgram"
label = lxpre8
#
image = /boot/vmlinuz-2.3.99-pre6
root = /dev/hda6
append ="video=matrox:1280x1024@75,mtrr,sgram"
label = lxpre6
#
image = /boot/vmlinuz-2.3.99-pre5
root = /dev/hda6
append ="video=matrox:1280x1024@75,mtrr,sgram"
label = lxpre5
#
image = /boot/vmlinuz-2.3.99-pre3
root = /dev/hda6
append ="mem=192M video=matrox:1280x1024@75,mtrr,sgram"
label = lxpre3
#
image = /boot/vmlinuz-2.2.14
append ="mem=192m"
root = /dev/hda6
label = lx14
#
--
Philipp Thomas
you mention keeping an extra copy of System.map but I don't
see it in the lilo.conf that you included.
How do you specify that the system.map is different with
each kernel?
Can the image= point to a link?
----- Original Message -----
From: Philipp Thomas
* muskrat@texas.net (muskrat@texas.net) [20000605 17:54]:
Is is possible (and straightforward) to keep two versions of the kernel around selecting which to actually boot in LILO?
Yes on both accounts ;-) Just rename one of the kernels (and System.map accordingly) and add an entry in /etc/lilo.conf. Here's what my lilo.conf at home looks like:
image = /boot/vmlinuz-2.4.0-test1-ac7 root = /dev/hda6 append ="video=matrox:1280x1024@75,mtrr,sgram" label = linux # image = /boot/vmlinuz-2.3.99-pre9 root = /dev/hda6 append ="video=matrox:1280x1024@75,mtrr,sgram" label = lxpre9 # image = /boot/vmlinuz-2.3.99-pre8 root = /dev/hda6 append ="video=matrox:1280x1024@75,mtrr,sgram" label = lxpre8 # image = /boot/vmlinuz-2.3.99-pre6 root = /dev/hda6 append ="video=matrox:1280x1024@75,mtrr,sgram" label = lxpre6 # image = /boot/vmlinuz-2.3.99-pre5 root = /dev/hda6 append ="video=matrox:1280x1024@75,mtrr,sgram" label = lxpre5 # image = /boot/vmlinuz-2.3.99-pre3 root = /dev/hda6 append ="mem=192M video=matrox:1280x1024@75,mtrr,sgram" label = lxpre3 # image = /boot/vmlinuz-2.2.14 append ="mem=192m" root = /dev/hda6 label = lx14 #
-- Philipp Thomas
Development, SuSE GmbH, Schanzaecker Str. 10, D-90443 Nuremberg, Germany #define NINODE 50 /* number of in core inodes */ #define NPROC 30 /* max number of processes */ -- Version 7 UNIX fuer PDP 11, /usr/include/sys/param.h
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Hi. The best way to do this is to put each kernel in its own directory.
For example, you can have /boot/stable/ and /boot/test/ (or whatever you
feel like calling the dirs).
Then each dir will have it's owm image and System.map. In /etc/lilo.conf you
could do
label=stable
image=/boot/stable/vmlinuz
root=/dev/hda2
label=test
images=/boot/test/vmlinuz
root=/dev/hda2
Before you build the kernels be sure to add the appropriate entry to
lilo.conf (especially if you do a make zlilo which runs lilo after the
build). Also set the INSTALL_PATH in the kernel top-level Makefile to point
to where ever the kernel and map are to be installed.
I have not tried this myself but I see no reason why is should not work. :)
kw
/* Keith Warno
** Developer & Sys Admin
** http://www.HaggleWare.com/
*/
----- Original Message -----
From: "Mike Kenzie"
* muskrat@texas.net (muskrat@texas.net) [20000605 17:54]:
Is is possible (and straightforward) to keep two versions of the kernel around selecting which to actually boot in LILO?
Yes on both accounts ;-) Just rename one of the kernels (and System.map accordingly) and add an entry in /etc/lilo.conf. Here's what my lilo.conf at home looks like:
image = /boot/vmlinuz-2.4.0-test1-ac7 root = /dev/hda6 append ="video=matrox:1280x1024@75,mtrr,sgram" label = linux # image = /boot/vmlinuz-2.3.99-pre9 root = /dev/hda6 append ="video=matrox:1280x1024@75,mtrr,sgram" label = lxpre9 # image = /boot/vmlinuz-2.3.99-pre8 root = /dev/hda6 append ="video=matrox:1280x1024@75,mtrr,sgram" label = lxpre8 # image = /boot/vmlinuz-2.3.99-pre6 root = /dev/hda6 append ="video=matrox:1280x1024@75,mtrr,sgram" label = lxpre6 # image = /boot/vmlinuz-2.3.99-pre5 root = /dev/hda6 append ="video=matrox:1280x1024@75,mtrr,sgram" label = lxpre5 # image = /boot/vmlinuz-2.3.99-pre3 root = /dev/hda6 append ="mem=192M video=matrox:1280x1024@75,mtrr,sgram" label = lxpre3 # image = /boot/vmlinuz-2.2.14 append ="mem=192m" root = /dev/hda6 label = lx14 #
-- Philipp Thomas
Development, SuSE GmbH, Schanzaecker Str. 10, D-90443 Nuremberg, Germany #define NINODE 50 /* number of in core inodes */ #define NPROC 30 /* max number of processes */ -- Version 7 UNIX fuer PDP 11, /usr/include/sys/param.h
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
* Mike Kenzie (KenzieM@sympatico.ca) [20000609 18:06]:
you mention keeping an extra copy of System.map but I don't see it in the lilo.conf that you included.
How do you specify that the system.map is different with each kernel?
You don't need to specify the System.map to use. Lilo doesn't need it, only
klogd needs it to give prettier output. The correct System.map to use is
determined by the name of the file, so for vmlinuz-2.4.0-test1-ac9
System.map-2.4.0-test1-ac9 will automatically be used. So the only
requirement is that you give kernel and the system map matching extensions.
Philipp
--
Philipp Thomas
participants (5)
-
keith@HaggleWare.com
-
KenzieM@sympatico.ca
-
muskrat@texas.net
-
pthomas@suse.de
-
zentena@hophead.dyndns.org