public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Florian Philipp <lists@f_philipp.fastmail.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: A pared down kernel config
Date: Mon, 07 Jan 2008 22:03:41 +0100	[thread overview]
Message-ID: <1199739821.6048.33.camel@NOTE_GENTOO64.PHHEIMNETZ> (raw)
In-Reply-To: <871w8ulf4s.fsf@newsguy.com>

[-- Attachment #1: Type: text/plain, Size: 1325 bytes --]


On Sun, 2008-01-06 at 17:15 -0600, reader@newsguy.com wrote:
> Florian Philipp <lists@f_philipp.fastmail.net> writes:
> 
> >> There's a reason for the existence of genkernel - it's so that you don't 
> >> have to go through all this pain and suffering, and can instead remove 
> >> stuff a bit at a time with reasonable confidence it won;t blow up in 
> >> your face :-)
> >> 
> >
> > There is a fairly easy trick to get rid of pointless options like unused
> > drivers even if you are not sure about your hardware or the kernel
> > options themselves: 
> > Compile them as modules, then boot the new kernel. If the modules don't
> > get loaded (lsmod is your friend) and everything works fine, throw them
> > out of your configuration.
> 
> Nice... a small question: how do you keep up with what gets installed?
> Do you ferret them out at /lib/modules with cmds like 
> find . -name '*.ko'
> 
> Or is there a log created at compile time.. or maybe create one like
> make modules_intall >mymod.log.  Just thinking outload.
> 
> Following a `genkernal all' I saw a very big list get installed but didn't
> think to log them.
> 
> I guess it would be harmless to just run the `make modules_intall' part
> again and catch a list.
> 

I think you search for "modprobe -l" :)

Have a nice day!

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-01-07 20:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-05 16:05 [gentoo-user] A pared down kernel config reader
2008-01-05 16:19 ` Hemmann, Volker Armin
2008-01-05 17:18   ` [gentoo-user] " reader
2008-01-05 17:32     ` Hemmann, Volker Armin
2008-01-05 18:21       ` reader
2008-01-05 19:45         ` Alan McKinnon
2008-01-05 23:18           ` reader
2008-01-05 23:23             ` reader
2008-01-06  0:45             ` Hemmann, Volker Armin
2008-01-06  6:58               ` Yahya Mohammad
2008-01-06 11:57                 ` Jan-Hendrik Zab
2008-01-06  8:08             ` Alan McKinnon
2008-01-05 20:56     ` Erik
2008-01-05 23:02       ` reader
2008-01-06  8:19         ` Alan McKinnon
2008-01-05 17:06 ` [gentoo-user] " Alan McKinnon
2008-01-06 10:38   ` Florian Philipp
2008-01-06 23:15     ` [gentoo-user] " reader
2008-01-07 21:03       ` Florian Philipp [this message]
2008-01-08  0:49         ` reader
2008-01-05 19:00 ` [gentoo-user] " Dale
2008-01-06 13:12 ` Stroller

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=1199739821.6048.33.camel@NOTE_GENTOO64.PHHEIMNETZ \
    --to=lists@f_philipp.fastmail.net \
    --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