From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Bernd Schubert <bernd-schubert@web.de>
Cc: clusternfs-users@lists.sourceforge.net, <nfs@lists.sourceforge.net>
Subject: Re: knfsd & unfsd on the same server
Date: 27 Feb 2003 18:54:10 +0100 [thread overview]
Message-ID: <shsheapip8d.fsf@charged.uio.no> (raw)
In-Reply-To: <200302271745.20691.bernd-schubert@web.de>
>>>>> " " == Bernd Schubert <bernd-schubert@web.de> writes:
> mount -t nfs -o mountprog=110005,nfsprog=110003,port=2050
> localhost:/test1 /mnt/test2
The 'nfsprog' option is unsupported by the Linux NFS client as the
mount program has no way of passing the number down to the kernel.
Cheers,
Trond
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-02-27 17:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 16:45 knfsd & unfsd on the same server Bernd Schubert
2003-02-27 17:54 ` Trond Myklebust [this message]
2003-02-27 18:45 ` Bernd Schubert
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=shsheapip8d.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=bernd-schubert@web.de \
--cc=clusternfs-users@lists.sourceforge.net \
--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.