Re: concurrent installs of previous + current kernels
> Of course I have - otherwise I wouldn't be asking the fine people on
> this list how to go about this.
Now, you're starting to give the necessary info.
> So like I said in my initial email, *concurrent* installs of kernel
> packages doesn't seem feasible by just installing the next kernel
> handed to me by apt-get. To be explicit, by concurrent, I mean that
> I could boot into both - release 17, and 21 - via the boot loader.
> As it stands, if I were to install the
> linux-image-2.6.26-2-686_2.6.26-21_i386.deb package, I would be only
> able to boot to release 21.
In the case of versions that are really different (2.6.26 and 2.6.32
and 2.6.18 and ...), there's no such conflict and they coexist just fine.
But, indeed, in the above case the same kernel versions are identical,
with just different Debian sub-revision: the Debian maintainers decided
to keep the same name, so you can't install them both at the same time.
Most likely the difference is very small.
In such a case I do not know how to keep them both installed at the
same time. If all you're worried about is the possibility that the new
kernel won't boot right, then I'd recommend you first install some
completely different kernel (e.g. 2.6.32-trunk from testing), which you
can install without removing your current kernel; then you try to boot
into this new kernel, and if that works, then you can upgrade your
2.6.26 to its newer stable revision, knowing that if that fails, you
can still boot to 2.6.32.
Stefan
Reply to: