[Mep-dev] Tuesday Challenge for 14 April 2009

[James French]

Timothy J. Salo wrote:
> o MEP's operating system doesn't need to support, and
>   probably shouldn't include support for, _any_ graphical
>   user interface.  (Any graphical interface should be
>   run on the user's desktop.)

Furthermore, (again depending on what the MEP actually is)
it's operating system (and hardware) should be able to run
_without_ any display.  And, the MEP should probably be able
to be administered remotely, including forcing it to reboot.
Note that these requirements are pretty hard.  I think all
PC-compatibly machines fail.  But, this is the environment
in which we operate - difficult-to-access repeaters and
really difficult-to-access satellites.

-tjs
=====

Tim,

Sounds like you are suggesting a Linux Terminal Server Project 
< http://www.ltsp.org > usage where the MEP interface is Terminal and Server
in one package with the means to provide Remote Terminal access from a remote
location.

Heres what I am thinking:

1) The MEP device (ATOM or Beagle or whatever) is located in a remote area
   with a 2.4GHz wireless or network card with a boot eeprom installed that
   has LTSP installed
2) The users home computer acts as a Server to the MEP system with access
   for Remote Desktop to configure powering/rebooting/configuring.
3) The users home computer provides ALL the software and just uses the MEP
   device to provide the interface between user and radio.

The above would be for a home station or even to provide for a remote location
like a repeater site.

You could configure the MEP station either as a Thin net client that doesn't need
peripherals like keyboard, mouse, or monitor or as a server with everything on the one system.

The idea came from rereading Timothy's messages and being at Dayton this past weekend
and picking up two thin net clients in the flea market for two dollars (Yes, Michelle,
they do power up :) ) and doing a little research to see if I could configure them for
a LTSP usage.

James W8ISS