It's clear more countries should've had a song to explain the situation.

https://youtu.be/BtulL3oArQw

> I doubt very much the company is going to survive this

I'm sick of hearing this stuff. I heard it about virtually every Trump-related news story for the last year, I heard it about New Orleans, I heard it about BP. I heard it about Volkswagen.

Look, the market already priced this disaster, based on what data is available. They lost about 15% of their value. They have solid fundamentals that aren't changing in any sort of way that pose an existential threat to the company; unless there's a lot more of this than we can see.

The NSA's SELinux?

https://www.nsa.gov/what-we-do...

To be fair, your AMD analogy would only work if AMD printed "Intel Pentium MMX" on their K6s, and they were packaged in the same PPGA package as a real Pentium MMX.

The chips that FTDI is disabling really are counterfeit - they look identical on the outside to a real FTDI chip, it's not just matching FTDI's VID/PID to use the same drivers.

No, it didn't. Well, maybe by Linux fans.

It got panned for not running Windows software, and Linux netbooks had something like a 25% return rate, when their Windows counterparts were much lower.

I routinely use both OpenVPN and Junos Pulse on my Android. What are you talking about?

It doesn't look like anything spectacular to me, but the tree placement, giant warehouse, and that it's on the side of a hill make me wonder if it's just a disposal site of some sort.

If it's anything of importance, I'll bet it's a nuclear or toxic waste disposal site.

Assuming it's working properly.

My VW's system is supposed to do that, but because it doesn't sense the door unlocking or opening properly, the alarm stays armed, and you then get the alarm going off when you try to start the car.

I always get frustrated when I have to dig deep and manually read over scanned non-OCR'd PDFs.

Honestly, all I want is for all the documents and laws to be available. I would think that SVN with a web component would be great to be able to see the current laws, including the ability to 'go back in time', and it would work for posting minutes and agendas as well.

I'm not overly concerned with -presentation-, having the data available in a digital form alone is a major step forward, and you can build out from there.

Apple's cheapest phone is $650. Google's is $299. You'd have to be a fool to expect that they would be treated the same with that price delta. Also just how much is Apple paying for their goddamn radio that a 32GB iPod Touch is $299, but it's $650 for 16GB iPod Touch + Phone capabilities (iPhone)?

The difference is that most network admins shirk from the task of responsibly implementing QoS, but they'd gladly pay a hefty licensing fee to their wireless vendors for a product with a name like WiFox that 'boosts performance' by clobbering the network instead of cleverly balancing it to perform well.

And a reason for poor uptake of Vista over 7 was immature image deployment and customization tools. Half the options weren't documented, and the process was very unclear. By the time 7 came out, there was enough backfill on the documentation and examples online for people like me to actually work on customizing corporate images.

This is actually something that's woefully inadequate in the Linux world, real-world examples of the cool stuff you can do with HOWTOs for building a server and clients that are running off of shared volumes and centralized authentication. All the parts are there, and they work fantastically, but you sort of have to figure it out yourself how to put it all together.

This isn't why Windows 7 is 6.1, or why Windows 8 is 6.2.

The reason is that Windows 7 actually is just a minor revision on Vista, and 8 is a minor revision from that. Under the hood, the big changes were between NT 4.0 and Windows 2000 (Windows NT 5), then between 2000 and Vista (Windows 6). The changes from 5.0 to 5.1 (2000 to XP) or from 6.0 to 6.1 to 6.2 (Vista, 7, and 8) were incremental in nature as far as the inner workings of the OS are concerned.

The real reason 7 felt so much faster than Vista: When they made Vista, they planned on you booting up very infrequently, so they scheduled a lot of junk to happen at boot and login, thinking that users would just 'sleep' instead of rebooting. Windows 7 (And Vista SP2) backs off a bit and does the housekeeping when you're not using the computer. Vista actually wasn't really 'slow', it's just 'irrationally busy' doing stuff with the I/O (indexing, precaching, defragmenting, etc.) while you're just trying to get to your gosh-darned desktop.

So your de-dupe ran for a week before you cut it out? On a modern CPU, the de-dupe is limited not by the CPU speed (since deduplication basically just checksums blocks of storage), but by the speed of the drives.

What you need to do is put all this data onto a single RAID10 array with high IO performance. 5TB of data, plus room to grow on a RAID10 with decent IOPS would probably be something like 6 3TB SATA drives on a new array controller. Set up the array with a large stripe size to prioritize reads (writes are going to be 'fast enough' on a RAID10, trust me). Once you have that hooked-up with your files copied onto it, you want to connect the drive to an OS that can natively deduplicate, like Windows Server 2012. If you must, you can set this box up as a storage server (with a low-end CPU, an old 'Core 2' should be able to keep up with 180MB/sec I/O), and keep your workstation separate. Reading this entire array (when full) through the CPU -should- take about 6-10 hours, deduplication will take slightly longer.

If you don't want to do deduplication at the block level, and you want to actually only have one copy of each duplicated file, you'll need to write scripts that do something like this:

1. Run through the data store and checksum each file (except for those ending in ".mychecksum" with AES128.
2. For each file, create an empty file named .."mychecksum" next to it. This will create the 'index' using the filesystem, which will be MUCH faster than having to read the data from inside each file.
3. Search through the store and concatenate all the ".mychecksum" files into a single CSV.
4. Run sed+unique on the file to see what will be nixed (i.e. Get a report)
5. Create another script that actually takes the output from step 4 and deletes ONE of the duplicate files. You can test by -renaming- ONE of the files to .deleteme and then deleting all those files after you confirm that it worked.
6. Repeat as necessary, possibly with a scheduled job.

GP also mentioned that nobody is making anything better than 1080p, which is what I was refuting.