Please do so and post to the list so I (and others) can add to it. This is a really annoying and sometimes disastrous bug. The packages that effect me are vmware lm_sensors nvidia drivers.
Before I found this, I have been caught out by a power surge rebooting the computer before I was ready and coming up with no nvidia driver: as I was not present, I got an earfull over the fact that NO older kernels would give a gui either. vmware will only build when the running kernel is the one you are online with. The upshot is your carefully saved older kernels that you keep as a backup are partly dysfunctional when needed most! BillK On Fri, 2003-02-28 at 02:22, Peter Gantner wrote: > Hi! > > I assume like me, there are a lot of people running several different > kernels, sometimes booting this, sometimes that. > > Now if one emerges a third-party modules, like the NVIDIA kernel > driver, emerge moves the module to the /lib/modules/<version> dir of > the current kernel, that is, the one the /usr/src/linux symlink points > to. > > Two things: > > [1] > > After that, in the automatic emerge clean, the module which was last > installed gets removed. > > IMO, this behaviour is undesireable, because next time you boot > another kernel, the nvidia.o module will be missing, and you have to > emerge again. > rinse. > repeat. > > I have not checked, but I assume the same is true for other modules, > like lm_sensors, v4l, emu10k1 etc. > > So I think by default, emerge should not remove kernel models during > (auto-)clean, only upon explicit unmerge. > > > [2] > > Wouldn't it be better if emerge scripts for kernel modules determined > the kernel version to use from `uname -r` instead of the > /usr/src/linux symlink? > > Should I file a bug for this? > Comments on that? > > > greets, > Peter -- William Kenworthy <[EMAIL PROTECTED]> -- [EMAIL PROTECTED] mailing list
