From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Virtual PC server
Date: Tue, 19 Sep 2006 08:58:47 +0100 [thread overview]
Message-ID: <aff54fa4ba993a36f5cc9f2612c71226@hamnavoe.com> (raw)
In-Reply-To: <7d3530220609181906l3ff6372dpce0c33dca3de1c51@mail.gmail.com>
> My main concern with the Virtual PC route is availability;
> any other pros or cons you guys can come up with?
My experience with Virtual PC (on a 1.25Ghz G4) is that it's much
too slow for any kind of serious use.
next prev parent reply other threads:[~2006-09-19 7:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 2:06 John Floren
2006-09-19 7:58 ` Richard Miller [this message]
2006-09-19 10:19 ` Anthony Sorace
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=aff54fa4ba993a36f5cc9f2612c71226@hamnavoe.com \
--to=9fans@hamnavoe.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).