[Virtual-pkg-base-maintainers] Bug#626479: Additional information

[Marek Lukaszuk]

On Thu, May 12, 2011 at 13:20, Eccles, David
<david.eccles at mpi-muenster.mpg.de> wrote:
> Some more information...
>
> running amd64 Debian unstable, linux image:
> linux-image-2.6.38-2-amd64_2.6.38-5_amd64.deb
>
> I'm using lvm, which has required me to forbid udev version 168-1 (it wasn't
> able to run udev at computer boot, which made X unusable due to a lack of
> mouse/keyboard control). I notice that this update changed udev to 168-2.
> Details of lvm setup follow :
>
> root at ubuntu:/target# lvm pvscan
>  PV /dev/sdb1   VG spin0_thaliana   lvm2 [931.51 GiB / 0    free]
>  PV /dev/sda1   VG ssd_thaliana     lvm2 [167.68 GiB / 0    free]
>  Total: 2 [1.07 TiB] / in use: 2 [1.07 TiB] / in no VG: 0 [0   ]
>
> root at ubuntu:/target# lvm lvscan
>  ACTIVE            '/dev/spin0_thaliana/home' [931.51 GiB] inherit
>  ACTIVE            '/dev/ssd_thaliana/boot' [188.00 MiB] inherit
>  ACTIVE            '/dev/ssd_thaliana/swap' [18.62 GiB] inherit
>  ACTIVE            '/dev/ssd_thaliana/root' [148.87 GiB] inherit

The problem is due to latest libc upgrade 2.13-3 it removed the link
/lib64 -> /lib once added my system started working.

Related bugs:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626447
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626449
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626450

Hope this helps,
Marek