this post was submitted on 03 Jul 2023
21 points (100.0% liked)

Linux

5241 readers
43 users here now

A community for everything relating to the linux operating system

Also check out [email protected]

Original icon base courtesy of [email protected] and The GIMP

founded 1 year ago
MODERATORS
 

Thoughts?

all 7 comments
sorted by: hot top controversial new old
[–] iaamp 10 points 1 year ago

It should be added that they likely talk about the controller of the airplanes. Afaik there already is Linux on airplanes, but to handle e.g. the entertainment system. Which seems like a better fit.

Having a non-Linux main controller OS with specific design and a lot smaller feature set than Linux flying the plane seems like a good idea. But maybe this could also be open sourced and standardized?

[–] varsock 8 points 1 year ago* (last edited 1 year ago)

I will admit reading the reasons against Linux made me a bit butthurt given how much it has accomplished and the ubiquity of it running on servers that host our services.

However, a (real time operating system) RTOS is distinct from a time-sharing operating system, such as Unix, which manages the sharing of system resources with a scheduler, data buffers, or fixed task prioritization in a multitasking or multiprogramming environment. And a time-sharing kernel is likely not suitable for the demands of real-time feedback that airplanes, especially fighter planes, are under. Admittingly I don't work on the kernels so I might be out of my league talking about it if there are ways to optimize them for RTOS applications. And I also don't work on airplane but hobby learning about them.

In an airplane, the pilots are voting members. If they they are nose diving and tell the airplane to pull up, the airplane will calculate how much of the full range of motion to allow the flaps to "bite" the air so that the plane doesn't desintigrate. This takes into account speed, altitude, air density, load on wings, load on frame, G forces pilots would experience, etc etc.

[–] ndotb 7 points 1 year ago

I'm not really going to address the speaker directly since after reading NSF forums for a few years, I'm convinced aerospace engineers can devolve any innocent or academic discussion into 4chan levels at rates exceeding the speed of light. Of note: the speaker doesn't speak to anything specific that is being worked on to address issues, and only addresses "linux" as a whole, which is about as useful as addressing SVR4 as a whole.

I will address the blog writer as not being particularly diligent in filling that gap, though. Here's a few links of what's going on in that realm since there's people here of all walks and ages:

Wind River RTLinux

Zephyr Project

OSADL SIL2LinuxMP

Xenomai

[–] shiroininja 5 points 1 year ago (1 children)

Given the problems Boeing have had with the software in their commercial fleet and Starliner….. are they sure?

[–] Shareni 4 points 1 year ago

Nah dude, having to reboot your planes to not lose all electrical power is a safety feature. Linux ain't got shit on that

[–] MooseBoys 4 points 1 year ago (1 children)

Linux should not be in the loop for critical systems. The software that takes the input from the throttle control and determines the proper fuel pump rate should be written directly for the microcontroller hardware. For the system that receives ground radio data and renders radar info to the dash panel, that can be running Linux.