1 |
El Miércoles, 1 de Noviembre de 2006 17:55, Florian D. escribió: |
2 |
> Pawel Kraszewski wrote: |
3 |
> > So manual config, automatic install |
4 |
> > is my way. |
5 |
> |
6 |
> ok, sorry for being off-topic, but what is the default installation |
7 |
> target for 'make install'? /boot/vmlinuz? and is there a |
8 |
> backup-function, say, that my last /boot/vmlinuz gets automatically |
9 |
> moved to /boot/vmlinuz.old or something? a pointer to documentation |
10 |
> would be welcome, dr.google knows nothing. |
11 |
> |
12 |
> > [OT] Yesterday I managed to finally compile OpenOffice on my AMD64. Boy, |
13 |
> > that's the speed improvement! For successful compilation I just needed |
14 |
> > the "JAVA_PKG_FORCE_VM=blackdown-jdk-1.4.2" trick. |
15 |
> |
16 |
> me too :-) |
17 |
|
18 |
|
19 |
Make install copies the kernel image to /boot/vmlinuz-<version-number> for |
20 |
vanilla kernels, for gentoo-sources it was something like |
21 |
vmlinux-gentoo-<version-number> or so, so, each kernel is copied with a |
22 |
different name. |
23 |
|
24 |
If you use this same name convention in your grub.conf, then it is a good |
25 |
thing, since you can keep old kernels until you know that your new kernel |
26 |
actually works, instead of being continually readjusting the vmlinuz link, |
27 |
which I find to be a hassle. |
28 |
|
29 |
It is a matter of copying the lines for your old kernel a couple of lines |
30 |
below and then changing the version number, and you get a new menu entry with |
31 |
your new kernel. |
32 |
|
33 |
All is better for me if each kernel has its name in the grub.conf file, cause |
34 |
I know what I am doing in every momment without having to leave the editor |
35 |
and go to the command line to see where is vmlinuz pointing at. |
36 |
|
37 |
Regards. |
38 |
|
39 |
-- |
40 |
gentoo-amd64@g.o mailing list |