Short story: upgraded squeeze to wheezy, kernel did not. But OS seems to run, so I'm using synaptic to install the kernel. (I know I should use apt-cache and apt-get, but I'm lazy and trying to do some other work that needs to be done today.)
Wondering why, wondering how big a hole-in-my-foot I'm going to end up with. We'll see. Wondering if this has happened to anyone else.Long story:
I have an AMD sempron 32 bit CPU, three disks. Currently only two OSses, both Debian, both were squeeze last week.
One is on the first hard disk, it controls the dual-boot process. (This was for when I was mostly running Fedora and sometimes playing with other stuff. I still plan to play with other stuff, if I can figure out how to chain grub to non-MSWindows OSses.)
The other is the working OS on the second disk, both the family accounts and some of my work accounts.The first disk is a very small install, single partition, minimal set of apps. I upgraded it using apt-get update with no problems. (That I've noticed yet. Haven't tried sound and some other not-so-simple stuff.)
In other words, I got into /etc/apt/sources.list and commented out the squeeze lines and added wheezy lines, per the documented procedures at
http://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html
Since that went fairly well, I tried the same thing on my working OS. Lots of things show that I need to tune settings, I expected that.I may have missed it in the middle of the night, but I didn't see any messages about not being able to install the kernel. No holds show up anywhere, either.
While restoring the PAM settings that keep my kids from logging in after 11:00 at night (not the right solution, I know.), I noticed that the kernel was still at 2.6.32. No sign of 3.2 in /boot or anywhere. Synaptic says it's not loaded.
So, I'm just doing the point-and-click install of the 3.2 kernel, hoping nothing too strange happens.Comments?
--
Joel Rees