• 0 Posts
  • 16 Comments
Joined 1 year ago
cake
Cake day: May 22nd, 2023

help-circle
  • Then those containers or virtual machines should add this or create the home as needed.

    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.

    Having/home listed as a tmp file on regular systems is problematic by the nature of what tmpfiles claims it does.

    systemd-tmpfiles claims the following:

    systemd-tmpfiles creates, deletes, and cleans up files and directories, using the configuration file format and location specified in tmpfiles.d(5). Historically, it was designed to manage volatile and temporary files, as the name suggests, but it provides generic file management functionality and can be used to manage any kind of files.

    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.


  • 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.










  • If you actually try to understand what’s happening, I think it’s one of the best ways to learn how a system is composed, at least if you install manually. What’s a partition, file system, what does mounting do, chroots, you name it.

    I don’t use Arch anymore but still think it’s a great distro to learn the basics while still having the luxury of new binary packages. Manual Arch install abstracts basically nothing away from you, for better or for worse.

    Currently on NixOS, I’d say while its engineering is better overall, the things you learn there are much more distribution-specific or maybe concept-specific and often not applicable to other distributions.

    I guess there are also probably ways to install e.g. Debian manually, I’ve never seen instructions for it though as there was always the focus on the installer, and frankly I’m not a big fan of apt and all. It always seemed to be much more convoluted than pacman plus it does a lot of stuff for you, whether you want it or not was my impression.





  • They aren’t really designed to stop people from breaking in but rather to stop intrusive people that you talk to first before deciding to not let them in. With the chain, you can open the door a bit without allowing the person outside to force himself in without too much force, e.g. by blocking the door with your foot as the door can only be opened fully after closing it.

    Advanced versions exist where if you put strain on the chain (mostly trying to push the door open from the outside) an alarm goes off.