Michal Suchánek wrote:
So while systemd enthusiasts that read everything about systemd from cover to cover and back again may know the casual packager or administrtator who has had systemd shoved down their throat by the committee which decides the default init system of their distro just reads the systemd.service(5), writes a service definition which may even work with some luck, rants how useless maintaining that service is, and moves on. This results in a lots of rants available when you ask WTF you should do to write a service file for this piece of software that has worked flawlessly for 25 years but now cannot be started on your system because it does not have a systemd service file. .... . and those are missing for the systemd man pages. So yes, in this regard systemd brings us once more closer to MS Windows way as you have nicely pointed out ;-)
Michal
im a noob and i know about systemd drop-ins. but i dont blind myself with an attitude of resentment. so lacking clear technical arguments we are now down to a few percevied problems with documentation, mud sliging and childish ranting. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org