From: Robby Workman <rw@rlworkman.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: systemd 183 and /lib/udev/devices/
Date: Mon, 28 May 2012 04:45:20 +0000 [thread overview]
Message-ID: <20120527234520.2440ba79@liberty.rlwhome.lan> (raw)
In-Reply-To: <alpine.LNX.2.01.1205271034530.1246@waverley.dhcp.wfu.edu>
On Sun, 27 May 2012 11:20:43 -0700
Paul Bender <pebender@san.rr.com> wrote:
> The sooner we fork udev, the better.
Well, I'm not pleased with the direction it's gone either, but I
am also aware that a fork to maintain udev is a lot of work that
will mostly be monotonous, boring, and time consuming. I don't
want to do it, and I doubt anyone else does either, especially
since it *is* possible to build standalone udev from the systemd
sources.
This is currently untested and should be considered a work in
progress, but it might serve as a useful starting point for
someone:
http://connie.slackware.com/~rworkman/standalone-udev-from-systemd/
-RW
prev parent reply other threads:[~2012-05-28 4:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-27 14:46 systemd 183 and /lib/udev/devices/ Allin Cottrell
2012-05-27 14:50 ` Tom Gundersen
2012-05-27 16:17 ` Allin Cottrell
2012-05-27 16:24 ` Tom Gundersen
2012-05-27 17:39 ` Bryan Kadzban
2012-05-27 18:20 ` Paul Bender
2012-05-27 20:00 ` Greg KH
2012-05-27 20:14 ` Kay Sievers
2012-05-27 20:51 ` Allin Cottrell
2012-05-28 4:45 ` Robby Workman [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=20120527234520.2440ba79@liberty.rlwhome.lan \
--to=rw@rlworkman.net \
--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).