From: sml@firstpost.pub
To: 9fans <9fans@9fans.net>
Subject: [9fans] Difference between Plan 9 legacy and 9front
Date: Thu, 27 Jan 2022 06:12:24 -0500 [thread overview]
Message-ID: <16432819440.2BDEed5fB.31029@composer.9fans.topicbox.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 795 bytes --]
Hello everyone,
I'm really looking forward to getting to grips with Plan 9 in depth, but would have a question in advance.
Since I want to use Plan 9 on an amd64 system, my understanding is that I am left with two options: Plan 9 legacy and 9front. I want to use Plan 9 on bare metal, so Plan9port would only be a stopgap.
To be able to decide on an option, I would like to understand the differences. Do the two systems differ in their stated goals, or is 9front's development merely historical (e.g. for licensing reasons)?
Many thanks in advance!
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tbaab87532a204e00-M2b585eb221494512ae85b9fe
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 5876 bytes --]
next reply other threads:[~2022-01-27 11:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 11:12 sml [this message]
2022-01-27 11:45 ` Alexandr Babic
2022-01-27 12:34 ` sml
2022-01-27 12:18 ` Keith Gibbs
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=16432819440.2BDEed5fB.31029@composer.9fans.topicbox.com \
--to=sml@firstpost.pub \
--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).