Automatic merge of trunk into multilib

This commit is contained in:
Thomas Trepl (Moody) 2022-03-22 05:45:10 +01:00
commit 60093fdb51
3 changed files with 21 additions and 10 deletions

View File

@ -75,15 +75,12 @@
</varlistentry>
<varlistentry>
<!-- To editors: remove it when downstreams are properly
fixed. -->
<!-- To editors: try to remove it once GJS fixed (at GNOME 43) -->
<term><parameter>--disable-exec-static-tramp</parameter></term>
<listitem>
<para>Disable static trampoline support. It's a new security
feature in libffi, but some BLFS packages (notably
<application>GJS</application> and
<application>gobject-introspection</application>) have not been
adapted for it.</para>
<application>GJS</application>) have not been adapted for it.</para>
</listitem>
</varlistentry>

View File

@ -48,7 +48,7 @@
<para>Compile the package:</para>
<screen><userinput remap="make">make</userinput></screen>
<screen><userinput remap="make">make prefix=/usr</userinput></screen>
<note>
<para>In the test output there are several places that

View File

@ -35,12 +35,22 @@
<literallayout>0: halt the computer
1: single-user mode
2: multi-user mode without networking
2: reserved for customization, otherwise does the same as 3
3: multi-user mode with networking
4: reserved for customization, otherwise does the same as 3
5: same as 4, it is usually used for GUI login (like X's <command>xdm</command> or KDE's <command>kdm</command>)
5: same as 4, it is usually used for GUI login (like GNOME's <command>gdm</command> or LXDE's <command>lxdm</command>)
6: reboot the computer</literallayout>
<note>
<para>
Classically, run level 2 above was defined as
"multi-user mode without networking", but this was only the case
many years ago when multiple users could log into a system connected via
serial ports. In today's environment it makes no sense and
we designate it now as "reserved".
</para>
</note>
</sect2>
<sect2 id="conf-sysvinit" role="configuration">
@ -127,7 +137,7 @@ EOF</userinput></screen>
<para>There are a number of directories under <filename
class="directory">/etc/rc.d</filename> that look like <filename
class="directory">rc?.d</filename> (where ? is the number of the run-level) and
<filename class="directory">rcsysinit.d</filename>, all containing a number of
<filename class="directory">rcS.d</filename>, all containing a number of
symbolic links. Some begin with a <emphasis>K</emphasis>, the others begin with
an <emphasis>S</emphasis>, and all of them have two numbers following the
initial letter. The K means to stop (kill) a service and the S means to start a
@ -155,7 +165,11 @@ EOF</userinput></screen>
to be started. They will be called with the parameter
<parameter>stop</parameter> to stop something. The logic behind this
is that when a user is going to reboot or halt the system, nothing
needs to be started. The system only needs to be stopped.</para>
needs to be started, but the order of shutdown needs to be controlled.
For these run levels, all <emphasis>K</emphasis> prefixed scripts will be
run before any <emphasis>S</emphasis> prefixed scripts are run with the
<parameter>stop</parameter> parameter.
</para>
<para>These are descriptions of what the arguments make the scripts
do:</para>