From: segaloco via COFF <coff@tuhs.org>
To: COFF <coff@tuhs.org>
Subject: [COFF] Inferno/Limbo Experiences
Date: Fri, 04 Aug 2023 16:50:42 +0000 [thread overview]
Message-ID: <kpJKPiqeZOQxGG2u4ghY61wylOWkNyzirJXObVRoj1ZsDnaWEyCZBSyXPeC5_I8z5eeaGvcnwkeeblcs9lxt5OACStO59UmfOvSR6iG8QsI=@protonmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
So as I was searching around for literature I came across someone selling a 2 volume set of Inferno manuals. I had never seen print manuals so decided to scoop them up, thinking they'd fit nicely with a 9front manual I just ordered too.
That said, I hate to just grab a book for it to sit on my shelf, so I want to explore Inferno once I've got literature in hand. Does anyone here know the best way of VMing Inferno these days, if I can just expect to find a copy of distribution media somewhere that'll work in VirtualBox or QEMU or if there's some particular "path of righteousness" I need to follow to successfully land in an Inferno environment.
Second, and I hope I don't spin up a debate with this, but is this something I'm investing good time in getting familiar with? I certainly don't hear as much about Inferno as I do about Plan9, but it does feel like it's one of the little puzzle pieces in this bigger picture of systems theory and development. Have there been any significant Inferno-adjacent developments or use cases in recent (past 10-15) years?
- Matt G.
[-- Attachment #2: Type: text/html, Size: 1503 bytes --]
next reply other threads:[~2023-08-04 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 16:50 segaloco via COFF [this message]
2023-08-04 17:06 ` [COFF] " Edouard Klein
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='kpJKPiqeZOQxGG2u4ghY61wylOWkNyzirJXObVRoj1ZsDnaWEyCZBSyXPeC5_I8z5eeaGvcnwkeeblcs9lxt5OACStO59UmfOvSR6iG8QsI=@protonmail.com' \
--to=coff@tuhs.org \
--cc=segaloco@protonmail.com \
/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).