From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Parallels v 3 and Plan 9, anyone tried yet?
Date: Wed, 29 Aug 2007 15:35:02 +0200 [thread overview]
Message-ID: <200708291335.l7TDZ3U08507@zamenhof.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Sat, 09 Jun 2007 05:04:27 -0700." <3e1162e60706090504h74728c4awcf08d2f5d7cda6af@mail.gmail.com>
late follow up. I'm running v 3 build 4560, with converted v 2 image.
seems to work fine, as far as I can judge --
apart from things I notice while typing this, see below (*)
did not (yet) try direct install of plan 9 in v 3.
resolution 1680x1050 is standard supported,
aux/vga -m vesa -p lists no depth 32 at all, only 8, 16 and 24.
this is on a quite recent 20" imac.
audio works per ac97 instructions in wiki
page 'Installing in parallels desktop on Mac OS X'
(*) minor problems:
I'm typing this from a vncv session to unix within the parallels
plan 9 on the mac. it works ok, but the mouse cursor does funny things.
screen shot http://www.cs.utwente.nl/~belinfan/parpic01.png
in the vnc-ed unix session I run rio as wm.
when I move the fat arrow in the vnc window,
while moving it a transparent square box
(or rather: hole, since it is tranparent)
of, dunno, 10x10 pixels appears in the mouse cursor,
moreover, pieces of the mouse cursor get left behind.
combined with the transparancy thing this means I can draw by
moving mouse moving south-east and can erase by moving mouse north-west.
also, probably unrelated to vncv, when I use lens outside the vncv window
I also see the image of the mouse cursor in the lens window. don't
recall seeing that in native plan 9.
turns out I have an 'international english' keyboard
where `/~ key is next to left shift key,
and a plus-minus/paragraph(?) key is at the usual `/~ position.
parallels seems not to know about this keyboard:
when I press the plus-minus/paragraph(?) key I get the `/~.
about the 'Installing in parallels desktop on Mac OS X' page:
I was surprised to see that
applying the suggested 'hget -o file URL' idiom to existing
/sys/src/9/port/devaudio.c overwrites the first part of it
by retreived file, but leaves the last part in place.
turns out 1) ac97 port/devaudio.c is shorter than the original
2) hget -o opens existing file without truncate, on purpose.
I guess in case of an existing (different) file, first get
original out of the way before using: hget -o file URL
Axel.
next prev parent reply other threads:[~2007-08-29 13:35 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 11:38 David Leimbach
2007-06-08 13:19 ` Gorka Guardiola
2007-06-08 15:01 ` Anant Narayanan
2007-06-08 15:46 ` Latchesar Ionkov
2007-06-08 16:17 ` andrey mirtchovski
2007-06-08 17:57 ` andrey mirtchovski
2007-06-08 18:33 ` Anant Narayanan
2007-06-08 18:37 ` andrey mirtchovski
2007-06-08 18:46 ` russell
2007-06-08 18:54 ` Anant Narayanan
2007-06-08 19:04 ` David Leimbach
2007-06-08 19:20 ` David Leimbach
2007-06-08 19:23 ` andrey mirtchovski
2007-06-08 19:35 ` David Leimbach
2007-06-08 19:43 ` andrey mirtchovski
2007-06-08 21:11 ` David Leimbach
2007-06-08 21:21 ` andrey mirtchovski
2007-06-08 21:42 ` David Leimbach
2007-06-09 0:41 ` andrey mirtchovski
2007-06-09 12:04 ` David Leimbach
2007-08-29 13:35 ` Axel Belinfante [this message]
2007-08-29 13:52 ` David Leimbach
2007-08-29 13:56 ` Craig-It Turner
2007-08-29 14:08 ` Axel Belinfante
2007-08-29 13:58 ` andrey mirtchovski
2007-08-31 8:44 ` Axel Belinfante
2007-08-31 14:09 ` David Leimbach
2007-06-08 18:52 ` Anant Narayanan
2007-06-08 19:03 ` 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=200708291335.l7TDZ3U08507@zamenhof.cs.utwente.nl \
--to=axel.belinfante@cs.utwente.nl \
--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).