- 2 Posts
- 172 Comments
Almost, as I said,
arch-chrootdidn’t exist back then, and while the official method is still manual,archinstallis 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.
Laser@feddit.orgto
Selfhosted@lemmy.world•I made my home lab immutable with Terraform | XDAEnglish
9·2 months agonix
Today is 11827 September 1993
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 -Syuhad 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(oraliasif 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/wwwis 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/wwwwhich 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
Well I sit kind of between these
Like I’m not getting a dedicated router and have no server room in my apartment, and my consumer router only supports two VLANs (main and guest). But I’d say the rest is rather sophisticated with all machines defined in my NixOS config, including automated generation of firewall and reverse proxy rules for which I wrote custom modules.
Media server isn’t super full but connected to jellyseer and the rest of the stack, accessible over TLS (Let’s Encrypt certificates) only, with the option to have users managed via IDM.
However, I only have devices on my network that I somewhat trust, with an Android TV box being the worst offender. The smart TV was never connected to my network.
Would be cool to isolate my work PCs somewhat (I work from home with company provided equipment) but it’s just not worth the trouble in my opinion. Not switching out a low power device that does most for two different devices that both use more power (since you usually need a router and a modem).
I don’t only run a reverse proxy because of having only a single public IPv4 address, but that probably is the best part
In general, I’d say reverse proxies make things somewhat easier to manage, especially when it comes to TLS. No need for every service to integrate it.
Laser@feddit.orgto
Programmer Humor@programming.dev•JPEG XL is Dead. Long Live JPEG XL
171·4 months agoThat would have been a brilliant move with wav vs MP3
Laser@feddit.orgto
Programmer Humor@programming.dev•JPEG XL is Dead. Long Live JPEG XL
591·4 months agoHow would a new format be backwards-compatible? At least JPEG-XL can losslessly compress standard jpg for a bit of space savings, and servers can choose to deliver the decompressed jpg to clients that don’t support JPEG-XL.
Also from Wikipedia:
Computationally efficient encoding and decoding without requiring specialized hardware: JPEG XL is about as fast to encode and decode as old JPEG using libjpeg-turbo
Being a JPEG superset, JXL provides efficient lossless recompression options for images in the traditional/legacy JPEG format that can represent JPEG data in a more space-efficient way (~20% size reduction due to the better entropy coder) and can easily be reversed, e.g. on the fly. Wrapped inside a JPEG XL file/stream, it can be combined with additional elements, e.g. an alpha channel.
That doesn’t help you if you want to get the result of something that happened in the function without capturing stdout, does it?
I didn’t mean that bash has no local variables, but rather that if you want to use a function as such without capturing stdout, you need variables that are scoped across your functions, which is usually global or at least effectively global.


This is what GPT was invented for