From: Adrian Bunk <bunk@stusta.de>
To: Matthew Wilcox <matthew@wil.cx>,
Joel Soete <soete.joel@tiscali.be>,
Roman Zippel <zippel@linux-m68k.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>
Subject: Re: NFSD needs EXPORTFS
Date: Thu, 3 Feb 2005 18:28:44 +0100 [thread overview]
Message-ID: <20050203172844.GC3121@stusta.de> (raw)
In-Reply-To: <20050203170111.GE20386@parcelfarce.linux.theplanet.co.uk>
On Thu, Feb 03, 2005 at 05:01:11PM +0000, Matthew Wilcox wrote:
>
> Got this report about 2.6.11-rc3. Is this the correct solution?
>
> ----- Forwarded message from Joel Soete <soete.joel@tiscali.be> -----
>
> A short analyse, it seems that's because NFSD was builtin while EXPORTFS
> was a module in my previous config file. Imho EXPORTFS would be build as
> NFSD?
>
> Is the following hunk would do the trick:
> --- fs/Kconfig.Orig 2005-02-03 16:45:13.562275206 +0100
> +++ fs/Kconfig 2005-02-03 16:46:36.496469111 +0100
> @@ -1400,6 +1400,7 @@
> tristate "NFS server support"
> depends on INET
> select LOCKD
> + select EXPORTFS
> select SUNRPC
> help
> If you want your Linux box to act as an NFS *server*, so that other
> ========><========
>
> Thanks in advance,
> Joel
If the problem occured with CONFIG_XFS_FS=m I understand what went
wrong.
It seems to be correct.
This was a side effect of Roman's fix for the XFS <-> EXPORTFS
dependency.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-02-03 17:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-03 17:01 NFSD needs EXPORTFS Matthew Wilcox
2005-02-03 17:28 ` Adrian Bunk [this message]
2005-02-03 17:59 ` Joel Soete
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=20050203172844.GC3121@stusta.de \
--to=bunk@stusta.de \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=soete.joel@tiscali.be \
--cc=zippel@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).