From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: decrapify your kernel config WAS: ps shows pegasus process running - what is it?
Date: Sun, 8 Nov 2009 22:41:08 +0000 [thread overview]
Message-ID: <6D611A39-D2CB-4084-8EFE-B2EF74D9F445@stellar.eclipse.co.uk> (raw)
In-Reply-To: <4AF7443D.7070708@gmail.com>
On 8 Nov 2009, at 22:20, Dale wrote:
> ...
> You seem to think it takes a rocket scientist to build a kernel, it
> doesn't. You just have to know what hardware you have and then enable
> the features you need. ... You can config a kernel in less than five
> minutes most likely then compile and you are done.
Thus we get 30-post long threads titled "kernel build - back in the
soup".
Sure, I might on this occasion prefer that this pegasus driver wasn't
compiled statically into the kernel, but only because it _confused_ me
(nothing more). Far more frequently I want to install Linux on a new
box or plug in a new piece of hardware and not have to worry about
what driver it uses - I just want the module to be there and to auto-
load.
Any time I spend messing with obscure kernel config options is time I
could be spending reading a good book, instead [1].
Sorry, spending time configuring my kernel loses, as does this thread.
Stroller.
[1] Feel free to spend with your kids, lying on a beach, skiing, or
whatever, as alternatives.
next prev parent reply other threads:[~2009-11-08 22:41 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-07 9:45 [gentoo-user] ps shows pegasus process running - what is it? Stroller
2009-11-07 10:01 ` Volker Armin Hemmann
2009-11-07 11:28 ` Stroller
2009-11-07 11:32 ` Volker Armin Hemmann
2009-11-07 23:51 ` [gentoo-user] Re: decrapify your kernel config WAS: " Stroller
2009-11-08 0:10 ` Volker Armin Hemmann
2009-11-08 0:24 ` Stroller
2009-11-08 0:50 ` Volker Armin Hemmann
2009-11-08 6:55 ` Dale
2009-11-08 21:20 ` Stroller
2009-11-08 21:35 ` Alan McKinnon
2009-11-08 22:20 ` Dale
2009-11-08 22:34 ` Alan McKinnon
2009-11-08 23:02 ` Dale
2009-11-08 23:08 ` Zeerak Waseem
2009-11-08 23:18 ` Alan McKinnon
2009-11-08 23:23 ` Stroller
2009-11-08 23:52 ` Dale
2009-11-08 22:41 ` Stroller [this message]
2009-11-08 22:51 ` Alan McKinnon
2009-11-08 23:21 ` Stroller
2009-11-08 23:40 ` Alan McKinnon
2009-11-08 23:05 ` Harry Putnam
2009-11-08 23:31 ` Volker Armin Hemmann
2009-11-09 16:56 ` Harry Putnam
2009-11-08 23:41 ` Dale
2009-11-08 23:28 ` Volker Armin Hemmann
2009-11-08 10:10 ` Florian Philipp
2009-11-08 10:24 ` Dale
2009-11-17 23:16 ` [gentoo-user] Re: decrapify your kernel config Stefan G. Weichinger
2009-11-17 23:26 ` Volker Armin Hemmann
2009-11-18 7:18 ` Alan McKinnon
2009-11-18 9:58 ` Volker Armin Hemmann
2009-12-02 18:46 ` Stefan G. Weichinger
2009-12-02 21:01 ` [gentoo-user] Re: OT: threads in thunderbird (WAS:decrapify your kernel config) Stefan G. Weichinger
2009-12-02 23:57 ` Zeerak Waseem
2009-12-03 0:14 ` Neil Bothwick
2009-12-03 11:43 ` Sebastian Beßler
2009-12-02 21:42 ` [gentoo-user] Re: decrapify your kernel config Stefan G. Weichinger
2009-11-18 14:43 ` daid kahl
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=6D611A39-D2CB-4084-8EFE-B2EF74D9F445@stellar.eclipse.co.uk \
--to=stroller@stellar.eclipse.co.uk \
--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