From: Krzysztof Halasa <khc@pm.waw.pl>
To: Matthias Andree <matthias.andree@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why don't we separate menuconfig from the kernel?
Date: 19 Sep 2005 18:28:38 +0200 [thread overview]
Message-ID: <m38xxt58eh.fsf@defiant.localdomain> (raw)
In-Reply-To: <20050919071521.GB14601@merlin.emma.line.org>
Matthias Andree <matthias.andree@gmx.de> writes:
> One of Linux's main problems is that all daemons that drive kernel core
> functionality are cluttered over various separate projects. While this
> allows for independent development, it's annoying if you need to hunt
> down the various daemons (udev, autofs, hotplug, iproute, to name the
> first that come to mind) only to find out the new version doesn't suit
> your distro. I'd rather wish there was a standard kernel "daemons"
> package.
Who would select what is a standard kernel daemon and what is not?
Who would maintain the package?
> Why should other projects that recycle kernel code impact how the kernel
> itself is made.
It's NOT kernel code.
--
Krzysztof Halasa
next prev parent reply other threads:[~2005-09-19 16:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-17 17:16 Why don't we separate menuconfig from the kernel? Krzysztof Halasa
2005-09-17 17:33 ` Michal Piotrowski
2005-09-17 19:18 ` Krzysztof Halasa
2005-09-18 0:46 ` Jesper Juhl
2005-09-18 0:56 ` Randy.Dunlap
2005-09-18 0:58 ` Jesper Juhl
2005-09-18 1:05 ` Krzysztof Halasa
2005-09-18 1:16 ` Jesper Juhl
2005-09-18 10:33 ` Krzysztof Halasa
2005-09-18 20:40 ` Daniel Barkalow
2005-09-19 7:15 ` Matthias Andree
2005-09-19 16:28 ` Krzysztof Halasa [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-18 1:53 Martin Fouts
2005-09-18 7:30 ` Sam Ravnborg
2005-09-18 10:36 ` Krzysztof Halasa
2005-09-18 10:55 ` Ian Campbell
2005-09-18 7:50 Martin Fouts
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=m38xxt58eh.fsf@defiant.localdomain \
--to=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@gmx.de \
/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