From: Thanos Chatziathanassiou <tchatzi@arx.gr>
To: nfs@lists.sourceforge.net
Subject: NFSv3 not supported ?
Date: Sun, 01 Sep 2002 21:01:01 +0300 [thread overview]
Message-ID: <3D7255DD.BFBBA4E5@arx.gr> (raw)
Hi list, lots of head-banging on this one:
Some time ago, I asked what this message meant:
``NFS: NFSv3 not supported warning: mount version older than kernel''
since my mount was most certainly up-to-date.
Trond answered that I did not specify ``include NFSv3 client support''
when compiling the kernel.
Last night, I decide to upgrade to kernel 2.4.19, when I specifically
remembered to include NFSv3 support, when asked. However, on the next
reboot, upon mount, the same message appeared.
As I figured out just now, the message will appear (although I'm not
sure if it really means what it says) if NFS support is compiled inside
the kernel, but won't appear, if NFS support is compiled as a module
(again, I don't really know if it is indeed NFSv3, but it says it is).
Can anyone explain this ? Is NFSv3 meant to be only compiled as a module
?
Regards,
Thanos Chatziathanassiou
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2002-09-01 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-01 18:01 Thanos Chatziathanassiou [this message]
2002-09-01 19:30 ` NFSv3 not supported ? Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2004-06-02 14:07 NFSv3 not supported! Jeffrey Layton
2004-06-02 14:15 ` Jeffrey Layton
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=3D7255DD.BFBBA4E5@arx.gr \
--to=tchatzi@arx.gr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.