Become a fan of Slashdot on Facebook


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Re:Forget the graphic cards... (Score 1) 92

It really depends on what your priorities are. My current system is an FX-8350, and the new stuff does look like a really nice upgrade. It's definitely faster, and definitely more power efficient. But I do need to factor the cost of a new mainboard, CPU, RAM against keeping what I have. I'll pay more for the ongoing running cost in electricity usage for sure, but that usage is dwarfed by the replacement cost of all that hardware--it will take many years to break even. So I'll probably hold off for a year or so, and the cost of all the parts will be even cheaper by that point. I'd be in more of a rush to upgrade if what I had was noticeably bad, but the 8350 is a fine processor for everything I do, from gaming to compiling and running multi-threaded analysis code. While the new stuff would be nice for all these things, it's not sufficiently compelling to replace the hardware today.

Comment Re:This just in (Score 2) 395

Kung Fury review and movie. If a single person with a small budget from Kickstarter can do that, then Hollywood should be orders of magnitude better. As it is, I found this more entertaining than the latest Iron Man or other Marvel stuff. I may just have questionable taste, but while this is a cheap and cheesy feature, it also quite clever--the whole thing is a parody of movie tropes, doesn't take itself seriously, and ticks a large number of boxes.

Comment Re:Don't help out previous employers either. (Score 1) 63

Exactly. If you're ethical, you won't leave any access possible, so there's no doubt as to your integrity. When I left my previous employer, a small business where I had full admin rights (I set most of it up), I made sure to wipe all my ssh keys, lock and delete my accounts so that the company directors could be sure I no longer had any access, remote or otherwise. No cron jobs, no source code, no customer information. A few months later they asked me if I could look into a problem that cropped up, and had to tell them it was impossible since I had no means to log in, but I could visit in person to briefly talk to their new staff. Mutual respect, and no possibility of any suspect practices due to being completely transparent about the leaving process. It's idiots like in TFA that give all of us a bad reputation, or at least cast a shadow of doubt upon our professionalism. Unfortunately, it's all too easy to do that if you don't want to act in good faith, particularly when you are entrusted with privileged access to a companies systems and processes.

Comment Re:Music makes no sense (Score 1) 167

Some electronic music, e.g. some trance, can be beautiful and subtle. But the best artists are often classically trained musicians, who can actually compose and arrange music. Both trance and classical music have very similar structure, so it makes sense that one can translate well to the other. For example, you can listen to some of Above & Beyond's early work like Tri-State, Sirens of the Sea performed by an orchestra; would have likely been better had it been written for an orchestra in the first place, but it showed that the various electronic instruments, effects etc. did almost directly translate to a classical setting. That said, there's an awful lot of crap out there, and being able to use a sequencer doesn't make you a gifted composer. I watched a youtube video of a trance producer last week going into how to use Ableton, and while interesting the result was terrible, almost as you say at pots and pans level.

Comment Re:64-bit (Score 1) 195

I've read the pages where Microsoft attempt to justify this decision, e.g. I don't buy it. It's institutional laziness and resistance to change first and foremost. Choosing on a per-application basis whether to make it 32-bit or 64-bit is madness, especially in the situation here where you force every plugin and library being loaded to be 32-bit. You're developing a *system*, but it's really an agglomeration of different bits with little coherence or common direction. Linux distributions got this right. The whole installation is x86 or amd64. No confused mess of the two, x86 compat libs aside. We didn't agonise over minutiae, we did a complete conversion by treating them as two separate architctures, with biarch and multiarch for running legacy code. As is typical for Microsoft, they didn't have a transition plan, leaving much of their product line 32-bit only despite most developers and user having fully transitioned to x64 Windows over a decade or more back. Meanwhile on FreeBSD, Linux and MacOS X 32-bit is a distant memory on 64-bit platforms; the transition was done well over a decade back for many distributions as amd64 rebuilds were completed. What's tragic is they did the exact same thing with the 32-bit transition. Remember what a mess it was in the mid-90s to mid 2000s with a jumble of 16- and 32-bit code? It's exactly the same mess today with 32-bit and 64-bit code! They need some direction from the top to pull their fingers out and go 64-bit only, or do builds of both. If the BSD and Linux distros can build code for >10 architectures then I'm sure Microsoft can manage two, or three if we count their arm port (which is even more limited due to their x86 depenence, who would have expected that... Maybe build all your code on all architectures and x64 and arm could be first-class citizens.)

