On Thu, 2010-12-30 at 01:31 -0700, Bob Proulx wrote: > If you are just now getting the grub 2 upgrade in Sid then it has been > a *long* time since you last upgraded. At least ten months? Since > before last February? (I can't quite remember when it went through a > brief search didn't refresh my memory enough to be sure.)
I don't think it was that long. I remember GRUB 2 coming in, but I stuck with the legacy package at the time. > What are the versions of your kernel and udev packages? I know you > say they are fine but inquiring minds want to know the version numbers > so that we can know this for ourselves. :-) Kernel is 2.6.26.4, udev is 164-3. > What does this say? > > cat /proc/partitions It reports the partitions properly. > Note that the current udev requires a kernel that is 2.6.28 or newer. > This is making upgrades from Lenny to Squeeze especially painful this > release cycle. That could certainly be an issue. I suppose there must be some good technical reason that dep wouldn't be tracked by apt. It's going to be tricky doing a kernel upgrade now, since my /boot directory containing the kernels and grub info is no longer accessible. That's going to confuse the heck out of apt and the rest of the usual boot/kernel configuration tools. I could d/l the current kernel package and manually extract the kernel and modules from it, but I'm not sure how best to go about booting to them. Suppose I remove and reinstall GRUB and my current kernel (essentially recreating my old /boot partition on the root partition)... is GRUB going to freak out with the device nodes inaccessible? Alternatively, could I just mknod the appropriate nodes for the moment in order to get the kernel sorted out? Other suggestions? Thanks, Todd -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1293716128.1997.47.ca...@timaeus.sophrosune.org
