From: "John Heim" <jheim@math.wisc.edu>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: compiling linux kernel
Date: Fri, 22 Aug 2008 12:22:33 -0500 [thread overview]
Message-ID: <018601c9047b$a9cf3f70$4ba65c90@vv507j> (raw)
In-Reply-To: <20080821182536.GA4528@implementation>
----- Original Message -----
From: "Samuel Thibault" <samuel.thibault@ens-lyon.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Thursday, August 21, 2008 1:25 PM
Subject: Re: compiling linux kernel
Tyler Littlefield, le Thu 21 Aug 2008 12:19:07 -0600, a écrit :
> I don't want to use my kernel that came with deb because it's huge, and I
> think I might get some better performance if there wasn't so much there,
> in terms of everything being modules, etc.
There is _no_ performance loss in everything being a module. Really,
there is little point in using one's own kernel nowadays (except
applying patches).
And bragging rights.
Well, I suppose that would only work on the uninformed. If you tell someone
in the know that you're using a custom kernel they might think you're a
dope.
When I was fairly new to linux, I ran into somebody at a party and the
conversation turned to how we spent our spare time. I said I was trying to
get up to speed on linux. This other guy said he was into linux too so I
asked which distro. He said, "I make my own." At the time I was very
impressed. But now I say, "What a waste of time."
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
Tyler Littlefield
` Samuel Thibault
` Tyler Littlefield
` Gregory Nowak
` Tyler Littlefield
` Tyler Spivey
` Tyler Littlefield
` John Heim [this message]
` Tyler Littlefield
` luke
` Gregory Nowak
` Samuel Thibault
` Georgina Joyce
` luke
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='018601c9047b$a9cf3f70$4ba65c90@vv507j' \
--to=jheim@math.wisc.edu \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).