Right, and it's less likely to die from shock or head crash or manufacturing defect, and when it runs out of erase cycles it fails soft; writes fail, but it's still readable; certainly a better failure mode than most drives. Yes, the X25-M has a 5 year design life, just as platter based drives, but I suspect it's also more likely to actually achieve it, firmware update screwups aside.
The MLC X25-M is rated at 20GB/day for a 5 year service life, why would most people care?
ATI drivers work well enough for me in Win XP, Windows Vista and Windows 7, on a HD3200, 4870 and 5870 respectively.
On the other hand the nForce 4 chipset on my motherboard died and my 8800GTS 512 died, so I tend to avoid their stuff now.
Aren't anecdotes great?
I would expect they'd be using some sort of slot, something like this. Motherboard manufacturers aren't exactly going to be thrilled at the idea of putting some yet more expensive components on there, but they might be happy to hook up a small ZIF socket thing like some of them do with CF.
Intel actually had some weird ZIF connected SSD's on there a while ago on preorder, but they appear to have disappeared.
Either way, it's nice to see some hybrid storage stuff which isn't ZFS L2ARC (zpool add tank cache
I've tried an X25-M on a few servers with LSI SAS controllers (as used by PERC 6i, though I don't think I've used that exact chip) and been disappointed to encounter IO hangs and other drives disappearing randomly; even just having an X25-M plugged in is enough to seemingly make the controller rather unhappy. Doesn't appear to be a driver problem, unless it's one shared by FreeBSD, Linux and Solaris.
Hopefully Intel will do an SAS version at some point; they could compete against 15kRPM drives rather well, I think.
Intel rated the first generation X25-M's at 100GB/day for 5 years, I'd be surprised if these were significantly worse.
In my tests, gcc only optimizes out null checks at -O3 or above, which is already known to make potentially unsafe optimizations. Maybe if -Wunreachable-code were part of -Wall it would have been easier to spot.
Why assume anything? I've been using the RC for 6 weeks, nothing wrong with it. Good step up from XP.
Toady would be the first to admit the interface sucks. Future developments are listed on the main site; note the sizable Interface Arc. e.g. Core52 is "INTERFACE OVERHAUL, (Future): A coherent interface, additional options and mouse support". It'll happen when it happens, probably once more of the underlying behaviour stabilizes.
In Dwarf Fortress, at least, you have to memorize an arcane system of key commands to navigate through a literal fortress of menus
The standard display lists those key commands in the side of the window. You likely will memorize at least some of them during use, but you certainly don't have to.
An 80x50 window with 16x16 tiles takes up a quarter of my display. I normally run much bigger than that, and the tiles look pretty distinguishable to me - certainly more so than just using colours to distinguish goat from goblin and peasant from hammerdwarf.
If I need a bigger overview, d12 supports zooming; it's still usable at 8x8, but I rarely find myself wishing the standard display was that small.
Dwarf Fortress is fucking retarded. A text based game that requires Windows or OSX, 512 MB of RAM, and an OpenGL video card. No Linux and no mobile device support
Linux version. And it works fine on my laptop, great way to wile away a 4 hour train journey.
What's the point?
Um, it's a fun game? What other point do you want?
Using what encoding scheme? With a single mark the best I can think of is to treat it as a variable-length base 1 value; increment a Bignum for each atom until you hit the mark, and the final binary encoding of that is the data.
A 10TB LoC would make up a Bignum 87960930222080 bits long (and thus with a range of 0 - 2^87960930222080 - 1). Sadly with this encoding scheme the universe only contains enough atoms (~10^80) to encode about 32 bytes of that.
You define the randomness of data by how compressible it is, duh
<?xml version="1.1" encoding="utf-8"?>
<random-data source="/dev/random">
<quad>äàÛ÷</quad>
<quad>o†*‰</quad>
<quad>G•Ÿó</quad>
<quad>Ðæö…</quad>
<quad>³¿ÙG</quad>
<quad>!sá</quad>
</random-data>
For 4k of data:
-rw-r--r-- 1 freaky freaky 4096 2009-06-27 18:04 rand.dat
-rw-r--r-- 1 freaky freaky 30093 2009-06-27 18:04 rand.xml
-rw-r--r-- 1 freaky freaky 5618 2009-06-27 18:04 rand.xml.bz2
-rw-r--r-- 1 freaky freaky 7519 2009-06-27 18:04 rand.xml.gz
You missed the "encrypt it" step.
Kleeneness is next to Godelness.
