9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Fwd: ubiquitous environment?
Date: Sat,  3 Mar 2018 15:24:15 -0800	[thread overview]
Message-ID: <CAJSxfmLM38T65S2e6U=ZyRON5_=2xrYS2--C6zEEMhEzZrKRGA@mail.gmail.com> (raw)
In-Reply-To: <CAOEdRO1WMXAPjW3ZbvL5tqBtRsEX0PSci-rTaMUxrmAayBaN6Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3027 bytes --]

You can dump the acme session at will and reload it to restore the session;
that combined with pxeloading a term or using drawterm, you almost don't
have to worry about losing your work or where you are. You can also use P9P
acme and import/fusemount the the Plan 9 fileserver with the same effect.

My home setup is a couple of Intel atom servers; one for Auth/Fileserver
(fossil+venti) and the other is a CPU (with a backup venti).  There are a
couple of RPi3's pxeloading the term kernel.  A Microtik RB tftp/bootp
loads a cpu kernel; it is the token MIPS machine (maybe VCore2 is supported
some day).  There are a couple of dormant (and noisy) x86 rackmount servers
that pxeboot cpu's for when I need a bit more oomph. Linux and MacOS
laptops have P9P and drawterm. I tend to fusemount the filesystem when I'm
using those.


On Sat, Mar 3, 2018 at 8:22 AM, Rudolf Sykora <rudolf.sykora@gmail.com>
wrote:

> Hello,
>
> I am not sure this email ever made it to the forum,
> hence I decided to ask once more...
>
> Thanks for any comments...
>
> ---------- Forwarded message ----------
> From: Rudolf Sykora <rudolf.sykora@gmail.com>
> Date: 16 June 2016 at 10:30
> Subject: ubiquitous environment?
> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
>
>
> Hello, everyone,
>
> I read the following some time ago and now got back to it.
> It's from an interview with Russ Cox.
> https://usesthis.com/interviews/russ.cox/
>
> --------------
> The thing I miss most about Plan 9 was the way that no matter which
> computer you sat down at, you had the same environment. Because we
> were working off a shared file server - there were no local disks on
> the Plan 9 workstations - you could go home and log in and all your
> work was there waiting. Of course, it only worked because we had good,
> fast connectivity to the file server, and only file state - not
> application state - transferred, but it was still a huge win.
>
> Today it's taken for granted that everyone has local files on disk and
> you need programs like Unison or Dropbox (or for the power users,
> Mercurial or Git) to synchronize them, but what we had in Plan 9 was
> completely effortless, and my dream is to return to that kind of
> environment. I want to be working on my home desktop, realize what
> time it is, run out the door to catch my train, open my laptop on the
> train, continue right where I left off, close the laptop, hop off the
> train, sit down at work, and have all my state sitting there on the
> monitor on my desk, all without even thinking about it.
> --------------
>
> Has anyone tried a setup like that? -- Having a server at work and
> working on it even from home/anywhere? And how is it set up? Does it mean
> that wherever you sit you somehow mount the window system to get
> to the exactly same state that you left the machine in?
> (Ie. something like a screen/tmux but supplied by the system itself?)
>
> Thanks for any comments!
>
> Ruda
>
>

[-- Attachment #2: Type: text/html, Size: 3669 bytes --]

  parent reply	other threads:[~2018-03-03 23:24 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
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 [this message]
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='CAJSxfmLM38T65S2e6U=ZyRON5_=2xrYS2--C6zEEMhEzZrKRGA@mail.gmail.com' \
    --to=skip.tavakkolian@gmail.com \
    --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).