9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Plan 9 on Mac Mini x86?
Date: Wed,  5 Apr 2006 09:24:10 -0700	[thread overview]
Message-ID: <3e1162e60604050924s14dc7701l605069d2eb49732c@mail.gmail.com> (raw)
In-Reply-To: <6e35c0620604050834x758eb82dp209ef5003416e444@mail.gmail.com>

On 4/5/06, Jack Johnson <knapjack@gmail.com> wrote:
> On 4/5/06, Daniel Soderstrom <snaggs@mac.com> wrote:
> > Can Plan 9 be installed on a x86 Mac Mini? I'd like to have a play
> > with Plan 9, but don't want a ugly bitsa PC taking up the space. I
> > should be able to do everything remotely on the Plan 9 box just using
> > ssh or x windows?
>
> Plan 9 runs well in QEMU, and there's a friendly port to OSX that
> seems to have universal binaries:
>
> http://www.kberg.ch/q/
>
> >From there, you can boot the ISO image directly, do a standard
> installation, and have the joy of easy access to a Web browser while
> you're learning how to set it up. :)
>
> Performance on an x86 Mac should be pretty good, but I've only tried
> it on PowerPC.

I've been using this all week.  It's not too shabby, though the mouse
cursor refresh seems a bit choppy.  I'm looking forward to seeing what
Parallels comes up with and if it will run closer to native speed. 
I'm happy to shell out 50 bucks for a good hypervisor. :-)

One word of caution, don't do the venti install on a large disk
partition in an emulator that can't do DMA.  Zeroing out the disk is
painful enough on real hardware though I think Russ has improved that
or will have those improvements available soon.

>
> SSH does exist for Plan 9, but the remote X alternatives are VNC and
> drawterm, as Plan 9 doesn't use X for its native display.
>

drawterm is like, sent from heaven or something :)

> Best of luck,
>
> -Jack
>


  reply	other threads:[~2006-04-05 16:24 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-05  7:46 Daniel Soderstrom
2006-04-05 14:26 ` David Leimbach
2006-04-05 14:39   ` Gabriel Diaz
2006-04-05 14:47     ` David Leimbach
2006-04-05 16:26       ` David Leimbach
2006-04-05 18:52         ` David Leimbach
2006-04-05 20:22           ` Jack Johnson
2006-04-06 22:06             ` andrey mirtchovski
2006-04-06 22:23               ` David Leimbach
2006-04-06 22:29                 ` andrey mirtchovski
2006-04-06 22:36                   ` David Leimbach
2006-04-06 22:40                     ` David Leimbach
2006-04-07  0:47                       ` David Leimbach
2006-04-07  1:43                         ` quanstro
2006-04-07  1:17                           ` David Leimbach
2006-04-05 14:42   ` Harri Haataja
2006-04-05 14:47   ` Ronald G Minnich
2006-04-05 15:22     ` David Leimbach
2006-04-05 15:34 ` Jack Johnson
2006-04-05 16:24   ` David Leimbach [this message]
2006-04-07  1:23 erik quanstrom
2006-04-07  1:29 ` David Leimbach
2006-04-07  3:52   ` lucio
2006-04-07  5:53     ` David Leimbach
2006-04-07  2:30 ` Russ Cox
2006-04-07  1:32 erik quanstrom
2006-04-07  1:43 ` David Leimbach
2006-04-07  2:23   ` jmk
2006-04-07  3:19     ` David Leimbach

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=3e1162e60604050924s14dc7701l605069d2eb49732c@mail.gmail.com \
    --to=leimy2k@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).