On Sat, Jul 14, 2007 at 12:00:25PM +0200, Steinar H. Gunderson wrote: > > I spent some time debugging through this, trying to figure out how cfs is > supposed to be working. It seems like the core of the problem is the line > > mount -oport=3049,intr,nfsvers=2 localhost:$NULL_EXPORT $CRYPT_ROOT || rc=1 > > However, cfsd never registers with the portmapper. If you don't use > portmapper, you'll need to specify the entire triplet port/version/protocol, > or the mount will fail -- for some reason, earlier versions of mount (ie. > versions from before the split into mount.nfs) were more forgiving about > this, but they are not anymore. In other words, the cfs package needs to add > ",udp" to its list of NFS-mounting option. Reassigning appropriately, and > setting severity as this completely breaks cfs TTBOMK.
If I understand this right, this bug doesn't affect etch since the version of mount in etch is more forgiving? If that's the case, can you please tag this bug "lenny sid"? Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
