Linux Distributions Archives
linux-distros.com
linux-distros.com
Yup, went and dug it out of the garage: https://ibb.co/PM4GTkt
I have never heard of this! I have always used XFree86 (later forked to Xorg) as far back as I can remember. From what I can find, this was a commercial/closed source server that shipped for $99. There doesn't seem to be much info it.
http://ictbanking.com/LJ/035/1374.html
Actually Metro-X server sounds quite cool for its time. Multi-display support, X-based GUI for configuration (anyone remember xf86config stuff?)...
I actually bought the Red Hat Linux 3.0.3 (and used it and its successors Until Red Hat 7) but the Metro-X didn't support my video card so I was stuck with the XFree86.
Does anyone know if the later Redhat versions (than 3.0.3) offered Metro-X? Probably not in the free, downloadable ISOs but was it bundled in the sold CDs or was this one time thing only?
Wow, yeah. I also remember the YaST X configuration tool that shipped with SuSE.
But something like OS install media I would expect to already have compression applied to payload. Eg. Rpm and deb files probably use gzip. That wouldn't compress too well. So maybe just .iso would be fine.
Rar itself seems to be pretty common in certain enthusiast communities where people tend to use windows. For example I still see it when people are passing Android ROMs and unlocking tools around on web forums. And very few other places.
1. Efficient random-access storage. If compression is supported, it is done on a per-member database.
2. Efficient all-at-once compression (block/solid compression). This is either handled explicitly by file format (RAR and 7z, for example), or the archive doesn't support compression (tar) and itself is processed through an external compressor.
On the first category, I would argue Zip has clear superiority over most other file formats. It supports all metadata fields for both DOS/Windows and Unix operating systems, and has very wide support amongst everything. Zip does not support the second category of archival formats.
In the second category, 7z (I don't know about RAR, but I suspect it holds true) only supports DOS attributes and modified dates, making it totally insufficient for backing up a lot of kinds of Unix file trees. tar is generally the de facto standard for Unix and naturally supports all metadata. I would argue gzip is long obsolete; zstd is much faster (it can nearly compete with xz too for file size).
tar files don't really support random access for individual members, lacking a central directory, though uncompressed files can be seeked rather rapidly anyway as the tar program just skips over members (each member encodes its length). Compressed tar files make this worse, since the entire archive must be uncompressed in memory just to find anything. This is a large reason that tar is mostly restricted to being used when extracting individual members is not a generally useful operation. If that is a useful operation in your datasets, go for Zip.
The main reason I've been told as to why this is seems to be the extensive error correction, which was a big deal with large game files back in the Dial-Up/ISDN days where a corrupted download was more common than now, and old habits die hard.
It's weird, come to think of it, that RAR has existed for a quarter of a century, and yet the format has never been documented or reverse-engineered and no FOSS implementations exist. The only way to make a RAR file is the official program, which is binary-only shareware; there is public source code for extracting RARs but under a license that explicitly forbids using it to reverse-engineer the format.
But I guess the overlap between people who care about all that and people interested in the kind of stuff RAR is used for is next to minimal.
I first installed it in late 1993, back in the kernel 0.99.10 days, eventually moving on to Slackware...