| 1 |
Denis wrote: |
| 2 |
> On Sat, Oct 31, 2009 at 12:52 PM, Harry Putnam <reader@×××××××.com> wrote: |
| 3 |
> |
| 4 |
>> And in fact does it really matter if its pointing at the newly |
| 5 |
>> installed or actual running kernel, when kernel compiling operations |
| 6 |
>> take place? |
| 7 |
>> |
| 8 |
> |
| 9 |
> When I upgrade a kernel, I first change the symlink using eselect to |
| 10 |
> point to the source I'm about to install. Then, after I configure and |
| 11 |
> compile the kernel, I use the "module-rebuild rebuild" to rebuild any |
| 12 |
> kernel modules against the new source. Move the bzImage to /boot, |
| 13 |
> reboot, and that's it. I don't know how genkernel changes any of this |
| 14 |
> - I use manual menuconfig. |
| 15 |
> |
| 16 |
> |
| 17 |
> |
| 18 |
|
| 19 |
I'm about the same. I update the symlink, build the kernel, update |
| 20 |
nvidia-drivers against the new kernel before I forget, copy bzImage to |
| 21 |
/boot and edit grub. I reboot when I get the chance. |
| 22 |
|
| 23 |
If the kernel is borked, I change the symlink back and reboot to my old |
| 24 |
kernel. I try to keep the symlink pointing to the kernel I am running |
| 25 |
even if it is not absolutely necessary. |
| 26 |
|
| 27 |
Dale |
| 28 |
|
| 29 |
:-) :-) |
Archives