From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev fork
Date: Wed, 12 Sep 2012 18:28:21 +0000 [thread overview]
Message-ID: <20120912182821.GA13272@kroah.com> (raw)
In-Reply-To: <20120912174951.GA32608@glow>
On Wed, Sep 12, 2012 at 06:15:43PM +0000, sickmind@lavabit.com wrote:
> On 11:05 Wed 12 Sep , Greg KH wrote:
> > On Wed, Sep 12, 2012 at 05:49:52PM +0000, sickmind@lavabit.com wrote:
> > > Hi,
> > >
> > > I know that many people do not like the way udev development went
> > > recently,
> >
> > What specifically are you objecting to?
>
> Extra dependencies and L. Poettering's position that running udev
> without systemd is a dead end and will not be supported in the future
> (this seem to be already discussed here before).
What dependencies? Run time? Build time? And why are dependencies
bad? Do you have no ram in your system for them?
Personally, I think running a Linux system without systemd is a deadend,
but hey, what do I know about these things? :)
> > > therefore we have a systemd-free fork of udev.
> >
> > udev works without systemd running on the system just fine for me,
> > doesn't it for you?
>
> Call me paranoid, but I'm afraid that won't last long.
Fear as a development motivator? That's odd, really?
greg k-h
next prev parent reply other threads:[~2012-09-12 18:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 17:49 udev fork sickmind
2012-09-12 17:51 ` sickmind
2012-09-12 18:05 ` Greg KH
2012-09-12 18:09 ` sickmind
2012-09-12 18:14 ` Greg KH
2012-09-12 18:15 ` sickmind
2012-09-12 18:28 ` Greg KH [this message]
2012-09-12 18:33 ` Lucas De Marchi
2012-09-12 20:56 ` Bruce Dubbs
2012-09-12 21:19 ` Greg KH
2012-09-12 21:30 ` sickmind
2012-09-12 22:11 ` Bruce Dubbs
2012-09-12 23:44 ` Allin Cottrell
2012-09-13 0:14 ` Bruce Dubbs
2012-09-13 0:38 ` Allin Cottrell
2012-09-13 2:29 ` Bruce Dubbs
2012-09-13 2:43 ` Paul Bender
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=20120912182821.GA13272@kroah.com \
--to=greg@kroah.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.