From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev fork
Date: Wed, 12 Sep 2012 18:14:09 +0000 [thread overview]
Message-ID: <20120912181409.GA12840@kroah.com> (raw)
In-Reply-To: <20120912174951.GA32608@glow>
On Wed, Sep 12, 2012 at 06:09:09PM +0000, sickmind@lavabit.com wrote:
> On 13:03 Wed 12 Sep , Bruce Dubbs wrote:
> > sickmind@lavabit.com wrote:
> > > On 17:49 Wed 12 Sep , sickmind@lavabit.com wrote:
> > >> Hi,
> > >>
> > >> I know that many people do not like the way udev development went
> > >> recently, therefore we have a systemd-free fork of udev. At the moment
> > >> most of the changes (except for systemd integration) have been ported,
> > >> and no stability issues are noticed. I hope it will be useful for those
> > >> who don't like systemd being pushed in their systems.
> > >>
> > >> P.S. This maillist seems to be dead for quite a while and most of the
> > >> discussion moved to systemd-related lists, so I hope nobody would mind
> > >> if we use it as our primary maillist.
> > >>
> > >> --
> > >> To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
> > >> the body of a message to majordomo@vger.kernel.org
> > >> More majordomo info at http://vger.kernel.org/majordomo-info.html
> > >
> > > BTW, I totally forgot to include a link to the repo. Here it is:
> > > https://bitbucket.org/braindamaged/udev
> >
> > A fork is way too much effort. The only thing you need is a different
> > Makefile. For a package that is Linux only, using autotools seems to be
> > a tremendous amount of overkill.
> >
> > http://www.linuxfromscratch.org/lfs/view/development/chapter06/udev.html
> > http://anduin.linuxfromscratch.org/sources/other/udev-lfs-189.tar.bz2
> >
> > Works for us.
> >
> > -- Bruce
>
> This is not entirely true. A different makefile might be a temporary
> solution, but udev is already dependent on libsystemd, and I'm afraid
> this process may go much much further.
I don't understand, what specifically is your objection with something
that might happen in the future? And, since it hasn't happened, how can
you object to it?
confused,
greg k-h
next prev parent reply other threads:[~2012-09-12 18:14 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 [this message]
2012-09-12 18:15 ` sickmind
2012-09-12 18:28 ` Greg KH
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=20120912181409.GA12840@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.