Read that article all the way to the end, they are not going rolling release. That was just is just a proposal for discussion. Later articles show that it got shot down, though this new 9 months of support for the non-LTS versions is almost the same. In practice was probably just trolling from your M$ buddy Rick Spencer who somehow got inside Ubuntu and has been starting to work his toxic magic on it.

But who compiled the compiler?
http://www.ece.cmu.edu/~ganger/712.fall02/papers/p761-thompson.pdf

Actually, that, too, has been thought of and worked out. The trusting-trust attack can be fully countered through Diverse Double-Compiling. It's all over my head but the material is there at several levels of detail for those who would read it.

It depends on what that two-factor authentication is. If it's just another password, then the keylogger can (and will) steal those and you are no better off security-wise than before. What's needed is something serious like one-time passwords. An added advantage with them is that even if they are sniffed, they are no good for an attacker to try to reuse.

If they mean "all underage" and not just "blatantly children", good luck with that. There are no characteristics that will distinguish between 17 and 18, or even older. What is the software going to think of Kat Young, for example? What about models who are just small?

Also are they going to attempt to sort through drawings at all, considering they are legal in some jurisdictions and not others?

I sense false positives and angry models in Google's future.

Most models are just small. The average female porn star is a 5'5" brunette woman who weighs 117lbs and has B-cup breasts, and measures 34"-24"-34". So half are smaller. The lightest is apparenly only 74lbs.

Judge Jackson put up with all kinds of crap during the antitrust trial that would have garnered normal people punishment for contempt of court. One of the more ridiculous examples was when Microsoft execs presented a forged video as evidence in the trial. Not only was the video doctored, it was doctored in a bad, amateurish manner, just like their software. Even at the time it was a puzzle why that went unpunished. Now we can see that was just standard operating procedures for M$.

That's one example, and did not run through to the end. Yes, it was at least close, but after contact cut off, it could have deviated quite a distance to either side or even fallen short.

With the US forces it was the same video shown over and over and over. The one down the elevator shaft. If it had happened more than once then we would have seen a more representative sample. One lucky shot was caught on film, that's all.

A good rule of thumb is to roll your sessions back prior to the start of every single class. This always gives a fresh machine and the students will quickly learn how to set their VM just the way they want it.

They can start each class with a fresh snapshot. In effect they would be restoring from backups. The configuration files from some other networked storage or their thumb drives and the applications themselves from the repositories. I've done something similar, but on bare metal, and after about half a dozen times they don't notice -- it had become such second nature to install and restore applications. Heck you might even have them practice installing the whole system from scratch. If you go that route, they can become quite proficient with installation and resource allocation. PXE booting a netinstall image helps there.

However, once you start to load packages from the net things can really slow down unless you prepare. The best way is to have a cache like APT-Cacher or Squid on your LAN or host system and have them configure their systems to use it for APT. For the cache to be most effective, you have to pre-load it before each class. That's easy and can be done while doing other things. It only takes time not attention. But once you have the cache loaded, installation will fly and can be done in 15 - 20 minutes. After that they weren't shy about installing on their own computers at home or helping their friends.

If SSH is working properly you don't need a VPN. In fact if your service is so insecure that it needs a VPN then it probably shouldn't be connected to the net in the first place. Same goes for Git, SVN and other versioning. I can think of dozens of work activities that would never need to use a VPN. The whole premise of low VPN usage smacks of MBA-driven ignorance and Windows quirks.

True. Those things are almost exact opposites. You will never waste money by cutting costs, if you are accounting correctly.

Creative accounting has created too many problems and expenses already. Cost cutting itself will never waste money if the actual cost cutting is really done right. I've seen and heard of too many cases, especially in larger companies, of being penny wise pound foolish.

Good point. Nicholas Negroponte's One Laptop Per Child didn't fail on its own, however. It had help from M$ and M$' better half, Intel. They got in and messed with OLPC causing delays, barriers and overruns. Even in the most generous assessments, Intel had a serious conflict of interest because it was actively trying to sell a product of its own which competed directly with OLPC. The OLPC was suppose to be based on the AMD Geode and Intel couldn't have that.

Yeah, and kid$ like you have been $aying this $ince '98, too. *Yawn*

To be fair it must be pointed out that M$ ran an $18 billion loss in 1998. Subsequently they may have gone over to Enron-style accounting to shuffle the numbers. Now even with all the voodoo economics, M$ is running a loss. Things would be even more bleak without tricks like deferred sales.

So if it were up to just the numbers, they would have been long gone.

He made no call to abolish the TSA. He made a call to privatize it. There is a world of difference. There would be even less oversight of the TSA if it were out of government hands. It's bad enough as it is. Privatizing it would just remove all accountability, not that there is that much now. If it really were a call to abolish the TSA, that is something that many freedom lovers could get behind.

Look at the stats. The old ones never really go away. They just get overshadowed by the newer ones. A little bit of trickery is also done with counting variants as separate malware. Anything to keep the stats down.

I don't want a touch screen. How about saving the touch screen and making a $150 laptop? The touch screen is just unwanted extra cost. I have a hard enough time keeping the screen clean without people intentionally smearing their grubby fingers across it. It's definitely not anything I want to pay extra for.

Netbooks are quite useful. I'd also like to see more ARM units with long battery life. The netbook form has more room for battery than a tablet does so there really aren't any excuses any more for not having 10 - 12 hours of battery. That's enough to get through a full day at a conference or long flight with transfers.

M$ did cause Nokia to tank. That was done via Elop. The topic of Elop comes up often at Tomi Ahonen's blog. He is the most accurate mobile forcaster around and has on multiple occasions enumerated the damage being caused by Microsoft's Elop at Nokia. Nokia was at the top of it's game when Elop killed it. The Linux phone that he stopped was getting better reviews than the iPhone. But at this point there's nothing viable left and he's even brought in more people from M$ than just himself to ensure that the damage is permanent. Most of the talent has been fired or left on their own. If you want to look for progress, you'll have to turn away from Nokia and towards Jolla. That's just a sample of what the state of Washington can expect with microsofter in charge.