wireless internet for flying info

[BackPacker]

I was under the impression that most real time software on aircraft was *nix based due to it's reliability ?

I would not automatically assume that. Under Unix, it is still the case that a high-priority process can bump a low priority process down the bottom of the priority stack, even if that low-priority process should be executed in real-time.

For proper real-time operations, where response times *have to be* below a certain amount of milliseconds, you typically run a Real-Time operating system, which is normally very minimalistic. Or you don't run an OS at all. Looking at for instance RTLinux, the idea is that you have a mini-kernel running all real-time processes, and the Linux kernel runs as one of the non-realtime processes under that real-time kernel. Or something close to that effect.

RTLinux - Wikipedia, the free encyclopedia

And of course it's not just the OS. The number of cycles spent to perform a certain time-critical task have to be 100% predictable so all system calls, I/O calls and so forth also need to have an upper limit. Not something that's true in UNIX or Windows. File I/O for instance is normally blocking, but what if the file is on a network server somewhere which cannot be reached?

Less time-critical things, like the inflight entertainment system, can run directly under Linux or any other "normal" OS, *nix or otherwise and in fact they do.

- BP

(Linux user since kernel 0.95, RHCA, LPIC-2, AIX CSE and then some.)

[IO540]

I think PP what you are actually describing is peoples' ignorance when it comes to configuring the most basic windoze security.

M$ ship the product wide open. Just like most wifi routers are shipped (and thus installed, by "ignorant" users) wide open.

Setting up wpa/psk on the router, and a few other bits like blocking the admin port, and setting a login/pwd on the windoze machine and disabling "simple file sharing" makes a pretty secure setup.

Whereas "unix" tends to be used by serious geeks and nerds who know a lot more about this stuff to start with.

As regards internet banking, the absolute #1 requirement is physical security of the machine. If you let kids (or careless adults going to odd websites) play on it, it will be loaded with trojans within days if not hours.

[Rod1]

First of all thanks for all the advice. I had decided on some form of windows based netbook as I have a variety of windows based programs for flight planning and GPS updating which I need to use as well as browsing the net. If I could be sure the apps would work on a Linux system with an “emulator” then I would be happy with this. If the stuff does not work or I have to spend days struggling then it would be a big mistake. How big is the risk?

Rod1

[Shunter]

I do not understand why one would buy a unix based laptop, only to load an emulator on it to run windoze XP so they can run the software they actually need.

Specialised applications aside (and yes LH2 you are an exceptionally competent geek ) unix on these tiny laptops is good for basically one thing which is running a browser.

As mentioned, WINE is not an emulator. It's an open source implementation of the Win32 API. Pedantic to some perhaps, but it's a big difference; some software actually benchmarks better on WINE than it does on Windows, games included! Stuff like NotamPlot is written in Java anyway, so doesn't suffer a lack of portability.

I have to say I find such comments disappointing; there's a great deal you can do with a Linux Eee, frequently exceeding the capabilities of Windows and none of it is particularly complicated. Windows is a 1-size-fits-all solution which simply doesn't fit all sizes. The monolithic architecture can't be chopped down in the same way that Linux can be modified to suit any need or situation; in this case a tiny, lightweight, resource-efficient mobile solution. I can run a Linux system with fluxbox, full office suite, media, comms, all flight info and planning without even using 100Mb of disc space. I can use logical volume management and software RAID the 2 SSDs to get make the thing go like the clappers.

Linux isn't difficult, just like speaking French isn't difficult. It's just different, and most certainly no longer the exclusive terrority of men with beards who wear dungarees as the Microsoft apologists would have you believe.

[flybymike]

If there is an interpreter who speaks English on this forum, I would be pleased to hear from him.

[BackPacker]

Mike, it's simple.

Windows is like a Cessna 182. A fairly robust aircraft with not too many vices. It's a bit overkill to train on, suitable for a lot of applications, and sometimes wanting.

UNIX in general comes in many flavours. From relatively small (think Gippsland Airvan) to very large (A380), each fit for a specific purpose but too expensive to do much else.

Linux is like the experimental/homebuild/kitplane scene. It's intellectual capital consists of a large number of publicly available plans and parts, and you pick a distribution (Red Hat, Ubuntu, SuSE, Debian) that suits your needs best by offering the best combination of plans and parts you need. Like you would choose between a pre-assembled Jabiru, Europa, RV, Glasair or something else. Or you assemble it yourself from the component parts. Compared to the Cessna 182 they do require some more knowledge and skill to operate but the end result is more suited to your problem.

WINE is like putting the controls and operating characteristics (the "API") of the Cessna 182 in the cockpit of your hotrod kitbuild airplane. It's useful for those pilots (read programs) that only know how to fly Cessna 182s (read run on Windows).

VMWare (and others like MS Virtual Server and Xen) is like taking an Airbus A380 and putting a Cessna 182 inside of it, giving it its own airspace, air traffic control, runways and everything. This means that a Cessna 182 pilot can buzz around from the front to the back and generally have a good time, without impacting any other airspace users, while you take the A380 somewhere else.

[PompeyPaul]

Advice

First of all thanks for all the advice. I had decided on some form of windows based netbook as I have a variety of windows based programs for flight planning and GPS updating which I need to use as well as browsing the net. If I could be sure the apps would work on a Linux system with an “emulator” then I would be happy with this. If the stuff does not work or I have to spend days struggling then it would be a big mistake. How big is the risk?

Rod1

Easiest life, if you want to run Win stuff, is to buy a laptop than runs windows natively. Buying a linux machine, and installing WinXP might fail if you can't get the drivers you need for your hardware. If you buy a Win laptop, pretty much everything will run out of the box. It may run slowly, it may be insecure, but it will all run and you'll find (fairly expensive) support for it at your local pc world.

If you don't mind fiddling with your machine and want something more reliable then buy a linux machine and run your apps through wine, or through a VM.

[PompeyPaul]

Great post

Great post Backpacker

[flybymike]

Backpacker, analogies like that I understand. Think I will stick to a bog standard C182

[Zulu Alpha]

Quite a few phones ( iphone, Nokia N95 etc.) have WiFi built in. This gives you the best of both worlds
Wi Fi when its available and Mobile data when you really must have the info.

ZA