public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Samuli Suominen <ssuominen@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] udev (viable) alternatives ?
Date: Thu, 25 Sep 2014 21:17:26 +0300	[thread overview]
Message-ID: <54245C36.50507@gentoo.org> (raw)
In-Reply-To: <loom.20140925T172011-995@post.gmane.org>


On 25/09/14 18:25, James wrote:
> Ok,
>
> So I have used eudev before, without issue before. Things are moving along
> so now I see an udev-215 upgrade to udev-261 on a system running lxde.
> I intend to migrate this system to lxqt in the next few weeks, after
> I build up a new workstation.
>
> So changing from udev-215 to eudev-1.10-r2 is as simple as 
> unmerging the former and emerging the latter ? The sytem
> is not tweaked very much and still running a 3.13.6 kernel, for now.
>
>
> Any other caveats (short term) on switching udev to eudev?

no support for kernel side predictable interface names where the naming
should
*really* be happening, eudev will always rename your interfaces with or
without USE="rule-generator"

to be explicit, eudev will ignore /lib/udev/hwdb.d/20-net-ifname.hwdb,
eudev will rename interfaces
marked as predictable by the kernel metadata, as in, eudev doesn't
contain this commit:

http://cgit.freedesktop.org/systemd/systemd/commit/network/99-default.link?id=04b67d49254d956d31bcfe80340fb9df7ed332d3

in fact, from what I last checked, eudev's networking is at same level
with udev-208, from time before the .link support at all

eudev is really useful only for sys-libs/musl users at this time, but
you are free to experiment with it!

- Samuli


  parent reply	other threads:[~2014-09-25 18:21 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-25 15:25 [gentoo-user] udev (viable) alternatives ? James
2014-09-25 17:47 ` Dale
2014-09-25 18:17 ` Samuli Suominen [this message]
2014-09-25 19:03   ` [gentoo-user] " James
2014-09-25 19:32     ` Dale
2014-09-26  0:23     ` Walter Dnes
2014-09-26  3:27       ` Alan McKinnon
2014-09-26  8:07         ` Neil Bothwick
2014-09-26  8:22           ` Canek Peláez Valdés
2014-09-26  8:46             ` Neil Bothwick
2014-09-26  8:47             ` Samuli Suominen
2014-09-26  9:04               ` Samuli Suominen
2014-09-26 16:47                 ` David W Noon
2014-09-27  2:06                   ` Samuli Suominen
2014-09-26  5:04     ` Samuli Suominen
2014-11-10 11:04       ` Tanstaafl
2014-11-10 12:30         ` Rich Freeman
2014-11-10 13:23           ` Tanstaafl
2014-11-10 14:23             ` Rich Freeman
2014-11-10 15:48         ` Samuli Suominen
2014-11-10 16:01           ` Tanstaafl
2014-11-11  5:20           ` Walter Dnes
2014-11-11  5:33             ` Samuli Suominen
2014-11-11  5:35             ` Canek Peláez Valdés
2014-11-11 12:18             ` Rich Freeman
2014-11-13 17:08               ` Walter Dnes
2014-11-17 10:27                 ` Tom H

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=54245C36.50507@gentoo.org \
    --to=ssuominen@gentoo.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