From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: From: Charles Forsyth Date: Wed, 8 Dec 2010 17:19:03 +0000 To: 9fans@9fans.net In-Reply-To: <5e3c9c7f180af13e74219014e5d078c8@ladd.quanstro.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: 89745050-ead6-11e9-9d60-3106f5b1d025 >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 i wouldn't! it's not set on the *mounted* file system in the scope of exportfs but on the file (/srv/boot), once opened, that provides the 9p stream that the *client* of exportfs is opening and wants to mount. it's typically $wsys in a cpu window, such as /mnt/term/srv/rio.forsyth.5 you can only see the bit on the qid you get from fstat, which is what exportfs does.