@ferricoxide @nixCraft No, the big deal that systemd solves is inter-service dependencies. Containers have nothing to do with it.
If you aren't familiar, have a look at sd_notify(3). It allows programs to report current status in a way that will show up in «systemctl status …».
Also, systemd timers are so much nicer than cron, especially being able to decide whether the schedule is in local time or UTC, on a job-by-job basis. And «Persistent=true» means that missed runs can be made up.
@ferricoxide @nixCraft Sys V init was created in the days when, in order to add or remove hardware, you had to reboot. With removable storage and other Thunderbolt things, you need something that can respond to the accessible hardware changing all the time.
Beyond single user mode, I think all of the init states are currently pointless.
@ferricoxide @nixCraft Dad worked for Bell Labs. I've been using UNIX since the ‘70s. 🙂
Yes, systemd is complicated, but it is solving complicated problems.
My decision was easy: most of the organizations willing to pay a comfortable salary are using Red Hat somewhere in their enterprise.
@Ganneff @nixCraft For basic things, sure. Seamless integration in a work environment where the organizational tooling was developed on Windows infrastructure and assumes Windows desktops? Still not quite where it needs to be. Even OSX, which is closer to ready, has some glaring gaps.
Not blaming either Linux or OSX, but it's a realistic problem one needs to contend with if you want to use them as desktops in enterprise organizations.
@nixCraft Compatability.
It continues to get better, but still a challenge. Especially when I need to use certain applications for work.
Hi, There's *finally* a way to run Affinity Photo and Designer on Linux and it's pretty easy actually. Steps: 1. Install Bottles (from https://usebottles.com/ or your appstore) 2. From Settings/Runners, install 'Caffe 7.10' 3. Download the custom recipe file (from Kontik from the Bottles Telegram...