9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: hahahahacker2009@gmail.com
To: 9fans@9fans.net
Subject: Re: [9fans] Should the original Plan9.iso be disregarded?
Date: Wed, 7 Jan 2026 22:49:16 +0700	[thread overview]
Message-ID: <1e0cd52a00363ea5f05929c58eb29214@gmail.com> (raw)
In-Reply-To: 17677637350.d153.44351@composer.9fans.topicbox.com

Quote:
> I have many copies of Plan 9 from various places over the years that I've tried out.
> In the case of the original plan9.iso I was able to get it to boot into Glenda as a live-user, and I am able to complete the installation. However, there is always a corrupt MBR when I try to boot it up.
> 

Plan 9 4th edition is not expected to boot on x86...
I can pxe boot it on my HP 8300 elite (core i5).

> I've successfully booted 9-front on VMware as well, and noticed that the Glenda logo window is missing. I honestly don't know the purpose of this window, but it displays the time/date and shows the Glenda character. That bothered me because to me, I wanted to demonstrate/experience the real Plan 9.
> 

That window is running faces -i, which read the mail box and show the
faces of people.  Right clicking a face will open the email!
If you have subscribed for 9fans emails and connect to gmail's imap
server, you will see the faces of everyone here (except me).

9front might have modified the installer

> I now have 9 Legacy images, and I'm going to give them a go as I THINK these are now the "vanilla" Plan 9 post Vita-Nuova ownership. Is that correct? Is it safe to assume 9-Legacy essentially replaces what I assume are the 4th edition Plan 9 images?
> 

Vita Nuova owns Inferno
Just use 9legacy, it is stable.
There is another iso image which contain Geoff's tree - perhaps less
stable, moving faster, does not include git and all the bug fixes, and
have refused changes to be usable in openbsd vmm.

Also - for the more experienced, how to get rid of the doasm notfound
and unbalanced PUSH/POP errors when the list of opcodes changes?  Even
compiling 6[acl] on another architecture does not work for me now.

> ------------------------------------------
> 9fans: 9fans
> Permalink: https://9fans.topicbox.com/groups/9fans/T3466290644f9d46b-Ma595f0e74f90df7992a575ae
> Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Te9ac761ea9ccc91c-M785fafffa2a5c20e3e212bef
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

             reply	other threads:[~2026-01-07 15:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-07 15:49 hahahahacker2009 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-01-07 15:58 [9fans] Should the original Plan9.iso be disregarded? hahahahacker2009
2026-01-07  5:28 drownthepoor
2026-01-07 15:28 ` Thaddeus Woskowiak

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=1e0cd52a00363ea5f05929c58eb29214@gmail.com \
    --to=hahahahacker2009@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).