From: NeilBrown <neilb@cse.unsw.edu.au>
To: Linus Torvalds <torvalds@osdl.org>
Cc: nfs@lists.sourceforge.net
Subject: [PATCH] kNFSd - 6 of 7 - Create a mountpoint for the nfsd filesystem.
Date: Tue, 05 Aug 2003 13:59:23 +1000 [thread overview]
Message-ID: <E19jsyp-0000nP-00@notabene> (raw)
### Comments for ChangeSet
Though the nfsd module can create this, having it always
there makes auto-loading-on-mount work better.
Note: it was previously recommended that the nfsd filesystem be mounted
on /proc/fs/nfs, which I was never comfortable with.
Henceforth the recommended location will be /proc/fs/nfsd.
nfs-utils 1.0.6 and later will support both.
----------- Diffstat output ------------
./fs/proc/root.c | 1 +
1 files changed, 1 insertion(+)
diff ./fs/proc/root.c~current~ ./fs/proc/root.c
--- ./fs/proc/root.c~current~ 2003-08-04 11:37:38.000000000 +1000
+++ ./fs/proc/root.c 2003-08-04 11:37:48.000000000 +1000
@@ -65,6 +65,7 @@ void __init proc_root_init(void)
#endif
proc_root_fs = proc_mkdir("fs", 0);
proc_root_driver = proc_mkdir("driver", 0);
+ proc_mkdir("fs/nfsd", 0); /* somewhere for the nfsd filesystem to be mounted */
#if defined(CONFIG_SUN_OPENPROMFS) || defined(CONFIG_SUN_OPENPROMFS_MODULE)
/* just give it a mountpoint */
proc_mkdir("openprom", 0);
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
reply other threads:[~2003-08-05 3:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E19jsyp-0000nP-00@notabene \
--to=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.