From: Tanstaafl <tanstaafl@libertytrek.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] systemd and kernel developers cooperating to turn it into a global cgroup manager?
Date: Sun, 20 Oct 2013 10:01:24 -0400 [thread overview]
Message-ID: <5263E234.4020305@libertytrek.org> (raw)
In-Reply-To: <5263D481.5020403@gentoo.org>
On 2013-10-20 9:02 AM, Samuli Suominen <ssuominen@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?
When did this happen? I thought that OpenRC was still the default?
>> 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?
next prev parent reply other threads:[~2013-10-20 14:02 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 4:27 [gentoo-user] systemd and kernel developers cooperating to turn it into a global cgroup manager? Mark David Dumlao
2013-10-19 15:02 ` Daniel Campbell
2013-10-19 23:35 ` Volker Armin Hemmann
2013-10-20 6:34 ` Daniel Campbell
2013-10-20 7:37 ` Samuli Suominen
2013-10-20 9:24 ` Daniel Campbell
2013-10-20 9:55 ` Samuli Suominen
2013-10-20 10:47 ` Daniel Campbell
2013-10-20 13:02 ` Samuli Suominen
2013-10-20 14:01 ` Tanstaafl [this message]
2013-10-20 14:03 ` Samuli Suominen
2013-10-21 2:34 ` Walter Dnes
2013-10-21 5:31 ` Daniel Campbell
2013-10-21 7:34 ` Samuli Suominen
2013-10-21 7:33 ` Samuli Suominen
2013-10-20 14:05 ` Samuli Suominen
2013-10-23 22:51 ` [gentoo-user] " Steven J. Long
2013-10-24 3:48 ` Daniel Campbell
2013-10-20 9:24 ` [gentoo-user] " Volker Armin Hemmann
2013-10-20 10:52 ` Daniel Campbell
2013-10-20 11:02 ` Volker Armin Hemmann
2013-10-20 11:18 ` Daniel Campbell
2013-10-21 20:33 ` Volker Armin Hemmann
2013-10-22 8:43 ` Daniel Campbell
2013-10-20 14:42 ` Tanstaafl
2013-10-21 1:14 ` Mark David Dumlao
2013-10-21 9:55 ` Tanstaafl
2013-10-21 10:11 ` Mark David Dumlao
2013-10-21 10:27 ` Tanstaafl
2013-10-21 10:48 ` Mark David Dumlao
2013-10-21 10:59 ` Tanstaafl
2013-10-21 11:10 ` Mark David Dumlao
2013-10-21 11:53 ` Tanstaafl
2013-10-21 20:34 ` Volker Armin Hemmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5263E234.4020305@libertytrek.org \
--to=tanstaafl@libertytrek.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox