Path: ...!weretis.net!feeder8.news.weretis.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: "Carlos E.R." <robin_listas@es.invalid>
Newsgroups: comp.os.linux.misc
Subject: Re: Here's One - NFS - Mounting Over Share = Nada
Date: Thu, 3 Apr 2025 20:48:58 +0200
Lines: 46
Message-ID: <qp13clxirc.ln2@Telcontar.valinor>
References: <UQ-dndQV6amaDnH6nZ2dnZfqnPednZ2d@giganews.com>
 <6ggvblxiu5.ln2@Telcontar.valinor> <vsj4l2$1jt3k$4@dont-email.me>
 <61jvblx7ff.ln2@Telcontar.valinor> <vsjqni$2bgo0$1@dont-email.me>
 <FLadnWvzcO68x3P6nZ2dnZfqnPidnZ2d@giganews.com>
 <68a2clxf62.ln2@Telcontar.valinor>
 <pImdnVzSPJVPNXP6nZ2dnZfqn_GdnZ2d@giganews.com>
 <vsmf9o$14dkr$2@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net SPuqxTaLYB/RzuxEucrAkww65nMPs3TAJKYkPhYlKKF7k6CP+N
X-Orig-Path: Telcontar.valinor!not-for-mail
Cancel-Lock: sha1:hY4mszm1V2mGYqr1g9L1l57MXQE= sha256:RS1KSgC4Ud+uPgWWveZavceXsfc1UNH0l/PpSxYfaZM=
User-Agent: Mozilla Thunderbird
Content-Language: es-ES, en-CA
In-Reply-To: <vsmf9o$14dkr$2@dont-email.me>
Bytes: 2983

On 2025-04-03 19:08, The Natural Philosopher wrote:
> On 03/04/2025 16:27, c186282 wrote:
>> On 4/3/25 8:07 AM, Carlos E.R. wrote:
>>> On 2025-04-03 11:51, c186282 wrote:



> Ahh. You need to add the 'crossmnt' directive to the servers /etc/ 
> exports file for the whatever it is you are mounting
> 
> 
> Then it will work the way you want it to

Right, because he is trying to export the parent directory. I export the 
mount points directly.

        crossmnt
               This option is similar to nohide but  it
               makes  it possible for clients to access
               all filesystems mounted on a  filesystem
               marked with crossmnt.  Thus when a child
               filesystem "B" is mounted  on  a  parent
               "A", setting crossmnt on "A" has a simi-
               lar effect to setting "nohide" on B.

               With nohide the child  filesystem  needs
               to   be   explicitly   exported.    With
               crossmnt it need not.  If a child  of  a
               crossmnt  file  is  not  explicitly  ex-
               ported, then it will be  implicitly  ex-
               ported  with  the same export options as
               the  parent,  except  for  fsid=.   This
               makes  it  impossible  to  not  export a
               child of a crossmnt filesystem.  If some
               but not all subordinate filesystems of a
               parent are to  be  exported,  then  they
               must be explicitly exported and the par-
               ent should not have crossmnt set.

               The nocrossmnt option can explictly dis-
               able  crossmnt if it was previously set.
               This is rarely useful.


-- 
Cheers, Carlos.