From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] interesting qemu problem
Date: Tue, 16 Mar 2010 19:07:27 -0400 [thread overview]
Message-ID: <26e5c9caa2b6ed707820426e080f733c@brasstown.quanstro.net> (raw)
In-Reply-To: <13426df11003161604t20c78a8btb4dc38bde0245c4e@mail.gmail.com>
> This image formerly ran in 256M, now requires 512M, because venti
> footprint is 140+211+211 ... wait, how does it ever fit in 512 anyway.
swap? this would answer two questions.
- erik
next prev parent reply other threads:[~2010-03-16 23:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 17:29 ron minnich
2010-03-16 17:48 ` erik quanstrom
2010-03-16 18:19 ` ron minnich
2010-03-16 23:04 ` ron minnich
2010-03-16 23:07 ` erik quanstrom [this message]
2010-03-16 23:16 ` ron minnich
2010-03-18 13:54 ` blstuart
2010-03-16 23:47 ` Eric Van Hensbergen
2010-03-16 23:52 ` ron minnich
2010-03-16 23:55 ` erik quanstrom
2010-03-17 0:04 ` Eric Van Hensbergen
2010-03-17 0:22 ` ron minnich
2010-03-28 14:34 ` Georg Lehner
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=26e5c9caa2b6ed707820426e080f733c@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.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 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).