Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror

Comment Re:Recoverable Failure rate: 99.9% HDD, 1% SSD (Score 1) 512

If you're using engine check lights as an analogy to SMART data so you know when to swap out a drive, I still disagree. Once SMART data goes bad, you can usually still get data off the drive but I wouldn't trust it to not have some corruption. I'd just yank the drive, rebuild the RAID if the machine needs high availability, or copy over from backup if it doesn't.

If recovering from backup and the backup isn't quite up to date I'd probably try some kind of data recovery, but I wouldn't want to rely on it.

Comment Re:Do the math (Score 1) 512

Compiling is almost ALWAYS IO bound for a project of any size. Why do you think make -j 4 or make -j 8 makes a noticeable difference on even single core machines? Because the compiler spends most of its time waiting on disk IO, reading and writing all those intermediate files.

From my experience when I toyed around with Gentoo a few years ago, make -j worked best when the number provided was {core count + 1}. Any more than that and it slowed down due to context switching overhead and/or disk head thrashing.

VisualStudio also supports parallel compilers for this exact same reason.

It has severe limitations. It doesn't work when you need to import TLB files, it does not work with incremental rebuilds, and it doesn't play particularly nicely with precompiled headers. The former is required for our project to build at all, and the latter 2 improve productivity more than using multiple threads (YMMV).

Comment Re:RAID (Score 2, Insightful) 552

That's just asinine. You should never rely on recovery of data from a broken drive to avoid data loss. Even if you do recover data from a broken HDD you shouldn't trust it hasn't had some form of corruption. Always have a backup. If you have backups, who cares if the drive is recoverable?

Also, don't buy Sandforce SSDs. There are plenty of alternatives that are faster and more reliable.

Comment Re:Still don't see patents helping (Score 1) 98

Open source communities can buy patents and use them to gain market share or revenue via licensing if they want, there's nothing inherent about releasing source that prohibits owning patents. They're expensive and difficult to acquire though which is why you don't often see it, so claiming a net benefit there is a bit of a stretch too.

Trade secrets on the other hand? The secrets are in the source, which once opened are no longer secret. I can't find any far-fetched argument that supports trade secret law in an OSS manner.

Comment Re:Political stupidity at it's zenith (Score 4, Insightful) 87

No, the announcement was for an OPT OUT system. They backtracked claiming they meant for it to be opt in, yet how something like that gets written up in sufficient detail describing how the opt out system would work when they intended opt in just boggles the mind (read: they're a pack of liars).

Slashdot Top Deals

"Any excuse will serve a tyrant." -- Aesop

Working...