1 |
On 06/21/2010 12:01 PM, Dale wrote: |
2 |
> Alex Schuster wrote: |
3 |
>> Dale writes: |
4 |
>> |
5 |
>> |
6 |
>>> I don't use genkernel anymore. I just roll my own. That way, I know |
7 |
>>> what is in there and what is not. Then if something doesn't work, I |
8 |
>>> know if it is the kernel or something else. With genkernel, you won't |
9 |
>>> have a clue what it is since you don't know much if anything about the |
10 |
>>> kernel and how it is configured. |
11 |
>>> |
12 |
>> That's not necessarily true. When I create a new kernel, I copy |
13 |
>> /usr/src/linux/.config into the new kernel directory, make oldconfig and |
14 |
>> menuconfig just as I like my kernel to be, and recreate the linux symlink |
15 |
>> to the new kernel directory. Then I do a genkernel --install --lvm --luks |
16 |
>> all&& emerge -a @module-rebuild, and am done. |
17 |
>> I never noticed genkernel changing anything in my configuration, .config, |
18 |
>> /proc/config.gz and the stuff in /etc/kernels/ are identical. Until not |
19 |
>> long ago, I did not even know that genkernel was intended to create a |
20 |
>> working kernel from scratch. |
21 |
>> |
22 |
>> Wonko |
23 |
>> |
24 |
>> |
25 |
> |
26 |
> I always do mine this way. I copy the .config from the old kernel to |
27 |
> the new kernel, run make oldconfig then afterwards make all && make |
28 |
> modules_install and then copy the kernel to /boot with my own numbering |
29 |
> system. That way I know which version and series the kernel is. After |
30 |
> that, edit grub with the new kernel and I'm done. I have only had that |
31 |
> fail once in the past six years or so and the kernel made some serious |
32 |
> changes and I had to start from scratch that one time. They moved |
33 |
> things around and oldconfig couldn't reorganize things on the new kernel. |
34 |
> |
35 |
> Point being, genkernal causes issues for people and they don't know how |
36 |
> to fix it because they expect genkernel to do everything. Problem with |
37 |
> that is that usually when someone has a kernel problem, they use |
38 |
> genkernel. If they do their own, it just works. Now someone new to |
39 |
> building a kernel may need some help but apparently genkernel needs some |
40 |
> help anyway. May as well learn how to roll your own. This is Gentoo |
41 |
> after all. |
42 |
|
43 |
The only thing that genkernel would add is your initrd. The kernel is |
44 |
exactly the same, whether you compile it with "make" or through |
45 |
"genkernel". Do a test and you'll see. (I'm assuming we're both talking |
46 |
about gentoo-sources, not vanilla-sources. Either way, they'd be the |
47 |
same.) Some might be confused about what happens in the steps if they |
48 |
haven't been down the "kernel compilation trail" more than once or |
49 |
twice, but for folks who just want to compile their kernel and plop it |
50 |
into place, along with a hands-off initrd, it's rather handy. |