From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] tiny horrible xen status
Date: Sat, 10 Mar 2007 11:28:44 +0000 [thread overview]
Message-ID: <0474229a31c3ce1eef2dc15df80721a5@hamnavoe.com> (raw)
In-Reply-To: <13426df10703091246r336ac630r93a138df77cb366d@mail.gmail.com>
> I need to have a small image that can serve
> as a cpu/auth server (since you have to drawterm in). Any ideas?
It doesn't take many files just to run as an authomous cpu/auth
server - my kfs for the ipEngine is less than 4MB (before compression).
The question is what you want to do once you've drawtermed in.
If you want something approaching a complete distribution, you can look
for large and little-used bits to prune away; or try a compressed
partition (e.g. paqfs).
next prev parent reply other threads:[~2007-03-10 11:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 20:46 ron minnich
2007-03-10 11:28 ` Richard Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-02 21:35 ron minnich
2007-02-02 22:22 ` John Floren
2007-02-02 22:50 ` ron minnich
2007-02-04 9:11 ` Richard Miller
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=0474229a31c3ce1eef2dc15df80721a5@hamnavoe.com \
--to=9fans@hamnavoe.com \
--cc=9fans@cse.psu.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).