From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Anatomy of a vblade image
Date: Tue, 15 Jul 2008 07:49:49 -0400 [thread overview]
Message-ID: <9398ef587c2de8891e55c7d8b1307824@quanstro.net> (raw)
In-Reply-To: <487C6892.1080208@proweb.co.uk>
> In the Linux world kvlade looks the way to go for performance but it
> didn't work on AMD64 when I tried it. I guess the Coraid boxes make Plan
> 9 go fast enough so I just need to stop worrying about it.
plan 9 is a good platform; it is very speedy and doesn't do anything
to you. we didn't need to make it go fast.
- erik
next prev parent reply other threads:[~2008-07-15 11:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b3d39ccfed51c9103afdc527ef7bbf31@quanstro.net>
2008-07-15 9:06 ` matt
2008-07-15 11:49 ` erik quanstrom [this message]
2008-07-15 14:18 ` John Waters
2008-07-15 16:23 erik quanstrom
[not found] <bcf6455ae643bb5cb35cb1b7877e2401@quanstro.net>
2008-07-13 20:13 ` matt
2008-07-13 20:54 ` erik quanstrom
2008-07-13 22:20 ` matt
-- strict thread matches above, loose matches on Subject: below --
2008-07-11 12:31 erik quanstrom
2008-07-11 12:23 matt
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=9398ef587c2de8891e55c7d8b1307824@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).