9front - general discussion about 9front
 help / color / mirror / Atom feed
From: "Lyndon Nerenberg (VE7TFX/VE6BBM)" <lyndon@orthanc.ca>
To: 9front@9front.org, Mack Wallace <mackbw@mapinternet.com>
Subject: Re: [9front] Is there a way to extend telnet through rexport?
Date: Mon, 05 Apr 2021 19:14:18 -0700	[thread overview]
Message-ID: <e83fff6fc99d7f5a@orthanc.ca> (raw)
In-Reply-To: <01000178a33d0f3b-ec840ea8-201f-432f-a5a5-b13993a12dba-000000@email.amazonses.com>

Mack Wallace writes:
> 
> I have a number of different sites which each have numerous disparate =
> systems that need to be administered - essentially by moving files =
> around. I want to use Plan9/9front to consolidate these systems at each =
> site and present them as a file structure on a server in the main =
> office. So essentially each location has its own subdirectory, and each =
> system as that site is represented by a subdirectory below that.

Depending on how 'disparate' those machines are, you might get
surprisingly close to your goal by running u9fs on the target hosts.
That, combined with a bit of ssh glue on the Plan9 side, will let
you import arbitrary filesystem trees from remote UNIX-like hosts.
It's not completely seamless, and you'll have to accept some very
basic 'all or nothing' permissions -- the exported filesystems will
have the permissions of the uid/gid running u9fs.  But you can get
a surprising amount of work done with this model, despite the
restrictions.

Several years ago I ran a setup like that to remotely monitor and
administer about a half dozen sites scattered all over the place;
it worked remarkably well, even if it wasn't the most blazingly
fast for network I/O.  Since then the Plan9 ssh implementations
have changed, so what I had before no longer works.  But, my lack
of motivation to fix bitrot aside, there's no reason I (read 'you')
couldn't build something like that today.

--lyndon

  parent reply	other threads:[~2021-04-06 10:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-05 18:13 Mack Wallace
2021-04-05 20:30 ` Steve Simon
2021-04-06  2:14 ` Lyndon Nerenberg (VE7TFX/VE6BBM) [this message]
2021-04-12 14:37   ` Mack Wallace

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e83fff6fc99d7f5a@orthanc.ca \
    --to=lyndon@orthanc.ca \
    --cc=9front@9front.org \
    --cc=mackbw@mapinternet.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).