LG TV.
And in return, every read becomes a write, and you lose all parallelism of read-primary workloads. Nope, atime's crazy. Relatime is a good hack, but better would be throwing that misfeature away.
Similarly I can go on about Posix locking, fcntl(..., F_[GS]ETLK(W)?,
rename? Rename we should keep. And hard links while we're at it.
The "encryption keys came from servers in China" one
(the "poor use of encryption" one is
Lead researcher Dr Alex Wilkinson said: "The gases within these canisters are such powerful greenhouse gases that they can contribute significantly to an individual's carbon footprint and if you are using one or two of these inhalers every month, then that can really add up to hundreds of kilos of carbon dioxide equivalent over the course of a year, which is similar to other actions that people are keen to take to reduce their carbon footprint such as going vegetarian."
Emphasis added.
My inhaler has 200 doses when new, and I use around 10 doses a month? (2-3 a week, exercise induced asthma). To use an inhaler up inside a month suggests you're using it ~6-7 times per day, which seems completely insane. To use 1.5 inhalers up in a month would be 10 doses a day...
Anyone with that kind of asthema issue shouldn't be using standard Albuterol inhalers of the type being discussed, so either my experience is deeply non-typical, or the study authors have no relevant experience.... and I can't be sure which.
(and given payola pushes this down to "makes money per stream", likely has an argument)
Which may be why Zimmerman's defense didn't invoke SYG.
IMHO, there was not proof beyond a reasonable double that Zimmerman was on top. It's quite possible he was on the bottom, and was legitimately scared for his life. From what I know from the trial, I don't think I'd have convicted either.
On the other hand, from what I know from the trial, I also wouldn't have convicted TM if TM had managed to kill Zimmerman. It's a crappy situation for everyone.
You're assuming that the drive failures are independent. His point is that they might not be: the common cause may be write cycles.
Let's say that a drive under your write patterns will last 9 months. (Bad wear leveling algo, combined with very re-write heavy data structures?). You put 5 of them in a raid 5 enclosure, all brand new drives. 9 months later, they all fail within minutes of each other. Whoops, lost your data.
If they fail for different reasons, you're more likely to be safe. If they all fail from wearing out the ability to erase cells, you're more likely to be hosed, until you've swapped out enough to randomize the write count./p?
That company.
"Did you put the disk in the DVD drive?"
Excuse me for being a horrible pedant, but I would also get confused if you told me to put a disk into the DVD drive. That drive takes discs... the ones that are visibly circular and have no case.
Ahem. Back to your point, and sorry for making the point of the original article.
I had a small OCZ SSD of some variety in my foo-server (which mounted the NAS for all the important changing data). One day I realized that / had gone ready-only days earlier. Console showed a write failure to the journal (ext3).
Rebooted it, and it worked for ~1 day. Reformatted (managed system, I have no idea if there was data corruption. Didn't seem to be any, but I didn't look for any) and it worked for around 1 week. At that point I gave up and replaced it. It had lasted for just over a year when it failed.
The two Intel SSDs I've bought have not failed yet, nor has another OCZ brand SSD (Vertex3, fwiw).
We want to create puppets that pull their own strings. - Ann Marion
