E.g. for quick provisioning of containers or virtual machines, this is also to make sure the required directories always exist. In a normal distribution, /home already exists, so systemd-tmpfiles does nothing, but there are cases where you want to setup a standard directory structure and this is a declarative alternative to scripts with a lot of mkdir, chmod and chown.
The name systemd-tmpfiles is kind of historic at this point, but wasn’t changed due to backwards compatibility and all.
In which store are you looking for it? Willy sells it down at the beach in his cabin
That’s reflected in the linked article:
First, we know the reason a bike will continue on its path isn’t just because of the force of momentum pushing it there. We know that because if you lock a bicycle’s handlebars so that they can’t turn, then the bike falls over, regardless of how fast it’s moving. So part of this riderless bike phenomenon has to do with its self-steering properties.
The search index isn’t managed by you package manager, is it?
OpenPGP is kind of like the opposite of that - it does a lot of things, and none of them particularly well. To quote:
PGP does a mediocre job of signing things, a relatively poor job of encrypting them with passwords, and a pretty bad job of encrypting them with public keys. PGP is not an especially good way to securely transfer a file. It’s a clunky way to sign packages. It’s not great at protecting backups. It’s a downright dangerous way to converse in secure messages.
minisign is more in the UNIX spirit.
There has even been -1% before
If it’s a machine you have control over you can install the terminfo. Or setting the TERM variable to something like xterm-256color when connecting, that usually works, though I haven’t tried with tmux.
kitty is great, for me it’s similar to mpv: it does what it’s supposed to do, no fluff. Just straight up performance.
Also lizard loses to both rock and scissors, so it was completely unviable until the invention of paper, and it’s only balanced when Spock is born.
I thought so too but learned recently that Guix system is nix under the hood, basically translates everything, so it’s more than a conceptual fork though obviously some more work went into it than your average Ubuntu fork.
It uses low-level mechanisms from the Nix package manager, but packages are defined as native Guile modules, using extensions to the Scheme language—which makes it nicely hackable.
Or you can add specialisations, which to be fair might require a reboot (system accounts might change during specialisations switch which will confuse the script trying to reload services for the now non-existent user) but it is how I have multiple DEs installed without their applications flooding the other ones, each with their own login manager (SDDM for plasma, gdm for gnome, greetd for sway).
Very good explanation. It’s an often overlooked property of NixOS and why I often feel like Nix on other systems is an okay way to get packages but you’re missing out on all the good stuff you get through the modules, like losing 95% of what makes the concept good.
I don’t think NixOS is the best possible solution to the problem, but it’s the only original distribution that even tries to tackle it instead of just working around it.
Another aspect I like about Nix compared to what I understand from Ansible (which I used a bit but not much) is that your configuration describes your system without any hidden state. Yes, you only get your dependencies through full evaluation, but what I mean is this: Let’s say you install something on a system, i.e. you add it to your list of packages, which you later remove. To my knowledge, Ansible won’t remove the package if not explicitly asked. However, if you explicitly tell Ansible to not have it installed, what happens if that package is later introduced as a dependency?
Ansible will always operate on a stateful system, which is kind of the combination of what others have already mentioned – it’s (EDIT: it being Nix) idempotent and there’s no hidden state that will break something down the way.
It’s in the release notes, you add a Wayland driver to your prefix via registry entry and then unset DISPLAY before starting wine.
https://gitlab.winehq.org/wine/wine/-/releases/wine-9.0
The Wayland driver is not yet enabled by default. It can be enabled through the HKCU\Software\Wine\Drivers registry key by running:
wine reg.exe add HKCU\Software\Wine\Drivers /v Graphics /d x11,wayland
and then making sure that the DISPLAY environment variable is unset.
Note that the registry entry is per prefix.
I’m on 9.0 staging and can use wine with Wayland, but not everything works, window bars etc look somewhat off and some games don’t start at all, like Stardew Valley. Other games I tried failed to hide the cursor. Others worked just fine.
You can even use cp of I recall correctly, dd allows to tune some parameters but it’s not strictly necessary.
A rather tame and boring release, which is perfectly fine after the bomb that was 9.0
systemd has its own containers, so this is the implementation of that requirement; “virtual machines” might use this exact binary to create home, among other directories like srv and what not. Someone at one point probably said “we always need to create these when spinning up systems, maybe systems can provide a mechanism to do that for us?” and then it was implemented.
systemd-tmpfiles claims the following:
I rather think having a purge command was the issue here, at the very least it should print a big fat warning at what it does, better even list all affected files and directories. There’s no reason a normal user needs this and with the name of the binary, it’s totally misleading, which is an issue in these situations.