On 02/05/2019 00:30, Tim Tassonis via blfs-dev wrote: > On 5/1/19 10:52 PM, Pierre Labastie via blfs-dev wrote: >> On 01/05/2019 20:38, Tim Tassonis via blfs-dev wrote: >>> On 5/1/19 5:41 PM, Pierre Labastie via blfs-dev wrote: >>>> On 01/05/2019 16:24, Douglas R. Reno via blfs-dev wrote: >>>>> >>>>> On 5/1/19 7:08 AM, Pierre Labastie via blfs-dev wrote: >>>>>> Hi, >>>>>> >>>>>> initd-tools is for managing bootscripts in /etc/rc?.d. Shouldn't it be >>>>>> removed >>>>>> from the systemd book? >>>>>> >>>>>> Pierre >>>>> >>>>> Hi Pierre, >>>>> >>>>> I placed it back in because systemd now supports the execution of SysV >>>>> bootscripts as native units (systemd-sysv-generator I think). I'd be happy >>>>> moving it back to sysv only though if you think that's best. I'm not sure >>>>> how >>>>> the targets and runlevels relate in this case though, I think it might >>>>> only >>>>> read out of /etc/init.d (but I don't have the documentation in front of me >>>>> right now). >>>>> >>>> >>>> Well, I didn't know that systemd could use sysv bootscripts... So my >>>> question >>>> is irrelevant. OTOH, this package needs LSB conform bootscripts, which >>>> ours in >>>> the SysV book are not... >>>> >>>> Pierre >>>> >>> >>> Well, I'm not sure about LSB conformance as such, but they mostly work fine >>> for me. I have stopped creating any rc?.d symlinks and just run >>> >>> >>> install_initd $INIT_SCRIPT >>> >>> to set them and >>> >>> remove_initd $INIT_SCRIPT >>> >>> to remove them. Works fine for me with: apache, exim, ssh, lxdm, samba, >>> slapd, >>> dovecot, nfs-server, nfs-client, atd, crond iptables, etc etc. >>> >>> >>> >>> Where do you get any problems? I'm sure it's easily fixable. >>> >> >> That was a long time ago, I do not remember. Sorry. Hmm, let me try to >> install >> everything in blfs-bootscripts (I'll have to trash the VM afterwards :). >> <long and boring> >> Let us try: >> sudo make $(grep ^install Makefile | cut -d: -f1) >> Hmm, why does it return: >> install -d -m 755 /lib/services >> install -m 754 blfs/services/dhclient /lib/services >> install -m 754 blfs/services/dhcpcd /lib/services >> install -m 754 blfs/services/bridge /lib/services >> install -m 754 blfs/services/ipx /lib/services >> install: cannot stat 'blfs/services/ipx': No such file or directory >> >> Let us comment out the ipx lines in Makefile >> Now: install: cannot stat 'blfs/services/pppoe': No such file or directory >> >> Let's comment out the pppoe lines. Then the heimdal lines. >> </long and boring> >> Now we have everything in init.d... >> Let's try: >> $ sudo remove_initd gpm >> Error: networkmanager dependency $remote_fs does not start in level 2 or >> sysinit >> Failed to verify the required start scripts for level 2 >> Failed to verify start scripts >> >> Here we go. Let's remove level 2 from Default-Start in networkmanager. >> Now acpid gives the same error... >> And a load others. OK, let's remove run level 2 for all of those (and add it >> to Default-Stop). Then I get something I cannot solve: >> Error: networkmanager dependency udev does not stop in level 0 or halt and >> reboot >> Failed to verify the required stop scripts for level 0 >> Failed to verify stop scripts >> >> But udev is supposed to start in mode S, and has not "stop" switch (ie "udev >> stop" returns an error). >> >> If you want to do something... > > > Well, I have not installed all the init scripts in lfs/blfs, but I also came > across some "level 2" problems, that I also solved by removing level 2 from > the scripts, as I never use that level anyway. > > Regarding udev / networkmanager: that works fine with me. the udev script > has: > > > # Provides: udev $time > # Required-Start: > # Should-Start: modules > # Required-Stop: > # Should-Stop: > # Default-Start: S > # Default-Stop: > > and nm has: > > # Provides: networkmanager > # Required-Start: dbus udev > # Required-Stop: dbus > # Default-Start: 3 4 5 > # Default-Stop: 0 1 6 > > > after my edits... > > It originally has: > > # Provides: networkmanager > # Required-Start: $remote_fs dbus udev > # Required-Stop: $remote_fs dbus udev > # Default-Start: 2 3 4 5 > # Default-Stop: 0 1 6 > > > In my scripts, I took out all level 2 references and all $remote_fs stuff, as > I don't have nfs installed on all systems and $remote_fs should really not > be a hard dependency for any package. > > This is not the fault of init-tools, but no service should rely per default > on a running nfs-client service. No idea how that got in. > >
I think it is worth a ticket: we should have consistent bootscripts. ticket #12010 Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
