On Tue, 10 Nov 2020 11:00:39 -0600 Bruce Dubbs via blfs-support <[email protected]> wrote:
> On 11/10/20 7:09 AM, Scott Andrews via blfs-support wrote: > > On Tue, 10 Nov 2020 06:00:54 -0500 > > Scott Andrews via blfs-support > > <[email protected]> wrote: > > > > [putolin] > > > >> man inittab > >> > >> A more elaborate inittab with different runlevels (see the > >> comments inside): > >> > >> # Level to run in > >> id:2:initdefault: > >> > >> # Boot-time system configuration/initialization > >> script. si::sysinit:/etc/init.d/rcS > >> > >> # What to do in single-user mode. > >> ~:S:wait:/sbin/sulogin > >> > >> # /etc/init.d executes the S and K scripts upon > >> change # of runlevel. > >> # > >> # Runlevel 0 is halt. > >> # Runlevel 1 is single-user. > >> # Runlevels 2-5 are multi-user. > >> # Runlevel 6 is reboot. > >> > >> l0:0:wait:/etc/init.d/rc 0 > >> l1:1:wait:/etc/init.d/rc 1 > >> l2:2:wait:/etc/init.d/rc 2 > >> l3:3:wait:/etc/init.d/rc 3 > >> l4:4:wait:/etc/init.d/rc 4 > >> l5:5:wait:/etc/init.d/rc 5 > >> l6:6:wait:/etc/init.d/rc 6 > >> > >> # What to do at the "3 finger salute". > >> ca::ctrlaltdel:/sbin/shutdown -t1 -h now > >> > >> # Runlevel 2,3: getty on virtual consoles > >> # Runlevel 3: getty on terminal (ttyS0) and modem > >> (ttyS1) 1:23:respawn:/sbin/getty tty1 VC linux > >> 2:23:respawn:/sbin/getty tty2 VC linux > >> 3:23:respawn:/sbin/getty tty3 VC linux > >> 4:23:respawn:/sbin/getty tty4 VC linux > > > > Moving init.d from /etc/rc.d/init.d directory to /etc/init.d is > > fully functional after fixing inittab. Changing all the lines in > > the run level paths from /etc/rc.d/init.d/ to /etc/init.d. It just > > works. > > > > As root user > > > > mv /etc/rc.d/init.d /etc > > sed -i 's|/etc/rc.d/init.d/|/etc/init.d|' /etc/inittab > > > > reboot all functional. > > What we have now is fully functional. What you suggest would require > a lot of changes in both LFS and BLFS. Really, the only reason to > use lsb-tools is to support packages that are not already in LFS/BLFS. > > If you want to remove LFS/BLFS symlinks, you can use make > uninstall-<package>. > > -- Bruce > > > > Actually that doesn't work as it also removes the init script and in my opinion you have missed the entire point. The point is to have all the init scripts from all packages installed in the same and consistence manner. BTW when you use lsb-tools to install the symlinks they are not the same as if they were installed by the make install-<package>, lfs-bootscripts included. uninstall: rm -rf ${DESTDIR}/lib/services ${DESTDIR}/lib/lsb ${ETCDIR}/rc.d ${ETCDIR}/init.d \ ${SBIN}/ifup ${SBIN}/ifdown ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ${MAN8}/ifup.8 ${MAN8}/ifdown.8 \ ${ETCDIR}/sysconfig/rc But this does in the spec file.... mv %{buildroot}/etc/rc.d/init.d %{buildroot}/etc/ rm -rf %{buildroot}/etc/rc.d/{rc0.d,rc1.d,rc2.d,rc3.d,rc4.d,rc5.d,rc6.d}' Post='/usr/sbin/install_initd <package>' What I suggest is to use standards. You do go by standards don't you or only when they are convenient? > Really, the only reason to > use lsb-tools is to support packages that are not already in LFS/BLFS. Then it really wasn't needed. A lot of useless work. But then you are anti package manager. Anyway I know you will do what YOU wish and I have fixed lsb-tools to do the correct thing and fixed the sysvinit package as well. No real work was required on my part other than a couple of sed commands. All that LFS needs to do is to remove the symlink installation in lfs-bootscripts and the corresponding blfs tarball. Fix lsb-tools and the inittab. Add the lsb-tool command to install the symlinks and it done. Not hard at all. Now compliant with the man page and LSB specs. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
