If I’m using Arch or another minimal distro, is it a good idea to install a syslog daemon? Or can I go without?
You dont need syslog. Journald is good enough for most systems.
What if I’m on another minimal distro, like Artix, that doesn’t use systemd? Journald is a systemd thing, and I’m not going to install systemd on top of a perfectly good init system.
Whatever floats your boat, but if something goes wrong you don’t really have anything to figure out what’s going on.
If you’re on arch you use redhat’s garbage. On non-corpo linux syslog can be disabled if you want, though I’d prefer to just symlink/mount /var/log to a memory filesystem instead.
On non-corpo linux syslog can be disabled
systemctl disable --now systemd-journald
I’d prefer to just symlink/mount /var/log to a memory filesystem instead
Set Storage=volatile in /etc/systemd/journald.conf
Like how you cropped my message to make it seem like I was implying you couldn’t disable logging on systemd
Then what’s the meaning of this whole part?
On non-corpo linux syslog can be disabled if you want, though I’d prefer to just symlink/mount /var/log to a memory filesystem instead.
Is it just a random tidbit that could be replaced with a blueberry muffin recipe without any change of meaning of the whole comment? Because it sure won’t help OP at all with their Arch-specific question, so it’s either that, or it provides contrast to the “corpo Linux”, which is how I interpreted it.
And here’s the remaining part of your comment I left out, just to make sure people won’t lose the context between two three sentence long comments (for those without any attention span, it comes before the previous quoted part):
If you’re on arch you use redhat’s garbage.
It’s often more useful for minimal installations to keep the system log daemon running so that you can see when things happen and stop them from happening.
Especially now that even very low power embedded systems run multiple cpu cores at multi-ghz clocks, interface with gigabytes of memory, hundreds of gigabytes of attached storage and communicate through multi-gigabit network links, lots of stuff can be happening that is unwanted or simply unnecessary without any external indications.
What are you trying to accomplish by not running a syslog daemon?
Not really trying to accomplish much, just trying to save a few seconds in the manual installation process.
If it’s a race from boot to login prompt then making sure the installer never has to dial out and retrieve packages would be a bigger savings. Making sure the installer is on the fastest bus possible would be huge too. I think one nvme installing to another one would be fastest (assuming enough lanes).
Don’t take the wheelie bars off your dragster to save weight, wheelies are slow.
It’s not necessary, but a good thing to have if something goes wrong and you want to debug/monitor something. It’s really up to you and your needs.
