All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yan-Ching CHU" <cs0u210a@liverpool.ac.uk>
To: Jan van Rensburg <jan.van.rensburg@epiuse.com>,
	Xen List <xen-devel@lists.sourceforge.net>
Cc: cs0u210a@liverpool.ac.uk, Ian Pratt <Ian.Pratt@cl.cam.ac.uk>,
	Bin Ren <br260@cam.ac.uk>
Subject: Re: Documentation
Date: Thu, 5 Feb 2004 11:49:52 -0000	[thread overview]
Message-ID: <009f01c3ebde$2aa1f4f0$a054fd8a@barcelona> (raw)
In-Reply-To: FED3CB2D-57B5-11D8-BC94-00039350B9F2@epiuse.com

Hi Jan,

Thanks for your initiative effort in documentation.

> Bin if you can bring your HOWTO up to date for 1.2 I will merge that 
> with Yan-Ching's and check in into Sourceforge with the FAQ as Ian 
> suggested. Ian, does Sourceforge's CVS check it into the main Xen tree 
> or do you propose a separate tree for the documentation?

I will try to bring my Howto 1.2-compatiable once it's ISO is released,
then Ian may want to check that in into the 1.2 and unstable tree.

> As far the the documentation structure is concerned I think there 
> should be 3 main areas: Overview, Developer and End User. I'll leave 
> the Developer part to someone else. The overview should contain at 
> least one doc describing in "layman" terms how xen works, what xen, 
> xeno linux, VM, domains etc are. A kind of a starting point. I can 
> write a first draft of this (if someone hasn't already done it. The 
> SOSP paper is a bit too much). The End User docs should contain the FAQ 
> and the merged HOWTO for now.

I will also keep in touch with you about the developer section because I am
going to modify the scheduler with more features. Throughout the process I 
should write down my experience and comments systemtically.

Cheers,
Yan-Ching CHU




-------------------------------------------------------
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

  parent reply	other threads:[~2004-02-05 11:49 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1AoeOt-000173-00@wisbech.cl.cam.ac.uk>
     [not found] ` <FED3CB2D-57B5-11D8-BC94-00039350B9F2@epiuse.com>
2004-02-05 10:15   ` Documentation Bin Ren
2004-02-05 11:49   ` Yan-Ching CHU [this message]
2020-06-06 17:09 Documentation G.W. Haywood
2020-06-07 21:23 ` Documentation Pablo Neira Ayuso
2020-06-10 12:55   ` Documentation G.W. Haywood
  -- strict thread matches above, loose matches on Subject: below --
2017-03-27  5:53 documentation Julia Lawall
2011-04-13 23:33 Documentation Eugene Shatsky
2011-04-14  4:44 ` Documentation Jonáš Vidra
2011-04-14 13:54 ` Documentation Edward Shishkin
2011-01-31 21:39 documentation Roberto Spadim
2011-01-31 21:43 ` documentation Mathias Burén
2011-01-31 21:58 ` documentation NeilBrown
2011-01-31 22:14   ` documentation Roberto Spadim
2011-02-01  9:37     ` documentation hansbkk
2011-02-01 13:49       ` documentation Roberto Spadim
2010-12-01 18:00 Documentation David Lambert
2010-12-01 18:06 ` Documentation Stefan Schmidt
2010-12-01 18:39   ` Documentation David Lambert
2010-12-01 18:54     ` Documentation Stefan Schmidt
2010-12-01 22:46       ` Documentation Robert Foerster
2010-12-02 20:37         ` Documentation David Lambert
2010-12-02 20:52           ` Documentation Robert Foerster
2010-12-03  7:35             ` Documentation Christophe Aeschlimann
2010-03-14  0:17 Documentation Giuseppe Macrì
2006-02-10  8:20 Documentation Nico -telmich- Schottelius
     [not found] <E1EiHi4-0000IY-16@host-192-168-0-1-bcn-london>
2005-12-02 21:22 ` Documentation John S Little
2005-12-02 22:30   ` Documentation Robb Romans
2005-12-03 11:26     ` Documentation Robin van Leeuwen
2005-12-04 14:05       ` Documentation John S Little
2005-12-05 16:46         ` Documentation Nivedita Singhvi
2005-12-05 17:11           ` Documentation Robb Romans
2005-12-05 18:09           ` Documentation John S Little
2005-12-05 23:57         ` Documentation Rich Persaud
2005-12-05 15:58       ` Documentation Robb Romans
2005-10-24 19:05 Documentation Vagin Andrey S.
2004-06-24 17:10 Documentation Tomas Ebenlendr
2004-06-24 22:03 ` Documentation Yoshinori K. Okuji
2004-06-25 13:17   ` Documentation Jeroen Dekkers
2004-06-26 15:05     ` Documentation Yoshinori K. Okuji
2004-05-27 13:12 Documentation Alexander E. Patrakov
2004-05-28 23:25 ` Documentation Greg KH
2004-06-02  6:11 ` Documentation Niko Sauer
2004-05-15 14:28 Documentation Jody
2004-05-17 13:35 ` Documentation Andrey Romanenko
2004-05-17 13:40 ` Documentation Miguel Bolanos
2003-06-06 13:20 Documentation Matthew Wilcox
2002-08-29  9:39 documentation vandana  mehtani
2002-08-29 15:46 ` documentation Dave Wilhardt
2002-04-24 14:26 documentation Guilhem Tardy
2002-04-24 16:58 ` documentation Takashi Iwai
2002-04-24 19:32   ` documentation Guilhem Tardy
2002-04-26 17:54     ` documentation Takashi Iwai
2002-05-03 16:11       ` documentation Guilhem Tardy
2002-05-03 16:22         ` documentation Paul Davis
2002-05-03 16:28         ` documentation Takashi Iwai
2002-03-22 15:32 Documentation Gopakumar.C.E
2002-03-30  7:42 ` Documentation Ralf Baechle
2002-02-02  9:18 Documentation Guillaume Chamberland-Larose
2002-02-02 10:39 ` Documentation Yven J. Leist
2002-02-05 18:18   ` Documentation Randy.Dunlap
2001-11-15 18:03 Documentation war

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='009f01c3ebde$2aa1f4f0$a054fd8a@barcelona' \
    --to=cs0u210a@liverpool.ac.uk \
    --cc=Ian.Pratt@cl.cam.ac.uk \
    --cc=br260@cam.ac.uk \
    --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.