Linked by Ben Hughes on Tue 5th Oct 2004 19:16 UTC
GNU/Linux, and all other operating systems, are based around a kernel which controls hardware access and maximizes CPU and RAM efficiency by controlling when and how much programs get to use. The difference between Linux and most other operating systems (closed source ones at least BSD and other open source OS's you can do this with) is that you can compile the kernel to meet your needs.
Permalink for comment
To read all comments associated with this story, please click here.
Maybe i'm just being a stupid n00b, but why does step 2 contain 2 almost identical mount commands?
Also, before cping the kernel to /boot, you should be sure and mount your /boot partition (assuming it's on a seperate partition). The most frequent screw up i make installing new kernels is forgetting to do that before cping the kernel to /boot.
If you like to compile kernels, it's also a good idea to always have at least one known good kernel in /boot and grub/lilo. If your new kernel won't boot, it's a lot easier to fix it by booting the good one than messing with a live cd.
Basically good advice, but a couple of comments:
Maybe i'm just being a stupid n00b, but why does step 2 contain 2 almost identical mount commands?
Also, before cping the kernel to /boot, you should be sure and mount your /boot partition (assuming it's on a seperate partition). The most frequent screw up i make installing new kernels is forgetting to do that before cping the kernel to /boot.
If you like to compile kernels, it's also a good idea to always have at least one known good kernel in /boot and grub/lilo. If your new kernel won't boot, it's a lot easier to fix it by booting the good one than messing with a live cd.