From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <f7d7f271631cab400d003688b7fa46cf@granite.cias.osakafu-u.ac.jp>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cpu command and 9660srv
From: Kenji Okamoto <okamoto@granite.cias.osakafu-u.ac.jp>
Date: Fri, 21 May 2004 17:43:01 +0900
In-Reply-To: <ab577951320ee2312f680ad667337133@terzarima.net>
MIME-Version: 1.0
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 8272f8d2-eacd-11e9-9e20-41e7f4b1d025

Thanks Charles,

> 9660srv 9660.$user
> mount /srv/9660.$user /somewhere mydevice

This is easier for our purpose, because users don't need to have knowledge
of Plan 9.   Additionaly, easy to make it a scripted command.   A disadvantage
is we cannot exit from cpu command without killing the 9660srv.$user process.

> even so, if you run 9660srv on the terminal, and mount it
> somewhere before typing cpu, the cpu will have access
> to the data through /mnt/term, and you can bind /mnt/term/n/cd /n/cd
> on the cpu to make access more convenient.

to bind the /mnt/term/n directory to /n?
Why the cpu command doesn't this?

Kenji