Custom Query (4816 matches)

Reported by Seth W. Klein: In the chroot command in ​http://www.linuxfromscratch.org/lfs/view/cvs/chapter06/chroot.html several environment variable references are unquoted. This leads to misleading error messages such as: chroot: cannot change root directory to /tools/bin/env: Not a directory when $LFS is not set. It is also broken if $LFS contains spaces. The correct form is: chroot "$LFS" /tools/bin/env -i \

HOME=/root TERM="$TERM" PS1='\u:\w\$ ' \ PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \ /tools/bin/bash +h

Other chroot commands probably have similar bugs.

Reported by DJ Lucas: Need to add /media and /srv to 'FHS compliance note' or (prefered) to creating directories command. Quote from 2.3:

3.11. /media : Mount point for removeable media 3.11.1. Purpose This directory contains subdirectories which are used as mount points for removeable media such as floppy disks, cdroms and zip disks. Historically there have been a number of other different places used to mount removeable media such as /cdrom, /mnt or /mnt/cdrom. Placing the mount points for all removeable media directly in the root directory would potentially result in a large number of extra directories in /. Although the use of subdirectories in /mnt as a mount point has recently been common, it conflicts with a much older tradition of using /mnt directly as a temporary mount point. 3.11.2. Specific Options The following directories, or symbolic links to directories, must be in /media, if the corresponding subsystem is installed: Directory Description floppy Floppy drive (optional) cdrom CD-ROM drive (optional) cdrecorder CD writer (optional) zip Zip drive (optional) On systems where more than one device exists for mounting a certain type of media, mount directories can be created by appending a digit to the name of those available above starting with ?0?, but the unqualified name must also exist. 3.12. /mnt : Mount point for a temporarily mounted filesystem 3.12.1. Purpose This directory is provided so that the system administrator may temporarily mount a filesystem as needed. The content of this directory is a local issue and should not affect the manner in which any program is run. This directory must not be used by installation programs: a suitable temporary directory not in use by the system must be used instead.

<Snip>

3.16. /srv : Data for services provided by this system 3.16.1. Purpose /srv contains site-specific data which is served by this system. Rationale This main purpose of specifying this is so that users may find the location of the data files for particular service, and so that services which require a single tree for readonly data, writable data and scripts (such as cgi scripts) can be reasonably placed. Data that is only of interest to a specific user should go in that users? home directory. The methodology used to name subdirectories of /srv is unspecified as there is currently no consensus on how this should be done. One method for structuring data under /srv is by protocol, eg. ftp, rsync, www, and cvs. On large systems it can be useful to structure /srv by administrative context, such as /srv/physics/www, /srv/compsci/cvs, etc. This setup will differ from host to host. Therefore, no program should rely on a specific subdirectory structure of /srv existing or data necessarily being stored in /srv. However /srv should always exist on FHS compliant systems and should be used as the default location for such data. Distributions must take care not to remove locally placed files in these directories without administrator permission.

Reported by DJ Lucas: I'd like to make a suggestion to move passwd into /bin. While this is not required or prohibited by any standard, it can be useful in single user mode when /usr is not availible. Only changes required to the book are that we remove the 'touch /usr/bin/passwd' in shadow install, and add 'mv /usr/bin/passwd /bin' after install. Shadow's shared libs are already installed into /lib.