On Tue, Sep 09, 2008 at 02:22:46PM +0300, Arie Skliarouk wrote: > I am running debian unstable as a virtual server under OpenVZ. > > The virtual server has [NFS] mounts, that are [re-]mounted using > "bind" option by the physical server. [...] The virtual server [...] > does not have any nfs-* packages installed. > > [...] new version of mount checks for nfs mounts and complain on NFS > mounts already mounted: > > # dpkg -i /var/cache/apt/archives/mount_2.13.1.1-1_i386.deb > (Reading database ... 40284 files and directories currently installed.) > Preparing to replace mount 2.13-7 (using .../mount_2.13.1.1-1_i386.deb) ... > You have NFS mount points currently mounted, and this version of mount > requires that nfs-common be upgraded before NFS mounts will work.
I have the same symptoms. Rather than remove the test, I suggest detecting when a virtual environment is in place. The most obvious way, I suppose, would be for mount to skip the test if nfs-common is not installed. If nfs-common isn't installed, then presumably any NFS entries it "sees" in /etc/mtab or /proc/mounts are either stale or not relevant to the running environment. If this is a bad idea, I'd appreciate explanatory details from the maintainer(s) -- currently it looks like this has just been tagged "wontfix" without any discussion. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
