Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 406963 - Kernel installation should tell people to use "make install"
Summary: Kernel installation should tell people to use "make install"
Status: RESOLVED DUPLICATE of bug 142317
Alias: None
Product: [OLD] Docs on www.gentoo.org
Classification: Unclassified
Component: Installation Handbook (show other bugs)
Hardware: All Linux
: Normal enhancement (vote)
Assignee: Docs Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-05 10:11 UTC by Pacho Ramos
Modified: 2013-12-22 17:49 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pacho Ramos gentoo-dev 2012-03-05 10:11:21 UTC
Currently, handbook ask people to install kernel files manually instead of simply running "make install":

Code Listing 3.8: Installing the kernel
# cp arch/x86_64/boot/bzImage /boot/kernel-2.6.34-gentoo-r1

Thanks

Reproducible: Always
Comment 1 nm (RETIRED) gentoo-dev 2012-03-06 09:15:41 UTC
also a duplicate of bug #334359. there's more than one reason why we haven't done this over the years -- they're listed on bugzilla and the mailing lists. doesn't work on all arches, for starters.

*** This bug has been marked as a duplicate of bug 142317 ***
Comment 2 Adrian 2013-12-22 03:34:41 UTC
"doesn't work on all arches" - so why not use it on common archs (i guess 99% of all gentoo users are on amd64 or x86?)?

(from the linked issue) "by hand is always much cleaner and simplier than using a script for that" - no it's not. `CTRL+R modu` quickly gets me the line (assuming i have something like `make all modules_install install` in my history). also, that's a single command that works for every single kernel version. the cp one - at least when including the version number - needs to be changed each time.
Comment 3 Sven Vermeulen (RETIRED) gentoo-dev 2013-12-22 17:49:55 UTC
For now, I'd like to keep the instructions as-is unless there is an improvement to be found or bug with the current method. Even if just because the "cp" command tells the user what is happening (whereas "make install" is a bit less obvious).

So it is not that this is *the* reason for the current commands, but more as a "works currently with quite a lot of history". There is always more than one way to do things of course.