From: adventuresin9@gmail.com
To: 9fans <9fans@9fans.net>
Subject: [9fans] Re: the practicality of plan 9
Date: Sun, 30 Oct 2022 14:06:55 -0400 [thread overview]
Message-ID: <16671532150.E6Ebca.2134@composer.9fans.topicbox.com> (raw)
In-Reply-To: <CANF_3RgxJEWY-QR4P18KzyOe0Haqh5ekQtp_hB_exrPEmWNz3w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1324 bytes --]
I can give some examples of my grid.
A big benefit to having a dedicated file server is that no matter what "terminal" I sit at, I always see the same desktop and files. I can sit at my desk with drawterm on a Linux workstation, or in bed with drawterm on a Windows laptop, or using a raspberry pi as a bare metal 9Front terminal.
CPU server doesn't have to mean number crunching. I have a raspberry pi cpu server that has a sensors hooked to it, and runs a file system to send commands to smart lights. And another that has sensors and displays simple data using an led grid. I made a kind of router using an old Dell and a used 4 port nic, and it is technically a cpu server, in that it has no monitor or keyboard and boots off the file server.
As a learning experience, having separate file/cpu/terminal is nice because you can actually practice integrating them on a network. However, if you are trying to do this out of a university dorm, then I could see things being so cramped that running a bunch of computers to kind of do 1 thing would seem overly complicated.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Td6c4be6d8502dbd0-Me1665fdd806705e533a7aa58
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 1950 bytes --]
next prev parent reply other threads:[~2022-10-30 18:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 17:04 [9fans] " fig
2022-10-30 17:41 ` sirjofri
2022-10-30 18:06 ` adventuresin9 [this message]
2022-10-30 18:24 ` 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=16671532150.E6Ebca.2134@composer.9fans.topicbox.com \
--to=adventuresin9@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).