9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Shawn Rutledge <lists@ecloud.org>
To: 9front@9front.org
Subject: Re: [9front] Enabling a service
Date: Tue, 7 May 2024 16:16:05 -0700	[thread overview]
Message-ID: <8557C94F-E6DF-42BA-B92E-6BBB0751116A@ecloud.org> (raw)
In-Reply-To: <F59EF54D6347DADE292FDFE273A87BC7@gaff.inri.net>

And yet, the FQA recommends laptops.  Usually the assumption with a laptop is you can take it on the subway or to the coffee shop and keep working.  That implies that you want to have some relevant files with you.  (So it’s good the default install has a local filesystem.)  Then later you get back to the home/office and maybe want to use a machine with a bigger monitor and more files available, but some work in progress is on the laptop so maybe you want to rcpu to it for a while.  Eventually files get synced up again (manually or automatically).  Maybe at home there is a file server, sure it’s good to have the dumps.  That’s probably how I’d use it as soon as I get to the point of depending on Plan 9 for any particular task, not just trying things.  (It reminds me of learning how to use Linux, 30 years ago.  It was at a similar level of development back then.)

So obviously there’s a tradeoff between 9front being usable by a laptop user today vs. trying to preserve the labs experience, and having to answer the same questions over and over (how do I start a service, why do I have to reboot into a different mode to make that possible).  I won’t ask how to do that; but others will.

As for "half-assed network services", I assume that means security concerns; ok so not enough faith in how secure the services are by default (well that ought to be fixable eventually?), and not enough faith in users not to realize that they should try experiments on a local LAN before connecting the services to the Internet (which usually involves some router work anyway, assuming the machine is behind one)?  People who take excessive risks are mainly risking their own files; they should know better, but they probably aren’t going to have a lot of files on Plan 9 anyway.  What’s the worst risk besides data theft?  A mail server getting used as a spam relay or something like that?  I agree that setting up a mail server should be more effort.

> 9p vs latency is a losing battle. trying to run a diskless terminal
> over the internet really, REALLY sucks. even drawterm is not great
> in this context.

I left a 9front machine running on my LAN in Norway while I’m in Phoenix for a while, and set up a wireguard vpn on the openwrt router in Norway so that I can connect to home.  Latency in Phoenix is worse than normal (Verizon wireless internet: it's only meant to be temporary).  Despite that, the performance I see connecting with rcpu or drawterm halfway around the world is comparable to connecting to Linux over VNC: not bad for an experiment (as long as wifi on 9front is not in the path!  ;-)  I don’t expect to play video over that link.  But I also have qualms about letting the router connect 9p over the Internet to that Plan 9 machine, since I don’t know yet all the varieties of half-assedness to expect by default.  I think I have to try the Plan 9 network forwarding at some point though, see if the claim that it’s as good as a VPN really holds up.  But I have to learn enough about security before even trying, it seems.


  parent reply	other threads:[~2024-05-07 23:20 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06 11:32 Rocky Hotas
2024-05-06 11:58 ` Alex Musolino
2024-05-06 12:43 ` ori
2024-05-06 15:16   ` Scott Flowers
2024-05-06 15:37     ` sirjofri
2024-05-06 16:32     ` Stanley Lieber
2024-05-06 22:18   ` Rocky Hotas
2024-05-06 22:59     ` ori
2024-05-06 23:00     ` ori
2024-05-07  8:22       ` Rocky Hotas
2024-05-07  8:29         ` Frank D. Engel, Jr.
2024-05-07  9:03           ` Rocky Hotas
2024-05-07  9:14         ` sirjofri
2024-05-07 21:11           ` Shawn Rutledge
2024-05-07 21:35             ` Kurt H Maier
2024-05-07 21:45               ` sirjofri
2024-05-07 21:54             ` sl
2024-05-07 21:58               ` sl
2024-05-07 23:15                 ` Lennart Jablonka
2024-05-07 23:16                 ` Shawn Rutledge [this message]
2024-05-07 23:45                   ` Shawn Rutledge
2024-05-08  0:34                   ` Kurt H Maier
2024-05-08  0:35                   ` sl
2024-05-08  1:05                     ` Jacob Moody
2024-05-08  1:24                       ` sl
2024-05-08  7:22                         ` hiro
2024-05-08 14:04                           ` Stanley Lieber
2024-05-08 12:08                         ` Stuart Morrow
2024-05-08 16:37                           ` Brian Stuart
2024-05-08 20:16                             ` hiro
2024-05-08 21:26                               ` Stuart Morrow
2024-05-08 21:17                             ` Disconnection-tolerant / distributed filesystems (was Re: [9front] Enabling a service) Shawn Rutledge
2024-05-08 14:25                         ` [9front] Enabling a service Jacob Moody
2024-05-08  3:41                       ` Ori Bernstein
2024-05-08  4:09                         ` sl
2024-05-08  8:39                           ` Frank D. Engel, Jr.
2024-05-08 14:17                             ` Jacob Moody
2024-05-08 15:49                               ` Frank D. Engel, Jr.
2024-05-08 16:10                                 ` Jacob Moody
2024-05-08 16:33                                   ` Frank D. Engel, Jr.
2024-05-08 17:27                                     ` Jacob Moody
2024-05-08 18:00                                       ` Steve Simon
2024-05-08 19:46                                         ` hiro
2024-05-08 19:46                                   ` Roberto E. Vargas Caballero
2024-05-08 20:34                                     ` tlaronde
2024-05-08 14:57                   ` Lucas Francesco
2024-05-08 15:10                     ` an2qzavok
2024-05-08  2:11             ` Thaddeus Woskowiak

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=8557C94F-E6DF-42BA-B92E-6BBB0751116A@ecloud.org \
    --to=lists@ecloud.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).