3 ms·
Poettering didn't join Microsoft until 2022, systemd has been around since 2010.
by stryan 3y ago
Poettering didn't join Microsoft until 2022, systemd has been around since 2010.
- jmclnx 3y agoTrue, but soon he will be dropping script integration, not that I care, but the coincidence is a interesting. Join M/S, drop shell scripts :)
- op00to 3y agoScript integration is not dropped. You can easily run a script from a unit file.
- bravetraveler 3y agoYea, they're dropping the native generator for /etc/init.d, I believe. Scripts placed here implicitly became systemd services. Nothing of huge value is lost. Distributions play an important part, we shouldn't forget. They can maintain something like this for users, if so inclined. This mostly hurts third party/ancient/naive packages that you probably, eventually, won't want to install on your distribution for other reasons. This won't affect any packages natively provided by your distribution of choice. Think those random RPMs/DEBs you get from an external vendor -- UPS, keyboard, whatever. They've had over a decade to see the writing on the wall, adding ~12 lines to their entire codebase/packaging spec. Probably a net-reduction given the NIH-syndrome of these scripts. Instead, I've seen them make this directory, put their scripts inside, and just expect things to work out. It did, arguably by chance. The compatibility was deliberate, but support isn't forever.
- op00to 3y agoThat’s wild! I too have seen horror I wish I could forget. For those still worried, the pain is limited to about 15 minutes of writing a unit file, testing it, and waiting for ci or builds to finish! I expect to have to do this for older or more esoteric stuff, but I also enjoy writing unit files.