From efd5d1f3039242ad62214476c986980eb2ea2957 Mon Sep 17 00:00:00 2001 From: DJ Lucas Date: Mon, 30 May 2016 04:37:33 +0000 Subject: [PATCH] Merge symlinks.xml and symlinksd.xml. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@11084 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter07/chapter07.xml | 6 ++-- chapter07/etcshellsd.xml | 48 ------------------------------ chapter07/symlinks.xml | 44 ++-------------------------- chapter07/symlinksd.xml | 63 ---------------------------------------- 4 files changed, 6 insertions(+), 155 deletions(-) delete mode 100644 chapter07/etcshellsd.xml delete mode 100644 chapter07/symlinksd.xml diff --git a/chapter07/chapter07.xml b/chapter07/chapter07.xml index 689e7b982..40a057869 100644 --- a/chapter07/chapter07.xml +++ b/chapter07/chapter07.xml @@ -17,18 +17,18 @@ + + + - - - diff --git a/chapter07/etcshellsd.xml b/chapter07/etcshellsd.xml deleted file mode 100644 index ddccafa9b..000000000 --- a/chapter07/etcshellsd.xml +++ /dev/null @@ -1,48 +0,0 @@ - - - %general-entities; -]> - - - - - - $LastChangedBy$ - $Date$ - - - Creating the /etc/shells File - - - /etc/shells - - - The shells file contains a list of - login shells on the system. Applications use this file to determine - whether a shell is valid. For each shell a single line should be - present, consisting of the shell's path, relative to the root of the - directory structure (/). - - For example, this file is consulted by chsh - to determine whether an unprivileged user may change the login shell for her - own account. If the command name is not listed, the user will be denied of - change. - - It is a requirement for applications such as - GDM which does not populate the - face browser if it can't find /etc/shells, or - FTP daemons which traditionally disallow access to users - with shells not included in this file. - -cat > /etc/shells << "EOF" -# Begin /etc/shells - -/bin/sh -/bin/bash - -# End /etc/shells -EOF - - diff --git a/chapter07/symlinks.xml b/chapter07/symlinks.xml index e80f839dd..f633695aa 100644 --- a/chapter07/symlinks.xml +++ b/chapter07/symlinks.xml @@ -5,12 +5,12 @@ %general-entities; ]> - + Managing Devices - + Network Devices @@ -113,48 +113,10 @@ creating your configuration files below. - - + CD-ROM symlinks diff --git a/chapter07/symlinksd.xml b/chapter07/symlinksd.xml deleted file mode 100644 index b0d6460cf..000000000 --- a/chapter07/symlinksd.xml +++ /dev/null @@ -1,63 +0,0 @@ - - - %general-entities; -]> - - - - - Creating Custom Symlinks to Devices - - - Dealing with duplicate devices - - As explained in , the order in - which devices with the same function appear in - /dev is essentially random. - E.g., if you have a USB web camera and a TV tuner, sometimes - /dev/video0 refers to the camera and - /dev/video1 refers to the tuner, and sometimes - after a reboot the order changes to the opposite one. - For all classes of hardware except sound cards and network cards, this is - fixable by creating udev rules for custom persistent symlinks. - The case of network cards is covered separately in - , and sound card configuration can - be found in BLFS. - - For each of your devices that is likely to have this problem - (even if the problem doesn't exist in your current Linux distribution), - find the corresponding directory under - /sys/class or - /sys/block. - For video devices, this may be - /sys/class/video4linux/videoX. - Figure out the attributes that identify the device uniquely (usually, - vendor and product IDs and/or serial numbers work): - -udevadm info -a -p /sys/class/video4linux/video0 - - Then write rules that create the symlinks, e.g.: - -cat > /etc/udev/rules.d/83-duplicate_devs.rules << "EOF" - -# Persistent symlinks for webcam and tuner -KERNEL=="video*", ATTRS{idProduct}=="1910", ATTRS{idVendor}=="0d81", \ - SYMLINK+="webcam" -KERNEL=="video*", ATTRS{device}=="0x036f", ATTRS{vendor}=="0x109e", \ - SYMLINK+="tvtuner" - -EOF - - The result is that /dev/video0 and - /dev/video1 devices still refer randomly to the tuner - and the web camera (and thus should never be used directly), but there are - symlinks /dev/tvtuner and - /dev/webcam that always point to the correct - device. - - - -