From: Ian Kent <raven@themaw.net>
To: Ondrej Valousek <webserv@s3group.cz>
Cc: autofs@linux.kernel.org
Subject: Re: Ubuntu NFS automount problem
Date: Tue, 25 Nov 2008 21:11:54 +0900 [thread overview]
Message-ID: <1227615114.3009.22.camel@zeus.themaw.net> (raw)
In-Reply-To: <492BE522.30703@s3group.cz>
On Tue, 2008-11-25 at 12:44 +0100, Ondrej Valousek wrote:
> > I don't think so, not the hosts map, since the export path doesn't match
> > the mount location path. There are other difficulties as well such as
> > having to modify paths in the export list as we go. However, exports
> > with "nohide" option should be automounted by the kernel client and not
> > confuse autofs so that part is ok with 5.0.4 or if the patch which deals
> > with this has been applied to 5.0.3.
> >
> > This is something I need to work on.
> >
> >
> So since the "nohide" option is a must for the Linux-based NFSv4 server,
> it will work (for most of the people)...
Don't forget that I need to remove the initial part of each export path
that corresponds to the NFSv4 export root which hasn't been done yet.
> Thanks,
> Ondrej
next prev parent reply other threads:[~2008-11-25 12:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-23 2:27 Ubuntu NFS automount problem Bill Shannon
2008-11-24 4:08 ` Ian Kent
2008-11-24 7:25 ` Bill Shannon
2008-11-24 12:52 ` Ian Kent
2008-11-24 15:42 ` Bill Shannon
2008-11-24 16:00 ` Peter Staubach
2008-11-24 16:26 ` Ian Kent
2008-11-24 20:31 ` Bill Shannon
2008-11-25 1:32 ` Ian Kent
2008-11-25 10:27 ` Ondrej Valousek
2008-11-25 11:27 ` Ian Kent
2008-11-25 11:44 ` Ondrej Valousek
2008-11-25 12:11 ` Ian Kent [this message]
2008-11-24 15:59 ` Bill Shannon
2008-11-24 17:43 ` Ian Kent
2008-11-24 20:35 ` Bill Shannon
2008-11-25 1:21 ` Ian Kent
-- strict thread matches above, loose matches on Subject: below --
2008-11-25 1:10 Brent Callaghan
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=1227615114.3009.22.camel@zeus.themaw.net \
--to=raven@themaw.net \
--cc=autofs@linux.kernel.org \
--cc=webserv@s3group.cz \
/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.