The PS2 one is pretty much the same, isn’t it? I’ve never used one of those myself though.
The PS2 one is pretty much the same, isn’t it? I’ve never used one of those myself though.
PS3 (that’s the Dualshock iirc?), Steam Controller, and the Wii U Pro Controller (I quite like the two analog sticks at the top). In that order probably.
Wait, 9/11 is still considered an ongoing national emergency? Lmfao
That probably means it was silently cutting off the password until now. Cursed, reminds me of the original unix crypt() which I think did the same.
Eh, that’s not really true. Games from decades ago still have a good chance to play fine on modern Windows because Microsoft cares about backwards compatibility. That’s like one of the main appeals of Win32.
I don’t think there’s a problem with deprecating and removing APIs like Apple does in principle but if you combine non-free/proprietary focused ecosystem with that, like they also do, it’s a software preservation disaster.
I’m talking about the text in the “The problem with async” section in the article you linked in the OP.
Unless you specifically want ebuilds, take a look at nixpkgs dockerTools. It does everything you list here.
https://nixos.org/manual/nixpkgs/stable/#sec-pkgs-dockerTools
Can we stop referring to the “what color is your function” post for languages it doesn’t apply for? Contrary to Javascript (where it does apply), Rust with tokio has adapters for both async -> sync (Runtime::spawn_blocking) and sync -> async (Runtime::block_on). It probably isn’t a good idea to overuse spawn_blocking but calling an async function from a sync one is literally no problem.
It was added in v256, maybe you don’t have that yet
official knife post
My backup service runs pg_dumpall, then borg create, then deletes the dump.
Another tip: take a look at systemd-networkd for managing your network connections! It has builtin support for creating wireguard tunnels and it’s very nice.
OSM data is generally on par or better than Google Maps data. The thing that’s lacking is the search engine.
The Nextcloud Windows client does VFS and there’s an experimental Mac client that does VFS.
NixOS can boot from a file system that only has /nix, since essentially the kernel command line has init=/nix/store/.../init
. Everything else will be created during boot by that if it isn’t already there. So technically you could only mount /nix and you would get a blank system every time you boot (but that wouldn’t be very useful in most cases). Mounting these is done in the initrd.
A lot of people have a setup where only select files are mounted from a persistent partition, such as /var/lib/postgresql, basically anything they want to keep across reboots, so that the rest is discarded when they reboot. This prevents the system from accumulating junk over time, from services you once used to have but no longer have running, and so on. Personally I found it too much of a hassle to keep track of what files I want to keep, so I save the entire /etc and /var. I still keep the tmpfs though because it’s pretty cool.
Yeah. Flakes are essentially three things (or four if you count the new CLI):
That’s it, essentially nothing else changes. It’s just a different entry point to Nix code including NixOS configurations.
Here’s a great article (apparently, I have only skimmed it myself) explaining flakes more in detail: https://jade.fyi/blog/flakes-arent-real/
I have NixOS running on my main desktop with some unusual changes:
True, I think hot reload is the one big thing it’s lacking.
Why not just use RTF documents?