Zac Medico schreef: > Holly Bostick wrote: > >> >> This sounds great, but what about the kernel I'm booted into, >> against which the module will *not* be compiled, if I have to >> reboot before actually configuring/compiling/installing the new >> kernel? >> > > You can get pretty close to your desired behavior (merge kernel last) > if you simple mask kernel package versions greater than the one that > is currently installed. > > mkdir -p /etc/portage echo ">sys-kernel/gentoo-sources-2.6.14-r2" >> > /etc/portage/package.mask > > That way, portage will not attempt to upgrade it until you tell it > that you are ready, by removing the mask. And yeah, if USE=symlink > causes problems, don't use it (in my suggested scenario above it > might be useful though).
So the ultimate conclusion is that I can either 1) disable the symlink USE flag and manage the redirect manually, which would enable me to download any kernel at any time without concern for whether a kernel module was upgrading in the same operation; or 2) manually mask kernels, which would enable me to upgrade any kernel modules at any time but force me to manually oversee the availability of kernel upgrades and manually enable them (and re-disable them following said upgrade). I guess I'll go for option 1, but the long and the short of it is that complete automation is unavailable and my only choice is what I prefer to manage manually. OK, then. <sigh> Thanks. Holly -- gentoo-user@gentoo.org mailing list
