Summary: | copy kernel to boot is not necessary, why is it there? | ||
---|---|---|---|
Product: | [OLD] Docs on www.gentoo.org | Reporter: | Dan Coats <admin> |
Component: | Other documents | Assignee: | Docs Team <docs-team> |
Status: | RESOLVED DUPLICATE | ||
Severity: | trivial | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://www.gentoo.org/doc/en/kernel-upgrade.xml | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Dan Coats
2007-10-24 12:18:14 UTC
additionally we get questions like. "when i do mount /boot it says cant find /boot in /etc/fstab" so maybe it even makes more since to say it like.. _______________________________________________________________________________ **If your /boot partition is on a separate you need to mount it first. # mount /boot **Then build and install your kernel. # make && make modules_install install **Now your kernel is at /boot/vmlinuz.<your-kernel-version> with symlinking **done for you to vmlinuz and If one existed your old kernel is linked to as **vmlinuz.old, Please confirm this with ls -al /boot _________________________________________________________________________________ Works for me too , but that wasn't the point. The point was to try to make the documentation work for more people, or at least be more simplified for those users still learning. i think this has come up before (switching to `make install`), so try searching bugzilla to see if there's any visible history ... i havent copied a kernel by hand in a long time because `make install` is so much easier reopening for proper resolution *** This bug has been marked as a duplicate of bug 183346 *** |