"smooth RAC cluster installation". That would make a pleasant change.

Of course they didn't deny they had it. *They* were the ones who told the authorities they had it.

Google never wanted the data. They would have deleted it immediately when they discovered that bits of random traffic data had been logged along with the SSIDs (which was the bit they were after), except that would have been regarded as destroying evidence. So instead they notified all the relevant authorities and waited for permission and/or orders to delete the data.

We know due to lots of stuff, like tree rings and lake sediments. While they all have margins of error, they are all in broad agreement that the temperature rises in the last century have been exceptional. We also have CO2 data from ice cores that shows that for 0.5M years CO2 levels varied between about 180 and 280ppm, in step with the ice ages and Milankovitch cycles, while in the last 100 years it has risen suddenly to 400ppm.

The relationship between CO2 content in the atmosphere, and how much heat the Earth absorbs from / radiates into space, is basic physics, and has been well understood for a hundred years or so. Increasing CO2 from 280ppm to 400ppm will cause a significant heating of the atmosphere and oceans. Dismissing it because it's only 0.00012 is vacuous handwaving.

IANAL. IANA American. However, my understanding is that: copyrights are decided in federal courts. This decision does not establish any precedent, although of course people in other trials may reference it as a useful example of something clearly argued. If appealed, it goes to the 9th circuit, which covers a few states including California. If that circuit makes a firm ruling on the copyrightability of the SSO of APIs, then that is precedent-setting for all lower courts within the 9th circuit area. Courts in other areas are not bound by it, but may of view it as a useful example. If further appealed to SCOTUS, then any decision there binds the entire country.

See Talk origins; in particular 29+ Evidences for Macroevolution

Did you mention hydrogen bombs to him?

and similarly, if the jury decide that that Google *did* copy the API (i.e. it wasn't fair use etc), then if after appeal it's decided that APIs are protectable, it avoids having to send the case back with a new jury to decide whether Google violated that copyright.

Its not a leak, Someone has already commented in the ticket that if you repeatedly create and destroy perl interpeters, then you need to set PL_destruct_level, because otherwise, (for efficiency), perl doesn't completely free the old interpreter, on the asumption that you're about to call exit(). So, it's just that no one got round to marking the ticket as rejected.

No, the "ALTER DATABASE BEGIN BACKUP" was just how the issue was first discovered. The issue is that someone with *low* privileges on an obscure, minor DB server can bump the SCN on that server, which if it happens to be linked to any other servers (like your big important one), causes the SCN to get bumped on those servers. So you can DoS all the other servers.

Well, the A380 was the first civil airliner to really use composites. It has >20%, whereas prior to that it was 10%. See "Advanced materials" on the A380 wikipedia page.

In case anyone was thinking that £12B is a lot for a database, what that money *actually* represents is providing a large chunk of the NHS's IT infrastructure for the next 12 years; or £1B per year for the IT needs of an organisation with 1.4 million employees and an annual turnover of £100B. The central data spine (which is the bit suffering the biggest problems and delays) is only one aspect of the system: it includes everything from making X-rays digitally available, to providing the network connectivity to individual GPs. Much of this is already in place and happily working.

Because unless you know what fried the primary controller, there's a good chance you'll just fry the back up controller too when turning it on.