NixOS went from not being visible to… beating Manjaro!

Whatever that’s supposed to tell

This is what GPT was invented for

Almost, as I said, arch-chroot didn’t exist back then, and while the official method is still manual, archinstall is part of the official ISO, while back then, no helper was provided, so you had to do it manually.

archinstall?

Back in my day, we needed to do all of that by hand, and there wasn’t even arch-chroot, no, we had to bind mount dev, proc and and sys manually as well!

Though in fairness, before that, there was the AIF, which I also used, but that doesn’t sound so manly.

Thanks, was wondering

You could also try replacing the steam lib with an emulator like https://mr_goldberg.gitlab.io/goldberg_emulator/

It’s a cool shell, I use it as a daily driver (though I’m keeping a close eye on elvish which syntactically is even further away from classic shell), but the comments read like fish is basically zsh. And while zsh is pretty close to bash, fish isn’t.

Be aware that fish isn’t a POSIX-compatible shell enough, so you have to adjust syntax.

pacman is very fast and handy. The (in)famous pacman -Syu had you system completely up to date in record time.

Sometimes I miss its speed and simplicity

Well, at least for nginx, you can specify the root (or alias if required) directive; to me, it makes very little sense to rely on defaults, you need to specify your servers / virtual hosts anyways, might as well make the configuration more self-documenting…

There’s also https://uapi-group.org/specifications/specs/linux_file_system_hierarchy/ nowadays, which aims to build on the FHS.

Well, /var/www is in fact not part of the FHS, not even optional… it doesn’t exist on my machines either. I think the better choice would be /srv/www which is an example given at https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch03s17.html

Is /var really such a mystery? I always understood it as the non-volatile system directory that can be written into. Like log files, databases, cache etc. /var/tmp it’s somewhat weird because a non-volatile temporary folder for me is just cache, and /var/lib is named somewhat weird because it doesn’t hold what I’d usually call libraries.

Not pictured: /opt, the raccoon

Soon, the kernel will have more NTFS drivers than native filesystems.

No issues here, but I haven’t benchmarked anything and any improvement could be placebo. It’s trivial with flakes

You probably know this, but you can even run the CachyOS kernel on NixOS. Currently doing exactly that

Then why go against the AUR and not the official mirrors? The former isn’t always exactly the epitome of securely packaged trusted applications

Oh, that’s good to know.

I think this is a huge release of just because of accessibility, that’s always been a pain point (read: basically impossible) with LaTeX, I heard ConTeXt is better there but I never got into it. typst on the other hand is very approachable and makes a lot of sense.

While I don’t need accessibility very much nowadays, it’s basically a requirement for usage in the public sector here as PDF/UA. Which I guess is the main motivation.

Looking forward to trying it out when it hits my repositories, which should be soonish.

Another option is docbook, but I never particularly enjoyed working with that…

It’s too funny to me that Arch of all distributions attracts the thigh /Unix socks crowd (for lack of better word). Nothing about Arch stands out for me in that regard, there’s no social statement or anything, and when I was more active in the community, it wasn’t known for that.

I was deep enough into Arch to run my own private repository using aurutils, but no thighs :(