On Monday 01 February 2010 14:00:07 Lev Lvovsky wrote: > What if any is the generally accepted way of maintaining multiple versions > of kernels? Just install each of their packages separately. Since the kernel team does support concurrent installs, the upstream version number is part of the package name: p linux-image-2.6.26-1-amd64 - Linux 2.6.26 image on AMD64 i A linux-image-2.6.26-2-amd64 - Linux 2.6.26 image on AMD64 p linux-image-2.6.29-bpo.2-amd64 - Linux 2.6.29 image on AMD64 p linux-image-2.6.30-2-amd64 - Linux 2.6.30 image on AMD64 p linux-image-2.6.30-bpo.1-amd64 - Linux 2.6.30 image on AMD64 p linux-image-2.6.30-bpo.2-amd64 - Linux 2.6.30 image on AMD64 i A linux-image-2.6.32-trunk-amd64 - Linux 2.6.32 for 64-bit PCs There's also a version-tracking package "linux-image-amd64". It doesn't have the upstream version as part of it's name, but only exists to simply pull in the appropriate real package. > This is also to keep 'apt-get upgrade' from finding anything else pending. You could pin the version-tracking package. -- Boyd Stephen Smith Jr. ,= ,-_-. =. bss@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/
Attachment:
signature.asc
Description: This is a digitally signed message part.