From: Kevyn Shortell <trance@gentoo.org>
To: Jason Stubbs <jasonbstubbs@mailandnews.com>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Speaking of new kernels being added to the tree
Date: Sat, 04 Oct 2003 22:22:58 -0700 [thread overview]
Message-ID: <1065331378.1642.36.camel@localhost> (raw)
In-Reply-To: <200310050828.34578.jasonbstubbs@mailandnews.com>
[-- Attachment #1: Type: text/plain, Size: 2364 bytes --]
>
> I think the main point to the discussion is new users. I, too, have never used
> genkernel so don't know how viable the idea of using it in its current state
> would be. Nor am I admonishing that it should be the "only way to go".
> However, everything in Gentoo is configured, compiled and installed through
> the single emerge command. It would make most sense to me to choose what
> classes of drivers/functionality I wanted through USE flags and then do
> post-installation configuration through /etc/modules.autoload*. Can anyone
> say why the kernel is special and should be done differently? - other than if
> it ain't broke don't fix it!
Because the kernel is much more than that. Linux as a whole has never
setup kernel building for new users, and probably never will. You
actually need to know a lot about your hardware to build an optimized
kernel for it.
To put into basic perspective, if you want to have USE flags for kernel
building, would you know to use something like:
USE="pnp network pci radeon 16550 tulip ohci ps2 ipv4 ext3 idecd ata100
dma
The list goes on and on. There are somethings as a user your going to
just have to decide to learn how to do. If not you can always use the rh
sources, and thier config to have a kernel that will boot almost
anything. Using use flags as you suggested, still requires you to know a
lot about your hardware, which wouldn't help you from using the current
kernel configuration system, which is not gentoo specific.
>
> I'm with almost all other people in that it would not be a high priority for
> some time to come. On the other hand, I'm against people who are putting
> forward arguments that the kernel is somehow special. Almost every other
> package is installed with extra cruft so that can't be used as an excuse.
> Gentoo is about making things easier for everyone which means safe defaults
> and easily accessible complete customisation, so Luke-Jr's idea at least
> deserves consideration rather than instant dismissal.
I don't think anyone has an argument with making things easier, but we
shouldn't make things easier for new users to the detriment of making
things more difficult for everyone else. There is a point where Gentoo
just might be more advanced than a new user is skill wise, and accept
that.
trance
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-05 5:23 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-03 9:36 [gentoo-dev] Speaking of new kernels being added to the tree Brad Laue
2003-10-03 9:54 ` Brad Laue
2003-10-03 18:12 ` C. Brewer
2003-10-03 19:26 ` Donnie Berkholz
2003-10-04 0:41 ` C. Brewer
2003-10-04 2:05 ` Donnie Berkholz
2003-10-04 3:50 ` C. Brewer
2003-10-03 15:34 ` Brian Jackson
2003-10-03 16:23 ` Brad Laue
2003-10-03 17:10 ` Brian Jackson
[not found] ` <3F7DA0C3.3000303@gentoo.org>
2003-10-03 17:10 ` Brian Jackson
2003-10-03 17:15 ` Jon Portnoy
2003-10-03 23:50 ` Luke-Jr
2003-10-03 23:58 ` Kurt Lieber
2003-10-04 0:01 ` Jason Stubbs
2003-10-04 2:16 ` Luke-Jr
2003-10-04 0:15 ` Luke-Jr
2003-10-04 2:25 ` Jon Portnoy
2003-10-04 3:56 ` Luke-Jr
2003-10-04 4:29 ` Jason Stubbs
2003-10-04 12:40 ` Stuart Herbert
2003-10-04 13:10 ` Luke-Jr
2003-10-04 13:51 ` Stuart Herbert
2003-10-04 14:04 ` Luke-Jr
2003-10-04 14:15 ` Stuart Herbert
2003-10-04 14:36 ` Luke-Jr
2003-10-04 15:09 ` Stuart Herbert
2003-10-04 17:20 ` Luke-Jr
2003-10-04 17:58 ` Marius Mauch
2003-10-04 15:56 ` Patrick Börjesson
2003-10-04 17:29 ` Luke-Jr
2003-10-04 18:27 ` Patrick Börjesson
2003-10-04 23:38 ` William Kenworthy
2003-10-05 0:48 ` Patrick Börjesson
[not found] ` <200310050343.49697.sn.ml@bayminer.com>
2003-10-05 1:52 ` William Kenworthy
2003-10-05 2:39 ` Luke-Jr
2003-10-04 13:33 ` Stroller
2003-10-04 14:08 ` William Kenworthy
2003-10-04 14:21 ` Luke-Jr
2003-10-04 14:14 ` Luke-Jr
2003-10-04 16:50 ` Peter Ruskin
2003-10-04 13:50 ` Patrick Börjesson
2003-10-04 13:57 ` Luke-Jr
2003-10-04 16:13 ` Jon Portnoy
2003-10-04 17:25 ` Luke-Jr
2003-10-04 23:28 ` Jason Stubbs
2003-10-05 0:17 ` Kumba
2003-10-05 0:25 ` James Harlow
2003-10-05 0:38 ` Jason Stubbs
2003-10-05 0:48 ` James Harlow
2003-10-05 2:10 ` Kumba
2003-10-05 2:27 ` Jason Stubbs
2003-10-05 2:06 ` Kumba
2003-10-05 2:44 ` Jason Stubbs
2003-10-05 4:54 ` Jon Portnoy
2003-10-05 5:28 ` Kevyn Shortell
2003-10-05 0:50 ` Jason Stubbs
2003-10-05 2:43 ` Luke-Jr
2003-10-05 3:04 ` Kumba
2003-10-05 14:24 ` Luke-Jr
2003-10-05 5:22 ` Kevyn Shortell [this message]
2003-10-05 11:30 ` Jason Stubbs
[not found] ` <200310051741.28963.sn.ml@bayminer.com>
2003-10-05 14:47 ` Jason Stubbs
2003-10-05 15:53 ` Luke-Jr
2003-10-05 16:05 ` Luke-Jr
2003-10-04 13:06 ` Luke-Jr
2003-10-04 6:16 ` Donnie Berkholz
2003-10-04 6:34 ` Kumba
2003-10-04 7:27 ` Kevyn Shortell
2003-10-04 13:16 ` Luke-Jr
2003-10-04 2:03 ` Stroller
2003-10-04 2:08 ` Donnie Berkholz
2003-10-04 4:08 ` Stroller
-- strict thread matches above, loose matches on Subject: below --
2003-10-05 18:24 Sami Näätänen
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=1065331378.1642.36.camel@localhost \
--to=trance@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=jasonbstubbs@mailandnews.com \
/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