Language Selection

English French German Italian Portuguese Spanish

Linux on a Plane: What a Pain!

Filed under
Linux

My wife and I recently came back from a business trip from Paris, and even though we thoroughly enjoyed ourselves, it was a long week of living out of a suitcase, and when we boarded the plane after twelve security checks in the airport, we were both ready to try to relax and not think about the jetlag that would result from our long flight back home. Thankfully, when we were walking to our confined torture seats, I noticed that every seat on the plane had a touch screen display that could be used to watch movies and television shows, play games, and listen to music, which was not the case on our flight out to Paris. Obviously, this was a welcome sight, but when I finally sat down in my seat, I knew that I was going to be in for an interesting flight.

You see, while everyone else on the plane appeared to have a fully functioning display, I was left with a black and white boot screen of doom that documented some errors that prevented the system from properly starting up. The operating system? Linux. The distribution? Red Hat. Yes, out of all the people on the plane, I was the one left with a Linux failure, which just couldn’t have been more appropriate. I realized the irony of the situation, and this amusement pushed aside the frustration for a short amount of time.

Part of the error message literally said something like:

"Can’t identify FLASH, sorry, man 89..."

Full Story.

Disagree with the conclusion.

I fail to see how this guy reaches the conclusion that Windows would be a better OS than Linux for this scenario.

Bad applications can be written for any OS.

I could say the same about my cable box at home which is running VxWorks. This is an OS which is specifically designed for embedded systems and yet my cable box is slow and crashy. At work we use VxWorks for airbourne software and as you can imagine, a crash in this scenario is completely unacceptable.

He does not state which airline it is but Virgin have implemented their in-flight entertainment system on Linux for their Airbus fleet. I'm sure that if Linux wasn't up to the job, Virgin would not be installing it

Virgin Red

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Security Leftovers

10 hot Android smartphones that got price cuts recently

With numerous smartphone getting launched each month, brands always adjust prices to give slightly competitive edge to older smartphone models and also to clear inventories. Here are 10 smartphones that got price cuts recently. Read more

Debian and Ubuntu News

  • Debian Project News - July 29th, 2016
    Welcome to this year's third issue of DPN, the newsletter for the Debian community.
  • SteamOS Brewmaster 2.87 Released With NVIDIA Pascal Support
  • Snap interfaces for sandboxed applications
    Last week, we took a look at the initial release of the "portal" framework developed for Flatpak, the application-packaging format currently being developed in GNOME. For comparison, we will also explore the corresponding resource-control framework available in the Snap format developed in Ubuntu. The two packaging projects have broadly similar end goals, as many have observed, but they tend to vary quite a bit in the implementation details. Naturally, those differences are of particular importance to the intended audience: application developers. There is some common ground between the projects. Both use some combination of techniques (namespaces, control groups, seccomp filters, etc.) to restrict what a packaged application can do. Moreover, both implement a "deny by default" sandbox, then provide a supplemental means for applications to access certain useful system resources on a restricted or mediated basis. As we will see, there is also some overlap in what interfaces are offered, although the implementations differ. Snap has been available since 2014, so its sandboxing and resource-control implementations have already seen real-world usage. That said, the design of Snap originated in the Ubuntu Touch project aimed at smartphones, so some of its assumptions are undergoing revision as Snap comes to desktop systems. In the Snap framework, the interfaces that are defined to provide access to system resources are called, simply, "interfaces." As we will see, they cover similar territory to the recently unveiled "portals" for Flatpak, but there are some key distinctions. Two classes of Snap interfaces are defined: one for the standard resources expected to be of use to end-user applications, and one designed for use by system utilities. Snap packages using the standard interfaces can be installed with the snap command-line tool (which is the equivalent of apt for .deb packages). Packages using the advanced interfaces require a separate management tool.
  • Ubuntu 15.10 (Wily Werewolf) Reaches End Of Life Today (July 28)
  • Ubuntu MATE 16.10 Yakkety Yak Gets A Unity HUD-Like Searchable Menu
    MATE HUD, a Unity HUD-like tool that allows searching through an application's menu, was recently uploaded to the official Yakkety Yak repositories, and is available (but not enabled) by default in Ubuntu MATE 16.10.

Tablet review: BQ Aquaris M10 Ubuntu Edition

As employees have become more and more flexible in recent years thanks to the power and performance of mobile devices, the way we work has changed dramatically. We frequently chop and change between smartphones, tablets and laptops for different tasks, which has led to the growth of the hybrid market – devices such as Microsoft’s Surface Pro 3 and Apple’s iPad Pro – that provide the power and functionality of a laptop with the mobility and convenience of a tablet. Read more