2. Linux From Scratch
3. chapter08_pkgmgt
4. Search

Filters

• Untranslated strings • state:empty
• Unfinished strings • state:<translated
• Translated strings • state:>=translated
• Strings marked for edit • state:needs-editing
• Strings with suggestions • has:suggestion
• Strings with variants • has:variant
• Strings with screenshots • has:screenshot
• Strings with labels • has:label
• Strings with context • has:context
• Unfinished strings without suggestions • state:<translated AND NOT has:suggestion
• Strings with comments • has:comment
• Strings with any failing checks • has:check
• Approved strings • state:approved
• Strings waiting for review • state:translated

state:empty

Position and priority

• Position and priority
• Position
• Priority
• Labels
• Source string
• Target string
• String age
• Last updated
• Number of words
• Number of comments
• Number of failing checks
• Key
• String location

	Translation	Source string	Target string
	Linux From Scratch/chapter08_pkgmgt — Chinese (Simplified Han script)	If the Linux kernel needs to be upgraded (for example, from 5.10.17 to 5.10.18 or 5.11.1), nothing else needs to be rebuilt. The system will keep working fine thanks to the well-defined interface between the kernel and userspace. Specifically, Linux API headers need not be upgraded along with the kernel. You will merely need to reboot your system to use the upgraded kernel.
	Linux From Scratch/chapter08_pkgmgt — Chinese (Simplified Han script)	If Glibc needs to be upgraded to a newer version, (e.g., from Glibc-2.36 to Glibc-&glibc-version;), some extra steps are needed to avoid breaking the system. Read <xref linkend='ch-system-glibc'/> for details.
	Linux From Scratch/chapter08_pkgmgt — Chinese (Simplified Han script)	If a package is (directly or indirectly) linked to both the old and new names of a shared library (for example, the package links to both <filename class='libraryfile'>libfoo.so.2</filename> and <filename class='libraryfile'>libbar.so.1</filename>, while the latter links to <filename class='libraryfile'>libfoo.so.3</filename>), the package may malfunction because the different revisions of the shared library present incompatible definitions for some symbol names. This can be caused by recompiling some, but not all, of the packages linked to the old shared library after the package providing the shared library is upgraded. To avoid the issue, users will need to rebuild every package linked to a shared library with an updated revision (e.g. libfoo.so.2 to libfoo.so.3) as soon as possible.
	Linux From Scratch/chapter08_pkgmgt — Chinese (Simplified Han script)	If a package containing a shared library is updated, and the name of the library doesn't change, but the version number of the library <emphasis role="bold">file</emphasis> decreases (for example, the library is still named <filename class='libraryfile'>libfoo.so.1</filename>, but the name of the library file is changed from <filename class='libraryfile'>libfoo.so.1.25</filename> to <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 (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> version; its version number is larger. This situation may arise if you have to downgrade a package, or if the authors change the versioning scheme for library files.
	Linux From Scratch/chapter08_pkgmgt — Chinese (Simplified Han script)	If a package containing a shared library is updated, and the name of the library doesn't change, but a severe issue (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 complete, will list which processes are using the old versions of those libraries (replace <replaceable>libfoo</replaceable> with the name of the library):
	Linux From Scratch/chapter08_pkgmgt — Chinese (Simplified Han script)	<userinput>grep -l '<replaceable>libfoo</replaceable>.*deleted' /proc/*/maps | tr -cd 0-9\\n | xargs -r ps u</userinput>
	Linux From Scratch/chapter08_pkgmgt — Chinese (Simplified Han script)	If <application>OpenSSH</application> is being used to access the system and it is linked to the updated library, you must restart the <command>sshd</command> service, then logout, login again, and run the preceding command again to confirm that nothing is still using the deleted libraries.
	Linux From Scratch/chapter08_pkgmgt — Chinese (Simplified Han script)	If the <command>systemd</command> daemon (running as PID 1) is linked to the updated library, you can restart it without rebooting by running <command>systemctl daemon-reexec</command> as the <systemitem class='username'>root</systemitem> user.
	Linux From Scratch/chapter08_pkgmgt — Chinese (Simplified Han script)	If an executable program or a shared library is overwritten, the processes using the code or data in that program or library may crash. The correct way to update a program or a shared library without causing the process to crash is to remove it first, then install the new version. The <command>install</command> command provided by <application>coreutils</application> has already implemented this, and most packages use that command to install binary files and libraries. This means that you won't be troubled by this issue most of the time. However, the install process of some packages (notably SpiderMonkey in BLFS) just overwrites the file if it exists; this causes a crash. So it's safer to save your work and close unneeded running processes before updating a package.
	Linux From Scratch/chapter08_pkgmgt — Chinese (Simplified Han script)	This scheme is used by the BLFS book to install some very large packages to make it easier to upgrade them. If you install more than a few packages, this scheme becomes unmanageable. And some packages (for example Linux API headers and Glibc) may not work well with this scheme. <emphasis role='bold'>Never use this scheme system-wide.</emphasis>