I've been running 2.3.x on one of my workstations for a little while now
(as part of my "well, magicfilter 2 is almost ready to go, so I might as
well start testing my kernel patches" February scheme) and, aside from
the usual crop of things that I had to convert to get 2.3 to actually
work on Mastodon, I found that the nfs client was spitting out a
fantastically large number of bitter complaints about lockd not running
on my (linux 2.0.28+logo + userland nfsd) local file server. Tonight, I
finally got fed up and hacked in a little patch to add the mount options
"lock" (try to run lockd) and "nolock" (what you'd expect) to
fs/nfs/nfsroot.c
They shut the kernel up, which is good. Are they correct?
--- linux-2.3.49-2/fs/nfs/nfsroot.c.orig Thu Mar 2 01:39:50 2000
+++ linux-2.3.49-2/fs/nfs/nfsroot.c Thu Mar 2 01:26:33 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 }
};
____
david parsons \bi/ rpc.lockd won't be around, no matter how politely
\/ africa asks for it.
-
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 : Tue Mar 07 2000 - 21:00:11 EST