compatibility with solaris '[no]browse' mount option

compatibility with solaris '[no]browse' mount option

[Jeff Moyer]

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

Re: compatibility with solaris '[no]browse' mount option

[Michael Blandford]

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?
>  
>
Best I recall, browse is the same thing as ghosting - correct?

Is browsing/ghosting an all on or all off scenario?  Ie, could you have 
a submap that has ghosting on but not for others?  If so, I don't think 
you can handle it in the startup script.  In this case, I think we would 
have to handle it in the parsing of the maps.

Otherwise, I think it could be handled in the startup script.

I have often wondered about ghosting = browsing and handling this as well.

Michael

Disclaimer: The content of this message is my personal opinion only and 
although I am an employee of Intel, the statements I make here in no way 
represent Intel's position on the issue, nor am I authorized to speak on 
behalf of Intel on this matter.

Re: compatibility with solaris '[no]browse' mount option

[Mike Waychison]

-----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-----

Re: compatibility with solaris '[no]browse' mount option

[Jeff Moyer]

==> Regarding Re: [autofs] compatibility with solaris '[no]browse' mount option; Mike Waychison <Michael.Waychison@Sun.COM> adds:

Michael.Waychison> -----BEGIN PGP SIGNED MESSAGE-----
Hash> SHA1

Michael.Waychison> 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

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

I'm not quite that oblivious.  Close, but not quite.  ;)

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

Ahh, that's what I was looking for (and Mike Blandford had touched on this
as well in his reply).

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

I look forward to seeing it.  However, this is no substitute for adding
this bit of compatibility to autofs4.

Thanks!

-Jeff

Re: compatibility with solaris '[no]browse' mount option

[Ian Kent]

On Mon, 14 Jun 2004, 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?

Yes it's a daemon option.

I'll check on the submount issue.

Ian

Re: compatibility with solaris '[no]browse' mount option

[Ian Kent]

On Tue, 15 Jun 2004, Ian Kent wrote:

> On Mon, 14 Jun 2004, 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?
> 
> Yes it's a daemon option.
> 
> I'll check on the submount issue.

I mean the ghost <-> browse equivalence.

Should at least be partially OK.

Ian