Funny enough most of the forums of the major distributions are full of people who have issues with systemd.
Maybe there is one new development going on, that you just missed: People want to actually USE their system, not deal with annoying scripts and config files. If a boot manager is not able to bring up a system including nfs-fileshares "out of the box" then it's simply broken. Face it.
To be honest: your communication skills just don't cut it. I'm out of this thread.
btw: Is this the way phoronix wants people to comment here? I'll be back right after improving my abuse-skills.
I see 2 packages: sysvinit and sysvinit-init. Are you saying I only need the second of these?
Will it activate all the init-scripts that were available in my old installation "Pre-Upgrade"?
Can I afterwards uninstall systemd? Or do I still need it?
And will everything that is now started by systemd then be started by sysvinit?
It may be a disappointment for you but I never flame people for not agreeing to my opinion.
I was curious and wanted to see whether you ever provided actual help to anybody in this forum but it seems your main mission is to offend people with rude posts. It's a shame your status here is "Phoronix Member".
My suggestions is to first check if old init scripts are the problem, before completely removing systemd. It's really the better way to boot.
I don't think it will allow you to uninstall systemd as it is a listed package in the base pattern. I had the same problems as you did with an upgrade from 11.4 to 12.1. After a few months of fighting it (and the developers unable to replicate it) I decided to do just a clean install and it fixed itself (kept the home paritions intact). Now I can easily have my NFS servers (v3 and 4) available without the boot process trying to mount before the network is up.
Out of curiosity, if you go into YaST partitioner does it show double entries in the list of nfs mounts?
I never used init-scripts for the nfs-mounts but only configured them via fstab.
So there shouldn't be an issue with initscripts.
I'm still on Grub v1.
No, the partitioner in YAST only shows the nfs-mounts once.
There is a thread in the opensuse forums that indicates that nfs mounts with systemd are not working by default because - according to them - systemd tries to mount fstab entries (including nfs) before network is available...