From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] missing includes for xen3
Date: Tue, 5 Dec 2006 13:38:08 -0700 [thread overview]
Message-ID: <13426df10612051238l10a86546ifd35ff12bd2f3211@mail.gmail.com> (raw)
In-Reply-To: <8f7aff7b74f603a6934253d3e165188e@hamnavoe.com>
On 12/5/06, Richard Miller <9fans@hamnavoe.com> wrote:
> "... to build a new kernel, copy or
> bind into /sys/src/9/xen3, copy or bind the xen/include/public
> directory from the Xen source distribution into /sys/src/9/xen3/xen-public,
> and mk"
Sorry, I don't know how I missed that! I am actually somewhat amazed
that anything in xen will directly compile -- this is a positive
change.
> By the way, I only just noticed that my Xen 3.0.3 updates had been lost when
> the sources fossil was reinitialised from the 2 November dump. I've re-done
> the updates now.
OK, I will get them.
Have you experimented with direct device access from domU? We are
looking at that now. Most of what they tell you in the manuals doesn't
seem to actually work.
ron
next prev parent reply other threads:[~2006-12-05 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 18:36 ron minnich
2006-12-05 20:03 ` Richard Miller
2006-12-05 20:38 ` ron minnich [this message]
2006-12-05 22:19 ` Richard Miller
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=13426df10612051238l10a86546ifd35ff12bd2f3211@mail.gmail.com \
--to=rminnich@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).