Hi Thorsten, Am Do., 20. Juni 2024 um 08:44 Uhr schrieb Thorsten Kukuk <kukuk@suse.com>:
The main remaining purpose of that is to forward the call to systemctl. That's what I wrote and why the SysV Init code can be removed?
of course. but you were saying "/sbin/service is a complicated shell script". I checked, the "forward call to systemctl" part is about 35 lines of shell. I think we can maintain that. Even for 20 years. no other dependencies other than shell, so it's not bloating the system.
I'm outing myself as an oldschool person here. I love the rcXXX links, and this might be useful for SLE15/Leap 15 users to transition to SLES16/Leap16? We said the same already from SLE12 to SLE15, and if we don't do it now, we will say the same from SLE16 to SLE17.
Well, we haven't committed a "warning, this will go away, use systemctl xxx instead" message. That's what I'd be looking for. You can even do exit 2 if $OPENQA_BE_PEDANTIC is set and we find internal uses of it.
As I wrote: most services have no rc* symlink, so you have to learn the use of systemctl anyways.
On my system about 50% have rc symlinks. but this is not a quantitative experience at all. The ones that I manually restart have rc links. I don't restart the others. rc<tab> gets me 90%+ there of what I want to do every day.
So why think about it every time again, if you can use a rc* symlink or if you need to use systemctl, why not using systemctl always?
It's a lot more typing, old habits die, and it's not about me. I can change. It's about everyone else.
As written: most service files have no rc* symlink, so we cannot speak about a distribution specific standard here.
It is a deprecated standard. I'm not arguing for continuing keeping it around or enforcing it. rpmlint has dropped the warnings that it used to have on this some time ago. I've seen people type rc<tab> and love it. It's a symlink, it costs no maintenance effort, it is not large in size (unlike other stuff that we carry around for compatibility) and we haven't properly informed the users about its removal. no deprecation warning message in sle12 or sle15.
And the documentation needs to be reworked anyways.
I think that'd be a great idea.
what do you like more, a "command not found" or a "hey, going forward please call systemctl foo instead"? That's what I suggested to do?
yeah, remove the sysv code. keep the systemctl forwarding with a "look you're a die hard like dirk is but going forward only systemctl xxx yyy will work" message and I'd be happy about it (add my patreon for donating me a coffee if you find the message useful). I can then tell you how much coffee I've received from our users.
There are several SLES16 feature requests to do it before SLES16, either requesting it direct or implicit. No, they are not from me. And if we don't do it now, we will not do it for SLES17 for the same reasons, too.
I'm all for removing sysv compat. Greetings, Dirk