These messages appears in the journal every boot (and likely every time new network device is attached): окт. 21 16:56:24 <HOSTNAME> /etc/init.d/net.enp2s5[509]: net.enp2s5: not allowed to be hotplugged They are caused by sys-fs/udev-init-scripts. $ equery belongs /lib/udev/rules.d/90-network.rules * Searching for /lib/udev/rules.d/90-network.rules ... sys-fs/udev-init-scripts-26 (/lib/udev/rules.d/90-network.rules) $ cat /lib/udev/rules.d/90-network.rules # do not edit this file, it will be overwritten on update # /etc/udev/rules/90-network.rules: triggering network init-scripts # Activate our network if we can SUBSYSTEM=="net", ACTION=="add", RUN+="net.sh %k start" SUBSYSTEM=="net", ACTION=="remove", RUN+="net.sh %k stop" May be we can override 90-network.rules with systemd generator or any other way? And actually I don't like hard dep on udev-init-scripts. =/
This can be "fixed" the same way as networkmanager: by adding the following code to net.sh if [ ! -e "/run/openrc/softlevel" ]; then # OpenRC is not running exit 0 fi
Related to bug 487922. One workaround would be this: ln -s /dev/null /etc/udev/rules.d/90-network.rules
(In reply to Mike Gilbert from comment #2) > Related to bug 487922. > Oh.. Yes, it would be better to move net.sh and 90-network.rules to netifrc package.
I don't think we need 2 bugs for 1 issue. *** This bug has been marked as a duplicate of bug 487922 ***
