Re: Removing sysV init files
On 15/01/16 21:58, Stefan Lippers-Hollmann wrote:
On 2016-01-15, Alec Leamas wrote:
On 15/01/16 21:06, Michael Biebl wrote:
Am 15.01.2016 um 21:01 schrieb Alec Leamas:
On 15/01/16 19:04, Russ Allbery wrote:
If the names do not match, you can ship a (static) symlink in the
package, say you have
/etc/init.d/foo and /lib/systemd/system/bar.service.
Then ship a symlink like this
/lib/systemd/system/foo.service → /lib/systemd/system/bar.service
It's more complicated. The systemd setup is three different services,
the sysV one. There is no systemd service directly corresponding to
the sysV one. In other words, here is two things taking place at once:
a major upgrade + sysV -> systemd.
No, actually it's not more complicated. There are two options to fix/
Thanks for all replies! I think the conclusion here is clear: the
scripts should be kept, possibly with some minimal updates.