Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror

Comment This is officially hyperbole (Score 1) 182

Okay, this is officially now hyperbole. It's one thing to cover major Boeing issues. But this is not an uncommon issue. I can see it in the sole Boeing reporting, without any AirBus reporting of the same.

I mean, I've never been on a Boeing that had gear totation or other issues, but I've been on plenty of AirBus aircraft that have, and had to fly by the tower to verify it wasn't just a sensor issue.

AirBus is just lucky they didn't have social media when they first implemented their automation decades ago ... all the same issues, input validation, man-machine interface issues (decent rate v. decent angle was one that caused hundreds of indents, and dozens of hull losses).

Let's stick to actual, major issues, like automation and plugs. Otherwise, this is becoming unjustified hyperbole. And yes, I've long been critical of Boeing too, especially in the 21st century. So don't throw the 'apologist' tag on me.

I mean, AirBus had more hull lost incidents and faster than Boeing, when the new, automated A300 series first came out. And AirBus didn't handle it well. Same with the man-machine issues, which were 'quick fixes' too, but they didn't do them until several hull loss events.

Comment Re:Pure Insanity (Score 1) 924

Changes like this make me wonder if the systemd developers even use Linux beyond their local development workstations ... cut (various "not how UNIX works)" cut ...

Ahhh yes, the common response, that systemd is for desktops. Sigh, for those in Red Hat who saw customers deploy Cluster Suite just to monitor services *and*, more importantly, resources (something Upstart doesn't do) for standalone, single system services, systemd does far, far more for servers than desktops. This is yet another. Customers not only desired systemd, but even the Debian vote exposed how many *major* (thousands of servers) Debian userbases wanted it too.

As someone who has extensive experience with LTSP and RHEV VDI, this was a long, requested change. Because multiuser environments absolutely need this. But ignorance is most common, especially those who haven't worked in 10,000 user Linux VDI environments, which is why get these types of responses. Same goes for the prior on PulseAudio, when the issue usually wasn't PulseAudio, but Ubuntu -- especially off-shoot, non GNOME/Unity Ubuntu -- integration issues.

As far as "how UNIX works," people should really change that to "how BSD works." Virtually all other UNIX implementations *do* have something with many systemd features and approaches.

Slashdot Top Deals

"Ada is PL/I trying to be Smalltalk. -- Codoso diBlini

Working...