From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sting Zax Subject: Xen intro Date: Sat, 3 Sep 2005 22:43:55 +0200 Message-ID: <3a0f1c62050903134343288200@mail.gmail.com> Reply-To: zstingx@gmail.com Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0262331851==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Mime-version: 1.0 Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============0262331851== Content-Type: multipart/alternative; boundary="----=_Part_3473_28351106.1125780235029" ------=_Part_3473_28351106.1125780235029 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello, I am quite newbie to Xen and I found today this Xen intro article of a=20 little help: http://www.linuxjournal.com/article/8540 (but no more than little; it deals only with the basics) I wish that Xen-3.0 will have a basic code design & implememation document= =20 (with pointers to code). Regards, Sting ------=_Part_3473_28351106.1125780235029 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello,
I am quite newbie to Xen and I found today this Xen intro article of a litt= le help:
http://www.linuxjourna= l.com/article/8540
(but no more than little; it deals only with the basics)

I wish that Xen-3.0 will have a basic code design & implememation docum= ent (with pointers to code).

Regards,
Sting

------=_Part_3473_28351106.1125780235029-- --===============0262331851== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0262331851==--