Previous Page
Next Page

F
FDDI

A standard for data transmission on fiber-optic lines in a LAN that can extend up to 200km (124 miles).



File access permissions

Used in Solaris to provide control over file access.



Filenames

The objects most often used to access and manipulate files. A file must have a name that is associated with an I-node. See I-node.



File system dump

A backup of a file system using the ufsdump command.



File system minfree space

The portion of a file system that is reserved and held back from users. It is only accessible by root.



File system type

Describes the type of file system such as UFS, PROCFS, TMPFS. Many file system administration commands require you to specify the file system type (fstype).



File system

A structure used to organize and store files on disk.



Finish script

Used in a JumpStart installation, this is a user-defined Bourne shell script, specified within the rules file, that performs tasks after the Solaris software is installed on the system, but before the system reboots. You can use finish scripts only with custom JumpStart installations.



Flash archive

Provides a method to store a snapshot of the Solaris operating environment complete with all installed patches and applications.



Flash installation

A complete snapshot of a Solaris operating environment, including with patches and applications.



Fragment

Also referred to as fragmentation. This is the method used by the UFS to allocate disk space efficiently.



Free block

Blocks not currently being used as I-nodes, indirect address blocks, or storage blocks are marked as free in the cylinder group map.



Free hog slice

A temporary slice that is automatically designated that expands and shrinks to accommodate the slice resizing operations.



Full backup

A backup that contains everything on the file system.



Full device name

A full device pathname is a series of node names separated by slashes (/). The root of the tree is the machine node, which is not named explicitly but is indicated by a leading slash (/). Each device pathname has this form: driver-name@unit-address:device-arguments.




Previous Page
Next Page