From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Dumas Patrice <dumas@centre-cired.fr>
Cc: nfs@lists.sourceforge.net
Subject: Re: error when insmod nfsd: unresolved symbol nfsd_linkage
Date: 12 Apr 2002 14:34:09 +0200 [thread overview]
Message-ID: <shsg02185a6.fsf@charged.uio.no> (raw)
In-Reply-To: <20020412135551.D26281@zeus.centre-cired.fr>
>>>>> " " == Dumas Patrice <dumas@centre-cired.fr> writes:
> Hi, I have just compiled linux-2.4.18 with
> linux-2.4.18-NFS_ALL.dif applied. All the nfs stuff was
> compiled as modules (without over TCP support). I made some
> changes in lockd/svcproc.c, but I touched nothing anywhere
> else. I am on a redhat 7.2, but the kernel is a normal kernel.
> Now, when I try to insmod the nfsd module (after sunrpc and
> lockd), I get
> ./nfsd.o: unresolved symbol nfsd_linkage
The above usually means that the kernel was compiled without
'CONFIG_NFSD=m' being set.
You probably forgot to run 'make oldconfig' after changing the .config
file by hand or something like that.
Cheers,
Trond
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2002-04-12 12:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-12 11:55 error when insmod nfsd: unresolved symbol nfsd_linkage Dumas Patrice
2002-04-12 12:34 ` Trond Myklebust [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=shsg02185a6.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=dumas@centre-cired.fr \
--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