9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: 9fans@9fans.net
Subject: Re: [9fans] the practicality of plan 9
Date: Sun, 30 Oct 2022 14:24:26 -0400	[thread overview]
Message-ID: <51836158C37DE6BC5B0D65B9E90CA3DE@eigenstate.org> (raw)
In-Reply-To: <CANF_3RgxJEWY-QR4P18KzyOe0Haqh5ekQtp_hB_exrPEmWNz3w@mail.gmail.com>

Quoth fig <type9freak@gmail.com>:
> so i ask: what are ways i could make a grid really shine? through design
> and/or usage, things that make a grid nice to have. i still enjoy 9front on
> a single machine, and plan9port is now a must-have on my unix machines. i
> know plan 9 wants a network, but why would a user want plan 9 to have a
> network? if that makes any sense :^)

As a single user, the biggest benefit I get is being
able to rapidly test and debug, with netboot, shared
binaries, and the ability to panic without losing any
work, and being able to share stuff with my home
machine when I'm hacking in a coffee shop (like I am now)

With a group of people, being able to share servers
means being able to share work. At the hackathon last
summer, we had set up a CPU/file server. We were
netbooting test kernels, but also sharing our work
in progress, data, and documents via our home dirs,
getting feedback, and even at times just editing
other people's files (the file server had permissions
wide open)


------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Td6c4be6d8502dbd0-Mde109e6c3a6a18b64306ac1d
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  parent reply	other threads:[~2022-10-30 18:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-30 17:04 fig
2022-10-30 17:41 ` sirjofri
2022-10-30 18:06 ` [9fans] " adventuresin9
2022-10-30 18:24 ` ori [this message]
2022-11-03 17:03   ` [9fans] " fig
2022-11-03 19:35     ` sirjofri
2022-11-08 23:07       ` fig
2022-11-09  3:20         ` Lucio De Re
2022-11-09  3:50           ` adventuresin9
2022-11-09 23:14             ` fig
2022-11-10  3:55               ` adventuresin9
2022-11-10  4:52                 ` fig
2022-11-10 12:05                   ` hiro
2022-12-18  1:30 ` Ethan Azariah
2022-12-18 16:29   ` cinap_lenrek

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=51836158C37DE6BC5B0D65B9E90CA3DE@eigenstate.org \
    --to=ori@eigenstate.org \
    --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).