From: Lukas Kolbe <lukas@einfachkaffee.de>
To: autofs@linux.kernel.org
Subject: Re: using both nfs3 and nfs4 in a single mount map
Date: Mon, 01 Oct 2007 22:16:23 +0200 [thread overview]
Message-ID: <1191269783.12687.6.camel@localhost> (raw)
In-Reply-To: <1185549849.22250.35.camel@sangay.TechFak.Uni-Bielefeld.DE>
Hello List!
> We have /homes coming from many different servers, the older ones only
> speak v3 and the newer ones would love to speak v4 as we would.
We do have a solution for this problem now, it seems. A bit of testing
worked fine at least: We just use different yp-maps for solaris and
Linux, and the linux map contains the
"-fstype=nfs4,proto=tcp,port=2049"-Option for the entries on servers
that support it. It seems like a hack, but at least it works.
For this to work, we just have to absolutely make sure that every single
linux machine on the network supports nfs4 ... and I have yet to see a
single one that does this well ;)
--
Lukas
next prev parent reply other threads:[~2007-10-01 20:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 15:24 using both nfs3 and nfs4 in a single mount map Lukas Kolbe
2007-07-27 15:38 ` Ian Kent
2007-07-27 15:45 ` Lukas Kolbe
2007-07-28 7:15 ` Ian Kent
2007-07-28 7:22 ` Ian Kent
2007-07-30 13:36 ` Lukas Kolbe
2007-07-30 14:38 ` Ian Kent
2007-07-30 14:54 ` Ian Kent
2007-07-31 20:38 ` AutoFS5 Ldap base strangeness Jim Summers
2007-08-01 13:13 ` using both nfs3 and nfs4 in a single mount map Lukas Kolbe
2007-08-01 16:27 ` Murata, Dennis
2007-08-03 3:16 ` Ian Kent
2007-08-03 15:44 ` Jeff Moyer
2007-08-10 13:25 ` Lukas Kolbe
2007-08-13 3:22 ` Ian Kent
2007-08-13 3:29 ` Ian Kent
2007-08-13 14:06 ` Lukas Kolbe
2007-08-01 19:12 ` Jeff Moyer
2007-08-01 19:29 ` Peter Staubach
2007-08-01 19:36 ` Jeff Moyer
2007-08-01 19:42 ` Peter Staubach
2007-10-01 20:16 ` Lukas Kolbe [this message]
2007-10-02 4:36 ` Ian Kent
-- strict thread matches above, loose matches on Subject: below --
2007-07-27 15:09 Lukas Kolbe
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=1191269783.12687.6.camel@localhost \
--to=lukas@einfachkaffee.de \
--cc=autofs@linux.kernel.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 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.