Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
Slashdot Deals: Cyber Monday Sale Extended! Courses ranging from coding to project management - all eLearning deals 20% off with coupon code "CYBERMONDAY20". ×

Submission + - TGV accident caused by overspeed

Cochonou writes: The analysis of the black boxes of the TGV which derailed on Saturday revealed that the accident resulted from an excessive speed caused by late braking. The test train entered a radius curve at a speed of 265 km/h instead of the maximum speed of 176 km/h. The French national railways company ruled out any other cause, such as mechanical failure or track mishap.
During test runs, a number of security features are disabled, in particular parts of the TVM system which would have prevented any overspeed during normal service. This leaves the train speed under the sole responsibility of the driver.
The accident which killed 11 people occurred on the last run of the scheduled trials on the new high-speed line between Paris and Strasbourg. As more details on the accident surface, it becomes evident that this last run was performed in a festive spirit, with relatives (including children) of the employees on board, and 7 people present in the train cab instead of 3. This casts a shadow on the security procedures of the French national railway company: it appears that the high-speed train technology is considered so safe that the risks inherent to trials runs were somehow neglected. The two drivers and the traction inspector have been suspended by SNCF pending possible criminal charges. Other changes in the management structure will probably follow.

Comment Conspiracy... (Score 1) 153

Whereas it's conceivable that a single software engineer, directed by a single manager, could have secretly written and uploaded the code that ran the defeat device

Of course is conceivable, but does anybody actually believe that ? You would need to be quite ingenuous to believe that... this is not an obscure open source project with almost no reviews, you cannot "slip" a patch without anyone noticing... moreover, you cannot keep that code for more than 6 years in the revision control system without anyone noticing.
This is not a conspiracy, this is just a company caught red handed.

Anyway, if you need any proof that this behaviour was indeed intended by the company, just have a look at this article: Bosch reportedly warned Volkswagen about illegal emissions software in 2007.

Comment Re:Can the enemy actually shoot down the F35? (Score 1) 732

I'm afraid what happened in Serbia is only one example, and it is something that really should never have happened. The radar used there was not particularly sophisticated. If anyone knows they can track a F-35 or F-22 right now then they are going to keep their cards close to their chest.

You can also shoot down the F-117 over Belgrade in the very comprehensive SAM Simulator. Try it, you will see this is not easy...

Comment Re:It's 2015! Almost 2016! Wtf! (Score 1) 515

It's not all about market muscle, even if this is a big part of the problem.
There is an area in which Linux is really lacking, which is "computer administration for dummies". Incidentally, the people who will be in the deepest trouble are home users, who are the administrators of their own computers, but have never learnt how to do that.
Grandma can use Linux: she will have a locked-down setup installed by her computer-savvy grandsons, and she only wants to go on the internet and print a few things.
Office users can use Linux, as their desktops are administrated by IT. Here the problem will be more about the OSS ecosystem. Almost every business uses "niche" software or "niche" features that are crucial to their operations.
But home users, who are always installing programs and configuring small things are in trouble. Let's say I run OpenSUSE... I can use YaST to configure my system. Or I can try to use the "system configuration" panel in KDE. Or I can use an independant KDE utility which will be happy to interfere with YaST settings, or will have absolutely no effect. Or I can use a command-line utility written in ncurses that I read about on the internet and was installed by default on the system (e.g alsamixer or others...). Or finally, I can hack directly the configuration text files, hoping that they have not been deprecated by a newer system.
If you know Linux, you will probably skip every of those steps to go to the final one, as it is the most reliable way to administer stuff with UNIX-likes. However, not every home user is either able to do that, or willing to learn that.
Let's compare the situation to Windows now, where you can go for 10 years with your home computer without even knowing what the registry is.

Never appeal to a man's "better nature." He may not have one. Invoking his self-interest gives you more leverage. -- Lazarus Long