From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Mon, 19 Mar 2007 09:34:03 -0500 From: "Eric Van Hensbergen" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] coraid ethernet console In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <95f6317dab359359885a16c68c407ef7@coraid.com> Topicbox-Message-UUID: 28af8252-ead2-11e9-9d60-3106f5b1d025 On 3/19/07, Russ Cox wrote: > > 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? > The freenix one was pretty dead stupid/simple. It just set the protocol to 0x0666. To my knowledge, no one outside of us has every really used the freenix console, although I did get a few requests for the code over the years. > is the protocol documented somewhere other than the code? > Nope. > security? > Nope - I believe the paper makes the argument that you could use VLANs to enforce security, but our primary use for the ethernet-based console was purely pragmatic -- the hardware we had didn't have serial, video, or any other means of getting output. -eric