• 0 Posts
  • 124 Comments
Joined 1 year ago
cake
Cake day: June 25th, 2023

help-circle










  • Around 12 years ago, I was able to break Debian or Ubuntu installs on weekly basis due to certain packages being too old, something being missing from repos so being forced to compile stuff manually, dealing with junky 3rd party repos etc. Then after switching, I hardly ever messed anything on Arch while also spending less time tweaking it than I did with Ubuntu. Even if I did break something, it was my fault. And it’s not that I cannot handle Debian-based OS installs if I have to. I think those systems are fine if they work for you by default and stock repos contain everything you need (and it’s usually enough for servers) The problem is, it’s not always like that and you just have to add some custom package (prepared by you or someone else) every once in a while, not necessarily with an official support. This is just plain easier on Arch.








  • Yes, systemd has ability to run user services. For every logged in user there is one daemon socket that user can access to run services without ever rising privileges. They can run in background automatically as soon as you log in (at least one user session must be opened) or alternatively you can enable lingering for your account that assures it’s always up, so your user services can start on boot without you even logging in. It gets units from couple of directories - system packages can install user services in /usr/lib/systemd, custom global user services can go to /usr/local/lib/systemd for any individual user, theres also /etc/systemd and ~/.config/systemd for unit files of particular user.