From: "Jesús Guerrero" <6thpink@terra.es>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] kernel recompile?
Date: Wed, 1 Nov 2006 17:37:22 +0100 [thread overview]
Message-ID: <200611011737.22907.6thpink@terra.es> (raw)
In-Reply-To: <4548D184.1020804@gmx.at>
El Miércoles, 1 de Noviembre de 2006 17:55, Florian D. escribió:
> Pawel Kraszewski wrote:
> > So manual config, automatic install
> > is my way.
>
> ok, sorry for being off-topic, but what is the default installation
> target for 'make install'? /boot/vmlinuz? and is there a
> backup-function, say, that my last /boot/vmlinuz gets automatically
> moved to /boot/vmlinuz.old or something? a pointer to documentation
> would be welcome, dr.google knows nothing.
>
> > [OT] Yesterday I managed to finally compile OpenOffice on my AMD64. Boy,
> > that's the speed improvement! For successful compilation I just needed
> > the "JAVA_PKG_FORCE_VM=blackdown-jdk-1.4.2" trick.
>
> me too :-)
Make install copies the kernel image to /boot/vmlinuz-<version-number> for
vanilla kernels, for gentoo-sources it was something like
vmlinux-gentoo-<version-number> or so, so, each kernel is copied with a
different name.
If you use this same name convention in your grub.conf, then it is a good
thing, since you can keep old kernels until you know that your new kernel
actually works, instead of being continually readjusting the vmlinuz link,
which I find to be a hassle.
It is a matter of copying the lines for your old kernel a couple of lines
below and then changing the version number, and you get a new menu entry with
your new kernel.
All is better for me if each kernel has its name in the grub.conf file, cause
I know what I am doing in every momment without having to leave the editor
and go to the command line to see where is vmlinuz pointing at.
Regards.
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2006-11-01 16:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 14:10 [gentoo-amd64] kernel recompile? Sean
2006-10-31 14:16 ` Piotr Pruszczak
2006-10-31 14:25 ` Daniel Iliev
2006-10-31 14:37 ` Piotr Pruszczak
2006-10-31 15:59 ` Daniel Iliev
2006-10-31 16:14 ` Boyd Stephen Smith Jr.
2006-11-02 9:48 ` Michel Merinoff
2006-11-02 10:36 ` Neil Bothwick
2006-10-31 16:19 ` Pawel Kraszewski
2006-10-31 16:49 ` Daniel Iliev
2006-10-31 17:04 ` Sean
2006-10-31 17:18 ` Mathieu Seigneurin
2006-10-31 17:31 ` Daniel Iliev
2006-10-31 18:14 ` Sean
2006-10-31 18:21 ` Daniel Iliev
2006-10-31 18:39 ` Daniel Iliev
2006-10-31 18:48 ` Sean
2006-10-31 19:11 ` Daniel Iliev
2006-10-31 19:38 ` sean
2006-10-31 21:57 ` Daniel Iliev
2006-11-01 19:24 ` sean
2006-11-01 20:39 ` Daniel Iliev
2006-11-01 9:05 ` Pawel Kraszewski
2006-11-01 12:47 ` Daniel Iliev
2006-11-01 14:32 ` Pawel Kraszewski
2006-11-01 16:55 ` Florian D.
2006-11-01 16:37 ` Jesús Guerrero [this message]
2006-11-01 19:14 ` Pawel Kraszewski
2006-11-01 17:06 ` [gentoo-amd64] [OT] " Daniel Iliev
2006-11-01 19:01 ` [gentoo-amd64] [OOT] Apologies Pawel Kraszewski
2006-11-01 20:02 ` [gentoo-amd64] [OOT] [SOLVED] Apologies Daniel Iliev
2006-10-31 14:22 ` [gentoo-amd64] kernel recompile? Sebastian Redl
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=200611011737.22907.6thpink@terra.es \
--to=6thpink@terra.es \
--cc=gentoo-amd64@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