From: "John Floren" <slawmaster@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Plan9 on Microsoft Virtual PC 2004
Date: Thu, 3 Aug 2006 15:53:26 -0700 [thread overview]
Message-ID: <7d3530220608031553u33e6c189v86b88327b83a85b5@mail.gmail.com> (raw)
In-Reply-To: <44D26194.5030007@med-associates.com>
On 8/3/06, Drew Hohmann <drew@med-associates.com> wrote:
> Hi All,
> Has anyone had any luck getting plan9 to work in Virtual PC 2004? It's
> the easiest way for me to get started with it, but on my 3.4GHz
> hyper-threaded P4, plan9 installs ok but then when it's finished and
> reboots I get constant disk errors (Virtual PC is setup with a fixed
> size 4GB hd, and I'm installing fossil+venturi).
> On my 900MHz P3 (still using VirtualPC), plan9 installed ok, then I
> rebooted, logged in as glenda, created a new account, and entered
> fshalt. fshalt sat their synchronizing, and 24hrs later was still
> sitting there busy synchronizing (Virtual PC was setup with a 6GB fixed
> size hd, and fossil+venturi was installed).
>
> Has anyone had any luck with Virtual PC? I'd really like to use
> fossil+venturi in a production system, so just installing fossil alone
> isn't worth it.
>
> Thanks for any help.
> Drew
>
Well, I think the synchronizing problems with fshalt could be because
fossil dumps to venti at the first boot; this takes a very long time
and would take a lot longer on a virtual machine. I don't know if
fshalt stops the process; if it doesn't, I assume it would wait for
the dump to finish.
John
--
"The first thing we do, let's kill all the lawyers" -- Shakespeare, Henry VI
prev parent reply other threads:[~2006-08-03 22:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 7:33 [9fans] Best installation for a standalone desktop csant
2006-08-03 14:08 ` Gorka guardiola
2006-08-03 14:39 ` "Nils O. Selåsdal"
2006-08-03 16:25 ` Gorka guardiola
2006-08-03 20:50 ` [9fans] Plan9 on Microsoft Virtual PC 2004 Drew Hohmann
2006-08-03 22:53 ` John Floren [this message]
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=7d3530220608031553u33e6c189v86b88327b83a85b5@mail.gmail.com \
--to=slawmaster@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).