From: Jason Stubbs <jasonbstubbs@mailandnews.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Speaking of new kernels being added to the tree
Date: Sun, 5 Oct 2003 09:50:57 +0900 [thread overview]
Message-ID: <200310050950.57147.jasonbstubbs@mailandnews.com> (raw)
In-Reply-To: <3F7F6307.1080001@gentoo.org>
On Sunday 05 October 2003 09:17, Kumba wrote:
> Jason Stubbs wrote:
> > 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!
>
> Honestly, the kernel is special. Everyone has a different x86
> machine...different NIC card, sound card, video card, motherboard, IDE
> chipset, scsi card, CPU....Some have V4L, some have I2C stuff, some have
> parallel ports, some have ISA, some have PCI, some have both, some have
> serial console, some have radeons, some have nvidias.....See the point?
What I was thinking with the USE flag idea was that "audio", for example,
would build all of the audio drivers, etc. Similar to what "emerge xfree"
does.
> x86 is *way* too diverse an architecture to configure solely through USE
> Flags. How can it be set so we know whether someone has a VIA IDE
> chipset and not an SiS, or how someone have a RealTek 8139-based NIC
> card, and whether they need the old RealTek driver, or the newer one?
Hmmm... it is safe to build in drivers for several chipsets, if not a little
bloated. The old/new realtek driver couldn't be handled, however. But that's
why it would be imperative to have a source extraction option to mimic what
is presently done.
> As much as we all love Gentoo for it's ability to configure things
> easily (in most cases), the kernel to me is just that one little nuance
> that stands apart from the base system. Everyone should learn how to
> configure their kernel, in my opinion. It is probably the one thing
> every linux distro should teach people how to do. The advantages far
> outweigh the disadvantages, and by building their own kernel, the user
> becomes aware of what is inside their machine.
I agree that all users should really know how to build a kernel. But I also
think that every user should know how to download a source tarball and
compile and install it manually. Knowledge is power...
All in all, I'm happy with the way things are done now. I'm just a firm
believer in standards.
Jason
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-10-05 0:54 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 [this message]
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
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=200310050950.57147.jasonbstubbs@mailandnews.com \
--to=jasonbstubbs@mailandnews.com \
--cc=gentoo-dev@gentoo.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