On Mon, Nov 9, 2009 at 3:34 PM, Allan Gottlieb <gottl...@nyu.edu> wrote:
> I am getting a blockage involving device mapper
>
> [ebuild U ] sys-libs/e2fsprogs-libs-1.41.9 [1.41.3-r1] USE="nls" 485 kB
> [0]
> [blocks B ] <sys-fs/e2fsprogs-1.41.8 ("<sys-fs/e2fsprogs-1.41.8" is
> blocking sys-libs/e2fsprogs-libs-1.41.9, sys-apps/util-linux-2.16.1)
> [blocks B ] <sys-libs/e2fsprogs-libs-1.41.8
> ("<sys-libs/e2fsprogs-libs-1.41.8" is blocking sys-apps/util-linux-2.16.1)
> [blocks B ] sys-fs/device-mapper ("sys-fs/device-mapper" is blocking
> sys-fs/udev-146-r1)
>
> I looked on bgo and found posts today involving this. They were
> "resolved" by noting "device-mapper was merged upstream into lvm2.
> Emerge a recent lvm2, it will automatically
> unmerge old device-mapper."
>
> I am not running lvm2 on this machine. I have device mapper because
>
> sys-fs/cryptsetup-1.0.6-r2 pulled in by:
> sys-apps/hal-0.5.12_rc1-r8
>
> sys-fs/device-mapper-1.02.24-r1 pulled in by:
> sys-fs/cryptsetup-1.0.6-r2
>
> Does this mean I should emerge lvm2 even though this machine does not
> use logical volumes?
>
> thanks,
> allan
The sys-fs/lvm2 package just contains utilities, it doesn't require
you to actually use LVM2. I also use it the same way as you. I now
have the lvm2 package and not device-mapper and everything still works
with my encrypted partition.
