On Thursday 27 Feb 2003 18: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.
With me it affects nvidia-kernel, alsa-driver and lm_sensors.
>
> 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?
>
In the meantime, you can use this workaround when you boot into a
newly-built kernel:
for package in {nvidia-kernel,alsa-driver,lm_sensors} ; do
echo "Removing any installation records for $package from /var/db/pkg/"
[ -e /var/db/pkg/$(epm -qaG|grep $package) ] && \
rm -Rf /var/db/pkg/$(epm -qaG|grep $package)
echo "Emerging $package"
emerge $package
done
You need to have epm emerged for this to work.
Peter
--
Gentoo-1.4.2.8 Unstable. KDE: 3.1.0 Qt: 3.1.0
AMD Athlon(tm) XP 1900+ 768MB. Kernel: 2.4.20-xfs_pre6. GCC 3.2.2
--
[EMAIL PROTECTED] mailing list
