[Mep-dev] Tuesday Challenge for 14 April 2009

[Timothy J. Salo]

Michelle wrote:
> “The problem with Google's approach is that it makes Android
> an island. The highly insular nature of the platform prevents
> Android users and developers from taking advantage of the rich
> ecosystem of existing third-party Linux applications. Android
> doesn't officially support native C programs at all, so it won't
> be possible to port your favorite GTK+ or Qt applications to
> Android. It's also not possible to run existing MIDP
> applications on Android because it uses an incompatible virtual
> machine.

I can't comment directly on Android.

First, I'm not sure what exactly MEP is supposed to be.  The
answer to that question will help clarify which operating
system software is most appropriate.  My view is that MEP
is (at least sort of) an embedded system.  You plug some
RF stuff into it and connect it to an Ethernet cable and
it provides a networking capability.  In particular,
you never plug a monitor into it.  (You should just use
a Web browser for any low-bandwidth graphical output.
I can't see why MEP would ever need high-bandwidth graphical
output.  But, I'm probably confused).

So, this view  might lead to several conclusions:

o MEP's operating system must include a good IP stack,
   support for Ethernet, probably at least a stripped-down
   Web server, probably sshd for remote access.  And, a
   bunch of other stuff, but you can probably see where I
   am headed.

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.)

The benefit of embedded Linux distributions is that they
are small, they run on small machines.  A problem with
embedded Linux distributions is that they keep breaking,
because mainstream Linux developers don't think about
embedded distributions, and so cause what Michelle refers
to as "package avalanche" without thinking about it, without
caring about it, and often for no good reason.

My first test for Android would be whether it supports
networked devices.  Does it support Ethernet interfaces
(of which there are a ton, it turns out)?  Does it have
a _good_ IP stack?  A _small_ Web server?  I don't
know the answers...

I do think that it would be useful for the amateur radio
community to gain expertise in embedded Linux systems.
I also have a vision where the MEP, future satellites,
repeaters, and who knows what else all run the same
operating system.  They also share a bunch of system
software, such as _good_ software that permits unattended
remote administration.

A few quick thoughts from,

	-tjs