From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev fork
Date: Wed, 12 Sep 2012 21:19:04 +0000 [thread overview]
Message-ID: <20120912211904.GA2652@kroah.com> (raw)
In-Reply-To: <20120912174951.GA32608@glow>
On Wed, Sep 12, 2012 at 03:56:33PM -0500, Bruce Dubbs wrote:
> 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.
Like what? Can't you add them?
> 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.
So you don't offer systemd to any LFS user either?
> >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,
No, that's not why they are switching to systemd.
> but in my opinion systemd is a solution only needed by a very small
> percentage of users.
I don't think you really understand what systemd offers. I don't know
anyone who has used it that has wanted to switch back. Also, it solves
numerous problems that people have been having for years. And further,
it's becoming a requirement for large industry groups that use Linux,
because they too want what it offers.
That's not to say you don't want it, that's fine, I understand, but to
deride it by saying only a small number of users want it is
disingenuous.
> It is quite opaque for new users trying to understand the boot
> process.
The 100+ man pages are not descriptive enough? :)
> We don't use an initrd for the same reason.
That's fine, but then how do you support a separate /usr partition? And
handle kernels built for a wide range of systems?
> The nice thing about Linux is that one size does not have to fit all.
Sure, and that's fine. But I think you are shortchanging your users
here. Again, just my opinion. Best of luck,
greg k-h
next prev parent reply other threads:[~2012-09-12 21:19 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
2012-09-12 21:19 ` Greg KH [this message]
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=20120912211904.GA2652@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.