Comment Re:You have a hardware problem. FS choice won't he (Score 1) 475

The device error correction is probabilistic. It won't necessarily know the data is "bad". And there can be firmware bugs which make it return or store bad data. What about phantom reads and writes. is a very interesting presentation from Bryan Cantrill about all sorts of bitrot and storage stuff.

Comment Re:Why so much love for ZFS, none for BTRFS? (Score 1) 475

When it comes to archival, ZFS is a production quality filesystem and volume manager intended for serious use. Btrfs is perpetually pre-alpha. Using it for archival would be foolish. It's also tied to a single implementation on a single operating system. I can (and have) run "zpool export" on a Linux server, removed the disks and slotted them into a FreeBSD server, then run "zpool import": data immediately on-line and mounted. It would also have worked for any other OS implementing ZFS; for data transportability it's the most feature cross-platform filesystem right now, given that the alternatives are crude filesystems like FAT. Archival implies the ability to read the data in a few decades, and I would bet that ZFS outlasts Btrfs by a significant margin. The single implementation of Btrfs might have been removed or changed incompatibly before you need to reread your data, and that presupposing that Btrfs wouldn't trash your data unrecoverably in the interim; after several total dataloss incidents with Btrfs due to implementation bugs in Btrfs, let's just say I'm a bit more grounded and objective as to its true merits.

Comment Re: bit rot (Score 1) 475

It did, but it was taken from OpenSolaris and ported to a number of platforms, notably FreeBSD and IllumOS (OpenIndiana, SmartOS, Nexenta), and also Linux. The featureset, integration and and usability on Linux is poorer than the rest. Though it works well, it's better on the others.

Comment Re:bit rot (Score 1) 475

Is it? After repeated dataloss using it with raid 0, 1 or none at all, plus other problems like becoming unusable from getting completely unbalanced, I'm a bit shy about trusting it quite so readily. It's hard to say it's "fine" when in all cases it was "fine" right up until the point it was "not fine" and lost all its data or went read only. "Working" isn't a useful observation for a filesystem; validating that it copes with every conceivable failure case by having the test cases to do that would, but it's been clear from all the failure scenarios I've encountered that this is missing. While the worst dataloss bugs have been fixed, it doesn't provide confidence that others remain lurking in there, or if regressions occur and reintroduce bugs. Btrfs continues to be a gamble which is not where you want to be when you care about data integrity. One of the reasons I switched to ZFS two years back. Once bitten, twice shy. But I've been badly bitten by ZFS on several occasions...

Comment Re:bit rot (Score 1) 475

ZFS can be more intelligent though, since it has more information about what the data means, rather than simply looking at raw blocks. If you have a copy count greater than one, it can use the redundant copies in addition to the mirrors or raid parity to self-heal. It can also ignore errors when it's in an unused block; that would otherwise be an error since there's no way to know the block is unimportant.

Comment Re:bit rot (Score 1) 475

LZ4 is performant, since it was intended to trade off compression efficiency for less CPU and memory usage. And is cleverly run multiple times over the same data to improve the compression, then bail out once it's no longer worth repeating. But some of the other options have terrible performance; gzip is dire, and gzip-9 barely usable. When I tried benchmarking these a few months back, they nearly tanked the server by making the filesystem nonresponsive and pushing the CPU utilisation through the roof copying a few hundred gigabytes of data (FreeBSD 11). LZ4 in comparison is barely noticeable--it's definitely the best choice.

Slashdot Top Deals

Disk crisis, please clean up!