Re: via mini-ipx

From: William Park (opengeometry_at_yahoo.ca)
Date: 03/05/05 

Date: Sat, 05 Mar 2005 19:53:39 GMT

john <john@nospam.com> wrote:
> I am considering using these boards to run linux and applications. I
> will use the eden esp processor. The MII board looks the best for my
> applications. Is anyone using thse? Are they reliable for outdoor
> applications? thx

I'm using Mercury board (www.mercury-pc.com) which is similar to VIA
M-series. For more detail,
    http://home.eol.ca/~parkw/thinflash.html 

-- 
William Park <opengeometry@yahoo.ca>, Toronto, Canada
Slackware Linux -- because it works.

Relevant Pages

  • Re: Linux Applications for OS X
    ... I hear that you can get most Linux applications installed for OS X. ... If you're willing to live with an ancient version of GNOME (the version in Fink) or build GNOME yourself against Apple's X11. ...
    (comp.sys.mac.advocacy)
  • Re: Big Mac Hoax 2: "OS X is Unix"
    ... moving from OS X to Linux I would also have to relearn... ... * We disagree as to which OS, OS X or Ubuntu, has a more consistent UI. ... Applications are, by their nature, system-wide files. ... * Standard OS X software packages have no dependency issues. ...
    (comp.sys.mac.advocacy)
  • Re: Linux Applications for OS X
    ... I hear that you can get most Linux applications installed for OS X. ... If you're willing to live with an ancient version of GNOME or build GNOME yourself against Apple's X11. ... You just named a large portion of the *nix apps with specific Mac ports, ...
    (comp.sys.mac.advocacy)
  • Re: The argument for fs assistance in handling archives
    ... because Apple customers are a captive lot... ... applications, ... > into a niche market). ... and Linux will be reduced to aping them when it should be leading ...
    (Linux-Kernel)
  • Re: .NET dead in 2 Years ?
    ... Is Longhorn the answer to all IT challenges? ... > the coexistence of Windows and Linux in the future? ... > to create rich-client applications that reside on a central server and, ... > Developers will only have to maintain one single version of the ...
    (microsoft.public.dotnet.general)