Paul Lussier wrote:
> In a message dated: Thu, 20 Dec 2001 15:33:00 PST
> "Taylor, ForrestX" said:
>
>
>>>Is this an undocumented feature?
>>>
>>I don't think that it is documented anywhere (Jeremy?).
>>
>
> Ouch! Oh well, as they say, "use the source!" :)
>
>
>>Like HPA mentioned, you need 2.4 kernels to do this.
>>
>
> What is it about the 2.4 kernel that's different? Is it that
> vfsbinds are only available in 2.4? Also, is there something in the
> newer autofs or mount code that tests for 2.4 or the vfsbind feature
> and decides to use that over symlinks?
Yes, and yes. At least autofs v3 attempts to establish a vfsbind during
its startup sequence, and if it succeeds uses vfsbinds, otherwise it uses
symlinks.
>>
>># add "nosymlink" here if you want to suppress symlinking local filesystems
>># add "nonstrict" to make it OK for some filesystems to not mount
>>opts="-fstype=nfs,hard,intr,nodev,nosuid"
>>
>
> So the only mention of 'nosymlink' is in an example auto.net file
> that only comes with the autofs source? It seems like this should be
> a documented option in either the autofs or mountd man pages.
>
This is autofs v4 only.
-hpa
