From: Benjamin Reed <ranger@befunk.com>
To: Jan van Rensburg <jan.van.rensburg@epiuse.com>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: FAQ
Date: Mon, 02 Feb 2004 10:10:48 -0500 [thread overview]
Message-ID: <401E6878.1010402@befunk.com> (raw)
In-Reply-To: <8A6995DE-5561-11D8-B61A-00039350B9F2@epiuse.com>
Jan van Rensburg wrote:
> Hi,
>
> With Ian's blessing I started a FAQ for Xen. This is the first step in
> creating comprehensive documentation for Xen.
>
> Up till now I've only tracked the mailing list for the last month or so,
> and incorporated Q and A's into the FAQ, so there's a lot of scope for
> improvement. I'd appreciate your comments, suggestions and more content.
>
> http://xen.epiuse.com/xen-faq.txt
Great!
If I can make a suggestion, I'd love to see documentation on how
disks/partitions are passed down to the virtual machines. Last I
checked there was basically nothing other than the code to try to ferret
out how to go about mounting partitions inside the vm's.
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-02-02 15:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 9:24 FAQ Jan van Rensburg
2004-02-02 15:10 ` Benjamin Reed [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-03 19:07 FAQ Williamson, Mark A
1999-06-06 4:55 FAQ Marshall Lake
1999-06-06 14:44 ` FAQ Jeff Tranter
1999-03-14 0:08 FAQ ralf
1999-03-15 7:23 ` FAQ Torbjorn Gannholm
1999-03-16 12:16 ` FAQ ralf
[not found] ` <Pine.LNX.3.95.990316181042.421B-100000@whale.dutch.mountain>
1999-03-17 10:42 ` FAQ ralf
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=401E6878.1010402@befunk.com \
--to=ranger@befunk.com \
--cc=jan.van.rensburg@epiuse.com \
--cc=xen-devel@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.