From: Bo Andresen <bo.andresen@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Problems with GRUB in the installation of Gentoo
Date: Wed, 15 Feb 2006 13:44:35 +0100 [thread overview]
Message-ID: <200602151344.38145.bo.andresen@gmail.com> (raw)
In-Reply-To: <20060215100205.516801d6@krikkit.digimed.co.uk>
On Wednesday 15 February 2006 11:02, Neil Bothwick wrote:
> On Mon, 13 Feb 2006 00:25:52 +0100, Bo Andresen wrote:
> > I always copy do:
> > cp arch/i386/boot/bzImage /boot/kernel-version-gentoo-r?
> > cp System.map /boot/System.map-version-gentoo-r?
> > cp .config /boot/config-version-gentoo-r?
>
> 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.
Now we are at it is there someone who is willing to explain to me how make
install works (I do know make i.e the basics)? I mean looking in the Makefile
I don't see any directives as to how to make install...
--
Bo Andresen
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-02-15 12:54 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 ` [gentoo-user] " Holly Bostick
2006-02-16 21:19 ` 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 ` Bo Andresen [this message]
2006-02-12 17:21 ` [gentoo-user] " 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=200602151344.38145.bo.andresen@gmail.com \
--to=bo.andresen@gmail.com \
--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