From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
okir@monad.swb.de, obelix123@toughguy.net
Subject: Re: [TRIVIAL][PATCH]:/proc/fs/nfsd/
Date: Fri, 5 Mar 2004 11:47:08 +0200 [thread overview]
Message-ID: <16B99F21693@vcnet.vc.cvut.cz> (raw)
On 5 Mar 04 at 21:08, Neil Brown wrote:
> > The following patch fixes it.
>
> Does it need fixing??
>
> If you remove this, then people who compile a kernel without nfsd
> support, and then later decide to compile an nfsd module and load it,
> will not be able to mount the nfsd filesystem at the right place.
> I think it is a very small cost, and a measurable gain, to leave it
> there.
Maybe I'm stupid, but why cannot knfsd module create fs/nfsd
directory at module load? That way you can do insmod/modprobe followed
by mount() to do that. And if you'll fiddle with do_mount a bit
(so that get_fs_type() is invoked before walking mount path)
you can do it even without modprobing knfsd in advance, by just
doing 'mount none /proc/fs/nfsd -t nfsd'.
Petr Vandrovec
next reply other threads:[~2004-03-05 10:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 9:47 Petr Vandrovec [this message]
2004-03-05 11:28 ` [TRIVIAL][PATCH]:/proc/fs/nfsd/ Neil Brown
-- strict thread matches above, loose matches on Subject: below --
2004-03-05 9:09 [TRIVIAL][PATCH]:/proc/fs/nfsd/ Raj
2004-03-05 10:08 ` [TRIVIAL][PATCH]:/proc/fs/nfsd/ Neil Brown
2004-03-05 10:35 ` [TRIVIAL][PATCH]:/proc/fs/nfsd/ Raj
2004-03-13 17:26 ` [TRIVIAL][PATCH]:/proc/fs/nfsd/ Adrian Bunk
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=16B99F21693@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=obelix123@toughguy.net \
--cc=okir@monad.swb.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox