From: Christoph Hellwig <hch@infradead.org>
To: "Kendrick M. Smith" <kmsmith@umich.edu>
Cc: linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: patch 38/38: SERVER: giant patch importing NFSv4 server functionality
Date: Wed, 14 Aug 2002 13:43:47 +0100 [thread overview]
Message-ID: <20020814134347.B14609@infradead.org> (raw)
In-Reply-To: <Pine.SOL.4.44.0208131912340.25942-100000@rastan.gpcc.itd.umich.edu>; from kmsmith@umich.edu on Tue, Aug 13, 2002 at 07:12:53PM -0400
On Tue, Aug 13, 2002 at 07:12:53PM -0400, Kendrick M. Smith wrote:
> --- old/fs/nfsd/nfssvc.c Fri Aug 9 11:16:02 2002
> +++ new/fs/nfsd/nfssvc.c Thu Aug 8 09:53:23 2002
> @@ -77,6 +77,18 @@ nfsd_svc(unsigned short port, int nrserv
> int none_left;
> struct list_head *victim;
>
> +#ifdef CONFIG_NFSD_V4
> + printk(KERN_INFO "Starting experimental NFSv4 server.\n");
> + printk(KERN_INFO "Note 1: The NFSv4 pseudo filesystem is not yet implemented!\n");
> + printk(KERN_INFO " The first export in your /etc/exports has been arbitrarily\n");
> + printk(KERN_INFO " selected as the root of the pseudofs. In order to see this\n");
> + printk(KERN_INFO " export, you will have to mount '/' instead of the export pathname.\n");
> + printk(KERN_INFO " Exports other than this one will not be available.\n");
> + printk(KERN_INFO "Note 2: Most of the NFSv4 state model is not yet implemented;\n");
> + printk(KERN_INFO " this server patch should still provide basic functionality.\n");
> + printk(KERN_INFO " However, byte-range file locking is not available.\n");
> +#endif
This belongs into a readme, not into kernel messages..
prev parent reply other threads:[~2002-08-14 12:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-13 23:12 Kendrick M. Smith
2002-08-14 12:43 ` Christoph Hellwig [this message]
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=20020814134347.B14609@infradead.org \
--to=hch@infradead.org \
--cc=kmsmith@umich.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®