When talking to a unfsd on 2.0.28+logo, 2.3.51 generates an amazing amount of
diagnostic messages all helpfully reminding me that, yes, there's still no
lock daemon running on the other end, just like there wasn't 10 seconds ago.
There are more serious problems with the nfs client (like it dropping half
the contents of directories while doing readdir :-() but this one seems to
be easy to patch around. It works for me(tm), and my inexperienced eye
doesn't seem to see anything wrong with it.
--- ./fs/nfs/nfsroot.c.orig Wed Sep 29 15:32:15 1999
+++ ./fs/nfs/nfsroot.c Sat Mar 11 08:49:21 2000
@@ -145,6 +145,8 @@
{ "nocto", ~NFS_MOUNT_NOCTO, NFS_MOUNT_NOCTO },
{ "ac", ~NFS_MOUNT_NOAC, 0 },
{ "noac", ~NFS_MOUNT_NOAC, NFS_MOUNT_NOAC },
+ { "lock", ~NFS_MOUNT_LOCK, 0 },
+ { "nolock", ~NFS_MOUNT_NONLM, NFS_MOUNT_NONLM },
{ NULL, 0, 0 }
};
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Mar 15 2000 - 21:00:30 EST