2008/10/20 erik quanstrom <quanstro@quanstro.net>

> >         #to solve the authentication --- see the text bellow
> >         mount /srv/penelopa $home/shared/penelopa
> >         unmount $home/shared/penelopa
>
> i don't see an explination for this below.  what does this
> accomplish?  if you are trying to load more keys into your
> factotum, this can be more cleanly be done by putting them
> in secstore(1).  secstored(8) will serve them.


Well. I mentioned this reason in the PS note. I do this only to be able to
enter my login and password somehow. If I leave out the mount/unmount
commands then the 'local mount' will ask for these instead, but then you
can't just enter those --- the input/output goes to somewhere (?
/dev/kprint) and you get to a situation that some of what you type goes
somewhere, some goes elsewhere... Is it better now? I have no other reason
than this one.
Further, I just didn't want to really serve those like you propose. I do not
have a real reason for this (though I could easily think of some). I am now
simply interested in the kind of authentication through giving a login and a
password, if it can be made secure (I also asked about this) like eg. an
ordinary ssh connection.


> >         local mount /srv/penelopa $home/shared/penelopa
> >         #sleep 1  # --- see the text bellow; this pertains to my main
>
> the plumber doesn't require that the command it runs finish
> before returning.  (think of plumbing a file.  you don't want
> to hang until the editor exits.)
>

Ok, understand. Thus I only either have to find a way to be sure the first
command has ended, or just rely it does during that 1s and live with that.


> > question
> >         local srvfs CALC $home/shared/penelopa/home/ruda/CPA-CALC  #****
> >         local mount /srv/CALC $home/shared/CALC
>
> why are you doing this?
>

Ok. By doing all the complicated dance _without_ these two commands, I
achieve I have _globally_ accesible files served by the penelopa machine.
These files can be accessed under $home/shared/penelopa. But usually I need
files from this filesystem that are rather deep down this filesystem, eg.
/usr/ruda/shared/penelopa/home/ruda/CPA-CALC/doing/leads/co/up. You just
can't work fine with such long paths (in acme you then don't see anything
else). So the first idea is to do some bind. And you want to do this bind
again in the namespace of the plumber through the 'local' trick (you want
this bind to be global too). Further, I want this "bind" to be bound into
the '$home/shared' directory, which, however, is taken care of by mntgen
(for basically any possible remote connection). I am unable to do bind there
(you cannot make a directory when mntgen is running). Thus I decided to
again serve a portion of the filesystem (all under /home/ruda/CPA-CALC) and
then mount it to $home/shared/CALC, which works. Uff.
[It's just so difficult to break the locality of the namespace to make
something nicely globally accessible... :))]

Hopefully I explained...

Ruda