From: fig <type9freak@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] the practicality of plan 9
Date: Thu, 3 Nov 2022 10:03:46 -0700 [thread overview]
Message-ID: <CANF_3RgSiR7o6NLd8GFLO8K_iVYKC6Ake-Kc59cFwKnTr+kCRA@mail.gmail.com> (raw)
In-Reply-To: <51836158C37DE6BC5B0D65B9E90CA3DE@eigenstate.org>
[-- Attachment #1: Type: text/plain, Size: 1495 bytes --]
ori, adventuresin9, sirjofri:
thank you kindly for your responses. i am very sick so i do not contain the
energy to quote your replies and respond to them individually. apologies.
i have a better understanding of plan 9 grids now. as i understand it, the
elegance of plan 9 is in its simplicity, not in unique features or
abilities.
your personal examples are appreciated. ori, kernel development seems
beyond my horizon at this point, but it may come sooner than i think.
adventuresin9, your explanation of a cpu server was very helpful. and
sirjofri, you seem to be correct about a file server being so nice. i set
up a local file server on a laptop just to experiment, and while i’m
definitely not taking full advantage of what it has to offer, i understand
the convenience.
thanks again you guys. i recently posted on the r/plan9 subreddit with a
short list of small questions. if anyone would be so generous as to provide
understanding to any of them, i would be most grateful. i am eager to give
back to the plan 9 community as soon as possible, instead of taking up your
time. i’m documenting all helpful information, scripts, etc. so that once i
get comfortable i can have make a document to help others go down the same
path.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Td6c4be6d8502dbd0-M552425660be782a5a9d011cd
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 2138 bytes --]
next prev parent reply other threads:[~2022-11-03 17:04 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 ` [9fans] " ori
2022-11-03 17:03 ` fig [this message]
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_3RgSiR7o6NLd8GFLO8K_iVYKC6Ake-Kc59cFwKnTr+kCRA@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).