All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Waychison <Michael.Waychison@Sun.COM>
To: jmoyer@redhat.com
Cc: autofs@linux.kernel.org
Subject: Re: compatibility with solaris '[no]browse' mount option
Date: Mon, 14 Jun 2004 18:03:05 -0400	[thread overview]
Message-ID: <40CE2099.8050605@sun.com> (raw)
In-Reply-To: <16589.63971.33237.4865@segfault.boston.redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jeff Moyer wrote:
> Hello,
>
> I've currently got a request to support the browse mount option.  It seems
> do-able entirely in the init script (and this seems the right place).
> Would there be any objections to such an approach?
>
> -Jeff
>
> _______________________________________________
> autofs mailing list
> autofs@linux.kernel.org
> http://linux.kernel.org/mailman/listinfo/autofs

How would you be able to do browsing from the init script given the
protocol restrictions imposed by autofs4?  Autofs4 uses the magic pgid
value as well as requiring a pipe fd to do communication.

If you are simply looking towards translating the browse option to the
ghosting used in automount4, then by all means go for it :)  However
please note that you will have to handle this in the daemon as well as
it is possible to nest indirect maps:

auto_master:

/src  auto_src -browse

auto_src:

linux -fstype=linux,browse auto_linux

If you are willing to wait, I've been working on the autofs
implementation I described at http://lkml.org/lkml/2004/1/6/167 that
will support browsing/lazy mounts.  I will be releasing it to the
community in the coming weeks pending some approvals..

- --
Mike Waychison
Sun Microsystems, Inc.
1 (650) 352-5299 voice
1 (416) 202-8336 voice
mailto: Michael.Waychison@Sun.COM
http://www.sun.com

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE:  The opinions expressed in this email are held by me,
and may not represent the views of Sun Microsystems, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAziCYdQs4kOxk3/MRAtDKAJ9LpL5XG6Jzz3GMxV37xn+fFFGnAACgkY69
d0xqX+0xTLKaTwja5pI1cGg=
=p9c+
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2004-06-14 22:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-14 19:17 compatibility with solaris '[no]browse' mount option Jeff Moyer
2004-06-14 21:48 ` Michael Blandford
2004-06-14 22:03 ` Mike Waychison [this message]
2004-06-14 22:15   ` Jeff Moyer
2004-06-15  1:48 ` Ian Kent
2004-06-15  1:49   ` Ian Kent

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=40CE2099.8050605@sun.com \
    --to=michael.waychison@sun.com \
    --cc=autofs@linux.kernel.org \
    --cc=jmoyer@redhat.com \
    /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.