Re: concurrent installs of previous + current kernels
On Tue, Feb 02, 2010 at 12:16:14AM EST, Lev Lvovsky wrote:
[..]
> > What makes you think so? Have you even tried it?
> Of course I have - otherwise I wouldn't be asking the fine people on
> this list how to go about this.
> As an example, the contents of the following linux kernel image deb:
>
> linux-image-2.6.26-2-686_2.6.26-21_i386.deb
>
> Among other things, is the following structure in /boot:
>
> ---
> % ls -la /tmp/deb/boot
> total 2492
> drwxr-xr-x 2 lev lev 4096 Dec 26 04:28 .
> drwxr-xr-x 5 lev lev 4096 Dec 26 04:28 ..
> -rw-r--r-- 1 lev lev 928295 Dec 26 04:28 System.map-2.6.26-2-686
> -rw-r--r-- 1 lev lev 91715 Dec 26 04:28 config-2.6.26-2-686
> -rw-r--r-- 1 lev lev 1506448 Dec 26 04:28 vmlinuz-2.6.26-2-686
> ---
> Unless there's some pre or post magic that goes on, these are the same
> files which are currently owned by the pre-existing (debian release
> 17) kernel package:
This is odd.
I keep an up-to-date ubuntu partition on the side, which I boot into
every now and then, and every couple of weeks or so, the update manager
installs a new version of the kernel. I can't look now but I believe I
have something like two or three different versions of 2.6.31 at
present. Say, 2.6.31-15, 2.6.31-16, and 2.6.31-17, complete with
modules, headers and all. There would be more, if I hadn't removed a few
older versions manually to keep my grub menu to somewhat manageable
lengths.
I missed most of this thread and maybe I minusnderstand this issue, but
it looks like there must be a dpkg/apt option somewhere or other that
lets you do what you want? Unless it's a packaging option that they are
using for their kernels?
Not much help, I guess, but maybe worth taking another look at the
manuals.
CJ
Reply to: