gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-06-19 03:39:20 +01:00
Code Issues Packages Projects Releases Wiki Activity

Automatic merge of trunk into multilib

Browse Source
This commit is contained in:
Thomas Trepl (Moody) 2022-10-03 00:30:10 +02:00
commit f3b2f16713
11 changed files with 22 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
bootscripts/lfs/init.d/checkfs
View File

@ -34,7 +34,7 @@
# Default-Start: S
# Default-Stop:
# Short-Description: Checks local filesystems before mounting.
# Description: Checks local filesystmes before mounting.
# Description: Checks local filesystems before mounting.
# X-LFS-Provided-By: LFS
### END INIT INFO

2
bootscripts/lfs/init.d/mountfs
View File

@ -55,7 +55,7 @@ case "${1}" in
stop)
# Don't unmount virtual file systems like /run
log_info_msg "Unmounting all other currently mounted file systems..."
# Ensure any loop devies are removed
# Ensure any loop devices are removed
losetup -D
umount --all --detach-loop --read-only \
--types notmpfs,nosysfs,nodevtmpfs,noproc,nodevpts >/dev/null

2
bootscripts/lfs/init.d/rc
View File

@ -183,7 +183,7 @@ fi
# Start all services marked as S in this runlevel, except if marked as
# S in the previous runlevel
# it is the responsabily of the script to not try to start an already running
# it is the responsibility of the script to not try to start an already running
# service
for i in $( ls -v /etc/rc.d/rc${runlevel}.d/S* 2> /dev/null)
do

2
bootscripts/lfs/init.d/template
View File

@ -45,7 +45,7 @@ case "${1}" in
# if it is possible to use killproc
killproc fully_qualified_path
# if it is not possible to use killproc
# (the daemon shoudn't be stopped by killing it)
# (the daemon shouldn't be stopped by killing it)
if pidofproc daemon_name_as_reported_by_ps >/dev/null; then
command_to_stop_the_service
fi

4
bootscripts/lfs/lib/services/init-functions
View File

@ -155,7 +155,7 @@ start_daemon()
fi
# Return a value ONLY
# It is the init script's (or distribution's functions) responsibilty
# It is the init script's (or distribution's functions) responsibility
# to log messages!
case "${retval}" in
@ -271,7 +271,7 @@ killproc()
fi
# Return a value ONLY
# It is the init script's (or distribution's functions) responsibilty
# It is the init script's (or distribution's functions) responsibility
# to log messages!
case "${retval}" in

2
bootscripts/lfs/sysconfig/createfiles
View File

@ -21,7 +21,7 @@
# dev creates a new device
# <devtype> is either block, char or pipe
# block creates a block device
# char creates a character deivce
# char creates a character device
# pipe creates a pipe, this will ignore the <major> and
# <minor> fields
# <major> and <minor> are the major and minor numbers used for

2
bootscripts/lfs/sysconfig/rc.site
View File

@ -32,7 +32,7 @@
#FAILURE_PREFIX="${FAILURE}*****${NORMAL} "
#WARNING_PREFIX="${WARNING} *** ${NORMAL} "
# Manually seet the right edge of message output (characters)
# Manually set the right edge of message output (characters)
# Useful when resetting console font during boot to override
# automatic screen width detection
#COLUMNS=120

10
chapter03/introduction.xml
View File

@ -104,4 +104,14 @@ popd</userinput></screen>
<para>This check can be used after retrieving the needed files with any of the
methods listed above.</para>
<para>If the packages and patches are downloaded as a non-&root; user,
these files will be owned by the user. The file system records the
owner by its UID, and the UID of a normal user in the host distro is
not assigned in LFS. So the files will be left owned by an unnamed UID
in the final LFS system. If you won't assign the same UID for your user
in the LFS system, change the owners of these files to &root; now to
avoid this issue:</para>
<screen role="nodump"><userinput>chown root:root $LFS/sources/*</userinput></screen>
</sect1>

4
chapter08/pkgmgt.xml
View File

@ -94,7 +94,7 @@
<filename class='libraryfile'>libfoo.so.1.24</filename>),
you should remove the library file from the previously installed version
(<filename class='libraryfile'>libfoo.so.1.25</filename> in this case).
Otherwise, a <command>ldconfig</command> command (invokeed by yourself from the command
Otherwise, a <command>ldconfig</command> command (invoked by yourself from the command
line, or by the installation of some package) will reset the symlink
<filename class='libraryfile'>libfoo.so.1</filename> to point to
the old library file because it seems to be a <quote>newer</quote>
@ -107,7 +107,7 @@
(especially, a security vulnerability) is fixed, all running programs
linked to the shared library should be restarted. The following
command, run as <systemitem class="username">root</systemitem> after
the update is cmplete, will list which processes are using the old versions of those libraries
the update is complete, will list which processes are using the old versions of those libraries
(replace <replaceable>libfoo</replaceable> with the name of the
library):</para>

1
chapter11/reboot.xml
View File

@ -107,6 +107,7 @@
<para>Then unmount the virtual file systems:</para>
<screen><userinput>umount -v $LFS/dev/pts
mountpoint -q $LFS/dev/shm &amp;&amp; umount $LFS/dev/shm
umount -v $LFS/dev
umount -v $LFS/run
umount -v $LFS/proc

2
part3intro/toolchaintechnotes.xml
View File

@ -151,7 +151,7 @@
referred to as the system triplet. Since the vendor field is mostly
irrelevant, autoconf allows to omit it. An astute reader may wonder
why a <quote>triplet</quote> refers to a four component name. The
reason is the kernel field and the os field originiated from one
reason is the kernel field and the os field originated from one
<quote>system</quote> field. Such a three-field form is still valid
today for some systems, for example
<literal>x86_64-unknown-freebsd</literal>. But for other systems,