1 |
Dale writes: |
2 |
|
3 |
> I don't use genkernel anymore. I just roll my own. That way, I know |
4 |
> what is in there and what is not. Then if something doesn't work, I |
5 |
> know if it is the kernel or something else. With genkernel, you won't |
6 |
> have a clue what it is since you don't know much if anything about the |
7 |
> kernel and how it is configured. |
8 |
|
9 |
That's not necessarily true. When I create a new kernel, I copy |
10 |
/usr/src/linux/.config into the new kernel directory, make oldconfig and |
11 |
menuconfig just as I like my kernel to be, and recreate the linux symlink |
12 |
to the new kernel directory. Then I do a genkernel --install --lvm --luks |
13 |
all && emerge -a @module-rebuild, and am done. |
14 |
I never noticed genkernel changing anything in my configuration, .config, |
15 |
/proc/config.gz and the stuff in /etc/kernels/ are identical. Until not |
16 |
long ago, I did not even know that genkernel was intended to create a |
17 |
working kernel from scratch. |
18 |
|
19 |
Wonko |