From: hiro <firstname.lastname@example.org>
To: 9fans <email@example.com>
Subject: Re: [9fans] Re: How do I run plan9 in virtualbox?
Date: Thu, 17 Aug 2023 12:13:43 +0200 [thread overview]
Message-ID: <CAFSF3XO0frASCJ2xxftmVzhyG3bqof6nNpFxXgKMFHN2wM1KvA@mail.gmail.com> (raw)
oh, sorry for overlooking this mail before. so quite lucky for you
that this thread has clawed itself back out of it's grave.
the problem with vbox is the people who maintain it and allow bugs to
slip in on every other release. there is zero quality control.
normally, it's not a host/cpu issue and it's not a 9front issue. it's
a little babies like to rattle the box issue.
yay, and the 1001th support request about vbox has been answered. my pleasure.
please rate us with 5 stars for our continued engagement on this topic..
On Thu, Aug 17, 2023 at 4:18 AM Don Bailey <firstname.lastname@example.org> wrote:
> forgot to respond to this but fwiw, running plan9 on virtualbox seems to work peachy. Hiro what was the bug(s) you were running into before? I've never ran into an issue with it, but I've only used vbox on Linux; maybe it's a host/CPU issue?
> On Wed, Aug 2, 2023 at 4:50 PM Robert W. Baskette <email@example.com> wrote:
>> If you feel like targeting ppc, you could host 9front in z/VM your z/Series.
>> Here's some docs to get you started: https://www.ibm.com/docs/en/cic/1.1.4?topic=tutorials-getting-started-zvm
>> On Wed, Aug 2, 2023 at 3:25 PM Don A. Bailey <firstname.lastname@example.org> wrote:
>>> If you’re not running plan9 on a Simics Alpha DEC hosted on a PA-RISC B class workstation, are you even running plan9?
>>> On Aug 2, 2023, at 3:14 PM, redhatuser <email@example.com> wrote:
>>> So according to you, which one do you use?
> 9fans / 9fans / see discussions + participants + delivery options Permalink
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2023-08-17 10:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 18:06 [9fans] " yourlitlen1g
2023-08-02 19:07 ` hiro
2023-08-02 19:13 ` [9fans] " redhatuser
2023-08-02 19:23 ` Don A. Bailey
2023-08-02 20:49 ` Robert W. Baskette
2023-08-17 2:17 ` Don Bailey
2023-08-17 7:07 ` Peter Hull
2023-08-17 10:08 ` hiro
2023-08-17 10:13 ` hiro [this message]
2023-08-02 20:13 ` hiro
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).