From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev fork
Date: Wed, 12 Sep 2012 20:56:33 +0000 [thread overview]
Message-ID: <5050F701.7020504@gmail.com> (raw)
In-Reply-To: <20120912174951.GA32608@glow>
Greg KH wrote:
> What dependencies? Run time? Build time? And why are dependencies
> bad? Do you have no ram in your system for them?
The configure scripts require packages that are not in LFS. We do not
want to add them just to satisfy a systemd build that we don't want.
However creating a custom Makefile to build udev from the current
systemd sources was not particularly hard.
> Personally, I think running a Linux system without systemd is a deadend,
> but hey, what do I know about these things? :)
I understand that big distros only want to support one methodology, but
in my opinion systemd is a solution only needed by a very small
percentage of users. It is quite opaque for new users trying to
understand the boot process. We don't use an initrd for the same reason.
The nice thing about Linux is that one size does not have to fit all.
-- Bruce
linuxfromscratch.org - Your distro, your rules.
next prev parent reply other threads:[~2012-09-12 20:56 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
2012-09-12 18:33 ` Lucas De Marchi
2012-09-12 20:56 ` Bruce Dubbs [this message]
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=5050F701.7020504@gmail.com \
--to=bruce.dubbs@gmail.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 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 NNTP newsgroup(s).