|
|
|
fspec(4) -- format specification in text files
|
|
ed(1), newform(1), tabs(1) PPPPaaaaggggeeee 2222 |
|
fstab(4) -- static information about filesystems
|
|
The filesystem types nfs2, nfs3, and nfs3pref are accepted for compatibility with earlier releases. nfs2 is equivalent to vers=2. nfs3 is equivalent to vers=3. nfs3pref is equivalent to nfs with no vers= option. Options used by the mount(1M) command on normal filesystems are ignored when applied to the root filesystem, since the fstab file cannot be read before mounting the root filesystem. These options include rw and ro (the root filesystem cannot be mounted read-only), grpid, quota and qnoenf... |
|
|
gettydefs(4) -- speed and terminal settings used by getty
|
|
/etc/gettydefs |
|
grio_disks(4) -- description of guaranteed I/O rates for disk devices
|
|
/etc/grio_disks |
|
group(4) -- group membership file
|
|
/etc/group |
|
hosts(4) -- trusted hosts by system and by user
|
|
The owner of the .rhosts file must be the super-user (i.e., root) or the user in whose home directory it resides. The contents of a user's .rhosts file will be disregarded if it is owned by another user or if its permissions allow anyone who is not the owner to modify the file. Use the chmod(1) command to add the proper protection: chmod 600 .rhosts Likewise, /etc/hosts.equiv must be owned by and writable only by the super-user. HOSTS.EQUIV(4) HOSTS.EQUIV(4) If the user's home directory is NFS... |
|
hosts.equiv(4) -- trusted hosts by system and by user
|
|
The owner of the .rhosts file must be the super-user (i.e., root) or the user in whose home directory it resides. The contents of a user's .rhosts file will be disregarded if it is owned by another user or if its permissions allow anyone who is not the owner to modify the file. Use the chmod(1) command to add the proper protection: chmod 600 .rhosts Likewise, /etc/hosts.equiv must be owned by and writable only by the super-user. Page 2 HOSTS.EQUIV(4) HOSTS.EQUIV(4) If the user's home directory... |
|
hwgraph(4) -- hardware graph and hardware graph file system
|
|
The internal hardware graph is exported to user-level through a pseudofile system (similar to /proc(4)). The hwgfs file system represents the collection of all interesting hardware and pseudo-devices as a file system tree of special files and directories. It is mounted at /hw by the kernel during system boot, and can be re-mounted using /etc/mnthwgfs. In order to represent the directed graph as a Unix file system tree, hwgfs imposes an artificial hierarchy on the hardware graph, and it uses hard... |
|
dmedia/iff(4) -- Amiga IFF/8SVX Audio File Format
|
|
The Audio File Library currently supports 13 of the commonly found audio file formats, i.e., is able to recognize, read, and write sample data and header information to and from files in these formats. It is important not to confuse sample or audio data formats with file formats. The former refers to the bit-wise organization of the sound samples in the file, i.e., whether the format is 8-bit integer or 16-bit unsigned, etc. Audio file format refers to the structure of the audio file header, the... |
|
inittab(4) -- script for the init process
|
|
/etc/inittab |
|
inode(4) -- format of an Extent File System inode
|
|
An inode is the volume data structure used by the Extent File System (EFS) to implement the abstraction of a file. (This is not to be confused with the in-core inode used by the operating system to manage memory-resident EFS files.) An inode contains the type (for example, plain file, directory, symbolic link, or device file) of the file; its owner, group, and public access permissions; the owner and group ID numbers; its size in bytes; the number of links (directory references) to the file; and... |
|
intro(4) -- introduction to file formats
|
|
|
|
dmedia/jpeg(4) -- JPEG compression format
|
|
The JPEG compression format is supported by several developer and enduser products. |
|
ldap.conf(4) -- Lightweight Directory Access Protocol configuration file
|
|
This file controls the behavior of the Lightweight Directory Access Protocol (LDAP) client implementation for nsd. It is read by the initialization routine of the ldap(7P) library when the nsd daemon is started, or sent the SIGHUP signal. This file contains information about remote LDAP daemons database schemas, and format rules. The file is made up of comment lines, table entries, server entries and the domain command. Comment lines begin with either a '#' or a ';' character, and are ignore... |
|
libdwarf(4) -- dwarf debugging information format library interface
|
|
Because the dwarf version 2 debugging information format uses several techniques to offer descriptive power and flexibility while retaining a compact representation, reading and writing the data is not simple. Consequently two C interfaces are provided. A consumer interface that allows easy reading of all the data, hiding representation details while providing all the data in the debugging information. See A Consumer Library Interface to DWARF, which is in troff in libdwarf2.1.mm and PostScript ... |
