On 20/10/13 17:01, Tanstaafl wrote: > On 2013-10-20 9:02 AM, Samuli Suominen <ssuomi...@gentoo.org> wrote: >> On 20/10/13 13:47, Daniel Campbell wrote: >>> Like I mentioned in a prior e-mail, the change didn't affect me when it >>> was pushed, and doesn't affect me now. I did recently have to reinstall >>> Gentoo, however (note, going from testing to stable isn't fun ;p), and >>> noticed it when I found Gentoo ships with systemd-udev instead of >>> eudev. > >> Yep, no plans on changing the default sys-fs/udev to anything else, no >> reason to. > > To be clear - you are saying that the new default init system for a > new gentoo install is systemd?
No, I'm saying the default /dev manager in Gentoo has been sys-fs/udev and will be sys-fs/udev > > When did this happen? I thought that OpenRC was still the default? It is. > >>> Perhaps the next time I need to install Gentoo, I'll find a way to get >>> eudev on there before even the first proper boot and avoid the problem >>> altogether. > >> It's true that sys-fs/eudev restored the *broken* rule_generator from >> old sys-fs/udev, you can get it by USE="rule-generator". >> But it's lot saner to keep using sys-fs/udev and just write custom rules >> to rename interfaces based on MACs to like lan*, internet* >> so all in all, currently, using sys-fs/eudev doesn't make sense unless >> you are experimenting/developing for it. > > The problem with this is, what happens if (or maybe *when*?) the > systemd maintainers make a change that then breaks udev for anything > but systemd? > That's a bridge we will cross when there is a bridge to be crossed, but from top of my head: We will maintain a minimal patchset that reverts the offending code. As in, that's nothing to be worried about before it happens.
