From: "Theodore Ts'o" <tytso@mit.edu>
To: andreas.thalhammer@linux.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Re for el_es: A Desktop Linux idea: modulized open hardware database for the linux kernel config
Date: Sun, 3 Nov 2013 15:02:27 -0500 [thread overview]
Message-ID: <20131103200227.GC7376@thunk.org> (raw)
In-Reply-To: <201311031957.29584.andreas.thalhammer@linux.com>
On Sun, Nov 03, 2013 at 07:57:29PM +0100, andreas.thalhammer@linux.com wrote:
>
> I’m sorry, but I cannot possibly do this all by myself. I was able
> to help in some Wikis and in Smolt, but I cannot setup such a
> system. Apparently I was only able to come up with the idea...
It's an idea that people have tossed around before, but utltimately,
it's far more work than it's worth, and it's a maintenance nightmare.
For most non-technical users, using a distro kernel is quite good
enough.
For power users, they have no trouble configuring their own custom
kernel --- they can start with a full distribution kernel config, run
"make localmodconfig" which will compile a kernel with the currently
loaded modules (which are presumably the ones required for your
hardware) compiled into the kernel, and then the power user can then
disable those modules that he or she does't think they'll ever need.
The set of people who aren't willing to use a distribution kernel, but
aren't clueful enough to figure out how to customize their own kernel,
is a pretty small set. And it's certainly not big enough such that
those of us who could implement such an idea would think that it's
worth the huge amount of effort it would require, and how to deal with
the enusing support burden when clueless end-users try to use it, and
then complain when the information is out of date.
If you told me that you wanted to try it, I would tell you that you
were going to be getting into a huge amount of work, and it's not
obvious to me that it's worth it --- but if you are going to volunteer
your own time, then it's ultimately up to you. But having you trying
to volunteer *other* people's time for what might be a sisyphean does
take a fair amount of chutzpah.
Regards,
- Ted
next prev parent reply other threads:[~2013-11-03 20:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-03 14:53 A Desktop Linux idea: modulized open hardware database for the linux kernel config andreas.thalhammer
2013-11-03 16:18 ` Aldo Iljazi
2013-11-03 16:43 ` andreas.thalhammer
2013-11-03 17:42 ` el_es
2013-11-03 18:53 ` andreas.thalhammer
2013-11-03 18:57 ` Re for el_es: " andreas.thalhammer
2013-11-03 20:02 ` Theodore Ts'o [this message]
2013-11-03 22:03 ` [Topic closed] " andreas.thalhammer
2013-11-12 22:13 ` Pavel Machek
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=20131103200227.GC7376@thunk.org \
--to=tytso@mit.edu \
--cc=andreas.thalhammer@linux.com \
--cc=linux-kernel@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