linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Colin Guthrie <gmane@colin.guthr.ie>
To: linux-hotplug@vger.kernel.org
Subject: Re: killing udev for non-systemd systems
Date: Tue, 14 Aug 2012 22:20:51 +0000	[thread overview]
Message-ID: <k0ej03$nqc$1@dough.gmane.org> (raw)
In-Reply-To: <20120814180111.GA7801@linux1>

'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/


      reply	other threads:[~2012-08-14 22:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-14 18:01 killing udev for non-systemd systems William Hubbs
2012-08-14 22:20 ` Colin Guthrie [this message]

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='k0ej03$nqc$1@dough.gmane.org' \
    --to=gmane@colin.guthr.ie \
    --cc=linux-hotplug@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).