All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
To: Jun Koi <junkoi2004@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Jean Guyader <jean.guyader@gmail.com>
Subject: Re: xen client installation question
Date: Thu, 16 Apr 2009 12:26:15 +0100	[thread overview]
Message-ID: <49E715D7.1060103@eu.citrix.com> (raw)
In-Reply-To: <fdaac4d50904160356h71ff50d7sd34c28a6c7165fbb@mail.gmail.com>

Jun Koi wrote:
> On Thu, Apr 16, 2009 at 5:51 PM, Jean Guyader <jean.guyader@gmail.com> wrote:
>   
>
> And could you explain why we have to use buildroot, and what is the
> benefit of using busybox+uclibc?
>   
as Jean was saying, this is mostly related to the size of the output. 
and also to be in a control environment in dom0, so we don't depend of 
different udev scripts or something like that.

also, using a proper build system, make the build system consistent 
across all users, and prevent to have random problems because
<random distributions> use <random software> of <random version> but we 
support only <other random version>.

Note that you should be able to compile most of the trees (kernel, 
toolstack, ...) by yourself on any distribution, if you install 
everything that's necessary.
but it won't be as easy and guaranteed to work as inside of our build.

-- 
Vincent

  parent reply	other threads:[~2009-04-16 11:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-16  8:38 xen client installation question Jun Koi
2009-04-16  8:51 ` Jean Guyader
2009-04-16 10:54   ` Jun Koi
2009-04-16 11:06     ` Jean Guyader
2009-04-16 11:16     ` Vincent Hanquez
2009-04-16 10:56   ` Jun Koi
2009-04-16 11:07     ` Jean Guyader
2009-04-16 11:26     ` Vincent Hanquez [this message]
2009-04-27  7:14       ` Jun Koi

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=49E715D7.1060103@eu.citrix.com \
    --to=vincent.hanquez@eu.citrix.com \
    --cc=jean.guyader@gmail.com \
    --cc=junkoi2004@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /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.