Date: Fri, 27 Aug 1999 23:01:20 -0230 (NDT) From: Neil Zanella <nzanella@math.mun.ca> To: Neil Blakey-Milner <nbm@mithrandr.moria.org> Cc: Sheldon Hearn <sheldonh@uunet.co.za>, freebsd-bugs@FreeBSD.ORG Subject: Re: misc/13407: FHS compliancy Message-ID: <Pine.BSF.4.01.9908272300010.553-100000@fermat.math.mun.ca> In-Reply-To: <19990827110218.A40666@rucus.ru.ac.za>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Fri 1999-08-27 (10:26), Sheldon Hearn wrote: > > > The document should at least be approchable from any location as it > > > resides at <ftp://metalab.unc.edu/pub/Linux/docs/fhs/fhs-2.0.tar.gz>. > > > All the details are in that document. > > > > If you want something done about it, your best bet is to single out the > > offending placements in FreeBSD and provide us with those, rather than > > expecting us to read the document. This advice seems sensible to me > > because you've already read the document to be complaining about > > FreeBSD's conformance. Required files for /bin: * General commands: The following commands have been included because they are essential. A few are present because of their traditional placement in /bin. + { cat, chgrp, chmod, chown, cp, date, dd, df, dmesg, echo, ed, false, kill, ln, login, ls, mkdir, mknod, more, mount, mv, ps, pwd, rm, rmdir, sed, setserial, sh, stty, su, sync, true, umount, uname } If /bin/sh is Bash, then /bin/sh should be a symbolic or hard link to /bin/bash since Bash behaves differently when called as sh or bash. pdksh, which may be the /bin/sh on install disks, should likewise be arranged with /bin/sh being a symlink to /bin/ksh. The use of a symbolic link in these cases allows users to easily see that /bin/sh is not a true Bourne shell. Since the de-facto standard location of the C-shell is /bin/csh, if and only if a C-shell or equivalent (such as tcsh) is available on the system, it should be available by the name /bin/csh. /bin/csh may be a symbolic link to /bin/tcsh or /usr/bin/tcsh. Note: The [ and test commands are built into most commonly used Bourne shell (/bin/sh) replacements. These two commands do not have to be placed in /bin; they may be placed in /usr/bin. They must be included as separate binaries with any UNIX or UNIX-like system attempting to comply with the POSIX.2 standard. * Restoration commands: These commands have been added to make restoration of a system possible (provided that / is intact). + { tar, gzip, gunzip (link to gzip), zcat (link to gzip) } If system backups are made using programs other than gzip and tar, then the root partition should contain the minimal necessary restoration components. For instance, many systems should include cpio as it is the next most commonly used backup utility after tar. Conversely, if no restoration from the root partition is ever expected, then these binaries may be omitted (i.e., a ROM chip root, mounting /usr through NFS). If restoration of a system is planned through the network, then ftp or tftp (along with everything necessary to get an ftp connection) should be available on the root partition. Restoration commands may appear in either /bin or /usr/bin on different systems. * Networking commands: These are the only necessary networking binaries that both root and users will want or need to execute other than the ones in /usr/bin or /usr/local/bin. + { domainname, hostname, netstat, ping } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.01.9908272300010.553-100000>