From: Primus <rprimus+plan9@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Updated qemu wiki guide
Date: Sat, 31 Mar 2007 10:14:06 +0100 [thread overview]
Message-ID: <f11045270703310214x62516990x222c215e52deb4e@mail.gmail.com> (raw)
In-Reply-To: <f11045270703310203h29ae4626p6db470a99347b79e@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]
Can the link to Xen (found at
http://plan9.bell-labs.com/wiki/plan9/sandbox/index.html) be
included/referenced
from the updated page?
Regards,
--
primus
(Train yourself and be your own master.)
Narrowness of experience leads to narrowness of imagination.
Unix is very simple, but it takes a genius to understand the simplicity.
(Dennis Ritchie)
GPG Key: DB3FB476
Key fingerprint: B0FB C67E 2E7E 7032 7FE6 7FBC 28E9 2848 DB3F B476
On 3/31/07, ramkromberg@mail.com <ramkromberg@mail.com> wrote:
>
> I updated the qemu wiki guide:
> http://plan9.bell-labs.com/wiki/plan9/Virtual_machines/index.html
>
> Its Still has some formating issues (see the history to understand what a
> mess It was pasted into it b4 :-) )...
> Enjoy
>
> Ram Kromberg
> ramkromberg@mail.com
>
> --
>
> <http://a8-asy.a8ww.net/a8-ads/adftrclick?redirectid=en-mail_a_01>
>
--
primus
(Train yourself and be your own master.)
Narrowness of experience leads to narrowness of imagination.
Unix is very simple, but it takes a genius to understand the simplicity.
(Dennis Ritchie)
GPG Key: DB3FB476
Key fingerprint: B0FB C67E 2E7E 7032 7FE6 7FBC 28E9 2848 DB3F B476
[-- Attachment #2: Type: text/html, Size: 2382 bytes --]
next prev parent reply other threads:[~2007-03-31 9:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-31 0:09 ramkromberg
[not found] ` <f11045270703310203h29ae4626p6db470a99347b79e@mail.gmail.com>
2007-03-31 9:14 ` Primus [this message]
2007-03-31 16:45 ` Lorenzo Fernando Bivens de la Fuente
2007-03-31 21:47 ramkromberg
2007-04-01 5:12 ` lucio
2007-04-01 6:15 ` Skip Tavakkolian
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=f11045270703310214x62516990x222c215e52deb4e@mail.gmail.com \
--to=rprimus+plan9@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).