On Sun, Jun 8, 2014 at 2:34 PM, Tanstaafl <tansta...@libertytrek.org> wrote: > > Question 1: > What if I am not using an empty (or single comment) > /etc/udev/rules.d/80-net-name-slot.rules? > > Does this mean I can ignore everything that follows (the comment really > should open with that if so)?
Yes > > Question 2: What is up with the last section talking about the net setup > rules only with respect to systemd? > > OpenRC is currently still the default init system for gentoo if I'm not > mistaken, so why does this comment only reference systemd, totally ignoring > OpenRC users? Nothing in this news item has anything to do with anybody who is using the sys-apps/systemd package (at least, they're not impacted by this particular upgrade). sys-fs/udev installs its default network configuration rules in the path /lib/systemd/network/, and if you want to override them you do this in /etc/systemd/network. If you do have sys-apps/systemd installed then you can override the rules in the same place, but the news item is about an upgrade to sys-fs/udev. If you missed the news, systemd took over udev ages ago, and has been renaming paths/binaries/etc. It still does the same things it did before the takeover. You will just see more references to systemd in path names. With just udev the only thing the network scripts do is control interface naming (I think). If you do migrate to systemd the more recent versions include systemd-networkd which can also configure the network. I've found that this works fairly well so far. It seems to be keeping my dhcp lease alive, which is more than I can say about dhcpcd after the last dracut upgrade (the box would drop off the network every 24h, and then lock up being that root was via nfs). Rich
