Aviation week also has an article with some additional details: http://aviationweek.com/techno...

.. and your attempts to mischief. Our junior high school was fairly progressed, when I attended it in '97-00. The school had a server-infrastructure with group policies, it had several computer labs, in total something like 60-70 networked Windows-computers to be shared amongst the schools 300 or so students. For off-hours internet access the school had it's own dial-up service.

The computers had this 'netop school' remote control software installed. The program enabled locking the screen, executing a command remotely and screencasts. The setup had a few master installations, which allowed, if authorized to use these features.

Computers and using them like this were a new thing, and as the teachers were mostly at least in their 40s, this setup was a challenge - so the IT-administration had issued pretty easy-to-remember passwords, which were easily captured just by looking over the typist's shoulder.

So this is where the fun starts. Anyone remember Back Orifice? Anyone remember what c:\con\con did? Me and my friends installed BO pretty much to every single computer on the school, so it was kind of a standard to steal homework, passwords, essays whatever remotely from other students. One of my proudest moments was executing c:\con\con on every school's computer simultaneously, and watching them all turn in a blue screen. Yes, many lost work that day.

A friend of mine managed to grab /etc/passwd from the school's linux server. This was before the days of shadow passwords. When out drinking with old friends, someone almost always reminds us of the janitor's password 'tractor' :D

I believe this kind of activity might lead to more severe problems these days: as a response to all this I was sent to study Java and humbleness to the local technical university at the age of 12. :)

Yes, a solid point. Basically the idea is same, it's the yearly inspection indicating the roadworthiness of the vehicle, so the fault could be either emissions not matching the scale or body fractures. Even tho one cannot estimate the cost of ownership from those stats, they are a pretty good indicator of the overall build quality of the vehicle.

http://www.anusedcar.com/ features compiled statistics. Most of the ford models are translatable to their US counterparts, but most of the trucks and bigger saloon cars are completely absent from the import programs and road traffic because in Europe we have this thing called climate change. :)

I am European, so my opinion is bound to be biased, but in short: you are wrong. I measure car quality by (fuel) efficiency, emissions, total cost of ownership and reliability. No American car manufacturer can match the level upheld by the big three (VAG/BMW/Mercedes). Ford comes close but their cars are just a little worse by every single criterion. There are statistics to support my claim, such as the inspection statistics released yearly from Germany.

Yes it will. They even demoed the OS on N9s, but the good question is, whether they'll actually release it for the N9.

In any case, the N9 will benefit a free operating system from Mer and Nemo UX - which will be application compatible with Sailfish.

There's three parts to this puzzle here. Mer, which is the core distribution. Nemo UX, an open source UI for phones built on top of Mer. Lastly, there's the Sailfish UI, which is the proprietary, Nemo-compatible Jolla-look&feel UX.

It's currently possible to build Mer along with Nemo for N900/N950/N9 (along with several non-Nokia devices), but as far as I understand, the Nemo UI is not usable for the former device. The Mer wiki has quite a lot of relevant information on the topic.

Well the leak is a fake. In case anyone wants to know, it shows a picture taken from a famous shocksite. I don't know if it destroys your hd or anything, I tried it inside a virtual machine.