From: Holly Bostick <motub@planet.nl>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Problems with GRUB in the installation of Gentoo
Date: Thu, 16 Feb 2006 22:03:48 +0100 [thread overview]
Message-ID: <43F4E8B4.6030906@planet.nl> (raw)
In-Reply-To: <E409A0EB8A569347802C508C49C13439072FF3@BCV0X134EXC0003>
Michael Kintzios schreef:
>
>> -----Original Message----- From: Neil Bothwick
>> [mailto:neil@digimed.co.uk] Sent: 16 February 2006 16:10 To:
>> gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re:
>> Problems with GRUB in the installation of Gentoo
>>
>>>> make install does exactly the same, and sets up the vmlinuz and
>>>> vmlinuz.old symlinks to point to your new and previous kernel
>>>> respectively, so you don't need to edit grub.conf.
>>> Hmm, it doesn't on my two boxen. :-( I do not have a vmlinuz,
>>> System.map and config links.
>>>
>>> Do I have to first set up the symlinks manually?
>> Looking as /sbin/installkernel, it doesn't appear that you have to
>> create the links. Of course, you do have to make sure /boot is
>> mounted first :)
>
> Yep, /boot is always mounted (just to be sure I won't forget it, I
> always mount it before I even cd into /usr/src/linux). Running make
> && make modules_install does *not* create any links in my /boot
> directory,
Neither make nor make modules_install is *supposed* to create any links
in your /boot directory.
Make compiles the kernel and static modules, make modules_install
compiles the dynamic modules and installs them in
/lib/modules/<kernel-version/<wherever_they_belong>.
This is why you then have to either copy the compiled kernel (and
supplemental files like .config and system.map, if you want) to /boot.
make install (which is a different command than make modules_install)
does this automatically, and additionally makes symlinks called vmlinuz
and vmlinuz.old (if a previous kernel exists), and updates lilo (if
available). If you use grub, if grub.conf is set to load vmlinuz as the
current kernel, and vmlinuz.old as the previous kernel, you don't then
have to update grub in any way when you have used make install to
install your newly-compiled kernel, because make install changes the
symlink for the previous kernel to vmlinuz.old, and makes the symlink
for the newly installed kernel vmlinuz. Kernels older than the current
and most-recent-previous can be added manually to the menu directly.
My impression is that you haven't yet run make install.
HTH,
Holly
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-02-16 21:26 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-12 16:48 [gentoo-user] Problems with GRUB in the installation of Gentoo Gilberto Martins
2006-02-12 17:12 ` [gentoo-user] " Gilberto Martins
2006-02-12 21:44 ` Bo Andresen
2006-02-12 21:59 ` Patrick Bloy
2006-02-12 22:12 ` Bo Andresen
2006-02-12 22:23 ` Gilberto Martins
2006-02-12 22:45 ` Bo Andresen
2006-02-12 23:04 ` Maarten
2006-02-12 23:07 ` Holly Bostick
2006-02-12 23:12 ` John Jolet
2006-02-12 23:28 ` Holly Bostick
2006-02-12 23:38 ` John Jolet
2006-02-12 23:42 ` CapSel
2006-02-13 0:18 ` Holly Bostick
2006-02-13 0:16 ` Bo Andresen
2006-02-13 1:07 ` Gilberto Martins
2006-02-13 2:28 ` Daniel da Veiga
2006-02-13 2:58 ` Gilberto Martins
2006-02-13 8:05 ` Maarten
2006-02-13 12:04 ` Gilberto Martins
2006-02-13 12:17 ` Bo Andresen
2006-02-13 13:15 ` Gilberto Martins
2006-02-13 14:27 ` Michael Kintzios
2006-02-13 17:02 ` Richard Fish
2006-02-13 17:49 ` Maarten
2006-02-14 2:39 ` Gilberto Martins
2006-02-14 10:26 ` Holly Bostick
2006-02-14 11:22 ` Maarten
2006-02-14 9:18 ` Michael Kintzios
2006-02-14 2:40 ` Gilberto Martins
2006-02-14 4:49 ` Richard Fish
2006-02-14 12:56 ` Gilberto Martins
2006-02-14 16:42 ` Cláudio Henrique
2006-02-12 23:25 ` Bo Andresen
2006-02-15 10:02 ` Neil Bothwick
2006-02-15 10:19 ` Michael Kintzios
2006-02-16 16:10 ` Neil Bothwick
2006-02-16 17:05 ` Michael Kintzios
2006-02-16 20:48 ` John Jolet
2006-02-16 21:40 ` [gentoo-user] " Mick
2006-02-16 22:33 ` Holly Bostick
2006-02-16 22:49 ` [gentoo-user] " Mick
2006-02-16 23:47 ` [gentoo-user] " Neil Bothwick
2006-02-17 13:45 ` Holly Bostick
2006-02-17 14:01 ` Neil Bothwick
2006-02-16 23:07 ` John Jolet
2006-02-16 21:03 ` Holly Bostick [this message]
2006-02-16 21:19 ` [gentoo-user] " Frino Klauss
2006-02-16 21:43 ` Holly Bostick
2006-02-16 21:49 ` Daniel da Veiga
2006-02-16 21:48 ` [gentoo-user] " Mick
2006-02-16 21:10 ` [gentoo-user] " Neil Bothwick
2006-02-16 22:39 ` [gentoo-user] " Mick
2006-02-15 12:44 ` [gentoo-user] " Bo Andresen
2006-02-12 17:21 ` Gilberto Martins
2006-02-12 18:02 ` John Jolet
2006-02-12 18:12 ` Gilberto Martins
2006-02-12 19:08 ` John Jolet
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=43F4E8B4.6030906@planet.nl \
--to=motub@planet.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