From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: moving from amd to p3?
Date: Sat, 16 Jun 2007 18:26:24 -0700 [thread overview]
Message-ID: <20070617012623.GA24480@localhost.localdomain> (raw)
In-Reply-To: <002d01c7b076$5a9ff390$ab00a8c0@tenstac>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, Jun 16, 2007 at 07:27:57PM -0500, Doug Sutherland wrote:
> Before you begin, do this to save your old .config
> and make sure you have a clean source tree
>
> cd /usr/src/linux
> cp .config .config.SAVE
This will only be the case if you're recompiling a kernel source tree
again. When you untar a fresh kernel source for the first time, the /usr/src/linux/.config
file won't exist. You can however move another .config file to
/usr/src/linux/.config, if you want to start with whatever is already
configured in that .config file, instead of starting completely from
scratch. Personally, when building a new kernel for a new machine, I
grab a .config file for the kernel/distro I'm already using, and
change that to suit my needs, instead of starting from scratch.
> make mrproper
>
> If you were installing speakup, at this point you would do
> the speakup patching of the kernel source.
Actually, as far as I know, and this is what I've always done, you're
supposed to untar the kernel, patch with speakup, run make mrproper
clean, then copy a .config file
into place if any. Also, if you're just
building a freshly untared kernel from kernel.org without speakup, or
any other patches, you don't need to do make mrproper, I never did
that in those cases.
> If you want to configure using your old configuration
> as a start and just change a few things, you can do
> make oldconfig
Before doing make oldconfig, make sure you have an existing
/usr/src/linux/.config, or /boot/config-2.6.21.5, if compiling a
2.6.21.5 kernel. If you don't have either of these, make oldconfig
will just use the defaults for your architecture. For the x86
architecture, this is /usr/src/linux/arch/i386/defconfig.
> make dep
Note that you don't need to run make dep if building a 2.6.x kernel.
> make bzImage
> make modules
If running debian, and if you've got kernelpackage installed, doing
make-kpkg kernel_image
at this point will run the 2 above make commands for you, and build a
package that you can install. When installing that package, it may
also install the kernel in the boot loader for you as well. Other
distros may have a similar shortcut.
- --
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGdI2/7s9z/XlyUyARApoFAJ99rmzVSGmmYHpUn8+aGbnG+rGjwwCeK6GP
ssV+B6eyesc5mBx66NZr+J4=
=mk3U
-----END PGP SIGNATURE-----
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 [this message]
` Doug Sutherland
` Gregory Nowak
` Doug Sutherland
` 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=20070617012623.GA24480@localhost.localdomain \
--to=greg@romuald.net.eu.org \
--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).