Changeset 18b6e01e
- Timestamp:
- 10/26/2001 01:55:47 PM (23 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v3_1, v3_2, v3_3, v4_0, v4_1, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- d9de0f90
- Parents:
- ef94a94
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter01/conventions.xml
ref94a94 r18b6e01e 23 23 24 24 <blockquote><para>This form of text is used for several purposes in the 25 book but mainly to emphasi se important points or to give examples as to25 book but mainly to emphasize important points or to give examples as to 26 26 what to type.</para></blockquote> 27 27 -
chapter05/kernel-exp-headers.xml
ref94a94 r18b6e01e 2 2 <title>Why we copy the kernel headers and don't symlink them</title> 3 3 4 <para>In the past, it was common practi se for people to symlink the4 <para>In the past, it was common practice for people to symlink the 5 5 /usr/include/linux and asm directories to /usr/src/linux/include/linux 6 6 and asm respectively. This is a <emphasis>bad</emphasis> idea as -
chapter06/aboutdebug.xml
ref94a94 r18b6e01e 36 36 37 37 <para>To remove debugging symbols from a binary (must be an a.out or ELF 38 binary) run <userinput>strip --strip-debug filename</userinput>. Wild 38 binary) run <userinput>strip --strip-debug filename</userinput>. Wildcards 39 39 can be used to strip debugging symbols from multiple files (use something 40 40 like <userinput>strip --strip-debug $LFS/usr/bin/*</userinput>).
Note:
See TracChangeset
for help on using the changeset viewer.