What the fuck? Lossy compression has nothing to do with the quality of data retrieval on a hard disk. If you've got data corruption, it'll affect any sort of file (and `flac -t` will tell you when a file is corrupted). a 320kbps MP3 stored with no intermitent data corruption from 2001 will have exactly the same bits and quality that it did in 2001. (Encoders have gotten better. A 320kbps MP3 from 2001 might sound worse than the song from the same source being encoded as 320kbps MP3 *today*, but that hs nothing to do with magical degradation.)

Of course it's still Ubuntu. It's just not Linux. It's GNU/kWindows.

The new file system is just a bag of bytes for names. You can store ë just fine, any way you want it (though UTF-8 and composed are probably the best options).

Yes, 2.0 supports Windows 8 and 10 compatibility, both 32- and 64-bit. Actually, Wine 1.8 was the first to include Windows 10 compatibility ;)

Maybe more accurately, the Windows ABI being the universal one thanks to Wine. DirectX can be hit-or-miss, especially if you don't have gallium drivers on your system.

Carmack always used OpenGL for his game engines too, a tradition maintained in Doom 2016 as well, despite being developed and released after his departure. The Vulkan version even runs well in Wine.

So... Microsoft has telemetry? You really trust Apple won't copy that?

Apple had it first as well.

It comes at a severe price, if that's what you're expecting. The WRT54G is obsolete enough that most aftermarket firmware have not supported it in years.

Random reads and writes work fine, assuming it's sanely implemented. ZFS only compresses per-block (normally up to 128KiB). Reading and writing those blocks doesn't depends on other blocks in the same file. It's not even difficult to have a file on ZFS whose blocks have different types of compression applied to it. Works fine.

2.6.39 was actually the one that directly preceded 3.0 ;)

Nothing particularly special about 2.6.32 compared to the others, but it just happened to be one release in which all the major enterprise distributions landed on for one release cycle (Debian 6, RHEL 6, SLES 11, ...). That fact alone just kind of drove to keeping it maintained officially, and everyone on those distributions could stay happy with new upstream kernels of that series without breaking any sort of compatibility on their systems (eg, any kernel modules installed).

2.6.32.70 should. 80386 support was dropped in 3.5.y and further.

Please note that no mainstream distro has supported the 386 in the past couple decades. You'll have to be building all your own stuff to get it working.

CentOS tracks RHEL completely. For as long as Red Hat supports RHEL6, CentOS 6 will be updated. (New Red Hat-maintained versions of 2.6.18 still show up in CentOS 5 updates, even.)

What happened to PHP 6.0? Are they skipping a version just to one-up Perl?

GRUB doesn't do stages anymore. That would be a "rescue>" prompt. It's a little better, and can usually help to save from minor configuration mishaps, though not useful for more major oopses (maybe you changed file systems and forgot to update GRUB, now the boot.img doesn't understand how to read the file system...). It also gives a lot of pause to the thought of "Oh crap, what are GRUB's commands?"

Those scripts and configuration files sprang into existence well before GRUB 0.97 even. In GRUB 2, they're still not required and the configuration file is not hard to hand-write if you don't want the auto-OS detection and config generation said scripts provide :P

So... Wine with a new WINEPREFIX for each program?

Run Wine in a Docker image? That's pretty well-sandboxed. and easy to set up.