On Mon, Nov 04, 2024 at 04:44:43PM +0000, Mark Hindley wrote: > On Mon, Nov 04, 2024 at 02:20:27PM +0000, Athanasius wrote: > > Ergo, there is no way that this if-up.d script, in its current form, > > can ever actually do anything useful when systemd is in use, > > Correct. In fact recent versions of systemd conflict with initscripts so the > package is not even installed on systemd systems anymore. > > > which it always is on modern Debian systems. > > Err, no! Alternative (non-systemd) inits are still available, viable and used > in > all current Debian suites. Consider runit-init, sysvinit and openrc.
Ah, so I was under a misapprehension then. This is probably due to issues in earlier Debian releases (i.e. the issues relating to Gnome3 under Bullseye on https://wiki.debian.org/Init ). It's possible the *actual* issue I'm running into is that the if-up.d script being named `mountnfs` causes a mistaken checking about `init.d/mountnfs.sh` ? It was certainly a surprise to find that an if-up.d script was bailing due to the status of a systemd-ised init.d/ script. Or is it simply that no-one had thought to ensure a systemd-init system had a working method of invoking NFS mounts after ifup brings an interface up ? -- - Athanasius (he/him) = Athanasius(at)miggy.org / https://miggy.org/ GPG/PGP Key: https://miggy.org/gpg-key "And it's me who is my enemy. Me who beats me up. Me who makes the monsters. Me who strips my confidence." Paula Cole - ME
