From: Jared Rhine <jared@wordzoo.com>
To: xen-devel@lists.sourceforge.net
Subject: saving domains
Date: Wed, 09 Feb 2005 18:20:48 -0800 [thread overview]
Message-ID: <87y8dxb1fj.wl@badger.wordzoo.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D123825@liverpoolst.ad.cl.cam.ac.uk>
[Ian == m+Ian.Pratt@cl.cam.ac.uk on Thu, 10 Feb 2005 01:51:50 -0000]
Ian> I don't really buy the resource usage argument as a python
Ian> interpreter is just over 2.5MB RSS and the daemon shouldn't be
Ian> CPU intensive.
I believe that those concerned about the Python dependency are more
concerned about the disk space and "fatness" of having python
installed at all. I know I could cook a version of XenCD which fit
into 256Mb or less of RAM if the rootfs didn't have to have Python
installed. Others are thinking way way smaller than that.
Mark> It seems a shame to rewrite in C but OTOH with the XCS
Mark> framework...
Yes, exactly. Eventually, someone is going to get annoyed enough at
the Python dependency to port x2d2 to xcs or write a lightweight
replacement. I'd like to see us standardize around xcs, and have a
healthy community of competing control tools.
Last time this came up, however, we got into intractable arguments
about TCP vs UDP for xcs and whether layering daemons was advised.
Those contributing working code will rightly determine where this all
ends up.
-- jared@wordzoo.com
http://www.geekcode.com/geek.html
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCM/CS/B
d s:++>+ a-
C++(++++)$ ULBSH++++ P+++ L+++ E++(+++) W++++ N- !o !K w !O M V
PS+++(-) PE++(--) Y+ PGP>++
t@ 5 X+ R>+ tv++>-- b>++ DI+ D- G
e++ h- r++>+++ y+++
------END GEEK CODE BLOCK------
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-02-10 2:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 1:51 saving domains Ian Pratt
2005-02-10 2:00 ` Mark Williamson
2005-02-10 2:06 ` Adam Heath
2005-02-10 2:20 ` Jared Rhine [this message]
2005-02-10 16:21 ` Ronald G. Minnich
-- strict thread matches above, loose matches on Subject: below --
2005-02-10 9:07 Zhiyi Huang
2005-02-10 9:20 ` Arthur Bergman
[not found] <BAY102-F15E8F04B4950494F7E1C67B3750@phx.gbl>
2005-02-10 6:57 ` Arthur Bergman
2005-02-10 2:13 Ian Pratt
2005-02-10 2:08 Ian Pratt
2005-02-09 23:54 Ian Pratt
2005-02-10 1:10 ` Jared Rhine
2005-02-10 1:35 ` Nivedita Singhvi
2005-02-10 2:11 ` Jared Rhine
2005-02-10 1:52 ` Adam Heath
2005-02-10 16:14 ` Ronald G. Minnich
2005-02-09 23:24 Tim Freeman
2005-02-09 23:30 ` Arthur Bergman
2005-02-10 2:27 ` Tim Freeman
2005-02-10 6:58 ` Arthur Bergman
2005-02-10 10:56 ` tdc
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=87y8dxb1fj.wl@badger.wordzoo.com \
--to=jared@wordzoo.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.