1 |
On Wed, Jul 11, 2012 at 10:06 AM, Rich Freeman <rich0@g.o> wrote: |
2 |
> On Wed, Jul 11, 2012 at 9:49 AM, Michael Mol <mikemol@×××××.com> wrote: |
3 |
>> Walter Dnes (very active over in gentoo-user) has put a lot of work |
4 |
>> into testing and documenting mdev as an alternative for udev. There's |
5 |
>> been a good deal of success there, up to and including it working with |
6 |
>> GNOME 2. The work's been documented on the wiki: |
7 |
>> https://wiki.gentoo.org/wiki/Mdev |
8 |
> |
9 |
> Unless you plan to stay on Gnome 2 forever or fork it you might want |
10 |
> to consider that Gnome at some point is going to require systemd, let |
11 |
> alone udev. Whether that happens or not remains to be seen. |
12 |
> |
13 |
> Not that mdev doesn't have its uses, but you're probably not going to |
14 |
> be running future releases of Gnome on it. |
15 |
|
16 |
I only mention Gnome 2 as an indicator of an example of system |
17 |
complexity support achieved. I don't know what's going to happen with |
18 |
future app interdependency with udev and systemd any more than anyone |
19 |
else. |
20 |
|
21 |
What's the generic laconic description of what udev and mdev do? |
22 |
Hotplug event handler? Is there a significant reason Gentoo shouldn't |
23 |
support selecting between such handlers? At the point where there's |
24 |
discussion between using systemd's in-tree copy of udev and a fork of |
25 |
udev, it seems appropriate to examine the possibility of a more |
26 |
general selection mechanism. |
27 |
|
28 |
Admittedly, with increased generality comes increased complexity. I |
29 |
don't know exactly where increased long-term complexity would come |
30 |
from, but my first guess would be redirecting where packages dependent |
31 |
on hooking the hotplug handler place their scripts. Anything else I |
32 |
can think of sounds more like an up-front effort cost, and not a |
33 |
long-term one. |
34 |
|
35 |
-- |
36 |
:wq |