From: "M. Osman Talayman" <firstname.lastname@example.org>
Subject: Re: [9front] Questions about the P9 kernel code
Date: Mon, 19 Sep 2022 11:14:55 +0200 [thread overview]
Message-ID: <CAJ4zFbJFe5yci=So67FWcYMmJo60d7XzYtpB_iYchQ5o_hkWgA@mail.gmail.com> (raw)
I have taken a step back since yesterdays conversation with Jacob. I'm
now going through K&R and working the exercises. At some point, I will
look into some of the libraries that come with the P9 C
I will also take your advice and, at some point, try to set up a P9
system consisting of an auth server (factotum), a couple of file
servers (using both fossil and venti) and a cpu server. I will use
RaspberryPis for this, or maybe do it using virtual machines.
If anyone knows of books or papers that are not on the P9 legacy or
Cat-v sites, that would be useful to me, please let me know.
Den man. 19. sep. 2022 kl. 09.28 skrev sirjofri
> Also my recommendation: Don't just "learn how the system works" but also "learn how to work with the system". Especially with plan 9 there's a huge difference.
> My learning experience was, 2 years learning the concepts by reading papers, documentation, man pages, basically everything I could find, but never really using the system. Then I started Plan 9 and everything was quite different. I had to reread many things, relearn many things and ask many question (while a chat platform like gridchat is much easier than email).
> Today, Plan 9 is my main platform, but only because I really learned how to use it (intuitively, not theoretically).
> Have fun on your journey.
next prev parent reply other threads:[~2022-09-19 9:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 16:21 M. Osman Talayman
2022-09-18 17:59 ` Jacob Moody
2022-09-18 18:20 ` M. Osman Talayman
2022-09-18 18:50 ` Jacob Moody
2022-09-19 7:25 ` sirjofri
2022-09-19 9:14 ` M. Osman Talayman [this message]
2022-09-19 9:51 ` hiro
2022-09-19 14:41 ` Jacob Moody
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).