9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Larkin Nickle <me@larbob.org>
To: 9front@9front.org
Subject: Re: [9front] Bounty: tmux-esque /dev/draw intermediary
Date: Fri, 8 Jul 2022 17:04:59 -0400	[thread overview]
Message-ID: <be202eb4-a772-80f0-0f22-c05fdafc1483@larbob.org> (raw)
In-Reply-To: <CAG3JMtYpy+-Wdk1BLj0MZLpTXbis8-W0RNVLTrb8KExGx5Eskw@mail.gmail.com>

On 2022-07-08 16:28, Thaddeus Woskowiak wrote:
> How would open fd's to files and binds to things in /mnt/term be
> handled on reconnect on a different machine with a different
> /mnt/term?
> 
> Maybe fixing vnc audio is a better bounty for now.
> 

Maybe fair, but I'll stick to my bounty as I'd have more of a use for it.

In terms of the filesystem, for my own uses, I'd be fine with just 
expecting the user to not have anything open from the terminal's fs when 
disconnecting and putting the onus on them as much as possible. As hiro 
said, /mnt/term/dev is a different story.

On 2022-07-08 16:51, hiro wrote:
 > now that there's clear interest expressed in true currency values i
 > might think about cleaning it up and finding other non-9p-layer
 > workarounds for speeding up streaming for my few specific cases.

Would be great!

  parent reply	other threads:[~2022-07-08 21:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08 17:49 Larkin Nickle
2022-07-08 19:24 ` michael.grunditz
2022-07-08 19:33   ` Larkin Nickle
2022-07-08 19:40     ` Stanley Lieber
2022-07-08 19:46       ` Kurt H Maier
2022-07-08 19:51       ` mkf9
2022-07-08 20:05         ` Larkin Nickle
2022-07-08 20:11         ` Stanley Lieber
2022-07-08 20:15           ` mkf9
2022-07-08 20:24           ` Larkin Nickle
2022-07-08 20:28 ` Thaddeus Woskowiak
2022-07-08 20:51   ` hiro
2022-07-10 10:46     ` Philip Silva
2022-07-08 21:04   ` Larkin Nickle [this message]
2022-07-08 21:11   ` mkf9

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=be202eb4-a772-80f0-0f22-c05fdafc1483@larbob.org \
    --to=me@larbob.org \
    --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).