9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: ramkromberg@mail.com
To: 9fans@cse.psu.edu
Subject: [9fans] [GUIDE] 9plan in qemu under windows
Date: Sat, 24 Mar 2007 19:11:49 +0200	[thread overview]
Message-ID: <20070324171149.AB7051BF297@ws1-1.us4.outblaze.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1972 bytes --]

The delay I'm referring to is the q&a: When not installing but rather
using the live boot, you are presented whenever you start the machine
with a series of questions (monitor, res, mouse), I managed to set
plan9.ini in the floppy image so that only one question will be
presented, but that is still one question too much.
Thats should be relevantly easy to those who are more experienced with
plan9 then me - which should be just about anyone in this forum...

The slow copy to HD is, as you said, me referring to the installation
process, this problem is consistent in all VM I tried to install plan 9
onto (vmware, virtual pc, parallels, many many others...) so I'm guessing
it has something to do with how plan9 acts rather then how the different
VMs preform, maybe this can be addressed in form of a kernel patch ? I
wouldn't know as I was yet to successfully diagnose the the exact cause
of the problem... - Thats the Todo part :-)
This requires a programmer that is capable to do what is required and
hopefully incorporate this modifications to the main build (one of the
nightly builds) so this won't require an attachment to this guide but
rather will be specified in the guide as a requirement to an updated
version of plan9.iso.

Their is also the issue of the sound, mp3 playback would be nice, but I
think that at least the /bin/games/* that require sound should work

Though I think this procedure is relatively safe to the experienced user
- without other people testing and feedbacking on it I stick to a strong
warning about hell's minions erupting from your monitor to devour your
souls and so and so...
Obviously the final step would be to upload a corrected and reorganized
version of this guide - again by someone other then me that has access to
the wiki and is less orinted to the random histerical shouting of 
"Beware the Darkness !!! The BSoD shall be its precursor !!!" ;-).

Ram Kromberg
ramkromberg@mail.com

[-- Attachment #2: Type: text/html, Size: 2218 bytes --]

             reply	other threads:[~2007-03-24 17:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-24 17:11 ramkromberg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-03-24 10:52 ramkromberg
2007-03-24 15:42 ` Jack Johnson
2007-03-24 19:33   ` Uriel

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=20070324171149.AB7051BF297@ws1-1.us4.outblaze.com \
    --to=ramkromberg@mail.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).