From: BRM <bm_witness@yahoo.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Knock on wood
Date: Wed, 12 Aug 2009 14:46:16 -0700 (PDT) [thread overview]
Message-ID: <532146.59293.qm@web65414.mail.ac4.yahoo.com> (raw)
In-Reply-To: <4A832D0E.3070907@kutulu.org>
> From: Mike Edenfield <kutulu@kutulu.org>
> To: gentoo-user@lists.gentoo.org
> Sent: Wednesday, August 12, 2009 4:58:54 PM
> Subject: Re: [gentoo-user] Knock on wood
>
On 8/12/2009 4:19 PM, Stroller wrote:
> > On 12 Aug 2009, at 15:20, Dale wrote:
> >>> ...
> >>> maske install does that for you, it also sets up the vmlinuz and
> >>> vmlinuz.old symlinks so you don't need to mess with your GRUB config.
> >>
> >> But it doesn't do it the way that I do. I have used it a few times but
> >> it didn't work like I do manually.
> > +1
> > I don't know why anyone would choose to compile & install the kernel any
> > way other than manually. It's only a handful of commands, after all.
> $ make && make modules_install
> $ cp arch/x86/boot/bzImage /boot/vmlinuz-2.6.28-hardened-r1-wombat-4
> $ cp .config /boot/config-2.6.28-hardened-r1-wombat-4
> $ cp System.map /boot/System.map-2.6.28-hardened-r1-wombat-4
> $ cd /boot
> $ mv vmlinuz vmlinuz.old
> $ mv System.map System.map.old
> $ mv config config.old
> $ ln -sf vmlinuz-2.6.28-hardened-r1-wombat-4 vmlinuz
> $ ln -sf config-2.6.28-hardened-r1-wombat-4 config
> $ ln -sf System.map-2.6.28-hardened-r1-wombat-4 System.map
> vs.
> $ make && make modules_install && make install
> I can't see any reason *not* to use make install, especially when its
> just doing exactly the same thing you are doing manually with about 100
> times as much typing.
$ make install
supposes you are installing to the standard location.
I forget why off hand - probably due to the conversion to gentoo on the machine a while back - but I'm installing to /boot/grub, not /boot.
So far as I am aware (I could be wrong), your method doesn't support that.
Ben
next prev parent reply other threads:[~2009-08-12 21:46 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 5:13 [gentoo-user] Knock on wood Alan E. Davis
2009-08-12 8:38 ` Neil Bothwick
2009-08-12 12:58 ` Dale
2009-08-12 9:10 ` Philip Webb
2009-08-12 11:43 ` bn
2009-08-12 12:13 ` William Kenworthy
2009-08-12 12:28 ` Etaoin Shrdlu
2009-08-12 12:44 ` Ward Poelmans
2009-08-12 12:51 ` Volker Armin Hemmann
2009-08-12 18:34 ` Ward Poelmans
2009-08-12 18:41 ` Volker Armin Hemmann
2009-08-12 15:52 ` bn
2009-08-12 13:37 ` Dale
2009-08-12 13:41 ` Neil Bothwick
2009-08-12 14:20 ` Dale
2009-08-12 18:02 ` Neil Bothwick
2009-08-12 20:19 ` Stroller
2009-08-12 20:36 ` Neil Bothwick
2009-08-12 23:48 ` Dale
2009-08-12 20:58 ` Mike Edenfield
2009-08-12 21:08 ` Volker Armin Hemmann
2009-08-12 21:25 ` Mike Edenfield
2009-08-12 21:46 ` BRM [this message]
2009-08-12 21:59 ` Neil Bothwick
2009-08-13 3:46 ` Mike Kazantsev
2009-08-13 7:31 ` Neil Bothwick
2009-08-14 4:41 ` Mike Kazantsev
2009-08-14 8:15 ` Neil Bothwick
2009-08-12 22:07 ` Stroller
2009-08-12 23:43 ` Neil Bothwick
2009-08-12 13:51 ` Philip Webb
2009-08-12 14:22 ` Dale
2009-08-12 20:01 ` Dan Farrell
2009-08-12 23:54 ` Dale
2009-08-13 17:08 ` Dan Farrell
2009-08-13 19:34 ` Dale
2009-08-13 19:58 ` Paul Hartman
2009-08-12 20:17 ` Stroller
2009-08-12 23:06 ` bn
2009-08-12 23:59 ` Dale
2009-08-12 15:28 ` Paul Hartman
2009-08-19 7:08 ` Keith Dart
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=532146.59293.qm@web65414.mail.ac4.yahoo.com \
--to=bm_witness@yahoo.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