Posted by: bha
A few technical details - 12/04/2001 22:02
Just goof'n around, here's what I can see...
It looks like the control/command channel is HTTP. The server is running an HTTP server on a high port. It will server up display layouts and other files.
I see data that looks like NFS! Could that be how music files get from the server to the receiver?
Start the server with /Log:filename and you will get a log file. Not much interesting, but it's a start.
There's lot's of stuff about the Mercury server and Mercury protocol. Anybody know what this is?
This is running Linux. The distribution is named mercury.arf on the server. Just un-tar it and you have the Linux image!
Do you think there is some "hold down this odd combination of buttons and turn it on" sequence that get's you a shell?
It looks like the control/command channel is HTTP. The server is running an HTTP server on a high port. It will server up display layouts and other files.
I see data that looks like NFS! Could that be how music files get from the server to the receiver?
Start the server with /Log:filename and you will get a log file. Not much interesting, but it's a start.
There's lot's of stuff about the Mercury server and Mercury protocol. Anybody know what this is?
This is running Linux. The distribution is named mercury.arf on the server. Just un-tar it and you have the Linux image!
Do you think there is some "hold down this odd combination of buttons and turn it on" sequence that get's you a shell?