Changeset 688a8f5
- Timestamp:
- 12/25/2022 02:07:00 PM (16 months ago)
- Branches:
- xry111/arm64, xry111/arm64-12.0
- Children:
- 0cbb853
- Parents:
- ed7a3952 (diff), fb3f5d7 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the(diff)
links above to see all the changes relative to each parent. - Files:
-
- 17 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter01/changelog.xml
red7a3952 r688a8f5 54 54 <listitem> 55 55 <para>[bdubbs] - Update to vim-9.0.1060. Addresses 56 <ulink url="&lfs-ticket-root; 5006">#5006</ulink>.</para>56 <ulink url="&lfs-ticket-root;4500">#4500</ulink>.</para> 57 57 </listitem> 58 58 <listitem> -
chapter07/kernfs.xml
red7a3952 r688a8f5 15 15 </indexterm> 16 16 17 <para>Applications running in user 17 <para>Applications running in userspace utilize various file 18 18 systems created by the kernel to communicate 19 19 with the kernel itself. These file systems are virtual: no disk -
chapter08/aboutdebug.xml
red7a3952 r688a8f5 18 18 the names of the routines and variables.</para> 19 19 20 <para> However, the inclusion of these debugging symbols enlarges a21 program or library significantly. The following is an exampleof the20 <para>The inclusion of these debugging symbols enlarges a 21 program or library significantly. Here are two examples of the 22 22 amount of space these symbols occupy:</para> 23 23 … … 29 29 <listitem> 30 30 <para>A <command>bash</command> binary without debugging symbols: 31 480 KB </para>31 480 KB (60% smaller)</para> 32 32 </listitem> 33 33 <listitem> … … 37 37 </listitem> 38 38 <listitem> 39 <para>Glibc and GCC files without debugging symbols: 16 MB </para>39 <para>Glibc and GCC files without debugging symbols: 16 MB (82% smaller)</para> 40 40 </listitem> 41 41 </itemizedlist> 42 42 43 <para>Sizes may vary depending on which compiler and C library were used, 44 but when comparing programs with and without debugging symbols, the 45 difference will usually be a factor between two and five.</para> 46 47 <para>Because most users will never use a debugger on their system software, 43 <para>Sizes will vary depending on which compiler and C library were used, 44 but a program that has been stripped of debugging symbols is usually some 45 50% to 80% smaller than its unstripped counterpart. 46 Because most users will never use a debugger on their system software, 48 47 a lot of disk space can be regained by removing these symbols. The next 49 48 section shows how to strip all debugging symbols from the programs and -
chapter08/cleanup.xml
red7a3952 r688a8f5 11 11 <title>Cleaning Up</title> 12 12 13 <para>Finally, clean up some extra files left aroundfrom running tests:</para>13 <para>Finally, clean up some extra files left over from running tests:</para> 14 14 15 15 <screen><userinput>rm -rf /tmp/*</userinput></screen> 16 16 17 <para>There are also several files in stalled inthe /usr/lib and /usr/libexec17 <para>There are also several files in the /usr/lib and /usr/libexec 18 18 directories with a file name extension of .la. These are "libtool archive" 19 files. As already said, on a modern Linux system the libtool .la files are19 files. On a modern Linux system the libtool .la files are 20 20 only useful for libltdl. No libraries in LFS are expected to be loaded 21 by libltdl, and it's known that some .la files can cause BLFS packages22 fail to build. Remove those files now:</para>21 by libltdl, and it's known that some .la files can break BLFS package 22 builds. Remove those files now:</para> 23 23 24 24 <screen><userinput>find /usr/lib /usr/libexec -name \*.la -delete</userinput></screen> -
chapter08/e2fsprogs.xml
red7a3952 r688a8f5 24 24 <title/> 25 25 26 <para>The e2fsprogs package contains the utilities for handling the26 <para>The E2fsprogs package contains the utilities for handling the 27 27 <systemitem class="filesystem">ext2</systemitem> file system. It also 28 28 supports the <systemitem class="filesystem">ext3</systemitem> and … … 45 45 <title>Installation of E2fsprogs</title> 46 46 47 <para>The e2fsprogs documentation recommends that the package be built in47 <para>The E2fsprogs documentation recommends that the package be built in 48 48 a subdirectory of the source tree: </para> 49 49 … … 51 51 cd build</userinput></screen> 52 52 53 <para>Prepare e2fsprogs for compilation:</para>53 <para>Prepare E2fsprogs for compilation:</para> 54 54 55 55 <screen><userinput remap="configure">../configure --prefix=/usr \ … … 75 75 <term><parameter>--disable-*</parameter></term> 76 76 <listitem> 77 <para>Th is prevents e2fsprogs frombuilding and installing the77 <para>These prevent building and installing the 78 78 <systemitem class="library">libuuid</systemitem> and 79 79 <systemitem class="library">libblkid</systemitem> libraries, the 80 80 <systemitem class="daemon">uuidd</systemitem> daemon, and the 81 <command>fsck</command> wrapper , asutil-linux installs more81 <command>fsck</command> wrapper; util-linux installs more 82 82 recent versions.</para> 83 83 </listitem> … … 176 176 <term><command>chattr</command></term> 177 177 <listitem> 178 <para>Changes the attributes of files on an <systemitem 179 class="filesystem">ext2</systemitem> file system; it also 180 changes <systemitem class="filesystem">ext3</systemitem> 181 file systems, the journaling version of <systemitem 182 class="filesystem">ext2</systemitem> file systems</para> 178 <para>Changes the attributes of files on <systemitem 179 class="filesystem">ext{234}</systemitem> file systems</para> 183 180 <indexterm zone="ch-system-e2fsprogs chattr"> 184 181 <primary sortas="b-chattr">chattr</primary> … … 203 200 <listitem> 204 201 <para>A file system debugger; it can be used to examine and change 205 the state of an <systemitem class="filesystem">ext2</systemitem>206 file system </para>202 the state of <systemitem class="filesystem">ext{234}</systemitem> 203 file systems</para> 207 204 <indexterm zone="ch-system-e2fsprogs debugfs"> 208 205 <primary sortas="b-debugfs">debugfs</primary> … … 235 232 <term><command>e2fsck</command></term> 236 233 <listitem> 237 <para>Is used to check, and optionally repair <systemitem 238 class="filesystem">ext2</systemitem> file systems and <systemitem 239 class="filesystem">ext3</systemitem> file systems</para> 234 <para>Is used to check and optionally repair <systemitem 235 class="filesystem">ext{234}</systemitem> file systems</para> 240 236 <indexterm zone="ch-system-e2fsprogs e2fsck"> 241 237 <primary sortas="b-e2fsck">e2fsck</primary> … … 248 244 <listitem> 249 245 <para>Is used to save critical <systemitem 250 class="filesystem">ext 2</systemitem> file system data to a file</para>246 class="filesystem">ext{234}</systemitem> file system data to a file</para> 251 247 <indexterm zone="ch-system-e2fsprogs e2image"> 252 248 <primary sortas="b-e2image">e2image</primary> … … 259 255 <listitem> 260 256 <para>Displays or changes the file system label on the <systemitem 261 class="filesystem">ext 2</systemitem> file system presenton a given257 class="filesystem">ext{234}</systemitem> file system on a given 262 258 device</para> 263 259 <indexterm zone="ch-system-e2fsprogs e2label"> … … 270 266 <term><command>e2mmpstatus</command></term> 271 267 <listitem> 272 <para>Checks MMP status of an ext4 filesystem</para> 268 <para>Checks MMP (Multiple Mount Protection) status of an <systemitem 269 class="filesystem">ext4</systemitem> file system</para> 273 270 <indexterm zone="ch-system-e2fsprogs e2mmpstatus"> 274 271 <primary sortas="b-e2mmpstatus">e2mmpstatus</primary> … … 280 277 <term><command>e2scrub</command></term> 281 278 <listitem> 282 <para>Checks the contents of a mounted ext[234] filesystem</para> 279 <para>Checks the contents of a mounted <systemitem 280 class="filesystem">ext{234}</systemitem> file system</para> 283 281 <indexterm zone="ch-system-e2fsprogs e2scrub"> 284 282 <primary sortas="b-e2scrub">e2scrub</primary> … … 290 288 <term><command>e2scrub_all</command></term> 291 289 <listitem> 292 <para>Checks all mounted ext[234] filesystems for errors</para> 290 <para>Checks all mounted <systemitem class="filesystem">ext{234}</systemitem> 291 file systems for errors</para> 293 292 <indexterm zone="ch-system-e2fsprogs e2scrub_all"> 294 293 <primary sortas="b-e2scrub_all">e2scrub_all</primary> … … 300 299 <term><command>e2undo</command></term> 301 300 <listitem> 302 <para>Replays the undo log undo_log for an ext2/ext3/ext4 filesystem 303 found on a device [This can be used to undo a failed operation by an 304 e2fsprogs program.]</para> 301 <para>Replays the undo log for an <systemitem 302 class="filesystem">ext{234}</systemitem> file system 303 found on a device. [This can be used to undo a failed operation by an 304 E2fsprogs program.]</para> 305 305 <indexterm zone="ch-system-e2fsprogs e2undo"> 306 306 <primary sortas="b-e2undo">e2undo</primary> … … 312 312 <term><command>e4crypt</command></term> 313 313 <listitem> 314 <para>Ext4 filesystem encryption utility</para> 314 <para><systemitem class="filesystem">Ext4</systemitem> 315 file system encryption utility</para> 315 316 <indexterm zone="ch-system-e2fsprogs e4crypt"> 316 317 <primary sortas="b-e4crypt">e4crypt</primary> … … 322 323 <term><command>e4defrag</command></term> 323 324 <listitem> 324 <para>Online defragmenter for ext4 filesystems</para> 325 <para>Online defragmenter for <systemitem 326 class="filesystem">ext4</systemitem> file systems</para> 325 327 <indexterm zone="ch-system-e2fsprogs e4defrag"> 326 328 <primary sortas="b-e4defrag">e4defrag</primary> … … 408 410 <term><command>mke2fs</command></term> 409 411 <listitem> 410 <para>Creates an <systemitem class="filesystem">ext2</systemitem> 411 or <systemitem class="filesystem">ext3</systemitem> file system on 412 the given device</para> 412 <para>Creates an <systemitem class="filesystem">ext{234}</systemitem> 413 file system on the given device</para> 413 414 <indexterm zone="ch-system-e2fsprogs mke2fs"> 414 415 <primary sortas="b-mke2fs">mke2fs</primary> … … 453 454 <term><command>mklost+found</command></term> 454 455 <listitem> 455 <para> Used to createa <filename class="directory">lost+found</filename>456 directory on an <systemitem class="filesystem">ext 2</systemitem> file456 <para>Creates a <filename class="directory">lost+found</filename> 457 directory on an <systemitem class="filesystem">ext{234}</systemitem> file 457 458 system; it pre-allocates disk blocks to this directory to lighten the 458 459 task of <command>e2fsck</command></para> … … 466 467 <term><command>resize2fs</command></term> 467 468 <listitem> 468 <para>Can be used to enlarge or shrink an<systemitem469 class="filesystem">ext 2</systemitem> file system</para>469 <para>Can be used to enlarge or shrink <systemitem 470 class="filesystem">ext{234}</systemitem> file systems</para> 470 471 <indexterm zone="ch-system-e2fsprogs resize2fs"> 471 472 <primary sortas="b-resize2fs">resize2fs</primary> … … 477 478 <term><command>tune2fs</command></term> 478 479 <listitem> 479 <para>Adjusts tunable file system parameters on an<systemitem480 class="filesystem">ext 2</systemitem> file system</para>480 <para>Adjusts tunable file system parameters on <systemitem 481 class="filesystem">ext{234}</systemitem> file systems</para> 481 482 <indexterm zone="ch-system-e2fsprogs tune2fs"> 482 483 <primary sortas="b-tune2fs">tune2fs</primary> … … 509 510 <term><filename class="libraryfile">libext2fs</filename></term> 510 511 <listitem> 511 <para>Contains routines to enable user-level programs to manipulate an512 <systemitem class="filesystem">ext 2</systemitem> file system</para>512 <para>Contains routines to enable user-level programs to manipulate 513 <systemitem class="filesystem">ext{234}</systemitem> file systems</para> 513 514 <indexterm zone="ch-system-e2fsprogs libext2fs"> 514 515 <primary sortas="c-libext2fs">libext2fs</primary> -
chapter08/libcap.xml
red7a3952 r688a8f5 24 24 <title/> 25 25 26 <para>The Libcap package implements the user -space interface to the POSIX26 <para>The Libcap package implements the userspace interface to the POSIX 27 27 1003.1e capabilities available in Linux kernels. These capabilities 28 28 partition the all-powerful root privilege into a set of distinct -
chapter08/pkgmgt.xml
red7a3952 r688a8f5 56 56 5.10.17 to 5.10.18 or 5.11.1), nothing else needs to be rebuilt. 57 57 The system will keep working fine thanks to the well-defined interface 58 between the kernel and user 58 between the kernel and userspace. Specifically, Linux API headers 59 59 need not be (and should not be, see the next item) upgraded 60 60 along with the kernel. You will merely need to reboot your system to use the -
chapter08/stripping.xml
red7a3952 r688a8f5 13 13 <para>This section is optional. If the intended user is not a 14 14 programmer and does not plan to do 15 any debugging o n the system software, the systemsize can be decreased16 by about 2 GB by removing the debugging symbols and unneededsymbol table17 entries from binaries and libraries. This causes no inconvenience other18 than not being able to debug the software fully anymore.</para>15 any debugging of the system software, the system's size can be decreased 16 by some 2 GB by removing the debugging symbols, and some unnecessary symbol table 17 entries, from binaries and libraries. This causes no real inconvenience for 18 a typical Linux user.</para> 19 19 20 20 <para>Most people who use the commands mentioned below do not 21 experience any difficulties. However, it is easy to make a typoand22 render the new system unusable , so before running the21 experience any difficulties. However, it is easy to make a mistake and 22 render the new system unusable. So before running the 23 23 <command>strip</command> commands, it is a good idea to make a 24 24 backup of the LFS system in its current state.</para> 25 25 26 <para>A <command>strip</command> command with 26 <para>A <command>strip</command> command with the 27 27 <parameter>--strip-unneeded</parameter> option removes all debug symbols 28 from a binary or library. And, itremoves all symbol table entries not28 from a binary or library. It also removes all symbol table entries not 29 29 needed by the linker (for static libraries) or dynamic linker (for 30 dynamic -linked binaries and shared libraries).</para>30 dynamically linked binaries and shared libraries).</para> 31 31 32 <para>The debugging symbols f or selected libraries are placed33 in separate files. Th is debugging information is needed if running34 regression tests that use<ulink32 <para>The debugging symbols from selected libraries are preserved 33 in separate files. That debugging information is needed to run 34 regression tests with <ulink 35 35 url='&blfs-book;/general/valgrind.html'>valgrind</ulink> or <ulink 36 url='&blfs-book;/general/gdb.html'>gdb</ulink> later in BLFS.36 url='&blfs-book;/general/gdb.html'>gdb</ulink> later, in BLFS. 37 37 </para> 38 38 39 39 <para>Note that <command>strip</command> will overwrite the binary or library 40 40 file it is processing. This can crash the processes using code or data from 41 the file. If the process running <command>strip</command> i tself is42 affected, the binary or library being stripped can be destroyed andcan43 make the system completely unusable. To avoid it, we'llcopy some libraries41 the file. If the process running <command>strip</command> is 42 affected, the binary or library being stripped can be destroyed; this can 43 make the system completely unusable. To avoid this problem we copy some libraries 44 44 and binaries into <filename class="directory">/tmp</filename>, strip them 45 there, and install them backwith the <command>install</command> command.46 Read the related entry in <xref linkend="pkgmgmt-upgrade-issues"/> forthe47 rationale to use the <command>install</command> command here.</para>45 there, then reinstall them with the <command>install</command> command. 46 (The related entry in <xref linkend="pkgmgmt-upgrade-issues"/> gives the 47 rationale for using the <command>install</command> command here.)</para> 48 48 49 49 <note><para>The ELF loader's name is ld-linux-aarch64.so.1 on … … 113 113 </userinput></screen> 114 114 115 <para>A large number of files will be reported as havingtheir file116 format not recognized. These warnings can be safely ignored. They117 indicate that those files are scripts instead ofbinaries.</para>115 <para>A large number of files will be flagged as errors because their file 116 format is not recognized. These warnings can be safely ignored. They 117 indicate that those files are scripts, not binaries.</para> 118 118 119 119 </sect1> -
chapter08/sysklogd.xml
red7a3952 r688a8f5 24 24 <title/> 25 25 26 <para>The sysklogd package contains programs for logging system messages,27 such as those givenby the kernel when unusual things happen.</para>26 <para>The Sysklogd package contains programs for logging system messages, 27 such as those emitted by the kernel when unusual things happen.</para> 28 28 29 29 <segmentedlist> … … 42 42 <title>Installation of Sysklogd</title> 43 43 44 <para>First, fix problems that causes a segmentation fault under45 some conditions in klogdand fix an obsolete program construct:</para>44 <para>First, fix a problem that causes a segmentation fault in klogd 45 under some conditions, and fix an obsolete program construct:</para> 46 46 47 47 <screen><userinput remap="pre">sed -i '/Error loading kernel symbols/{n;n;d}' ksym_mod.c -
chapter08/sysvinit.xml
red7a3952 r688a8f5 116 116 <term><command>fstab-decode</command></term> 117 117 <listitem> 118 <para>Run a command with fstab-encoded arguments</para>118 <para>Runs a command with fstab-encoded arguments</para> 119 119 <indexterm zone="ch-system-sysvinit fstab-decode"> 120 120 <primary sortas="b-fstab-decode">fstab-decode</primary> … … 127 127 <listitem> 128 128 <para>Normally invokes <command>shutdown</command> with the 129 <parameter>-h</parameter> option, except when already in run-level 0,130 thenit tells the kernel to halt the system; it notes in the131 file <filename>/var/log/wtmp</filename> that the system is being132 broughtdown</para>129 <parameter>-h</parameter> option, but when already in run-level 0, 130 it tells the kernel to halt the system; it notes in the 131 file <filename>/var/log/wtmp</filename> that the system is 132 going down</para> 133 133 <indexterm zone="ch-system-sysvinit halt-sysv"> 134 134 <primary sortas="b-halt">halt</primary> … … 141 141 <listitem> 142 142 <para>The first process to be started when the kernel has initialized 143 the hardware whichtakes over the boot process and starts all the144 proces es specified in its configuration file</para>143 the hardware; it takes over the boot process and starts all the 144 processes specified in its configuration file</para> 145 145 <indexterm zone="ch-system-sysvinit init-sysv"> 146 146 <primary sortas="b-init">init</primary> … … 153 153 <listitem> 154 154 <para>Sends a signal to all processes, except the processes in its own 155 session soit will not kill its parent shell</para>155 session; it will not kill its parent shell</para> 156 156 <indexterm zone="ch-system-sysvinit killall5"> 157 157 <primary sortas="b-killall5">killall5</primary> -
chapter08/util-linux.xml
red7a3952 r688a8f5 78 78 79 79 <para>The --disable and --without options prevent warnings about 80 building components that require packages not in LFSor are80 building components that either require packages not in LFS, or are 81 81 inconsistent with programs installed by other packages.</para> 82 82 … … 93 93 module. Building it into the kernel will prevent booting. For complete 94 94 coverage, other BLFS packages must be installed. If desired, this test can 95 be run after rebooting into the completed LFS system and running:</para>95 be run by booting into the completed LFS system and running:</para> 96 96 97 97 <screen role="nodump"><userinput>bash tests/run.sh --srcdir=$PWD --builddir=$PWD</userinput></screen> … … 126 126 chmem, choom, chrt, col, colcrt, colrm, column, ctrlaltdel, delpart, dmesg, 127 127 eject, fallocate, fdisk, fincore, findfs, findmnt, flock, fsck, 128 fsck.cramfs, fsck.minix, fsfreeze, fstrim, getopt, hexdump, hwclock, 129 ionice, ipcmk, ipcrm, ipcs, irqtop, isosize, kill, last, lastb (link to 130 last), ldattach, linux32, linux64, logger, look, losetup, lsblk, lscpu, 131 lsipc, lsirq, lslocks, lslogins, lsmem, lsns, mcookie, mesg, mkfs, mkfs.bfs, mkfs.cramfs, mkfs.minix, mkswap, 128 fsck.cramfs, fsck.minix, fsfreeze, fstrim, getopt, hardlink, hexdump, hwclock, 129 ionice, ipcmk, ipcrm, ipcs, irqtop, isosize, kill, last, 130 lastb (link to last), ldattach, linux32 (link to setarch), linux64 (link to setarch), 131 logger, look, losetup, lsblk, lscpu, lsipc, lsirq, lsfd, lslocks, lslogins, 132 lsmem, lsns, mcookie, mesg, mkfs, mkfs.bfs, mkfs.cramfs, mkfs.minix, mkswap, 132 133 more, mount, mountpoint, namei, nsenter, partx, pivot_root, prlimit, 133 134 readprofile, rename, renice, resizepart, rev, rfkill, rtcwake, script, 134 135 scriptlive, scriptreplay, setarch, setsid, setterm, sfdisk, sulogin, swaplabel, 135 swapoff (link to swapon), swapon, switch_root, taskset, uclampset, ul,136 umount, uname26 , unshare, utmpdump, uuidd, uuidgen, uuidparse, wall, wdctl, whereis,137 w ipefs, and zramctl</seg>136 swapoff, swapon, switch_root, taskset, uclampset, ul, 137 umount, uname26 (link to setarch), unshare, utmpdump, uuidd, uuidgen, uuidparse, 138 wall, wdctl, whereis, wipefs, and zramctl</seg> 138 139 <seg>libblkid.so, libfdisk.so, libmount.so, 139 140 libsmartcols.so, and libuuid.so</seg> … … 198 199 <term><command>blkzone</command></term> 199 200 <listitem> 200 <para> Runs zone command on the given block device</para>201 <para>Is used to manage zoned storage block devices</para> 201 202 <indexterm zone="ch-system-util-linux blkzone"> 202 203 <primary sortas="b-blkzone">blkzone</primary> … … 259 260 <term><command>choom</command></term> 260 261 <listitem> 261 <para>Displays and adjusts OOM-killer score</para> 262 <para>Displays and adjusts OOM-killer scores, used to determine 263 which process to kill first when Linux is Out Of Memory</para> 262 264 <indexterm zone="ch-system-util-linux choom"> 263 265 <primary sortas="b-choom">choom</primary> … … 391 393 <term><command>findfs</command></term> 392 394 <listitem> 393 <para>Finds a file system by label or Universally Unique Identifier395 <para>Finds a file system, either by label or Universally Unique Identifier 394 396 (UUID)</para> 395 397 <indexterm zone="ch-system-util-linux findfs"> … … 403 405 <listitem> 404 406 <para>Is a command line interface to the libmount library 405 for work with mountinfo, fstab and mtab files</para>407 for working with mountinfo, fstab and mtab files</para> 406 408 <indexterm zone="ch-system-util-linux findmnt"> 407 409 <primary sortas="b-findmnt">findmnt</primary> … … 483 485 </listitem> 484 486 </varlistentry> 487 488 <varlistentry id="hardlink"> 489 <term><command>hardlink</command></term> 490 <listitem> 491 <para>Consolidates duplicate files by creating hard links</para> 492 <indexterm zone="ch-system-util-linux hardlink"> 493 <primary sortas="b-hardlink">hardlink</primary> 494 </indexterm> 495 </listitem> 496 </varlistentry> 485 497 486 498 <varlistentry id="hexdump"> 487 499 <term><command>hexdump</command></term> 488 500 <listitem> 489 <para>Dumps the given file in hexadecimal or in another given490 format</para>501 <para>Dumps the given file in hexadecimal, decimal, octal, 502 or ascii</para> 491 503 <indexterm zone="ch-system-util-linux hexdump"> 492 504 <primary sortas="b-hexdump">hexdump</primary> … … 681 693 </listitem> 682 694 </varlistentry> 695 696 <varlistentry id="lsfd"> 697 <term><command>lsfd</command></term> 698 <listitem> 699 <para>Displays information about open files; replaces <command>lsof</command></para> 700 <indexterm zone="ch-system-util-linux lsfd"> 701 <primary sortas="b-lsfd">lsfd</primary> 702 </indexterm> 703 </listitem> 704 </varlistentry> 683 705 684 706 <varlistentry id="lsipc"> … … 852 874 <term><command>namei</command></term> 853 875 <listitem> 854 <para>Shows the symbolic links in the given path names</para>876 <para>Shows the symbolic links in the given paths</para> 855 877 <indexterm zone="ch-system-util-linux namei"> 856 878 <primary sortas="b-namei">namei</primary> … … 894 916 <term><command>prlimit</command></term> 895 917 <listitem> 896 <para>Get and set a process'resource limits</para>918 <para>Gets and sets a process's resource limits</para> 897 919 <indexterm zone="ch-system-util-linux prlimit"> 898 920 <primary sortas="b-prlimit">prlimit</primary> … … 965 987 <term><command>rtcwake</command></term> 966 988 <listitem> 967 <para>Used to enter a system sleep state until specified wakeup989 <para>Used to enter a system sleep state until the specified wakeup 968 990 time</para> 969 991 <indexterm zone="ch-system-util-linux rtcwake"> … … 986 1008 <term><command>scriptlive</command></term> 987 1009 <listitem> 988 <para>Re-run session typescripts using timing information</para>1010 <para>Re-runs session typescripts using timing information</para> 989 1011 <indexterm zone="ch-system-util-linux scriptlive"> 990 1012 <primary sortas="b-scriptlive">scriptlive</primary> … … 1006 1028 <term><command>setarch</command></term> 1007 1029 <listitem> 1008 <para>Changes reported architecture in a new program environment and1030 <para>Changes reported architecture in a new program environment, and 1009 1031 sets personality flags</para> 1010 1032 <indexterm zone="ch-system-util-linux setarch"> … … 1059 1081 <term><command>swaplabel</command></term> 1060 1082 <listitem> 1061 <para> Allows to change swapareaUUID and label</para>1083 <para>Makes changes to the swap area's UUID and label</para> 1062 1084 <indexterm zone="ch-system-util-linux swaplabel"> 1063 1085 <primary sortas="b-swaplabel">swaplabel</primary> … … 1079 1101 <term><command>swapon</command></term> 1080 1102 <listitem> 1081 <para>Enables devices and files for paging and swapping and1103 <para>Enables devices and files for paging and swapping, and 1082 1104 lists the devices and files currently in use</para> 1083 1105 <indexterm zone="ch-system-util-linux swapon"> … … 1100 1122 <term><command>taskset</command></term> 1101 1123 <listitem> 1102 <para>Retrieves or sets a process' CPU affinity</para>1124 <para>Retrieves or sets a process's CPU affinity</para> 1103 1125 <indexterm zone="ch-system-util-linux taskset"> 1104 1126 <primary sortas="b-taskset">taskset</primary> … … 1110 1132 <term><command>uclampset</command></term> 1111 1133 <listitem> 1112 <para>Manipulate the utilization clamping attributes of the1134 <para>Manipulates the utilization clamping attributes of the 1113 1135 system or a process</para> 1114 1136 <indexterm zone="ch-system-util-linux uclampset"> … … 1162 1184 <term><command>utmpdump</command></term> 1163 1185 <listitem> 1164 <para>Displays the content of the given login file in a more1186 <para>Displays the content of the given login file in a 1165 1187 user-friendly format</para> 1166 1188 <indexterm zone="ch-system-util-linux utmpdump"> … … 1184 1206 <term><command>uuidgen</command></term> 1185 1207 <listitem> 1186 <para>Creates new UUIDs. Each new UUID can reasonably be considered1208 <para>Creates new UUIDs. Each new UUID is a random number likely to be 1187 1209 unique among all UUIDs created, on the local system and on other 1188 systems, in the past and in the future</para> 1210 systems, in the past and in the future, with extremely high 1211 probability (~340 trillion trillion trillion unique UUIDs are possible)</para> 1189 1212 <indexterm zone="ch-system-util-linux uuidgen"> 1190 1213 <primary sortas="b-uuidgen">uuidgen</primary> … … 1196 1219 <term><command>uuidparse</command></term> 1197 1220 <listitem> 1198 <para>A nutility to parse unique identifiers</para>1221 <para>A utility to parse unique identifiers</para> 1199 1222 <indexterm zone="ch-system-util-linux uuidparse"> 1200 1223 <primary sortas="b-uuidparse">uuidparse</primary> … … 1228 1251 <listitem> 1229 1252 <para>Reports the location of the binary, source, and man page 1230 f or the given command</para>1253 files for the given command</para> 1231 1254 <indexterm zone="ch-system-util-linux whereis"> 1232 1255 <primary sortas="b-whereis">whereis</primary> -
chapter09/bootscripts.xml
red7a3952 r688a8f5 75 75 <listitem> 76 76 <para>Checks the integrity of the file systems before they are mounted 77 (with the exception of journal and networkbased file systems)</para>77 (with the exception of journaling and network-based file systems)</para> 78 78 <indexterm zone="ch-config-bootscripts checkfs-bootscripts"> 79 79 <primary sortas="d-checkfs">checkfs</primary> … … 174 174 <term><command>mountfs</command></term> 175 175 <listitem> 176 <para>Mounts all file systems, except onesthat are marked177 <emphasis>noauto</emphasis> or are network based</para>176 <para>Mounts all file systems, except those that are marked 177 <emphasis>noauto</emphasis>, or are network based</para> 178 178 <indexterm zone="ch-config-bootscripts mountfs-bootscripts"> 179 179 <primary sortas="d-mountfs">mountfs</primary> … … 209 209 <para>The master run-level control script; it is responsible for 210 210 running all the other bootscripts one-by-one, in a sequence determined 211 by the name of the symbolic links being processed</para>211 by the names of the symbolic links to those other bootscripts</para> 212 212 <indexterm zone="ch-config-bootscripts rc-bootscripts"> 213 213 <primary sortas="d-rc">rc</primary> … … 240 240 <term><command>setclock</command></term> 241 241 <listitem> 242 <para>Resets the kernel clock to local time in casethe hardware clock243 is not set to UTC time</para>242 <para>Resets the system clock to local time if the hardware clock 243 is not set to UTC</para> 244 244 <indexterm zone="ch-config-bootscripts setclock-bootscripts"> 245 245 <primary sortas="d-setclock">setclock</primary> … … 306 306 <listitem> 307 307 <para>Prepares the <filename class="directory">/dev</filename> 308 directory and starts Udev</para>308 directory and starts the udev daemon</para> 309 309 <indexterm zone="ch-config-bootscripts udev-bootscripts"> 310 310 <primary sortas="d-udev">udev</primary> -
chapter09/introduction.xml
red7a3952 r688a8f5 12 12 13 13 <para>Booting a Linux system involves several tasks. The process must 14 mount both virtual and real file systems, initialize devices, activate swap,15 check file systems for integrity, mount an y swap partitions or files, set14 mount both virtual and real file systems, initialize devices, 15 check file systems for integrity, mount and activate any swap partitions or files, set 16 16 the system clock, bring up networking, start any daemons required by the 17 system, and accomplish any other custom tasks needed by the user. This17 system, and accomplish any other custom tasks specified by the user. This 18 18 process must be organized to ensure the tasks are performed in the correct 19 order but, at the same time, be executed as fastas possible.</para>19 order and executed as quickly as possible.</para> 20 20 21 21 <sect2 id='sysv-desc'> … … 24 24 <para>System V is the classic boot process that has been used in Unix and 25 25 Unix-like systems such as Linux since about 1983. It consists of a small 26 program, <command>init</command>, that sets up basic pro grams such as26 program, <command>init</command>, that sets up basic processes such as 27 27 <command>login</command> (via getty) and runs a script. This script, 28 28 usually named <command>rc</command>, controls the execution of a set of … … 32 32 <para>The <command>init</command> program is controlled by the 33 33 <filename>/etc/inittab</filename> file and is organized into run levels that 34 can be run by the user. In LFS, they are used as follows:</para>34 can be chosen by the user. In LFS, they are used as follows:</para> 35 35 36 36 <literallayout>0 — halt … … 71 71 <listitem> 72 72 <para>Serial processing of boot tasks. This is related to the previous 73 point. A delay in any process such as a file system check, will73 point. A delay in any process, such as a file system check, will 74 74 delay the entire boot process.</para> 75 75 </listitem> … … 77 77 <listitem> 78 78 <para>Does not directly support advanced features like 79 control groups (cgroups) ,and per-user fair share scheduling.</para>79 control groups (cgroups) and per-user fair share scheduling.</para> 80 80 </listitem> 81 81 -
chapter09/network.xml
red7a3952 r688a8f5 18 18 <title>Creating Network Interface Configuration Files</title> 19 19 20 <para> Which interfaces are brought up and down by the network script21 usually de pends on the files in <filename22 class="directory">/etc/sysconfig/</filename>. This directory should20 <para>The files in <filename class="directory">/etc/sysconfig/</filename> 21 usually determine which interfaces are brought up and down by the network 22 script. This directory should 23 23 contain a file for each interface to be configured, such as 24 <filename>ifconfig.xyz</filename>, where <quote>xyz</quote> should describe24 <filename>ifconfig.xyz</filename>, where <quote>xyz</quote> describes 25 25 the network card. The interface name (e.g. eth0) is usually appropriate. 26 Inside this file are attributes to thisinterface, such as its IP27 address(es), subnet masks, and so forth. It is necessary that the stem of28 the filename be <emphasis>ifconfig</emphasis>.</para>26 Each file contains the attributes of one interface, such as its IP 27 address(es), subnet masks, and so forth. The stem of 28 the filename must be <emphasis>ifconfig</emphasis>.</para> 29 29 30 30 <note> … … 39 39 configuration of the udev daemon running on the system. The udev 40 40 daemon for LFS (installed in <xref linkend="ch-system-eudev"/>) will 41 not run until the LFS system is booted. So it's unreliable to42 determine the interface names being used in LFS systemby running41 not run until the LFS system is booted. So the interface names 42 in the LFS system cannot always be determined by running 43 43 those commands on the host distro, 44 <emphasis>even thoughin the chroot environment</emphasis>.</para>44 <emphasis>even in the chroot environment</emphasis>.</para> 45 45 </note> 46 46 … … 60 60 EOF</userinput></screen> 61 61 62 <para>The values in italics must be changed in e very file to match63 the proper setup.</para>62 <para>The values in italics must be changed in each file, to set 63 the interfaces up correctly.</para> 64 64 65 65 <para>If the <envar>ONBOOT</envar> variable is set to <quote>yes</quote> the 66 66 System V network script will bring up the Network Interface Card (NIC) during 67 the system boot process. If set to anything b ut <quote>yes</quote>the NIC68 will be ignored by the network script and not be automatically brought up.69 The interfacecan be manually started or stopped with the67 the system boot process. If set to anything besides <quote>yes</quote>, the NIC 68 will be ignored by the network script and will not be started automatically. 69 Interfaces can be manually started or stopped with the 70 70 <command>ifup</command> and <command>ifdown</command> commands.</para> 71 71 … … 85 85 variable entirely.</para> 86 86 87 <para>The <envar>PREFIX</envar> variable contains the number of88 bits used in the subnet. Each octet inan IP address is 8 bits. If the89 subnet's netmask is 255.255.255.0, then it is using the first three octets87 <para>The <envar>PREFIX</envar> variable specifies the number of 88 bits used in the subnet. Each segment of an IP address is 8 bits. If the 89 subnet's netmask is 255.255.255.0, then it is using the first three segments 90 90 (24 bits) to specify the network number. If the netmask is 255.255.255.240, 91 it would beusing the first 28 bits. Prefixes longer than 24 bits are91 the subnet is using the first 28 bits. Prefixes longer than 24 bits are 92 92 commonly used by DSL and cable-based Internet Service Providers (ISPs). 93 93 In this example (PREFIX=24), the netmask is 255.255.255.0. Adjust the … … 140 140 141 141 <sect2 id="ch-config-hostname"> 142 <title>Configuring the system hostname</title>142 <title>Configuring the System Hostname</title> 143 143 144 144 <indexterm zone="ch-config-hostname"> … … 157 157 <para><replaceable><lfs></replaceable> needs to be replaced with the 158 158 name given to the computer. Do not enter the Fully Qualified Domain Name 159 (FQDN) here. That information is putin the159 (FQDN) here. That information goes in the 160 160 <filename>/etc/hosts</filename> file.</para> 161 161 -
chapter09/symlinks.xml
red7a3952 r688a8f5 18 18 data or physical characteristics like the bus, slot, or MAC address. The 19 19 purpose of this naming convention is to ensure that network devices are 20 named consistently and not based on the time the network card was 21 discovered. For example, on a computer having two network cards made by 22 Intel and Realtek, the network card manufactured by Intel may become eth0 23 and the Realtek card becomes eth1. In some cases, after a reboot the cards 24 could get renumbered the other way around.</para> 25 26 <para>In the new naming scheme, typical network device names would then 27 be something like enp5s0 or wlp3s0. If this naming convention is not 28 desired, the traditional naming scheme or a custom scheme can be 20 named consistently, not based on when the network card was 21 discovered. In older versions of Linux—on a computer with two 22 network cards made by Intel and Realtek, for instance—the 23 network card manufactured by Intel might have become eth0 24 while the Realtek card became eth1. After a reboot, the cards 25 would sometimes get renumbered the other way around.</para> 26 27 <para>In the new naming scheme, typical network device names are 28 something like enp5s0 or wlp3s0. If this naming convention is not 29 desired, the traditional naming scheme, or a custom scheme, can be 29 30 implemented.</para> 30 31 … … 32 33 <title>Disabling Persistent Naming on the Kernel Command Line</title> 33 34 34 <para>The traditional naming scheme using eth0, eth1, etc can be35 <para>The traditional naming scheme using eth0, eth1, etc. can be 35 36 restored by adding <userinput>net.ifnames=0</userinput> on the 36 kernel command line. This is most appropriate for thosesystems37 that have only one ethernet device of the sametype. Laptops38 often have multiple ethernet connections that arenamed eth0 and39 wlan0 and are also candidates forthis method. The command line40 is passedin the GRUB configuration file.37 kernel command line. This is most appropriate for systems 38 that have just one ethernet device of a particular type. Laptops 39 often have two ethernet connections named eth0 and 40 wlan0; such laptops can also use this method. The command line 41 is in the GRUB configuration file. 41 42 See <xref linkend="grub-cfg"/>.</para> 42 43 </sect3> … … 57 58 <screen role="nodump"><userinput>cat /etc/udev/rules.d/70-persistent-net.rules</userinput></screen> 58 59 59 <note><para>In some cases such as when MAC addresses have been assigned to60 a network card manually or in a virtual environment such as Qemu or Xen,61 the network rules file may not have beengenerated because addresses60 <note><para>In some cases, such as when MAC addresses have been assigned to 61 a network card manually, or in a virtual environment such as Qemu or Xen, 62 the network rules file may not be generated because addresses 62 63 are not consistently assigned. In these cases, this method cannot 63 64 be used.</para></note> 64 65 65 <para>The file begins with a comment block followed by two lines for each66 <para>The file begins with a comment block, followed by two lines for each 66 67 NIC. The first line for each NIC is a commented description showing its 67 68 hardware IDs (e.g. its PCI vendor and device IDs, if it's a PCI card), 68 along with its driver in parentheses, if the driver can be found. Neither69 along with its driver (in parentheses, if the driver can be found). Neither 69 70 the hardware ID nor the driver is used to determine which name to give an 70 71 interface; this information is only for reference. The second line is the 71 72 udev rule that matches this NIC and actually assigns it a name.</para> 72 73 73 <para>All udev rules are made up of several keys, separated by commas and 74 optional whitespace. This rule's keys and an explanation of each of them 75 are as follows:</para> 74 <para>All udev rules are made up of several keywords, separated by commas and 75 optional whitespace. Here are the keywords, and an explanation of each one:</para> 76 76 77 77 <itemizedlist> … … 89 89 ignore VLAN or bridge sub-interfaces (because these sub-interfaces do 90 90 not have drivers). These sub-interfaces are skipped because the name 91 that would be assigned would collide with the irparent devices.</para>92 </listitem> 93 <listitem> 94 <para><literal>ATTR{address}</literal> - The value of this key is the91 that would be assigned would collide with the parent devices.</para> 92 </listitem> 93 <listitem> 94 <para><literal>ATTR{address}</literal> - The value of this keyword is the 95 95 NIC's MAC address.</para> 96 96 </listitem> … … 103 103 </listitem> 104 104 <listitem> 105 <para><literal>NAME</literal> - The value of this key is the name that105 <para><literal>NAME</literal> - The value of this keyword is the name that 106 106 udev will assign to this interface.</para> 107 107 </listitem> … … 111 111 you know which name has been assigned to each of your network cards before 112 112 proceeding, and be sure to use that <literal>NAME</literal> value when 113 creating your configuration files below.</para>113 creating your network configuration files.</para> 114 114 115 115 </sect3> … … 119 119 <sect2 revision="sysv"> 120 120 121 <title>CD-ROM symlinks</title>121 <title>CD-ROM Symlinks</title> 122 122 123 123 <para>Some software that you may want to install later (e.g., various 124 media players) expect the <filename class="symlink">/dev/cdrom</filename>124 media players) expects the <filename class="symlink">/dev/cdrom</filename> 125 125 and <filename class="symlink">/dev/dvd</filename> symlinks to exist, and 126 126 to point to a CD-ROM or DVD-ROM device. Also, it may be convenient to put … … 140 140 on which type of device you have.</para> 141 141 142 <para>There are advantages to each approach; the correct approach to use143 will dependon what kinds of device changes may happen. If you expect the142 <para>There are advantages to each approach; the correct approach 143 depends on what kinds of device changes may happen. If you expect the 144 144 physical path to the device (that is, the ports and/or slots that it plugs 145 145 into) to change, for example because you plan on moving the drive to a 146 146 different IDE port or a different USB connector, then you should use the 147 147 <quote>by-id</quote> mode. On the other hand, if you expect the device's 148 identification to change, for example because it may die, and you would149 replace it with a different device with the same capabilities and which150 is pluggedinto the same connectors, then you should use the148 identification to change, for example because it may die, and you intend 149 to replace it with a different device that 150 plugs into the same connectors, then you should use the 151 151 <quote>by-path</quote> mode.</para> 152 152 … … 199 199 the same device. If you need that, then inspect (and possibly edit) the 200 200 generated <filename>/etc/udev/rules.d/70-persistent-cd.rules</filename> 201 file after booting, to make sure the assigned symlinks match what you need.</para>201 file after booting, to make sure the assigned symlinks match your needs.</para> 202 202 203 203 </sect2> … … 205 205 <sect2> 206 206 207 <title>Dealing with duplicate devices</title>207 <title>Dealing with Duplicate Devices</title> 208 208 209 209 <para>As explained in <xref linkend="ch-config-udev"/>, the order in … … 215 215 after a reboot the order changes. 216 216 For all classes of hardware except sound cards and network cards, this is 217 fixable by creating udev rules for custompersistent symlinks.217 fixable by creating udev rules to create persistent symlinks. 218 218 The case of network cards is covered separately in 219 219 <xref linkend="ch-config-network"/>, and sound card configuration can -
chapter09/udev.xml
red7a3952 r688a8f5 17 17 18 18 <para>In <xref linkend="chapter-building-system"/>, we installed the udev 19 packagewhen <phrase revision="sysv">eudev</phrase>19 daemon when <phrase revision="sysv">eudev</phrase> 20 20 <phrase revision="systemd">systemd</phrase> was built. Before we go into the 21 details regarding how thisworks, a brief history of previous methods of21 details regarding how udev works, a brief history of previous methods of 22 22 handling devices is in order.</para> 23 23 … … 26 26 class="directory">/dev</filename> (sometimes literally thousands of nodes), 27 27 regardless of whether the corresponding hardware devices actually existed. This 28 was typically done via a <command>MAKEDEV</command> script, which contain sa28 was typically done via a <command>MAKEDEV</command> script, which contained a 29 29 number of calls to the <command>mknod</command> program with the relevant 30 30 major and minor device numbers for every possible device that might exist in 31 31 the world.</para> 32 32 33 <para>Using the udev method, only those devices which are detected by the34 kernel get device nodes created for them. Because these device nodes will be35 created each time the system boots , they will be stored on a <systemitem33 <para>Using the udev method, device nodes are only created for those devices 34 which are detected by the kernel. These device nodes are 35 created each time the system boots; they are stored in a <systemitem 36 36 class="filesystem">devtmpfs</systemitem> file system (a virtual file system 37 37 that resides entirely in system memory). Device nodes do not require much … … 52 52 detection, creation, and naming. The latter issue, that of device node 53 53 naming, was perhaps the most critical. It is generally accepted that if 54 device names are allowed to be configurable, thenthe device naming policy55 should be up to a system administrator, not imposed on them by any56 particulardeveloper(s). The <systemitem54 device names are configurable, the device naming policy 55 should be chosen by system administrators, and not imposed on them by the 56 developer(s). The <systemitem 57 57 class="filesystem">devfs</systemitem> file system also suffered from race 58 conditions that were inherent in its design and could not be fixed without a 59 substantial revision to the kernel. It was marked as deprecated for a long 60 period – due to a lack of maintenance – and was finally removed 58 conditions that were inherent in its design; these could not be fixed without a 59 substantial revision of the kernel. <systemitem class="filesystem">devfs</systemitem> 60 was marked as deprecated for a long 61 time, and was finally removed 61 62 from the kernel in June, 2006.</para> 62 63 … … 64 65 as the 2.6 series of stable kernels, a new virtual filesystem called 65 66 <systemitem class="filesystem">sysfs</systemitem> came to be. The job of 66 <systemitem class="filesystem">sysfs</systemitem> is to export a view of67 <systemitem class="filesystem">sysfs</systemitem> is to provide information about 67 68 the system's hardware configuration to userspace processes. With this 68 userspace-visible representation, the possibility of developing a userspace 69 replacement for <systemitem class="filesystem">devfs</systemitem> became 70 much more realistic.</para> 69 userspace-visible representation, it became possible to develop a userspace 70 replacement for <systemitem class="filesystem">devfs</systemitem>.</para> 71 71 72 72 </sect2> … … 82 82 class="filesystem">sysfs</systemitem> knows about the devices present on 83 83 a system and what device numbers should be used for them. Drivers that 84 have been compiled into the kernel directly register their objects with a84 have been compiled into the kernel register their objects in 85 85 <systemitem class="filesystem">sysfs</systemitem> (devtmpfs internally) 86 as they are detected by the kernel. For drivers compiled as modules, this 87 registration will happen when the module is loaded. Once the <systemitem 88 class="filesystem">sysfs</systemitem> filesystem is mounted (on /sys), 89 data which the drivers register with <systemitem 86 as they are detected by the kernel. For drivers compiled as modules, 87 registration happens when the module is loaded. Once the <systemitem 88 class="filesystem">sysfs</systemitem> filesystem is mounted (on 89 <filename class="directory">/sys</filename>), 90 data which the drivers have registered with <systemitem 90 91 class="filesystem">sysfs</systemitem> are available to userspace 91 92 processes and to udevd for processing (including modifications to device … … 97 98 <title>Device Node Creation</title> 98 99 99 <para>Device files are created by the kernel bythe <systemitem100 class="filesystem">devtmpfs</systemitem> file system. Any driver that101 wishes to register a device node will go throughthe <systemitem100 <para>Device files are created by the kernel in the <systemitem 101 class="filesystem">devtmpfs</systemitem> file system. Any driver that 102 wishes to register a device node will use the <systemitem 102 103 class="filesystem">devtmpfs</systemitem> (via the driver core) to do it. 103 104 When a <systemitem class="filesystem">devtmpfs</systemitem> instance is 104 105 mounted on <filename class="directory">/dev</filename>, the device node 105 will initially be createdwith a fixed name, permissions, and106 will initially be exposed to userspace with a fixed name, permissions, and 106 107 owner.</para> 107 108 … … 173 174 174 175 <sect3> 175 <title>A kernel module is not loaded automatically</title>176 <title>A Kernel Module Is Not Loaded Automatically</title> 176 177 177 178 <para>Udev will only load a module if it has a bus-specific alias and the … … 207 208 208 209 <sect3> 209 <title>A kernel module is not loaded automatically, and udev is not210 intended to load it</title>210 <title>A Kernel Module Is Not Loaded Automatically, and Udev Is Not 211 Intended to Load It</title> 211 212 212 213 <para>If the <quote>wrapper</quote> module only enhances the … … 237 238 238 239 <sect3> 239 <title>Udev loads some unwanted module</title>240 <title>Udev Loads Some Unwanted Module</title> 240 241 241 242 <para>Either don't build the module, or blacklist it in a … … 251 252 252 253 <sect3> 253 <title>Udev creates a device incorrectly, or makes a wrong symlink</title>254 <title>Udev Creates a Device Incorrectly, or Makes the Wrong Symlink</title> 254 255 255 256 <para>This usually happens if a rule unexpectedly matches a device. For … … 262 263 263 264 <sect3> 264 <title>Udev rule works unreliably</title>265 <title>Udev Rule Works Unreliably</title> 265 266 266 267 <para>This may be another manifestation of the previous problem. If not, … … 276 277 277 278 <sect3> 278 <title>Udev does not create a device</title>279 280 <para>F urther text assumes that the driver is built staticallyinto the281 kernel or already loaded as a module, and that you have already checked282 that udev doesn't createa misnamed device.</para>283 284 <para> Udev has no information needed to create a device node if a kernel285 driver does not export its data to286 <systemitem class="filesystem">sysfs</systemitem>. This is most common279 <title>Udev Does Not Create a Device</title> 280 281 <para>First, be certain that the driver is built into the 282 kernel or already loaded as a module, and that 283 udev isn't creating a misnamed device.</para> 284 285 <para>If a kernel driver does not export its data to 286 <systemitem class="filesystem">sysfs</systemitem>, udev lacks the 287 information needed to create a device node. This is most likely to happen 287 288 with third party drivers from outside the kernel tree. Create a static 288 289 device node in <filename>/usr/lib/udev/devices</filename> with the … … 296 297 297 298 <sect3> 298 <title>Device naming order changes randomly after rebooting</title>299 <title>Device Naming Order Changes Randomly After Rebooting</title> 299 300 300 301 <para>This is due to the fact that udev, by design, handles uevents and -
prologue/why.xml
red7a3952 r688a8f5 329 329 <para>Libcap</para> 330 330 331 <para>This package implements the user -space interfaces to331 <para>This package implements the userspace interfaces to 332 332 the POSIX 1003.1e capabilities available in Linux kernels. 333 333 </para>
Note:
See TracChangeset
for help on using the changeset viewer.