From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Wed,  8 Dec 2010 11:24:02 -0500
To: forsyth@terzarima.net, 9fans@9fans.net
Message-ID: <5e3c9c7f180af13e74219014e5d078c8@ladd.quanstro.net>
In-Reply-To: <8f646c8069d0c94b170f73daec7c7a42@terzarima.net>
References: <8f646c8069d0c94b170f73daec7c7a42@terzarima.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] the futility of QTMOUNT
Topicbox-Message-UUID: 896f57d0-ead6-11e9-9d60-3106f5b1d025

On Wed Dec  8 11:18:55 EST 2010, forsyth@terzarima.net wrote:
> QTMOUNT allows exportfs to detect an attempt to open a /srv file
> that has been opened and mounted somewhere on the system running exportfs
> (i'll refer to that as the `called system' and the client of exportfs as
> the `calling system').

exportfs never detects this bit being set.  i would expect the
type to be 90, not 80 in this example

; mkdir q; mount /srv/boot q; ls -qd q
(0000000000000001 48 80) q

if this isn't when QTMOUNT is set, when would it be set?
i can't find a single file in the system with qid.type&0x10.

- erik