Changes in / [688a8f5:ed7a3952]
- Files:
-
- 17 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter01/changelog.xml
r688a8f5 red7a3952 54 54 <listitem> 55 55 <para>[bdubbs] - Update to vim-9.0.1060. Addresses 56 <ulink url="&lfs-ticket-root; 4500">#4500</ulink>.</para>56 <ulink url="&lfs-ticket-root;5006">#5006</ulink>.</para> 57 57 </listitem> 58 58 <listitem> -
chapter07/kernfs.xml
r688a8f5 red7a3952 15 15 </indexterm> 16 16 17 <para>Applications running in user space utilize various file17 <para>Applications running in user space 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
r688a8f5 red7a3952 18 18 the names of the routines and variables.</para> 19 19 20 <para> The inclusion of these debugging symbols enlarges a21 program or library significantly. Here are two examplesof the20 <para>However, the inclusion of these debugging symbols enlarges a 21 program or library significantly. The following is an example 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 (60% smaller)</para>31 480 KB</para> 32 32 </listitem> 33 33 <listitem> … … 37 37 </listitem> 38 38 <listitem> 39 <para>Glibc and GCC files without debugging symbols: 16 MB (82% smaller)</para>39 <para>Glibc and GCC files without debugging symbols: 16 MB</para> 40 40 </listitem> 41 41 </itemizedlist> 42 42 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, 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, 47 48 a lot of disk space can be regained by removing these symbols. The next 48 49 section shows how to strip all debugging symbols from the programs and -
chapter08/cleanup.xml
r688a8f5 red7a3952 11 11 <title>Cleaning Up</title> 12 12 13 <para>Finally, clean up some extra files left overfrom running tests:</para>13 <para>Finally, clean up some extra files left around 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 the /usr/lib and /usr/libexec17 <para>There are also several files installed in the /usr/lib and /usr/libexec 18 18 directories with a file name extension of .la. These are "libtool archive" 19 files. On a modern Linux system the libtool .la files are19 files. As already said, 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 break BLFS package22 builds. Remove those files now:</para>21 by libltdl, and it's known that some .la files can cause BLFS packages 22 fail to build. Remove those files now:</para> 23 23 24 24 <screen><userinput>find /usr/lib /usr/libexec -name \*.la -delete</userinput></screen> -
chapter08/e2fsprogs.xml
r688a8f5 red7a3952 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 ese preventbuilding and installing the77 <para>This prevents e2fsprogs from 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 ;util-linux installs more81 <command>fsck</command> wrapper, as 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 <systemitem 179 class="filesystem">ext{234}</systemitem> file systems</para> 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> 180 183 <indexterm zone="ch-system-e2fsprogs chattr"> 181 184 <primary sortas="b-chattr">chattr</primary> … … 200 203 <listitem> 201 204 <para>A file system debugger; it can be used to examine and change 202 the state of <systemitem class="filesystem">ext{234}</systemitem>203 file system s</para>205 the state of an <systemitem class="filesystem">ext2</systemitem> 206 file system</para> 204 207 <indexterm zone="ch-system-e2fsprogs debugfs"> 205 208 <primary sortas="b-debugfs">debugfs</primary> … … 232 235 <term><command>e2fsck</command></term> 233 236 <listitem> 234 <para>Is used to check and optionally repair <systemitem 235 class="filesystem">ext{234}</systemitem> file systems</para> 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> 236 240 <indexterm zone="ch-system-e2fsprogs e2fsck"> 237 241 <primary sortas="b-e2fsck">e2fsck</primary> … … 244 248 <listitem> 245 249 <para>Is used to save critical <systemitem 246 class="filesystem">ext {234}</systemitem> file system data to a file</para>250 class="filesystem">ext2</systemitem> file system data to a file</para> 247 251 <indexterm zone="ch-system-e2fsprogs e2image"> 248 252 <primary sortas="b-e2image">e2image</primary> … … 255 259 <listitem> 256 260 <para>Displays or changes the file system label on the <systemitem 257 class="filesystem">ext {234}</systemitem> file systemon a given261 class="filesystem">ext2</systemitem> file system present on a given 258 262 device</para> 259 263 <indexterm zone="ch-system-e2fsprogs e2label"> … … 266 270 <term><command>e2mmpstatus</command></term> 267 271 <listitem> 268 <para>Checks MMP (Multiple Mount Protection) status of an <systemitem 269 class="filesystem">ext4</systemitem> file system</para> 272 <para>Checks MMP status of an ext4 filesystem</para> 270 273 <indexterm zone="ch-system-e2fsprogs e2mmpstatus"> 271 274 <primary sortas="b-e2mmpstatus">e2mmpstatus</primary> … … 277 280 <term><command>e2scrub</command></term> 278 281 <listitem> 279 <para>Checks the contents of a mounted <systemitem 280 class="filesystem">ext{234}</systemitem> file system</para> 282 <para>Checks the contents of a mounted ext[234] filesystem</para> 281 283 <indexterm zone="ch-system-e2fsprogs e2scrub"> 282 284 <primary sortas="b-e2scrub">e2scrub</primary> … … 288 290 <term><command>e2scrub_all</command></term> 289 291 <listitem> 290 <para>Checks all mounted <systemitem class="filesystem">ext{234}</systemitem> 291 file systems for errors</para> 292 <para>Checks all mounted ext[234] filesystems for errors</para> 292 293 <indexterm zone="ch-system-e2fsprogs e2scrub_all"> 293 294 <primary sortas="b-e2scrub_all">e2scrub_all</primary> … … 299 300 <term><command>e2undo</command></term> 300 301 <listitem> 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> 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> 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><systemitem class="filesystem">Ext4</systemitem> 315 file system encryption utility</para> 314 <para>Ext4 filesystem encryption utility</para> 316 315 <indexterm zone="ch-system-e2fsprogs e4crypt"> 317 316 <primary sortas="b-e4crypt">e4crypt</primary> … … 323 322 <term><command>e4defrag</command></term> 324 323 <listitem> 325 <para>Online defragmenter for <systemitem 326 class="filesystem">ext4</systemitem> file systems</para> 324 <para>Online defragmenter for ext4 filesystems</para> 327 325 <indexterm zone="ch-system-e2fsprogs e4defrag"> 328 326 <primary sortas="b-e4defrag">e4defrag</primary> … … 410 408 <term><command>mke2fs</command></term> 411 409 <listitem> 412 <para>Creates an <systemitem class="filesystem">ext{234}</systemitem> 413 file system on the given device</para> 410 <para>Creates an <systemitem class="filesystem">ext2</systemitem> 411 or <systemitem class="filesystem">ext3</systemitem> file system on 412 the given device</para> 414 413 <indexterm zone="ch-system-e2fsprogs mke2fs"> 415 414 <primary sortas="b-mke2fs">mke2fs</primary> … … 454 453 <term><command>mklost+found</command></term> 455 454 <listitem> 456 <para> Createsa <filename class="directory">lost+found</filename>457 directory on an <systemitem class="filesystem">ext {234}</systemitem> file455 <para>Used to create a <filename class="directory">lost+found</filename> 456 directory on an <systemitem class="filesystem">ext2</systemitem> file 458 457 system; it pre-allocates disk blocks to this directory to lighten the 459 458 task of <command>e2fsck</command></para> … … 467 466 <term><command>resize2fs</command></term> 468 467 <listitem> 469 <para>Can be used to enlarge or shrink <systemitem470 class="filesystem">ext {234}</systemitem> file systems</para>468 <para>Can be used to enlarge or shrink an <systemitem 469 class="filesystem">ext2</systemitem> file system</para> 471 470 <indexterm zone="ch-system-e2fsprogs resize2fs"> 472 471 <primary sortas="b-resize2fs">resize2fs</primary> … … 478 477 <term><command>tune2fs</command></term> 479 478 <listitem> 480 <para>Adjusts tunable file system parameters on <systemitem481 class="filesystem">ext {234}</systemitem> file systems</para>479 <para>Adjusts tunable file system parameters on an <systemitem 480 class="filesystem">ext2</systemitem> file system</para> 482 481 <indexterm zone="ch-system-e2fsprogs tune2fs"> 483 482 <primary sortas="b-tune2fs">tune2fs</primary> … … 510 509 <term><filename class="libraryfile">libext2fs</filename></term> 511 510 <listitem> 512 <para>Contains routines to enable user-level programs to manipulate 513 <systemitem class="filesystem">ext {234}</systemitem> file systems</para>511 <para>Contains routines to enable user-level programs to manipulate an 512 <systemitem class="filesystem">ext2</systemitem> file system</para> 514 513 <indexterm zone="ch-system-e2fsprogs libext2fs"> 515 514 <primary sortas="c-libext2fs">libext2fs</primary> -
chapter08/libcap.xml
r688a8f5 red7a3952 24 24 <title/> 25 25 26 <para>The Libcap package implements the user space interface to the POSIX26 <para>The Libcap package implements the user-space 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
r688a8f5 red7a3952 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 space. Specifically, Linux API headers58 between the kernel and user space. 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
r688a8f5 red7a3952 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 f the system software, the system'ssize can be decreased16 by some 2 GB by removing the debugging symbols, and some unnecessarysymbol table17 entries , from binaries and libraries. This causes no real inconvenience for18 a typical Linux user.</para>15 any debugging on the system software, the system size can be decreased 16 by about 2 GB by removing the debugging symbols and unneeded symbol table 17 entries from binaries and libraries. This causes no inconvenience other 18 than not being able to debug the software fully anymore.</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 mistakeand22 render the new system unusable . So before running the21 experience any difficulties. However, it is easy to make a typo 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 the26 <para>A <command>strip</command> command with 27 27 <parameter>--strip-unneeded</parameter> option removes all debug symbols 28 from a binary or library. It alsoremoves all symbol table entries not28 from a binary or library. And, it removes all symbol table entries not 29 29 needed by the linker (for static libraries) or dynamic linker (for 30 dynamic allylinked binaries and shared libraries).</para>30 dynamic-linked binaries and shared libraries).</para> 31 31 32 <para>The debugging symbols f rom selected libraries are preserved33 in separate files. Th at debugging information is needed to run34 regression tests with<ulink32 <para>The debugging symbols for selected libraries are placed 33 in separate files. This debugging information is needed if running 34 regression tests that use <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 s42 affected, the binary or library being stripped can be destroyed ; thiscan43 make the system completely unusable. To avoid this problem wecopy some libraries41 the file. If the process running <command>strip</command> itself is 42 affected, the binary or library being stripped can be destroyed and can 43 make the system completely unusable. To avoid it, we'll copy some libraries 44 44 and binaries into <filename class="directory">/tmp</filename>, strip them 45 there, then reinstall themwith the <command>install</command> command.46 (The related entry in <xref linkend="pkgmgmt-upgrade-issues"/> givesthe47 rationale for using the <command>install</command> command here.)</para>45 there, and install them back with the <command>install</command> command. 46 Read the related entry in <xref linkend="pkgmgmt-upgrade-issues"/> for the 47 rationale to use 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 flagged as errors becausetheir file116 format isnot recognized. These warnings can be safely ignored. They117 indicate that those files are scripts , notbinaries.</para>115 <para>A large number of files will be reported as having their file 116 format not recognized. These warnings can be safely ignored. They 117 indicate that those files are scripts instead of binaries.</para> 118 118 119 119 </sect1> -
chapter08/sysklogd.xml
r688a8f5 red7a3952 24 24 <title/> 25 25 26 <para>The Sysklogd package contains programs for logging system messages,27 such as those emittedby the kernel when unusual things happen.</para>26 <para>The sysklogd package contains programs for logging system messages, 27 such as those given 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 a problem that causes a segmentation fault in klogd45 under some conditions,and fix an obsolete program construct:</para>44 <para>First, fix problems that causes a segmentation fault under 45 some conditions in klogd 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
r688a8f5 red7a3952 116 116 <term><command>fstab-decode</command></term> 117 117 <listitem> 118 <para>Run sa command with fstab-encoded arguments</para>118 <para>Run 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, but when already in run-level 0,130 it tells the kernel to halt the system; it notes in the131 file <filename>/var/log/wtmp</filename> that the system is 132 goingdown</para>129 <parameter>-h</parameter> option, except when already in run-level 0, 130 then it tells the kernel to halt the system; it notes in the 131 file <filename>/var/log/wtmp</filename> that the system is being 132 brought 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 ; ittakes over the boot process and starts all the144 proces ses specified in its configuration file</para>143 the hardware which takes over the boot process and starts all the 144 proceses 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 ;it will not kill its parent shell</para>155 session so 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
r688a8f5 red7a3952 78 78 79 79 <para>The --disable and --without options prevent warnings about 80 building components that either require packages not in LFS,or are80 building components that 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 bybooting into the completed LFS system and running:</para>95 be run after rebooting 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, 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, 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, 133 132 more, mount, mountpoint, namei, nsenter, partx, pivot_root, prlimit, 134 133 readprofile, rename, renice, resizepart, rev, rfkill, rtcwake, script, 135 134 scriptlive, scriptreplay, setarch, setsid, setterm, sfdisk, sulogin, swaplabel, 136 swapoff , swapon, switch_root, taskset, uclampset, ul,137 umount, uname26 (link to setarch), unshare, utmpdump, uuidd, uuidgen, uuidparse,138 w all, wdctl, whereis, wipefs, and zramctl</seg>135 swapoff (link to swapon), swapon, switch_root, taskset, uclampset, ul, 136 umount, uname26, unshare, utmpdump, uuidd, uuidgen, uuidparse, wall, wdctl, whereis, 137 wipefs, and zramctl</seg> 139 138 <seg>libblkid.so, libfdisk.so, libmount.so, 140 139 libsmartcols.so, and libuuid.so</seg> … … 199 198 <term><command>blkzone</command></term> 200 199 <listitem> 201 <para> Is used to manage zoned storage block devices</para>200 <para>Runs zone command on the given block device</para> 202 201 <indexterm zone="ch-system-util-linux blkzone"> 203 202 <primary sortas="b-blkzone">blkzone</primary> … … 260 259 <term><command>choom</command></term> 261 260 <listitem> 262 <para>Displays and adjusts OOM-killer scores, used to determine 263 which process to kill first when Linux is Out Of Memory</para> 261 <para>Displays and adjusts OOM-killer score</para> 264 262 <indexterm zone="ch-system-util-linux choom"> 265 263 <primary sortas="b-choom">choom</primary> … … 393 391 <term><command>findfs</command></term> 394 392 <listitem> 395 <para>Finds a file system , eitherby label or Universally Unique Identifier393 <para>Finds a file system by label or Universally Unique Identifier 396 394 (UUID)</para> 397 395 <indexterm zone="ch-system-util-linux findfs"> … … 405 403 <listitem> 406 404 <para>Is a command line interface to the libmount library 407 for work ingwith mountinfo, fstab and mtab files</para>405 for work with mountinfo, fstab and mtab files</para> 408 406 <indexterm zone="ch-system-util-linux findmnt"> 409 407 <primary sortas="b-findmnt">findmnt</primary> … … 485 483 </listitem> 486 484 </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>497 485 498 486 <varlistentry id="hexdump"> 499 487 <term><command>hexdump</command></term> 500 488 <listitem> 501 <para>Dumps the given file in hexadecimal , decimal, octal,502 or ascii</para>489 <para>Dumps the given file in hexadecimal or in another given 490 format</para> 503 491 <indexterm zone="ch-system-util-linux hexdump"> 504 492 <primary sortas="b-hexdump">hexdump</primary> … … 693 681 </listitem> 694 682 </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>705 683 706 684 <varlistentry id="lsipc"> … … 874 852 <term><command>namei</command></term> 875 853 <listitem> 876 <para>Shows the symbolic links in the given path s</para>854 <para>Shows the symbolic links in the given pathnames</para> 877 855 <indexterm zone="ch-system-util-linux namei"> 878 856 <primary sortas="b-namei">namei</primary> … … 916 894 <term><command>prlimit</command></term> 917 895 <listitem> 918 <para>Get s and sets a process'sresource limits</para>896 <para>Get and set a process' resource limits</para> 919 897 <indexterm zone="ch-system-util-linux prlimit"> 920 898 <primary sortas="b-prlimit">prlimit</primary> … … 987 965 <term><command>rtcwake</command></term> 988 966 <listitem> 989 <para>Used to enter a system sleep state until thespecified wakeup967 <para>Used to enter a system sleep state until specified wakeup 990 968 time</para> 991 969 <indexterm zone="ch-system-util-linux rtcwake"> … … 1008 986 <term><command>scriptlive</command></term> 1009 987 <listitem> 1010 <para>Re-run ssession typescripts using timing information</para>988 <para>Re-run session typescripts using timing information</para> 1011 989 <indexterm zone="ch-system-util-linux scriptlive"> 1012 990 <primary sortas="b-scriptlive">scriptlive</primary> … … 1028 1006 <term><command>setarch</command></term> 1029 1007 <listitem> 1030 <para>Changes reported architecture in a new program environment ,and1008 <para>Changes reported architecture in a new program environment and 1031 1009 sets personality flags</para> 1032 1010 <indexterm zone="ch-system-util-linux setarch"> … … 1081 1059 <term><command>swaplabel</command></term> 1082 1060 <listitem> 1083 <para> Makes changes to the swap area'sUUID and label</para>1061 <para>Allows to change swaparea UUID and label</para> 1084 1062 <indexterm zone="ch-system-util-linux swaplabel"> 1085 1063 <primary sortas="b-swaplabel">swaplabel</primary> … … 1101 1079 <term><command>swapon</command></term> 1102 1080 <listitem> 1103 <para>Enables devices and files for paging and swapping ,and1081 <para>Enables devices and files for paging and swapping and 1104 1082 lists the devices and files currently in use</para> 1105 1083 <indexterm zone="ch-system-util-linux swapon"> … … 1122 1100 <term><command>taskset</command></term> 1123 1101 <listitem> 1124 <para>Retrieves or sets a process' sCPU affinity</para>1102 <para>Retrieves or sets a process' CPU affinity</para> 1125 1103 <indexterm zone="ch-system-util-linux taskset"> 1126 1104 <primary sortas="b-taskset">taskset</primary> … … 1132 1110 <term><command>uclampset</command></term> 1133 1111 <listitem> 1134 <para>Manipulate sthe utilization clamping attributes of the1112 <para>Manipulate the utilization clamping attributes of the 1135 1113 system or a process</para> 1136 1114 <indexterm zone="ch-system-util-linux uclampset"> … … 1184 1162 <term><command>utmpdump</command></term> 1185 1163 <listitem> 1186 <para>Displays the content of the given login file in a 1164 <para>Displays the content of the given login file in a more 1187 1165 user-friendly format</para> 1188 1166 <indexterm zone="ch-system-util-linux utmpdump"> … … 1206 1184 <term><command>uuidgen</command></term> 1207 1185 <listitem> 1208 <para>Creates new UUIDs. Each new UUID is a random number likely to be1186 <para>Creates new UUIDs. Each new UUID can reasonably be considered 1209 1187 unique among all UUIDs created, on the local system and on other 1210 systems, in the past and in the future, with extremely high 1211 probability (~340 trillion trillion trillion unique UUIDs are possible)</para> 1188 systems, in the past and in the future</para> 1212 1189 <indexterm zone="ch-system-util-linux uuidgen"> 1213 1190 <primary sortas="b-uuidgen">uuidgen</primary> … … 1219 1196 <term><command>uuidparse</command></term> 1220 1197 <listitem> 1221 <para>A utility to parse unique identifiers</para>1198 <para>An utility to parse unique identifiers</para> 1222 1199 <indexterm zone="ch-system-util-linux uuidparse"> 1223 1200 <primary sortas="b-uuidparse">uuidparse</primary> … … 1251 1228 <listitem> 1252 1229 <para>Reports the location of the binary, source, and man page 1253 f iles for the given command</para>1230 for the given command</para> 1254 1231 <indexterm zone="ch-system-util-linux whereis"> 1255 1232 <primary sortas="b-whereis">whereis</primary> -
chapter09/bootscripts.xml
r688a8f5 red7a3952 75 75 <listitem> 76 76 <para>Checks the integrity of the file systems before they are mounted 77 (with the exception of journal ing and network-based file systems)</para>77 (with the exception of journal 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 thosethat are marked177 <emphasis>noauto</emphasis> ,or are network based</para>176 <para>Mounts all file systems, except ones 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 s of the symbolic links to those other bootscripts</para>211 by the name of the symbolic links being processed</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 system clock to local time ifthe hardware clock243 is not set to UTC </para>242 <para>Resets the kernel clock to local time in case the hardware clock 243 is not set to UTC time</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 the udev daemon</para>308 directory and starts Udev</para> 309 309 <indexterm zone="ch-config-bootscripts udev-bootscripts"> 310 310 <primary sortas="d-udev">udev</primary> -
chapter09/introduction.xml
r688a8f5 red7a3952 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, 15 check file systems for integrity, mount an d activate any swap partitions or files, set14 mount both virtual and real file systems, initialize devices, activate swap, 15 check file systems for integrity, mount 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 specified by the user. This17 system, and accomplish any other custom tasks needed by the user. This 18 18 process must be organized to ensure the tasks are performed in the correct 19 order and executed as quicklyas possible.</para>19 order but, at the same time, be executed as fast 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 cesses such as26 program, <command>init</command>, that sets up basic programs 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 chosen by the user. In LFS, they are used as follows:</para>34 can be run 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
r688a8f5 red7a3952 18 18 <title>Creating Network Interface Configuration Files</title> 19 19 20 <para> The files in <filename class="directory">/etc/sysconfig/</filename>21 usually de termine which interfaces are brought up and down by the network22 script. This directory should20 <para>Which interfaces are brought up and down by the network script 21 usually depends on the files in <filename 22 class="directory">/etc/sysconfig/</filename>. 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> describes24 <filename>ifconfig.xyz</filename>, where <quote>xyz</quote> should describe 25 25 the network card. The interface name (e.g. eth0) is usually appropriate. 26 Each file contains the attributes of oneinterface, such as its IP27 address(es), subnet masks, and so forth. The stem of28 the filename mustbe <emphasis>ifconfig</emphasis>.</para>26 Inside this file are attributes to this interface, such as its IP 27 address(es), subnet masks, and so forth. It is necessary that the stem of 28 the filename 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 the interface names42 in the LFS system cannot always be determinedby running41 not run until the LFS system is booted. So it's unreliable to 42 determine the interface names being used in LFS system by running 43 43 those commands on the host distro, 44 <emphasis>even in the chroot environment</emphasis>.</para>44 <emphasis>even though 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 ach file, to set63 the interfaces up correctly.</para>62 <para>The values in italics must be changed in every file to match 63 the proper setup.</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 esides <quote>yes</quote>,the NIC68 will be ignored by the network script and will not be started automatically.69 Interfacescan be manually started or stopped with the67 the system boot process. If set to anything but <quote>yes</quote> the NIC 68 will be ignored by the network script and not be automatically brought up. 69 The interface 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 specifies the number of88 bits used in the subnet. Each segment ofan IP address is 8 bits. If the89 subnet's netmask is 255.255.255.0, then it is using the first three segments87 <para>The <envar>PREFIX</envar> variable contains the number of 88 bits used in the subnet. Each octet in an IP address is 8 bits. If the 89 subnet's netmask is 255.255.255.0, then it is using the first three octets 90 90 (24 bits) to specify the network number. If the netmask is 255.255.255.240, 91 the subnet isusing the first 28 bits. Prefixes longer than 24 bits are91 it would be 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 goesin the159 (FQDN) here. That information is put in the 160 160 <filename>/etc/hosts</filename> file.</para> 161 161 -
chapter09/symlinks.xml
r688a8f5 red7a3952 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, 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 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 30 29 implemented.</para> 31 30 … … 33 32 <title>Disabling Persistent Naming on the Kernel Command Line</title> 34 33 35 <para>The traditional naming scheme using eth0, eth1, etc .can be34 <para>The traditional naming scheme using eth0, eth1, etc can be 36 35 restored by adding <userinput>net.ifnames=0</userinput> on the 37 kernel command line. This is most appropriate for systems38 that have just one ethernet device of a particulartype. Laptops39 often have two ethernet connectionsnamed eth0 and40 wlan0 ; such laptops can also usethis method. The command line41 is in the GRUB configuration file.36 kernel command line. This is most appropriate for those systems 37 that have only one ethernet device of the same type. Laptops 38 often have multiple ethernet connections that are named eth0 and 39 wlan0 and are also candidates for this method. The command line 40 is passed in the GRUB configuration file. 42 41 See <xref linkend="grub-cfg"/>.</para> 43 42 </sect3> … … 58 57 <screen role="nodump"><userinput>cat /etc/udev/rules.d/70-persistent-net.rules</userinput></screen> 59 58 60 <note><para>In some cases ,such as when MAC addresses have been assigned to61 a network card manually ,or in a virtual environment such as Qemu or Xen,62 the network rules file may not begenerated because addresses59 <note><para>In some cases such as when MAC addresses have been assigned to 60 a network card manually or in a virtual environment such as Qemu or Xen, 61 the network rules file may not have been generated because addresses 63 62 are not consistently assigned. In these cases, this method cannot 64 63 be used.</para></note> 65 64 66 <para>The file begins with a comment block ,followed by two lines for each65 <para>The file begins with a comment block followed by two lines for each 67 66 NIC. The first line for each NIC is a commented description showing its 68 67 hardware IDs (e.g. its PCI vendor and device IDs, if it's a PCI card), 69 along with its driver (in parentheses, if the driver can be found). Neither68 along with its driver in parentheses, if the driver can be found. Neither 70 69 the hardware ID nor the driver is used to determine which name to give an 71 70 interface; this information is only for reference. The second line is the 72 71 udev rule that matches this NIC and actually assigns it a name.</para> 73 72 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> 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> 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 parent devices.</para>92 </listitem> 93 <listitem> 94 <para><literal>ATTR{address}</literal> - The value of this key wordis the91 that would be assigned would collide with their parent devices.</para> 92 </listitem> 93 <listitem> 94 <para><literal>ATTR{address}</literal> - The value of this key 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 wordis the name that105 <para><literal>NAME</literal> - The value of this key 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 network configuration files.</para>113 creating your configuration files below.</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 sthe <filename class="symlink">/dev/cdrom</filename>124 media players) expect 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 143 dependson what kinds of device changes may happen. If you expect the142 <para>There are advantages to each approach; the correct approach to use 143 will depend 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 intend149 to replace it with a different device that150 plugsinto the same connectors, then you should use the148 identification to change, for example because it may die, and you would 149 replace it with a different device with the same capabilities and which 150 is plugged 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 your needs.</para>201 file after booting, to make sure the assigned symlinks match what you need.</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 to createpersistent symlinks.217 fixable by creating udev rules for custom 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
r688a8f5 red7a3952 17 17 18 18 <para>In <xref linkend="chapter-building-system"/>, we installed the udev 19 daemonwhen <phrase revision="sysv">eudev</phrase>19 package when <phrase revision="sysv">eudev</phrase> 20 20 <phrase revision="systemd">systemd</phrase> was built. Before we go into the 21 details regarding how udevworks, a brief history of previous methods of21 details regarding how this 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 eda28 was typically done via a <command>MAKEDEV</command> script, which contains 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, device nodes are only created for those devices34 which are detected by the kernel. These device nodes are35 created each time the system boots ; they are stored in a <systemitem33 <para>Using the udev method, only those devices which are detected by the 34 kernel get device nodes created for them. Because these device nodes will be 35 created each time the system boots, they will be stored on 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 configurable,the device naming policy55 should be chosen by system administrators, and not imposed on them by the56 developer(s). The <systemitem54 device names are allowed to be configurable, then the device naming policy 55 should be up to a system administrator, not imposed on them by any 56 particular developer(s). The <systemitem 57 57 class="filesystem">devfs</systemitem> file system also suffered from race 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 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 62 61 from the kernel in June, 2006.</para> 63 62 … … 65 64 as the 2.6 series of stable kernels, a new virtual filesystem called 66 65 <systemitem class="filesystem">sysfs</systemitem> came to be. The job of 67 <systemitem class="filesystem">sysfs</systemitem> is to provide information about66 <systemitem class="filesystem">sysfs</systemitem> is to export a view of 68 67 the system's hardware configuration to userspace processes. With this 69 userspace-visible representation, it became possible to develop a userspace 70 replacement for <systemitem class="filesystem">devfs</systemitem>.</para> 68 userspace-visible representation, the possibility of developing a userspace 69 replacement for <systemitem class="filesystem">devfs</systemitem> became 70 much more realistic.</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 register their objects in84 have been compiled into the kernel directly register their objects with a 85 85 <systemitem class="filesystem">sysfs</systemitem> (devtmpfs internally) 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 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 91 90 class="filesystem">sysfs</systemitem> are available to userspace 92 91 processes and to udevd for processing (including modifications to device … … 98 97 <title>Device Node Creation</title> 99 98 100 <para>Device files are created by the kernel inthe <systemitem101 class="filesystem">devtmpfs</systemitem> file 102 wishes to register a device node will usethe <systemitem99 <para>Device files are created by the kernel by the <systemitem 100 class="filesystem">devtmpfs</systemitem> filesystem. Any driver that 101 wishes to register a device node will go through the <systemitem 103 102 class="filesystem">devtmpfs</systemitem> (via the driver core) to do it. 104 103 When a <systemitem class="filesystem">devtmpfs</systemitem> instance is 105 104 mounted on <filename class="directory">/dev</filename>, the device node 106 will initially be exposed to userspacewith a fixed name, permissions, and105 will initially be created with a fixed name, permissions, and 107 106 owner.</para> 108 107 … … 174 173 175 174 <sect3> 176 <title>A Kernel Module Is Not Loaded Automatically</title>175 <title>A kernel module is not loaded automatically</title> 177 176 178 177 <para>Udev will only load a module if it has a bus-specific alias and the … … 208 207 209 208 <sect3> 210 <title>A Kernel Module Is Not Loaded Automatically, and Udev Is Not211 Intended to Load It</title>209 <title>A kernel module is not loaded automatically, and udev is not 210 intended to load it</title> 212 211 213 212 <para>If the <quote>wrapper</quote> module only enhances the … … 238 237 239 238 <sect3> 240 <title>Udev Loads Some Unwanted Module</title>239 <title>Udev loads some unwanted module</title> 241 240 242 241 <para>Either don't build the module, or blacklist it in a … … 252 251 253 252 <sect3> 254 <title>Udev Creates a Device Incorrectly, or Makes the Wrong Symlink</title>253 <title>Udev creates a device incorrectly, or makes a wrong symlink</title> 255 254 256 255 <para>This usually happens if a rule unexpectedly matches a device. For … … 263 262 264 263 <sect3> 265 <title>Udev Rule Works Unreliably</title>264 <title>Udev rule works unreliably</title> 266 265 267 266 <para>This may be another manifestation of the previous problem. If not, … … 277 276 278 277 <sect3> 279 <title>Udev Does Not Create a Device</title>280 281 <para>F irst, be certain that the driver is builtinto the282 kernel or already loaded as a module, and that 283 udev isn't creatinga misnamed device.</para>284 285 <para> If a kernel driver does not export its data to286 <systemitem class="filesystem">sysfs</systemitem>, udev lacks the287 information needed to create a device node. This is most likely to happen278 <title>Udev does not create a device</title> 279 280 <para>Further text assumes that the driver is built statically into the 281 kernel or already loaded as a module, and that you have already checked 282 that udev doesn't create a misnamed device.</para> 283 284 <para>Udev has no information needed to create a device node if a kernel 285 driver does not export its data to 286 <systemitem class="filesystem">sysfs</systemitem>. This is most common 288 287 with third party drivers from outside the kernel tree. Create a static 289 288 device node in <filename>/usr/lib/udev/devices</filename> with the … … 297 296 298 297 <sect3> 299 <title>Device Naming Order Changes Randomly After Rebooting</title>298 <title>Device naming order changes randomly after rebooting</title> 300 299 301 300 <para>This is due to the fact that udev, by design, handles uevents and -
prologue/why.xml
r688a8f5 red7a3952 329 329 <para>Libcap</para> 330 330 331 <para>This package implements the user space interfaces to331 <para>This package implements the user-space 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.