From: mycroftiv@sphericalharmony.com
To: 9front@9front.org
Subject: Re: [9front] wanted: ssh server, tmux-alike (no offense, hubfs)
Date: Wed, 18 Dec 2019 11:27:09 -0600 [thread overview]
Message-ID: <6D91B2BCEB36C948D6F6F3D7441A72EA@sphericalharmony.com> (raw)
In-Reply-To: 4BE2FCA4-3D57-4BB2-94D4-C7077EE667D3@stanleylieber.com
You might take a look also at consolefs(4) which I believe could be configured to do pretty much what hubfs does.
There are a fair amount of knobs on hubfs, but some awkward things like the lack of replay-sync between stdout and stderr remain.
As to whether a specific combination of use-case, application, and user will end up producing the desired results, no guarantees.
If you do decide to experiment with hubfs, I'll try to tech-support. I'm more irc/gridchat oriented than email though in general.
-mycro
next reply other threads:[~2019-12-18 18:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 17:27 mycroftiv [this message]
[not found] <D7C0B9052E9D2EE1EBF66ECBD03A8BFB@ewsd.inri.net>
2019-12-18 9:12 ` hiro
2019-12-18 15:45 ` Stanley Lieber
2019-12-18 22:17 ` hiro
2019-12-19 4:24 ` Jacob Moody
2019-12-19 5:39 ` Stanley Lieber
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=6D91B2BCEB36C948D6F6F3D7441A72EA@sphericalharmony.com \
--to=mycroftiv@sphericalharmony.com \
--cc=9front@9front.org \
/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).