From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] coraid ethernet console
Date: Mon, 19 Mar 2007 09:39:09 -0400 [thread overview]
Message-ID: <ee9e417a0703190639o5dacb3cah2f671dd8c310849e@mail.gmail.com> (raw)
In-Reply-To: <95f6317dab359359885a16c68c407ef7@coraid.com>
> 1. consolefs doesn't yet speak cec. (good soc project.)
as long as you have a cec client that presents a file,
consolefs should be able to read it. consolefs doesn't
speak serial either.
what is the relation between cec and this ethernet console?
http://www.usenix.org/events/usenix03/tech/freenix03/kistler.html
it would be nice if they could use the same protocols, though
i don't know how complicated the freenix one is. ericvh?
is the protocol documented somewhere other than the code?
security?
thanks.
russ
next prev parent reply other threads:[~2007-03-19 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-18 22:56 erik quanstrom
2007-03-19 13:39 ` Russ Cox [this message]
2007-03-19 14:29 ` erik quanstrom
2007-03-19 14:34 ` Eric Van Hensbergen
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=ee9e417a0703190639o5dacb3cah2f671dd8c310849e@mail.gmail.com \
--to=rsc@swtch.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).