Change nobody/nogroup uid/git to 65534.
Update to meson-0.62.1.
Update to libpipeline-1.5.6.
Update to elfutils-0.187.
Update to Jinja2-3.1.2.
Update to vim-8.2.4814.
Update to sysvinit-3.03.
Update to linux-5.17.5.
Update to gcc-11.3.0.
Update to coreutils-9.1.
Update to bc-5.2.4.
In serveral places we use the pip3 command to install Python 3 programs
and modules for all users as root. This conflicts with the Python
developers' recommendation to build packages in a virtual environment as
a regular user. To this end, a multi-line warning is written when using
pip3 as the root user.
This change shows users how to avoid this warning.
Update to sysvinit-3.02.
Update to zlib-1.2.12.
Update to expat-2.4.8.
Update to Jinja2-3.1.1.
Update to Python-3.10.4.
Update to procps-ng-4.0.0.
Update to iproute2-5.17.0.
Update to meson-0.62.0.
Update to linux-5.17.1.
Update to util-linux-2.38.
Telling the user to override CFLAGS and CXXFLAGS may cause two problems:
1. We've added --with-gcc-arch=native, so the configure script will add
"-march=native" into CFLAGS. Then we've not really verified which
-march= value is the last one in the GCC command line and being really
used.
2. User may just export CFLAGS="-march=x86_64", without "-O2". This
will produce unoptimized binaries.
Otherwise, warnings are issued when changing runlevel. "ip route"
is a good test of whether network is already up. If users want to
change some config, they should use ifup/down, not the network
bootscript.
Now start and reboot should be called as "script start", and they
should be the last in their runlevel. Note that install_initd
needs to be patched for this to work; see
https://github.com/lfs-book/LSB-Tools/pull/12
Presently, there are a lot of special cases:
- runlevel 0 and 6 unconditionally run "script stop" if they
find a Kxxscript symlink. This may lead to trying to stop an
already stopped device if for example switching to runlevel 0/6
from runlevel 1. This can be fixed by stating the convention
that it is the responsability of scripts to check that the service
is running before killing it (or not running before starting it).
Still, we shouldn't try to stop a service if it was marked K in
the previous runlevel. And same for S files: we shouldn't try to
start a service that was marked S in the previous runlevel. Note
that changing runlevel is not a "reset": if a user has manually
changed the state of a daemon, this state will remain the same
upon changing runlevel if the S/K status of that dameon is
the same in both runlevels.
- Sxxscript symlinks in runlevel 0/6 are run as "script stop"
instead of the more intuitive "script start". This does not interact
well with LSB-tools (some scripts would need "Default-Start: S 0 6"
but then it is impossible to get correct "Required-Start" or
"Should-Start" fields). Furthermore, having a counter-intuitive
behavior is error prone. So now runlevel 0/6 will run "script
sart" for a Sxxscript.
