Public bug reported:
Installation of AFS client in dapper, makes the client fails when done
like:
aptitude install openafs-module-<kvers>-<abi> openafs-client
while this works fine:
aptitude install openafs-module-<kvers>-<abi>
depmod <kvers>-<abi>
aptitude install openafs-client
Postrm script has a
# Automatically added by dh_installmodules
if [ "$1" = "configure" ] && [ -x "`which update-modules 2>/dev/null`" ]; then
update-modules >/dev/null || [ "$?" = 3 ]
fi
but there is no <kvers>-<abi> info. So something
is wrong.
I assume everyone (like me) tries to install updated
openafs-modules-<kvers>-abi together with an updated
kernel, so after a reboot everything works again as before.
openafs-client init.d script does also strange things. First it
goes to great detail to figure out the full path for the right kernel-module,
then it simple uses
modprobe openafs${MP}
which fails due to missing/failed depmod run. While
insmod <fullpath>
would work (hack hack ;)
Achim
** Affects: openafs (Ubuntu)
Importance: Untriaged
Status: Unconfirmed
--
module list not updated when openafs-module-<kvers>-<abi> is installed
https://launchpad.net/bugs/52792
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
