On Tue, Mar 13, 2012 at 2:09 AM, Walter Dnes <waltd...@waltdnes.org> wrote:
> On Mon, Mar 12, 2012 at 06:22:39PM -0500, Dale wrote
>
>> I think mdev has shown it can be fixed.  Given time, it just may replace
>> udev then the udev dev can screw up his own stuff on not bother other
>> distros.  I'm giving mdev some thought here.  I want /usr on LVM which
>> means it has to be separate.
>
>  Sorry, in lste-breaking news, it looks like udev is a mandatory
> dependancy for lvm2.  No udev ==> No lvm2

It seems so; from lvm2 2.02.93:

DEPEND_COMMON="!!sys-fs/device-mapper
        readline? ( sys-libs/readline )
        clvm? ( =sys-cluster/dlm-2*
                        cman? ( =sys-cluster/cman-2* ) )
        >=sys-fs/udev-151-r4"

...

        econf $(use_enable readline) \
                $(use_enable selinux) \
                --enable-pkgconfig \
                --with-confdir="${EPREFIX}/etc" \
                --sbindir="${EPREFIX}/sbin" \
                --with-staticdir="${EPREFIX}/sbin" \
                --libdir="${EPREFIX}/$(get_libdir)" \
                --with-usrlibdir="${EPREFIX}/usr/$(get_libdir)" \
                --enable-udev_rules \
                --enable-udev_sync \
                --with-udevdir="${EPREFIX}/lib/udev/rules.d/" \
                ${myconf} \
                CLDFLAGS="${LDFLAGS}" || die

Maybe you could try to modify the LVM ebuild to point udevdir to a
black hole and disable udev_rules and udev_sync. But that would be at
best a hack; I'm not familiar enough with the LVM code to know if they
actually need udev to run, or it only installs some rules so it can
run better with it.

Regards.
-- 
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México

Reply via email to