Bug 408379 – sys-fs/udev should depend on sys-fs/udev-init-scripts conditionally

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Canek Peláez Valdés 2012-03-15 17:05:28 UTC]

sys-fs/udev depends on sys-fs/udev-init-scripts. All the files installed by sys-fs/udev-init-scripts (with the possible exception of 40-gentoo.rules) are redundant to a Gentoo machine running with systemd. Being able to optionally not install sys-fs/udev-init-scripts would be nice; perhaps with a "+openrc" USE flag, set by default.

Reproducible: Always

[Comment 1 William Hubbs 2012-03-19 14:13:00 UTC]

The only reason I am hesitating on this bug is
/etc/modprobe.d/blacklist.conf. Do systemd systems need this file?

[Comment 2 Canek Peláez Valdés 2012-03-19 18:54:46 UTC]

(In reply to comment #1)
> The only reason I am hesitating on this bug is
> /etc/modprobe.d/blacklist.conf. Do systemd systems need this file?

I don't think so. systemd depends on udev, and new versions of udev on kmod, and kmod man pages have no mention of "blacklist.conf". In fact, the only reference in kmod to blacklists is (I believe) in the context of aliases for modules.

From the man page of modprobe.conf:

"blacklist modulename

            Modules can contain their own aliases: usually these are aliases
            describing the devices they support, such as "pci:123...".  These
            "internal" aliases can be overridden by normal "alias" keywords,
            but there are cases where two or more modules both support the same
            devices, or a module invalidly claims to support a device that it
            does not: the <command>blacklist</command> keyword indicates that
            all of that particular module's internal aliases are to be ignored."

These blacklists can be specified in any *.conf file inside /etc/modprobe.d. I myself am not using /etc/modprobe.d anymore.

[Comment 3 William Hubbs 2012-03-20 04:48:40 UTC]

This has been fixed in udev-182.