9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: fig <type9freak@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: [9fans] the practicality of plan 9
Date: Sun, 30 Oct 2022 10:04:13 -0700	[thread overview]
Message-ID: <CANF_3RgxJEWY-QR4P18KzyOe0Haqh5ekQtp_hB_exrPEmWNz3w@mail.gmail.com> (raw)

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

hi everyone. let me say up front that i do not think plan 9 has to be
practical to be worth liking or using. please do not take this email as
provocative or interrogatory, we are all on the *9fans* mailing list for a
reason.

a month or so ago, i tried ‘getting into’ plan 9, and i have been
unsuccessful due to the difficulty of making a grid when i can’t port
forward or basic protocols like irc or torrent on my university network.
that being said, i have not given up, and my plan 9 plans are lying dormant
until i can attend the next sdf plan 9 bootcamp (when is that btw?) which
im betting on improving my proficiency with the OS so i can solve these
problems.

but today i was thinking about my grid, what my cpu server and file server
would be, and i realized that these servers would likely be not much more
powerful than the “terminal” machine i would be accessing them from in the
first place. now this doesn’t make plan 9 useless— it’s still so
interesting to me— but i want to be able to find some advantage to having a
grid.

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 :^)

fig

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

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

             reply	other threads:[~2022-10-30 17:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-30 17:04 fig [this message]
2022-10-30 17:41 ` sirjofri
2022-10-30 18:06 ` [9fans] " adventuresin9
2022-10-30 18:24 ` [9fans] " ori
2022-11-03 17:03   ` 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=CANF_3RgxJEWY-QR4P18KzyOe0Haqh5ekQtp_hB_exrPEmWNz3w@mail.gmail.com \
    --to=type9freak@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).