From: "Doug Sutherland" <doug@proficio.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: moving from amd to p3?
Date: Sun, 17 Jun 2007 00:18:57 -0500 [thread overview]
Message-ID: <00b901c7b09f$01b66dd0$ab00a8c0@tenstac> (raw)
In-Reply-To: <20070617034325.GA27838@localhost.localdomain>
I didn't know that make oldconfig would recognize new
options and prompt you for them. I guess that's because
I don't usually use oldconfig. Since having the right config
is the most important part of the kernel build, I always do
it from scratch, with only the new source tree and nothing
old in there. Perhaps I'm a glutton for punishment. hehe.
But for those who haven't compiled kernel, it's really
not that hard. Like most things, there's only one way to
learn, by screwing up a few times and making kernels
that won't boot, and learning how to recover from that,
learning by trial and error what some of those drivers
are and are not. I also highly recommend doing the
linuxfromscratch thing if you have the time and patience.
It's quite satisfying to build the entire mess from source
and gives you a much better understanding of the
fundamentals of linux.
When I first started using linux I had this constant fear
of missing stuff, if I didn't have everything installed then
I wouldn't be able to build or use xyz software later.
Now I'm the opposite, I always want a minimal system,
only what I need and nothing more. Some of these
distros have 6GB of software on the disks. Insane.
-- Doug
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
Littlefield, Tyler
` Doug Sutherland
` Scott Berry
` Littlefield, Tyler
` Doug Sutherland
` Littlefield, Tyler
` Doug Sutherland
` Gregory Nowak
` Doug Sutherland
` Gregory Nowak
` Doug Sutherland [this message]
` Gregory Nowak
` Scott Berry
` Doug Sutherland
` Gregory Nowak
` Doug Sutherland
` Littlefield, Tyler
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='00b901c7b09f$01b66dd0$ab00a8c0@tenstac' \
--to=doug@proficio.ca \
--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).