Hi, Rich Freeman wrote: > On Tue, Feb 25, 2014 at 6:39 AM, Thomas D. <whi...@whissi.de> wrote: >> Also, I cannot belief that I cannot overwrite >> "/lib/udev/rules.d/80-net-setup-link.rules" via "/etc/udev/rules.d"... > > I don't see why not - from the news item: > So, to clarify, you can override the new .rules file or the .link file in /etc > but using the kernel parameter is the most consistent way.
Maybe I am wrong, but when talking about kernel parameter we are talking only about net.ifnames= right? So with this parameter we can only disable the new naming, right? But as said, I am using udev to name my interfaces -- the new kernel naming isn't my problem. I don't understand how this should help me. My fear is that all my routers and servers with multiple interfaces won't come up anymore after the upgrade because they don't have my custom names anymore because due to the new rule, udev didn't or failed to rename... >> Don't get me wrong. Yes, I don't use systemd and I am a happy OpenRC >> user but I have no problems with systemd (as long as it doesn't affects >> me). But this upgrade seems to affect non-systemd users. >> > > The only thing that changed is the location where a config setting is > stored. Nobody has to use systemd as a sysvinit replacement. Have you read documentation? It is not about locations at all... my problem is that it seems like that I have to use a new syntax from systemd-udev when doing something in "/etc/systemd" but as said: I am using sys-fs/udev, I don't care about systemd... why should I learn systemd when I am only using udev? >> Wasn't Gentoo about choices? > > Well, we generally don't give users a choice in where config files are > installed. No, not locations. My choice was not to use systemd. Now a package, sys-fs/udev, turns into systemd-udev... Also: If it wouldn't be possible to keep sys-fs/udev as it was I wouldn't bother that much. But as said, Lars (Polynomial-C) showed us that we don't need to turn sys-fs/udev into systemd-udev... So I am asking why we are doing that for people who don't use systemd? Polynomical-C doesn't uses much patches... no, the magic is in the ebuild. Upstream still supports the "old" usage... it is the Gentoo ebuild which turns the package into systemd-udev... And that's what I meant when I said "give something 'back'": It should be possible to create an ebuild for systemd and non-systemd users. Yes, more maintenance is needed. But taking a package which was working fine for non-systemd users and transform it into a systemd package isn't nice and fair. You get my point? -Thomas
