Package: modules
Version: 2.0.0-8
The /etc/init.d/modules script makes a symlink, /lib/modules/current.
There is no need for the symlink, and in fact, it breaks some systems.
I have a linux server, and several diskless clients that use the server
for nfs. All of them share the /lib directory. As things stand now, I have
to make sure the server and all clients are running the same version of
the kernel. When I boot one of the clients that's running a different
version of the kernel than what the server is using, the init.d/modules
script does
ln -snf /lib/modules/`uname -r` /lib/modules/current
This breaks the server, so it can no longer find the correct modules!
I believe that the symlink is unneccessary. /etc/conf.modules already has
things in it like:
path[fs]=/lib/modules/`uname -r`/fs
path[misc]=/lib/modules/`uname -r`/misc
path[net]=/lib/modules/`uname -r`/net
..
That make the module utilities look in the proper directory according to
kernel version. My systems run fine if I delete the /lib/modules/current
symlink and make no other changes.
--
#!/usr/bin/perl -lisubstr($_,39+38*sin++$y/9,2)=$s # [EMAIL PROTECTED]
for($s=' '||McQ;$_='JOEY HESS 'x8;print){eval$^I} # Joey Hess
"How appropriate, you fight like a cow." - - Guybrush Threepwood
