It's optional for the packages that use it, and they only use it to
provide additional support for profiling.
Sysprof now requires two more packages which are specific to it, so
let's archive it.
It fixes the "Operating System Details" content in appstreamcli sysinfo
output.
Note that the file name is derived from HOME_URL and ID properties from
/etc/os-release, and the HOME_URL property is just added (at LFS
r12.0-44). If HOME_URL is not set, the file should be renamed to
"lfs.xml" and the <id> in the file should be "lfs", instead of
"org.linuxfromscratch.lfs".
We were saying "-jN means using N cores (or N threads)". This is
completely wrong. "-jN" only tells the building system to run N jobs
simultaneously, but each job can start their own subprocesses or threads
and there is no way for the building system to know how many
subprocesses or threads a job will start.
This caused a lot of misunderstandings and encouraged users to wrongly
blame building systems.
Fix the description of -jN, and add how to use cgroup to control the
usage of CPU cores and system RAM.
On a systemd-based system, systemd is the cgroup manager and manually
operating on cgroups may puzzle systemd. So use systemd-run for
creating and setting up cgroup. On a sysv-based system create and set
up the cgroup manually.
- make change from /usr to opt/xorg "nodump"
- make the removal of "-nolisten tcp" "nodump"
- narrow the change from none to on to the "Numlock" line: otehrwise
the comments about this option become incomprehensible:
(e.g. "option can be on, off, or on")
When using "patch -d <dir> -i <path>", the <path> relative to the
directory <dir>, not the directory where the patch command is
run. Using < instead of -i allows to use a path relative to where
the command is run.
The name of the package in the install command was inadvertently
changed to dbusmock. But this name is unknown to the build system,
and should be python-dbusmock (or python_dbusmock).
