From: Harm Geerts <harmgeerts@home.nl>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Gentoo failed to start
Date: Sat, 2 Sep 2006 04:25:58 +0200 [thread overview]
Message-ID: <200609020425.58708.harmgeerts@home.nl> (raw)
In-Reply-To: <7573e9640609011852y162aa81bg69664dac4bde508c@mail.gmail.com>
On Saturday 02 September 2006 03:52, Richard Fish wrote:
> On 9/1/06, Stephen Liu <satimis@yahoo.com> wrote:
> > I think I have to run another round again wiping out the complete HD.
>
> Yeah, I think so...
>
> > Another thing, what did you mean "...Use whatever name you feel is
> > appropriate for your kernel choice and remember it as you will need it
> > later on when you configure your bootloader. Remember to replace
> > kernel-2.6.17-gentoo-r5 with the name and version of your kernel."
>
> When you compile the kernel, it is going to build a file called
> bzImage, that you have to copy to /boot. But it is very rare to copy
> it to /boot/bzImage...most linux users will rename the file to
> something else. Some people (and helper scripts like genkernel)
> prefer to use the full version of the kernel, so if you build a kernel
> from gentoo-sources-2.6.17-r5, you might:
>
> cp arch/x86_64/boot/bzImage /boot/linux-2.6.17-gentoo-r5
> ... or ...
> cp arch/x86_64/boot/bzImage /boot/vmlinuz-2.6.17-gentoo-r5
> ... or ...
> cp arch/x86_64/boot/bzImage /boot/mykernel-17r5
>
> It is usually a good idea to keep a backup kernel in /boot that you
> can use in case a kernel upgrade goes wrong. So I usually keep 2
> kernels, /boot/vmlinuz-2.6 and /boot/vmlinuz-safe. Once I know that
> vmlinuz-2.6 boots and works reliably, I will copy it to -safe.
This can also be done with installkernel from sys-apps/debianutils
>From it's manpage:
installkernel installs a new kernel image onto the system from the Linux
source tree. It is called by the Linux kernel makefiles when "make install"
is invoked there.
The new kernel is installed into {directory}/vmlinuz-{version}, a link is made
from {directory}/vmlinuz to the new kernel, and the previously installed
kernel is available as {directory}/vmlinuz.old.
> The second part about remembering the name for your boot loader refers
> to your menu.lst/grub.conf entries. You must specify the actual name
> that you copied your kernel image to, or (as you already saw), you
> will get a "file not found" when you try to boot.
>
> So if you copy bzImage to /boot/vmlinuz-2.6, you must use an entry like:
>
> title Whatever
> kernel hd(0,0)/vmlinuz-2.6 ...
>
> The title doesn't really matter, but the "kernel" line needs to
> reference your actual kernel file.
For grub.conf you can use the symlinks installkernel creates (vmlinuz and
vmlinuz.old). Now you'll never have to change your grub config again, just
make sure /boot is mounted ;)
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-09-02 2:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060901144037.98416.qmail@web35206.mail.mud.yahoo.com>
2006-09-01 16:01 ` [gentoo-user] Gentoo failed to start Stephen Liu
2006-09-01 19:11 ` Richard Fish
2006-09-01 23:46 ` Stephen Liu
2006-09-02 1:52 ` Richard Fish
2006-09-02 2:25 ` Harm Geerts [this message]
2006-09-03 8:56 ` Nick Rout
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=200609020425.58708.harmgeerts@home.nl \
--to=harmgeerts@home.nl \
--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