From: "Benjamin Huntsman" <BHuntsman@mail2.cu-portland.edu>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] Virtual PC + Win64 = i/o errors
Date: Mon, 6 Apr 2009 07:38:22 -0700 [thread overview]
Message-ID: <621112A569DAE948AD25CCDCF1C075331AB4BD@dolly.ntdom.cupdx> (raw)
In-Reply-To: <85e5bd63fb2f1d7989c3f57f9c52f7a9@quanstro.net>
[-- Attachment #1: Type: text/plain, Size: 168 bytes --]
>do you have a way of compiling kernels?
Sure do! The original copy of the same VM in question still runs fine on it's original host...
Thanks much!!
-Ben
[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 2364 bytes --]
next prev parent reply other threads:[~2009-04-06 14:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 20:42 Benjamin Huntsman
2009-04-05 22:33 ` erik quanstrom
2009-04-05 23:40 ` Benjamin Huntsman
2009-04-06 14:18 ` erik quanstrom
2009-04-06 14:38 ` Benjamin Huntsman [this message]
2009-04-07 5:00 ` erik quanstrom
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=621112A569DAE948AD25CCDCF1C075331AB4BD@dolly.ntdom.cupdx \
--to=bhuntsman@mail2.cu-portland.edu \
--cc=9fans@9fans.net \
/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).