So we've had some debates on the merits of each in the past and such. So I wanted to compile a proper master thread for two reasons:
1. Give up to date info on what IRIXNet is doing about disc preservation and how we plan to tackle disc image stuff.
2. Give reasons for our current/past opinions, and also explain how we're gonna change that up.
3. Give people (myself being also guilty) an outlet to hash this out.
Ok. With that out of the way, here's what we're doing about disc images in the near future:
One of our US servers with big storage space is going offline soon. I'm not ready to replace it yet, so it's likely some of our services will require the use of mirrors (
ftp.irixnet.org being the big one) for the foreseeable future once it shuts off. Once we've got something to replace it, I will bring that back online and start thinking of how to handle adding disc images.
What's current/non-negotiable:
They will either use .img or .efs file extensions. Not .iso or proprietary .mdf/mds or .nrg or whatever. This is because these aren't ISO-9660 or Joliet/Rockridge type images, nor are they UDF or customized ISO FS (as in the case of most video games on CD/DVD) I'm aware some of the more stupid programs on OSes like macOS or Windows won't properly recognize them with that, but that's not a problem I can resolve since we're not the programmer of those programs. You'll need to find workarounds or use a better program.
They will be stored separate from network install files.
They will not be given storage priority (Meaning that space-constrained boxes will not host them)
As for /why/ we've not allocated them in the past, and why we've been resistant to it, here's why:
For much of the earlier history, I couldn't afford massive servers with terabytes of disc space. In my experience, deduplication doesn't work on efs images properly. I don't know why, but it's probably to do with how block-level deduplication works and needs to be explained by someone smarter than me. In any case, when I experimented with it at length, it simply straight up didn't work, and the dedup percentage for ZFS plummeted. That meant I simply had less storage density out of them.
Additionally, you cannot mount/use EFS images on IRIX. No loopback FS. No burning capability out of the box. No efs2tar type program. It means you can't use them on the OS that it's designed for, so I elected for tarballs.
Tarballs are easier to use for network installs, and efs2tar only works on WSL, macOS and GNU/Linux, not on any other OS including vanilla Windows or the BSDs or whatever. That makes it harder than you think for interoperability reasons.
We've had jrra.zone and other sources as well, covering what we couldn't, so there was outlets.
Some people are OK with anarchy/disorganized/not properly named sources or without interop guidelines. I try to keep things a bit more orderly and high quality. It doesn't please everyone, and I get that, but it's the majority that counts there.
Anyways, let's hash it out. If you're frustrated with my approach, tell me.
I'm the system admin of this site. Private security technician, licensed locksmith, hack of a c developer and vintage computer enthusiast.
https://contrib.irixnet.org/raion/ -- contributions and pieces that I'm working on currently.
https://codeberg.org/SolusRaion -- Code repos I control
Technical problems should be sent my way.