From: geoff@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: [9fans] aoe on sources
Date: Fri, 10 Aug 2007 15:14:37 -0400 [thread overview]
Message-ID: <84bac35989ca45a9fd0ab5de0c9f8f19@plan9.bell-labs.com> (raw)
I've incorporated Coraid's AoE code into our kernel.
Code and manual pages (aoe(3) and sdaoe(3)) are on sources now.
To use it, you need to include
dev
# ...
aoe
misc
# ...
sdaoe
in your kernel configuration(s), and follow the
instructions in the above-mentioned manual pages.
It's very lightly tested so far, but I'll exercise it against
a Coraid EtherDrive soon.
There is at least one important fix in our version of the
Coraid code, so if you're running old Coraid code, you should
update.
next reply other threads:[~2007-08-10 19:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 19:14 geoff [this message]
2007-08-10 19:34 ` erik quanstrom
2007-08-16 6:04 ` YAMANASHI Takeshi
2007-08-16 11:52 ` erik quanstrom
2007-08-17 1:10 YAMANASHI Takeshi
2007-08-17 1:18 ` erik quanstrom
2007-08-17 1:32 YAMANASHI Takeshi
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=84bac35989ca45a9fd0ab5de0c9f8f19@plan9.bell-labs.com \
--to=geoff@plan9.bell-labs.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).