> It does have lots of car chases and explosions

It was pretty clear from the trailer that they douched up the Mad Max series real good. I won't watch it, but not because it has been ensnared in the incessant gender-war yammering that is almost inescapable these days.

> You are ridiculous.

Not really.

...that will let you know where The Authorities think you are at any given moment based on cell tower data?

What is the resolution?

> They were also able to precisely track a virtual reality headset with the same precision.

One does not "precisely track" a VR headset with two centimeter resolution. I'll guess that they continued to use the IMU tracking that is built into the Samsung Gear VR, and they used it to display the tracking of external objects that were measured with two centimeter resolution.

Conventional methods of payment would tie one's searches to one's identity. I would want assurances that it was not technically possible to log my searches.

is wrong with the comments section. We installed cameras around the house and ran the cables through the attic to the DVR in our closet. Houses in the neighborhood have been broken into and a car was stolen two doors down. We hope that having the cameras will deter crime and if they don't, we'll at least have footage. Our neighbor has a camera and it was very useful in catching some kids that burned down a bush in front of our house.

What the fuck is up with the kneejerk reaction to an article that is just suggesting that you try to get the bad guy's faces rather than the top of their heads? That sounds like good advice.

why would anyone want to run Google Chrome on a company Linux server?

Automated regression tests on the development build of a web application is one reason. Web pages can and should be tested, just like the unit tests for the code that backs them.

> SunOS/Solaris started out lean; when it got bloated, people like me jumped ship. Linux started out lean and it is getting bloated; when it is getting too bloated, I will jump ship again.

FWIW, Linus said that Linux is bloated. That was at LinuxCon in 2009. I don't think that's much of a factor. I'll agree with you that Linux has plenty of life left in it.

> Wow. How impressive. Oh wait, Linux has had EDAC since 2006. But you keep paying your millions to Oracle. I'm sure its worth it.

Actually, this might be worth an illustration. It was a long time back, so I'm sure I've forgotten a few details, but I'll give you the big picture.

Around 2000, Sun Microsystems had a problem with the L2 cache on their 400mhz CPUs. It seems that IBM misrepresented the error rate on the chips, and they were having bit errors that were much higher than specified. Because of what was supposed to be an incredibly low error rate, they engineered the L2 cache with parity protection. That's enough to detect an error and cause a UE (uncorrectable error) event. So I know that your EDAC functionality in 2006 was in Solaris well before 2000.

After that problem, Sun Microsystems did two things. First, they mirrored the L2 cache. Second, they completely beefed up their handler for CE/UE (correctable errors and uncorrectable errors) along the memory/cache/bus/cpu to bring it up to Enterprise level error handling. You get an Uncorrectable Error in your CPU's L2 cache. Do you panic? I looked over the EDAC documentation and I could be wrong (please correct me, if so) but it looks like that would result in a panic. Or you could just have it log that the UE event happened but take no action.

What would Solaris do differently? It would find the page of virtual memory that had the corresponding error. Has it been modified? If not, just discard the page, log the event, and go on. There is a whole set of rules it goes through to determine the best way to keep the system running when it hits an uncorrectable error. Let's say that the page was modified and that there was an uncorrectable error in the L2 cache. We panic now, right? No. Solaris checks and sees who the page of memory belongs to. If it is a user process, then that process is simply killed (and the event logged) and the OS continues running. Only if it is a dirty page of active kernel memory do we have a panic.

That isn't just recovering from a soft error. That's recovering from a hard error. So, as this story illustrated, there are quite a number of things happening behind the scenes in an enterprise level OS. You picked a good example with Linux EDAC.

> Why bother? Just shut down that server, replace the memory, restart. If your application can't handle a brief downtime for one of your servers, there is something wrong with the application, and no OS magic can fix that for you.

You know, it is kind of funny. Person A will argue, "See? Linux has all of the cool features of an enterprise class operating system. What makes Solaris on SPARC so special?" When you point out just a fraction of the things that Linux doesn't do, person B will jump in and claim, "OMG that OS is so bloated that people are running away from it for that very reason!"

Hey, Solaris on SPARC certainly has its issues, but let's be real here. People are not running away from it in any significant numbers due to the inclusion of enterprise-class features. The irony to that argument is that you'll find that many of these "bloated" enterprise-class features in Solaris have been working their way into Linux for years. Linux has been making great strides over the past ten years.

Wow. It took them that long to put in a handler for CE and UE events? I see. What we're talking about goes beyond that first level of handling those events.