Package: kmod Version: 9-1 It may be too early to call this a bug, but I figured I'd open one anyway and ensure there's awareness of the potential. With the advent of individual modules for NFS v2 v3 and v4 clients (see commit 89d77c8fa8) the nfs4 as nfs alias shipped by the kmod Debian package in /lib/modprobe.d/aliases.conf causes NFS v4 mounts to fail. For v4 mounts to work, that alias needs to be removed. Obviously this is going to be problematic, and I don't know what the best solution is, and things could still change by the time 3.6 ships. There's already a thread on linux-nfs that's started to discuss the problem http://marc.info/?t=134403918000007 how they got all the way to -rc1 without having a plan of attack is baffling, but here we are...
If there's a way to take module vermagic into account, or even kernel version, within the modprobe.d/*.conf files, I suppose that's one potential answer. Just changing the names of the NFS client modules so they don't collide with the old alias might work too. -- Jamie Heilman http://audible.transient.net/~jamie/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
