From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <00fb0ebd4d792996dce87ee1b473e8c7@9srv.net>
References: <CANszf4g8wKc0q+aRxcGkGjPC7NhK3MkkQ50A5X8QOf7n_G3O5Q@mail.gmail.com>
	<00fb0ebd4d792996dce87ee1b473e8c7@9srv.net>
Date: Sun,  7 Apr 2013 09:40:12 +0100
Message-ID: <CAOw7k5j6mKQKjwDZoMpdamGrJHrpVA_eEHj0s9sJmF7R-2kBvQ@mail.gmail.com>
From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: multipart/alternative; boundary=bcaec52c5e65c76e7904d9c14421
Subject: Re: [9fans] Fsctotum per user instances?
Topicbox-Message-UUID: 3efe4722-ead8-11e9-9d60-3106f5b1d025

--bcaec52c5e65c76e7904d9c14421
Content-Type: text/plain; charset=UTF-8

an auth/factotum is started by some initialisation code when you boot and
log in to your terminal.
on the cpu server, the same is true for the host owner (the owner of the
cpu service),
but then when you cpu(1) into a cpu server, your profile has a switch on
the service environment variable,
which is "cpu" for an incoming cpu call:

h% cat $home/lib/profile
...
switch($service){
case terminal
...
case cpu
...
bind /mnt/term/mnt/factotum /mnt/factotum
...
}

within cpu, the terminal's name space is available at /mnt/term, so it
simply binds the /mnt/factotum
in that name space onto /mnt/factotum in the cpu server, so you have all
your keys.

Note that this is a simple way in which the use of file servers to provide
system services and resources,
combined with 9P to import and export them, allows an interesting function
to be provided without having
any further code or special protocols.

--bcaec52c5e65c76e7904d9c14421
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>an auth/factotum is started by some initialisation co=
de when you boot and log in to your terminal.</div><div>on the cpu server, =
the same is true for the host owner (the owner of the cpu service),</div><d=
iv>
but then when you cpu(1) into a cpu server, your profile has a switch on th=
e service environment variable,</div><div style>which is &quot;cpu&quot; fo=
r an incoming cpu call:</div><div><br></div><div>h% cat $home/lib/profile</=
div>
<div>...</div><div>switch($service){</div><div>case terminal</div><div><spa=
n class=3D"" style=3D"white-space:pre">	</span>...</div><div>case cpu</div>=
<div><span class=3D"" style=3D"white-space:pre">	</span>...</div><div><span=
 class=3D"" style=3D"white-space:pre">	</span>bind /mnt/term/mnt/factotum /=
mnt/factotum</div>
<div><span class=3D"" style=3D"white-space:pre">	</span>...</div><div>}</di=
v><div><br></div><div class=3D"gmail_extra" style>within cpu, the terminal&=
#39;s name space is available at /mnt/term, so it simply binds the /mnt/fac=
totum</div>
<div class=3D"gmail_extra" style>in that name space onto /mnt/factotum in t=
he cpu server, so you have all your keys.</div><div class=3D"gmail_extra" s=
tyle><br></div><div class=3D"gmail_extra" style>Note that this is a simple =
way in which the use of file servers to provide system services and resourc=
es,</div>
<div class=3D"gmail_extra" style>combined with 9P to import and export them=
, allows an interesting function to be provided without having</div><div cl=
ass=3D"gmail_extra" style>any further code or special protocols.</div></div=
>

--bcaec52c5e65c76e7904d9c14421--