Stefan, On Feb 1, 2010, at 6:09 PM, Stefan Monnier wrote:
>> So assuming that I only have stable + security in my apt sources.list >> config, how would I manage to keep the older version of the kernel >> package, as well as the newest version? > > Huh... you install the new kernel. My thought too, but that doesn't work - the older version is removed. > >> 'apt-get install' will remove the binaries from the previously >> installed kernel package. > > 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: --- % dpkg -L linux-image-2.6.26-2-686 |grep "/boot" /boot /boot/config-2.6.26-2-686 /boot/vmlinuz-2.6.26-2-686 /boot/System.map-2.6.26-2-686 --- 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. -lev -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
