| 1 |
On Mon, Nov 9, 2009 at 3:34 PM, Allan Gottlieb <gottlieb@×××.edu> wrote: |
| 2 |
> I am getting a blockage involving device mapper |
| 3 |
> |
| 4 |
> [ebuild U ] sys-libs/e2fsprogs-libs-1.41.9 [1.41.3-r1] USE="nls" 485 kB [0] |
| 5 |
> [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) |
| 6 |
> [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) |
| 7 |
> [blocks B ] sys-fs/device-mapper ("sys-fs/device-mapper" is blocking sys-fs/udev-146-r1) |
| 8 |
> |
| 9 |
> I looked on bgo and found posts today involving this. They were |
| 10 |
> "resolved" by noting "device-mapper was merged upstream into lvm2. |
| 11 |
> Emerge a recent lvm2, it will automatically |
| 12 |
> unmerge old device-mapper." |
| 13 |
> |
| 14 |
> I am not running lvm2 on this machine. I have device mapper because |
| 15 |
> |
| 16 |
> sys-fs/cryptsetup-1.0.6-r2 pulled in by: |
| 17 |
> sys-apps/hal-0.5.12_rc1-r8 |
| 18 |
> |
| 19 |
> sys-fs/device-mapper-1.02.24-r1 pulled in by: |
| 20 |
> sys-fs/cryptsetup-1.0.6-r2 |
| 21 |
> |
| 22 |
> Does this mean I should emerge lvm2 even though this machine does not |
| 23 |
> use logical volumes? |
| 24 |
> |
| 25 |
> thanks, |
| 26 |
> allan |
| 27 |
|
| 28 |
The sys-fs/lvm2 package just contains utilities, it doesn't require |
| 29 |
you to actually use LVM2. I also use it the same way as you. I now |
| 30 |
have the lvm2 package and not device-mapper and everything still works |
| 31 |
with my encrypted partition. |
Archives