[systemd-devel] killing udev for non-systemd systems

2012-08-14 Thread William Hubbs
Hey Lennart, Kay and all,

On Wed, Aug 01, 2012 at 06:58:39PM +0200, Lennart Poettering wrote:
 Well, we intent to continue to make it possible to run udevd outside of
 systemd. But that's about it. We will not polish that, or add new
 features to that or anything.
 
 OTOH we do polish behaviour of udev when used *within* systemd however,
 and that's our primary focus.
 
 And what we will certainly not do is compromise the uniform integration
 into systemd for some cosmetic improvements for non-systemd systems.
 
 (Yes, udev on non-systemd systems is in our eyes a dead end, in case you
 haven't noticed it yet. I am looking forward to the day when we can drop
 that support entirely.)

There are a number of reasons from what I see on my distro's development
list and from what I've seen insome patches proposed here, that everyone
isn't comfortable with systemd.

I thought the merge was more for administrative reasons, because there
is common source code between systemd and udev that you did not want to
provide as libraries.

Now though, with the attitude toward non-systemd systems that I see
above, I am starting to wonder.

You have taken a piece of software which is important to many linux
systems (udev) and merged it into an init system (systemd) which is not
used everywhere for a number of reasons. Now you are planning to kill
udev for systems that do not use systemd. Why is that? Why are you
saying that udev on non-systemd systems is a dead end?

Is there some alternative for non-systemd systems?

William



pgp0yNhUoOJ4y.pgp
Description: PGP signature
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] killing udev for non-systemd systems

2012-08-14 Thread Colin Guthrie
'Twas brillig, and William Hubbs at 14/08/12 19:01 did gyre and gimble:
 You have taken a piece of software which is important to many linux
 systems (udev) and merged it into an init system (systemd) which is not
 used everywhere for a number of reasons. Now you are planning to kill
 udev for systems that do not use systemd. Why is that? Why are you
 saying that udev on non-systemd systems is a dead end?
 
 Is there some alternative for non-systemd systems?

I think you're over reacting here.

The comment about it being a dead end is likely more related to how
device management and service management are *very* closely linked
sometimes - especially if you want to do things properly and non-racy
without lots of good will sprinkled over things in the hope that they
glue together OK. So to get the most out of udev and do things properly
you *need* to integrate properly with the init system. That's what I
read from the dead end statement anyway.

While I'm sure Lennart and Kay are looking forward to the day they can
drop any semblance of support for a separate udev entirely, I doubt very
much it's any time in the next little while (although I'm always
prepared to be proved wrong).

And besides, even if they do it's easy enough to fork using git and
maintain a separate version while still sharing most of the code if that
floats your boat.

I suspect in a few years time we'll see a much more focused systemd
world anyway and the people who are not using it now for whatever reason
will see the light/drink the kool-aid :p

Col

-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited http://www.tribalogic.net/
Open Source:
  Mageia Contributor http://www.mageia.org/
  PulseAudio Hacker http://www.pulseaudio.org/
  Trac Hacker http://trac.edgewall.org/

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel