And like a typical IT guy, what you "know" is beyond question. No way you could possibly be wrong.

If, someday, you work with enterprise systems, you might come to realize that very large systems are often riddled with inefficiencies. When multiple parties are involved, or legal compliance, those inefficiencies can become powerfully entrenched.

Take a look at some of the high rated comments on this article for explanations as to why and how banking is not as efficient as you imagine.

Yep. Bought a Honda Insight this year. Unlike the Prius, it has all physical buttons.

Sadly, the Prius dominates that market segment, and the Insight is being discontinued.

Perhaps someone should introduce Julian to Marcus Porcius Cato.

I just want to point out the the post you replied to was voicing a "no" vote for overtime exemptions, which is the same position that you are advocating.

Quite the opposite. In the last few years, Firefox has worked harder on reducing memory use and improving performance than anyone, and it shows.

That's true of all browsers. Firefox uses less RAM than any other browser, with an equal number of tabs open, on any platform I've seen numbers for.

A lot of us benefit from Free Software. Android is primarily developed by Google, so it has a steady source of funding. GNU/Linux has a large community of volunteers, but is honestly developed primarily by businesses that get revenue from server support contracts (Red Hat, Intel, SuSE, IBM, Google, to name a few).

Firefox is, by a host of measures, the best browser available. If I'm reading arewefastyet properly, it's the browser with the fastest Javascript engine now. The last time I checked, it's the smallest download. It uses the least RAM. It starts fastest. It supports plugins on all platforms, including mobile.

The browser is key to practically every Internet service, and they all really should be contributing to the development of the one browser that's fully Free Software. Sadly, unlike Android and GNU/Linux, Firefox is essentially ad-supported. It's a bad situation for us, the users.

No, you don't. glibc still uses /etc/resolv.conf. If you modify the file, changes will take effect immediately, unless a specific application caches the DNS configuration. Firefox, for instance, does (IIRC). That has nothing to do with resolvconf, though.

That's actually not correct. If the ssh session is terminated, the shell will cease executing the command line it has. To be specific, it will receive SIGPIPE (IIRC) and exit.

You should use screen, or tmux, or nohup for this sort of thing.

You mean .doc?

Some, maybe. It's getting harder to name them. Firefox is a smaller download, uses less RAM, starts faster, and (if arewefastyet is to be believed) has a faster JavaScript engine now. And the mobile version supports plugins. And I can run my own sync server if I want to.

No, it doesn't. I operate lots of machines with ECC RAM. I've seen ECC correction. Bits flip, but nowhere near that frequently. It's very rare.

The original advisory notes that "Since Drupal uses PDO, multi-queries are allowed." I can find documentation that confirms that's true of the MySQL PDO adapter. Is that also true for PDO for other databases, or is this vulnerability specific to MySQL?

Interesting note: that's not always the case. If you're on a network with a lot of broadcast traffic, WiFi will keep the phone from entering deep sleep, and your battery life will be terrible. It took me quite a while to figure out that my battery life's turn for the worse coincided with starting a new job, where the WiFi network is really big.

If you haven't used iostat before: Run "iostat -x 2" to get a report of block device utilization every two seconds. Ignore the first report; it details utilization since system boot. All subsequent reports will be for the period after the previous report.

If you can repeat your earlier tests, and want to see if there's actually a Linux bug, compare numbers when the program opens DBs before forking, and when it opens them after. If you're seeing bad latency in the former case, but similar B/s, that might indicate a bug. If you're seeing much higher %system (CPU), that might be a bug. Maybe. Otherwise, it's probably an indication that the program behaves differently in those cases, which is not a Linux bug.