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