public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: eddantes@wanadoo.fr
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Anton Altaparmakov <aia21@cus.cam.ac.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [2.5.7] undefined reference to `sys_nfsservctl'
Date: Wed, 20 Mar 2002 18:55:07 +0100	[thread overview]
Message-ID: <3C98CCFB.1080601@wanadoo.fr> (raw)
In-Reply-To: <Pine.SOL.3.96.1020320162809.19016A-100000@draco.cus.cam.ac.uk> <shsd6xztcj8.fsf@charged.uio.no>



Trond Myklebust wrote:

>>>>>>" " == Anton Altaparmakov <aia21@cus.cam.ac.uk> writes:
>>>>>>
> 
>      > Al Viro has a patch for this on his ftp site but you can get
>      > over the compile problemy by simply enabling both nfs and nfs
>      > server in the kernel configuration, no patch needed in that
>      > case... I.e. you want to set these:
> 
>     >> # CONFIG_NFS_FS is not set CONFIG_NFS_V3 is not set CONFIG_NFSD
>     >> # is not set CONFIG_NFSD_V3 is not set
> 
> No point in compile in the NFS client unless you really need it.
> sys_nfsservctl is a knfsd-only thing, so you shouldn't need either
> CONFIG_NFS_FS or CONFIG_NFS_V3 if you only want get around the bug.



Yes, I'd prefer not to compile in stuff I don't need. And I definitely 
don't need NFS.

OTOH, I went on Al Viro's ftp to try to find the patch. Which file is it? :)

/Dantes




  reply	other threads:[~2002-03-20 17:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-20 16:26 [2.5.7] undefined reference to `sys_nfsservctl' eddantes
2002-03-20 16:32 ` Anton Altaparmakov
2002-03-20 16:43   ` Trond Myklebust
2002-03-20 17:55     ` eddantes [this message]
2002-03-20 17:52       ` Anton Altaparmakov

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=3C98CCFB.1080601@wanadoo.fr \
    --to=eddantes@wanadoo.fr \
    --cc=aia21@cus.cam.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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