Promising to give the trove of the former Secretary of State’s emails to the highest bidder, the specialist is showing subject lines as proof of what appear to be legitimate messages.
Link to Original Source
What was holding things up, it turned out, was that the ID plate that should have been attached to the inboard edge of the flaperon was missing. And that was not the only problem. According to the New York Times, Boeing and the National Transportation Safety Board found that the object did not match Malaysia Airlines' maintenance records.
...How the part found its way to a beach on La Reunion is another issue. The Depeche article contained a tantalizing hint. "According to a Toulouse aeronautics expert who requested anonymity," the article stated, "the element of the wing would not have floated for several months at the water's surface but would have drifted underwater a few meters deep." It's not yet known why investigators reached this conclusion, but one clue might be that the flaperon found on La Reunion was encrusted on every edge with goose barnacles. These animals are a type of crustacean that attaches while young to a floating object and spends its entire adult life affixed to the same spot. Since they obviously can only survive underwater, their distribution around the object suggests that the entirety of it must have spent at least several months submerged.
When the couple unfurled the note inside, they found a message in English, German and Dutch. It asked the finder to fill in some information on where and when they had found the bottle, before returning it to the Marine Biological Association in Plymouth. It said whoever did so would be rewarded with one shilling.
Communications director of the Marine Biological Association, Guy Baker, told The Daily Telegraph: "It was quite a stir when we opened that envelope, as you can imagine." Once at the association, staff recognised the bottle was one of 1,020 released into the North Sea between 1904 and 1906 as part of a project to test the strength of currents. Mr Baker told the paper: "It was a time when they were inventing ways to investigate what currents and fish did. Many of the bottles were found by fishermen trawling with deep sea nets. Others washed up on the shore, and some were never recovered. Most of the bottles were found within a relatively short time. We're talking months rather than decades."
True to their word, the association sent a shilling to the couple as the promised payment.
The plane that so audaciously changed the shape of the world is now on the wrong side of history. Airlines are retiring older 747s — JAL no longer flies them — and Boeing's attempt at catch-up, the latest 747-8 model, has had technical problems and is selling only very slowly. The air above my garden will not be troubled by 747s for very much longer.
The article gives brief but detailed outline of the 747's history, and why passengers and pilots still love it. I love it because of this:
The 747 was America at its proud and uncontaminated best. 'There's no substitute for cubic inches,' American race drivers used to say and the 747 expresses that truth in the air. There is still residual rivalry with the upstart European Airbus. Some Americans, referring to untested new technologies, call it Scarebus. There's an old saying: 'If it ain't Boeing, I ain't going.'
A comparison to the European Concorde is illuminating. The supersonic Anglo-French plane was an elite project created for elite passengers to travel in near space with the curvature of the Earth on one hand and a glass of first growth claret on the other. The 747 was mass-market, proletarianising the jet set. It was Coke, not grand cru and it was designed by a man named Joe. Thus, the 747's active life was about twice that of Concorde.
The Jumbo Revolution is a wonderful Smithsonian Channel story of the history of the 747.
I am a supporter and committer; my name is on a couple of files in the Linux source. If you're saying that doesn't make me a True Scotsman, then so be it. Why would Linux be a good choice if suspending is a coin flip? Because I don't suspend servers or a handful of other devices Linux supports. I'll stop supporting Linux when < 95% of what I want to do just works perfectly fine and Java is a first class citizen on Windows or BSD; I'll also need Python, Ruby and Perl to be painless to install and run. I'll switch my file server to BSD, like my router/firewall, when it offers me something over Slackware. Also, there's the issue of a few hundred Linux servers, VMs and appliances we have all over the world in my work life.
I accept the suspend thing on my Fedora/Linux Mint dual boot because it's my secondary desktop that I have Steam installed in Linux Mint for gaming and my backup development environment/testing/VM setup on. I boot between the two of those enough that I don't hibernate often. I'll suspend to RAM if I'm going back to what I'm doing within the day, otherwise I just shutdown.
For me, bottom line, the things Linux gets wrong are mostly annoyances and on the whole the OS makes my life better. YMMV of course, but for my use cases the good vastly outweighs the bad. I'll agree though that some of the bad is pretty darn ugly; I'm in complete agreement that SystemD is crap. I want to kill that part of the stack with fire.
As I'm sure you're aware, the resume process has to do everything in a precise order because some subsystems rely on others to be awake before they can proceed. Every driver has to interact with less traversed paths of code and they have to work on sometimes obscure hardware where the documentation doesn't exist or is wrong (think reverse engineered drivers), and every piece has to work more or less flawlessly or the rest of the chain can't load.
As I understand it, the state of the machine is written out to page file and has to be loaded back from there and then run as if nothing had happened. Consider just the case of software that doesn't behave correctly when the system time jumps ahead a couple of hours mid computation. I've had issues with KDE not being able to wake up from screen saver (maybe USB didn't reinitialize correctly and it can't see my mouse/keyboard inputs?) or the screen not coming back without power cycling my monitor after thawing out the state.
There's a lot that can go wrong, and it seems it usually does. I know even Windows sometimes has issues when I close my laptop and head into the office - sometimes it remains running the entire time (I think VirtualBox is the cause - but I can't reliably reproduce, so I'm not sure).
You are false data.