[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <2d05c4580903090721p2a6022base9e7dafa719e448e@mail.gmail.com>
Date: Mon, 9 Mar 2009 15:21:24 +0100
From: Dragoslav Zaric <dragoslav.zaric.kd@...il.com>
To: LKML <linux-kernel@...r.kernel.org>
Subject: Boot correct kernel
Hello,
I had generic kernel 2.6.27-7 and it worked fine. Then I installed
2.6.28 that had errors during
install, but system anyway booted to 2.6.28. When I did apt-get
install of some app in this bad
2.6.28 kernel I got error messages that something is wrong. So I
entered boot menu and booted
to old 2.6.27-7 kernel and when I tried to do apt-get install of some
app, the system again looked at
2.6.28 like current kernel !!
So I looked where does files of current kernel are copied and there
are few folders (files):
/boot/vmlinuz*VERSION*
/boot/initrd*VERSION*
/boot/System-map*VERSION*
/boot/config-*VERSION*
/lib/modules
and also menu list in /boot/grub/menu.lst
So, when you have more kernels, let's say 4 working and one bad
kernel, when the system
boots selected kernel, should the system copy all files from selected
kernel to all places where
current running system kernel should be ?? That way you will always
have correct kernel running
whole system, and all installed modules for that kernel could be
loaded looking at modinfo of modules
or modules could be sorted into folders for each kernel version.
--
Thanks
Dragoslav Zaric
[Programmer ; M.Sc. in Astrophysics]
[Belgrade ; Serbia]
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists