| View previous topic :: View next topic |
| Author |
Message |
RioFL
Guru
Joined: 31 Oct 2002
Posts: 407
|
 Posted: Thu Jun 02, 2005 2:03 pm Post subject: initial kernel install - something I have always wondered... |
 |
|
Why do the docs make you copy bzImage over to /boot when a make install does better? I have never understood this point. When I do a fresh install I simply do as I always do with a make, make install, make modules_install, and it just works.. then I don't have to change grub.conf to mess with bzImage first then vmlinuz later on..
Any reason for this? Is it wrong to make install and let it create the vmlinuz links and install the map and stuff by itself? |
|
| Back to top |
|
 |
96140
Retired Dev
Joined: 23 Jan 2005
Posts: 1324
|
| Posted: Thu Jun 02, 2005 2:18 pm Post subject: |
|
|
Actually, I prefer an even greater automation of the kernel compile/install process: | Code: | | # make && make modules && make modules_install && make install |
Sure, it's redundant, but it only requires me to update the pointers in grub.conf to the new kernel; everything is installed and all symlinks are updated using this series of commands. And if something goes wrong during the compile or install, you can see exactly where it happened once the process stops. Plus, it's good to use this as occasionally, there are new kernel versions that won't otherwise install properly to /boot due to a bug in that kernel or elsewhere. I went through this recently with 2.6.11-gentoo-r6 and before that, -r4.
But in short, there's nothing wrong with make install. Apparently, even some devs haven't heard of that command and some others think it's unsupported. But for me it's the only way to go; there's always the chance of doing manual kernel installs improperly due to misspellings, missed steps, etc. |
|
| Back to top |
|
|
RioFL
Guru
Joined: 31 Oct 2002
Posts: 407
|
| Posted: Thu Jun 02, 2005 2:49 pm Post subject: |
|
|
| nightmorph wrote: | Actually, I prefer an even greater automation of the kernel compile/install process: | Code: | | # make && make modules && make modules_install && make install |
Sure, it's redundant, but it only requires me to update the pointers in grub.conf to the new kernel; everything is installed and all symlinks are updated using this series of commands. And if something goes wrong during the compile or install, you can see exactly where it happened once the process stops. Plus, it's good to use this as occasionally, there are new kernel versions that won't otherwise install properly to /boot due to a bug in that kernel or elsewhere. I went through this recently with 2.6.11-gentoo-r6 and before that, -r4.
But in short, there's nothing wrong with make install. Apparently, even some devs haven't heard of that command and some others think it's unsupported. But for me it's the only way to go; there's always the chance of doing manual kernel installs improperly due to misspellings, missed steps, etc. |
cool thanks.. since i use a standardized grub.conf, it always points to the symlinks so i never have to edit the file when changing kernels.. this is primarily why i do the make install so it does all it needs to do and grub can work by default  |
|
| Back to top |
|
|
bet1m
l33t
Joined: 04 Dec 2004
Posts: 631
Location: Kosova/Prishtine
|
| Posted: Thu Jun 02, 2005 7:04 pm Post subject: |
|
|
I allways copy it, and run /sbin/lilo .
_________________
#370559 |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Installing Gentoo
