From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Fri, 22 Feb 2013 09:14:08 -0500
To: 9fans@9fans.net
Message-ID: <53ee78b855503f0b5aa5f63a79ee567c@brasstown.quanstro.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: [9fans] mount(2)
Topicbox-Message-UUID: 1d62a356-ead8-11e9-9d60-3106f5b1d025

i was trying something a little bit different on the file
server (ken's) and i noticed that mount -n does not work
unless the user is none.  digging in i see that ken's file
server will allow none with no afid, but will not allow
anyone else.  this seems sensible.  if you don't want auth,
attach as none.  however, mount(2) combined with the
mnt driver doesn't cooperate.  there's no way to specify
the attaching user.  (unless i'm missing something.)

(fossil just treats the attaching user as none.  if there's
no afid.)

so, why doesn't mount(2) take an attaching user argument?

- erik