Re: [9fans] Canonical way to configure permanent remote cpu access

[lucio@proxima.alt.za]

> Having got Plan 9 running on the Pi with the networking functioning
> and having also compiled the version of drawterm for Mac OS X cocoa,
> I'm now wishing to configure Plan 9 so that it permanently allows
> access from remote terminals for authenticated users.

I'm going to shoot a bit from the hip here, but others will no doubt
correct my mistakes.

My immediate concern with the PI is that it's going to get into
trouble, eventually, with CF memory.  I would consider using rotating
rust if users are going to need it for storage, even add an external
file server if it's worthwhile.  I'm not convinced that one could set
up a CPU server with practically read-only storage, but that's not out
of the question if drawterm is the dominant access.

But you will need an auth server which you can piggyback on the CPU
server.  You need to read the relevant documents in /sys/doc.  The
secstore is optional, but very convenient; it is orthogonal to the
auth server, but only a CPU server will support it properly.

I rue the lack of support for 9p2000 in the conventional operating
systems, I would delegate all permanent storage to Plan 9 if I had a
choice.  Linux is an exception, but like windows it likes lots of disk
storage on the workstation, which is precisely what I would like to
eliminate (going back to my previous theme - drawterm gives you access
to local storage across many platforms, but I don't find that at all
appealing, which is why I use 9vx in preference to drawterm).

++L