Maybe you want to migrate a PostgreSQL database to a newer version without starting PostgreSQL server.
Maybe you installed OpenSSH but don’t want sshd to run yet, because you haven’t hardened the configs.
Maybe you installed Nginx as a part of a migration from Apache httpd, but httpd is already running.
In addition, Arch hardly configures your system in a custom way, too. When you install a package, most of the time, it responds with “here are the files from the developer that you asked for.”
If you don’t like this philosophy, then your feelings are perfectly valid, and this is a textbook example of why different distributions exist 👍
This is one of the reasons why I am very unsure about the whole archinstall thing. On the one hand, it lowers the barrier of entry for less techy people, which is always good. On the other hand, it allows for installing the OS without ever having to use the archwiki, which leads to people making a blog post like this that could be solved by looking for “bluetooth” in the archwiki and following the instructions. To somebody not familiar with the OS, this makes it seem like arch is much more complicated than it actually is. “To run arch, you have to hope that there is a blog post or youtube video for simple things like bluetooth!”
No, you simply go here: wiki.archlinux.org(Also very useful resource if you are on any other distro btw)
What on Earth for. I don’t think I’ve used it more than a couple of times over the last 5 years, and that was for arcane stuff like enabling rc.local (which is something every user should probably not know about…)
Plex, CUPS (printing services), Minecraft servers, VPN, file sharing, DHCP/DNS/Wifi, bluetooth are some examples of basic level things systemd can help regular users manage.
Add comment