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?
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 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.
Upvoted solely for the last line