On Tue, Nov 10, 2009 at 4:08 PM, Dale <rdalek1...@gmail.com> wrote: > Neil Bothwick wrote: >> On Tue, 10 Nov 2009 22:39:24 +0200, Alan McKinnon wrote: >> >> >>> You likely don;t need it then. device-mapper is only used by lvm and >>> software- raid type packages. If you use those, you will know about it >>> >> >> It's also used by cryptsetup. >> >> >> > > Yup, I'm not sure if I am using that or not. I don't think so but I > don't want to remove it without making sure. Be my luck it will blow up > or something. lol This is what equery returns tho: > > sys-apps/hal-0.5.13-r2 (kernel_linux & crypt? >=sys-fs/cryptsetup-1.0.5) > sys-apps/pmount-0.9.20 (crypt? >=sys-fs/cryptsetup-1.0.5) > > Don't get me started on hal. Is this a USE flag thing? I need to check > on this more. > > Dale > > :-) :-)
Well, if you're not using encrypted partitions, you're not using cryptsetup. Hal's (and by the looks of it, pmount's) use of the crypt use flag pulls in cryptsetup, and in turn, all its dependencies. If you're not using cryptsetup, just put sys-apps/hal -crypt into your package.use list, and if you use pmount as well, the equivalent for it. That should drop any dependency on cryptsetup, and if cryptsetup's the only thing pulling in lvm2 (and previously device-mapper), that'll no longer be depended on either. -- Poison [BLX] Joshua M. Murphy
