9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Steve Simon <steve@quintile.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Fwd: ubiquitous environment?
Date: Sat,  3 Mar 2018 19:13:57 +0000	[thread overview]
Message-ID: <90864FBC-2F73-41EE-B47E-FCF123478CC3@quintile.net> (raw)
In-Reply-To: <CAFSF3XOKOJA54m8pP94p3NRJwvY8XupGA5NrU8yrVUaba9bLgA@mail.gmail.com>

i am pretty sure nemo’s octopus window system in planB had a way to save and restore its state so you could migrate your sessions from one terminal to another.

also, i would have thought you could build a windows drawterm which also included the code from exportfs so you could use 9fs and aan to get at the files on your windows box.

one bit that rangboom added was to be able to mount a filesystem  on windows from plan9. the windows IFS subsystem id not simple or friendly.

personally i think this idea will become more and more important as we get fiber to the home, local storage will become a thing of the past. 

-Steve


> On 3 Mar 2018, at 17:41, hiro <23hiro@gmail.com> wrote:
> 
> I have 9front running on a server at ovh france, my workstation is a
> windows 7 machine with drawterm in autostart. drawterm itself is run
> with -p option so that it can make use of AAN, which recovers broken
> TCP connections e.g. after resuming from sleep in the mornings or
> during any network state changes (windows frequently resets TCP
> connections even if it wouldn't be needed).
> 
> This way my rio windows always stay open on windows, even though all
> the windows network shares, vnc sessions, ssh stuff break every time
> and have to be painstakingly reconnected.
> If I could make the drawterm files accessible to windows (you rangboom
> people please step forward), then I could mount the cifs share on
> 9front, and then mount that on windows via drawterm to have more
> stable connectivity to my windows shares.
> I hope the rangboom people will share their technology so we won't
> have to port cifsd to drawterm instead.
> 
> if i am in the train and on my laptop i can log into the same server.
> i have a little LTE wifi router that maintains a tunnel to france so i
> can keep on using the same IP when my laptop and phone leave the house
> (actually AAN wouldn't even be needed for mobility if it wasn't for
> crappy low NAT timeouts during temporary connection problems and
> sleep).
> 
> Since my laptop is a separate terminal with it's own rio session,
> sadly the rio windows are not synced. As Russ mentioned though i have
> access to the same files.
> You have to be careful with open sam windows in case they have unsaved
> changes, but the dropbox people have the same merge conflicts. As a
> windows user I learned to save my files instead. :)
> 
> It would be nice to have less local state (i.e. rio windows, devdraw).
> Multiple approaches could be used quite easily.
> One of them that is very curious is mycroftiv's ANTS project, which
> separates the state of rio rc windows from the graphical environment.
> 
> acme also has state-saving functionality. it needs to be killed or
> told to though. in my scenario it wouldn't get killed cause my session
> survives, and i don't want it to close on one side normally :)
> 
> no idea if sam has anything for this, so right now i advocate
> discipline instead.




  reply	other threads:[~2018-03-03 19:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAOEdRO14fa3VT_dWatAo66aB3YD530Q3uK=KC2DjJ2T5wjQ1wQ@mail.gmail.com>
2018-03-03 16:22 ` Rudolf Sykora
2018-03-03 17:41   ` hiro
2018-03-03 19:13     ` Steve Simon [this message]
2018-03-03 19:18       ` Francisco J Ballesteros
2018-03-03 19:23         ` Steve Simon
2018-03-03 19:27           ` Francisco J Ballesteros
2018-03-03 20:17       ` Kurt H Maier
2018-03-03 23:32       ` hiro
2018-03-03 23:46         ` Steve Simon
2018-03-04  0:02           ` hiro
2018-03-04  0:03             ` hiro
2018-03-03 23:24   ` Skip Tavakkolian
2018-03-03 23:40     ` hiro
2018-03-03 23:43     ` hiro
2018-03-04  0:10       ` Skip Tavakkolian
2018-03-03 23:56   ` cigar562hfsp952fans
2018-03-04  7:17     ` Francisco J Ballesteros
2018-03-04  8:23       ` Ethan Grammatikidis
2018-03-04  8:57   ` Ethan Grammatikidis
2018-03-08 12:38     ` Rudolf Sykora
2018-03-08 19:19       ` FJ Ballesteros
2018-03-09  0:45         ` Aram Hăvărneanu
2018-03-09  5:50           ` Sean Callanan
2018-03-09  6:23           ` Francisco J Ballesteros
2018-03-08 23:29       ` 岡本健二

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=90864FBC-2F73-41EE-B47E-FCF123478CC3@quintile.net \
    --to=steve@quintile.net \
    --cc=9fans@9fans.net \
    /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).