Re: [gentoo-user] [~and64] Headsup for googled the previous one to vmlinu-chrome users

[Tom H <tomh0665@gmail.com>]

On Fri, May 22, 2015 at 6:58 PM, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Fri, 22 May 2015 23:29:40 +0100, Mick wrote:
>>>
>>> make install does it exactly the way you are doing it, but faster and
>>> less prone to error.
>>
>> Hmm ... I may have used it the wrong way quite a few years ago, but it
>> would only keep two kernels at a time or something like that. That
>> made me carry on copying kernel files into boot manually. In this way
>> at least I know where I put them and what options I pass on to them.
>
> make install installs the kernel it just made. It doesn't, and can't,
> touch other kernels. The only change it makes to /boot beyond copying
> three files there is to adjust the symlinks if they are already present.
>
> I've never understood the approach of trusting the makefile to configure
> your kernel, compile it, compile any number of modules and install all
> those modules, but when it comes to copying one file to /boot, that has
> to be done manually because the makefile can't be trusted to get things
> right.

"/sbin/installkernel" renames the already-installed vmlinuz and
System.map if it's installing the same version of the kernel.