From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Managing my kernel
Date: Thu, 17 May 2007 13:17:05 -0700 [thread overview]
Message-ID: <49bf44f10705171317ia37675dp147fb73a0b77e4b8@mail.gmail.com> (raw)
In-Reply-To: <200705141809.37504.volker.armin.hemmann@tu-clausthal.de>
> > I've been puzzling a bit lately over the best way to manage my kernel.
> > I've always tried to keep it as minimal as possible, and I only
> > enable things as I need them. I also don't build modules from the
> > kernel at all.
> >
> > Is there a better way to go? I'm starting to think it might be better
> > to build every single module and let the system load them as it needs
> > them.
> >
> > - Grant
>
> well, from my point of view:
>
> everything needed for booting: in kernel
> everything needed all the time: in kernel
> everything that needs a good kicking once in a while (usb, sound): modules
> everything that needs parameters: modules
> everything that is not needed all the time: module
So you don't leave anything unbuilt? Is there any real disadvantage
to that as long as you modularize as much as possible? It sounds
delightfully simple to go that route. That would be a really portable
kernel too.
- Grant
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-05-17 20:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 15:48 [gentoo-user] Managing my kernel Grant
2007-05-14 16:09 ` Hemmann, Volker Armin
2007-05-14 22:37 ` Aleksandar L. Dimitrov
2007-05-14 21:16 ` Neil Bothwick
2007-05-15 2:16 ` Aleksandar L. Dimitrov
2007-05-17 20:17 ` Grant [this message]
2007-05-14 18:18 ` Dale
2007-05-15 0:33 ` Mark Kirkwood
2007-05-15 1:57 ` Dan Farrell
2007-05-15 7:21 ` Etaoin Shrdlu
2007-05-15 19:49 ` Dan Farrell
2007-05-15 20:06 ` Boyd Stephen Smith Jr.
2007-05-17 6:38 ` Mark Kirkwood
-- strict thread matches above, loose matches on Subject: below --
2007-05-15 0:54 burlingk
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=49bf44f10705171317ia37675dp147fb73a0b77e4b8@mail.gmail.com \
--to=emailgrant@gmail.com \
--cc=gentoo-user@lists.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