glossary.html

这是NTFS文件0.5版本技术文件

      <dd><a name="logfile"></a></dd>
      <dt>$LogFile <a href="../files/logfile.html">(More...) </a></dt>
        <dd>
        This <a href="#metadata">metadata</a> file is used
        to guarantee data integrity in case of a system failure. It has two
        copies of the restart area and the infinite logging area. The log file
        is near the centre of the volume, just after the second cluster of
        the boot file. [Better say 'run' than cluster. The boot file usually
        extends over several clusters at the beginning of the disk, and then has
        a single run of just one cluster (the copy of the boot sector). Also,
        isn't it 'infinite'?]
        Transactional logging file
        </dd>

      <dd><a name="logged_utility_stream"></a></dd>
      <dt>$LOGGED_UTILITY_STREAM <a href="../attributes/logged_utility_stream.html">(More...) </a></dt>
        <dd>
        This <a href="#attribute">attribute</a> is used by encrypted files.
        </dd>

      <dd><a name="lcn"></a></dd>
      <dt>Logical Cluster Number (LCN)</dt>
        <dd>
        A volume is divided into clusters.  They are
        numbered sequentially, starting at zero.
        <br>See also:
        <a href="#cluster">Cluster</a> and
        <a href="#volume">Volume</a>.
        </dd>

      <dd><a name="lsn"></a></dd>
      <dt>Logical Sequence Number (LSN)</dt>
        <dd>
        A serial number used to
        identify an NTFS log record.
        </dd>

      <dt>LSN <a href="#lsn">(See Logical Sequence Number)</a></dt>
    </dl>

    <hr>

    <dl>
      <dd><a name="m"></a></dd>

      <dd><a name="magic_number"></a></dd>
      <dt>Magic Number</dt>
        <dd>
        Most of the on-disk structures in NTFS have a unique constant identifying them.
        This number is usually located at the beginning of the structure and can be
        used as a sanity check.
        </dd>

      <dd><a name="master_file_table"></a></dd>
      <dt>Master File Table <a href="#master_file_table">(See $MFT)</a></dt>

      <dd><a name="max"></a></dd>
      <dt>$Max</dt>
	<dd>
	$Max is a named Data Stream of $UsnJrnl.
	<br>See also:
	<a href="#usnjrnl">$UsnJrnl</a>
	</dd>

      <dd><a name="mb"></a></dd>
      <dt>MB <a href="#units">(See Units)</a></dt>

      <dd><a name="metadata"></a></dd>
      <dt>Metadata</dt>
        <dd>
        Data on the storage unit used by the filesystem only, as a
        frame to access user data. Metadata constitutes the structure of the
        filesystem). Metadata examples from various filesystems include FATs,
        inode tables, free block lists, free block bitmaps, logging areas, and
        the superblock.

	<pre>
	meta-data

	Data about data. In data processing, meta-data is definitional data
	that provides information about or documentation of other data managed
	within an application or environment.

	For example, meta data would document data about data elements or
	attributes, (name, size, data type, etc) and data about records or
	data structures (length, fields, columns, etc) and data about data
	(where it is located, how it is associated, ownership, etc.). Meta
	data may include descriptive information about the context, quality
	and condition, or characteristics of the data.
	</pre>
        </dd>

      <dd><a name="mft"></a></dd>
      <dt>$MFT <a href="../files/mft.html">(More...) </a></dt>
        <dd>
        This <a href="#metadata">metadata</a> file, the Master File Table,
        is an index of all the files on the volume.  It contains the
        attributes of each file and the root of any indexes.
        </dd>

      <dd><a name="mftmirr"></a></dd>
      <dt>$MFTMirr <a href="../files/mftmirr.html">(More...) </a></dt>
        <dd>
        This <a href="#metadata">metadata</a> file stores a copy of
        the first four records of $MFT.  It is a safety measure
        which probably only gets used when chkdsk is run.
        </dd>

      <dd><a name="mountmgrdatabase"></a></dd>
      <dt>$MountMgrDatabase</dt>
        <dd>
	$MountMgrDatabase is a named Data Stream of dot (the root directory).
	It contains a list of mounted volumes.
        <br>See also:
        <a href="#dot">Dot, Root Directory</a>.
        </dd>

      <dd><a name="mst"></a></dd>
      <dt>MST <a href="#multi_sector_transfer">(See Multi-Sector Transfer)</a></dt>

      <dd><a name="multi_sector_transfer"></a></dd>
      <dt>Multi-Sector Transfer</dt>
        <dd>
	<pre>
	multiple sectors, fixup, safety checks
	</pre>
        </dd>
    </dl>

    <hr>

    <dl>
      <dd><a name="n"></a></dd>

      <dd><a name="nibble"></a></dd>
      <dt>Nibble</dt>
        <dd>
        Half of a byte (4 bits).
        </dd>

      <dd><a name="nt_authority"></a></dd>
      <dt>NT Authority</dt>
        <dd>
        The NT Authority defines the scope of the security identifier.
        Numbers 0&nbsp;-&nbsp;4 represent internal identifiers, e.g.
        World, Local.  5 represents the NT Authority.
        <br>See also:
        <a href="#nt_sub_authority">NT Sub Authority</a>
        <a href="#sid">SID</a>
        <a href="#security_descriptor">$SECURITY_DESCRIPTOR</a>
        </dd>

      <dd><a name="ntfs"></a></dd>
      <dt>NTFS <a href="../attributes/volume_information.html">(More...) </a></dt>
        <dd>
        NTFS is the file system of Windows NT, Windows 2000 and Windows XP.
        <br>See also:
        <a href="#filesystem">Filesystem</a>
        </dd>

      <dd><a name="nt_sub_authority"></a></dd>
      <dt>NT Sub Authority</dt>
        <dd>
        The Sub Authority can contain any number of fields (five is usual).
        Sub Authorities beginning with 21 (0x15) denote a NT Domain identifier.
        <a href="#nt_authority">NT Authority</a>
        <a href="#sid">SID</a>
        <a href="#security_descriptor">$SECURITY_DESCRIPTOR</a>
        </dd>
    </dl>

    <hr>

    <dl>
      <dd><a name="o"></a></dd>

      <dd><a name="o"></a></dd>
      <dt>$O</dt>
        <dd>
        This is one of the named indexes belonging to $Quota and $ObjId.
        <br>See also:
        <a href="#index">Index</a>,
        <a href="#q">$Q</a>,
        <a href="#objid">$ObjId</a> and
        <a href="#quota">$Quota</a>.
        </dd>

      <dd><a name="object_id"></a></dd>
      <dt>$OBJECT_ID <a href="../attributes/object_id.html">(More...) </a></dt>
        <dd>
        This <a href="#attribute">attribute</a> stores a mapping between a
        SID and a Security Hash.
        </dd>

      <dd><a name="objid"></a></dd>
      <dt>$ObjId <a href="../files/objid.html">(More...) </a></dt>
        <dd>
        This <a href="#attribute">attribute</a> record's the unique identifiers
        given to files and directorys when using Distributed Link Tracking.
        </dd>
    </dl>

    <hr>

    <dl>
      <dd><a name="p"></a></dd>

      <dd><a name="pam"></a></dd>
      <dt>PAM</dt>
        <dd>
        Pluggable Authentication Modules (PAM) are a set of libraries
        for validating security on Linux.
        </dd>

      <dd><a name="partition"></a></dd>
      <dt>Partition <a href="#volume">(See Volume)</a></dt>

      <dd><a name="partition_table"></a></dd>
      <dt>Partition Table</dt>
        <dd>
	<pre>
	partition table...
	SFS Win2K dynamic disk
	</pre>
        </dd>

      <dd><a name="permissions"></a></dd>
      <dt>Permissions</dt>
        <dd>
        There are two mechanisms for storing permissions in NTFS.
        One is a superset of DOS File Permissions, which includes
        <q>Read Only</q> and <q>Hidden</q>.
        The other is based on ACEs and allows granting specific
        permissions to specific users.
        <br>See also:
        <a href="#ace">$ACE</a>,
        <a href="#file_permissions">File Permissions</a> and
        <a href="#security_descriptor">$SECURITY_DESCRIPTOR</a>
        </dd>

      <dd><a name="posix"></a></dd>
      <dt>POSIX</dt>
        <dd>
        An acronym (pronounced like positive) for Portable Operating System
        Interface, suggested by Richard M. Stallman.  It is a set of
        international standards (ISO/IEC 9945-1:1996(E), ANSI/IEEE Std 1003.1
        1996 Edition) to interface with Unix-like exploitation systems, e.g.
        Linux. NTFS does not support Unix-like device files.
        </dd>

      <dd><a name="property_set"></a></dd>
      <dt>$PROPERTY_SET <a href="../attributes/property_set.html">(More...) </a></dt>
        <dd>
	<pre>obsolete</pre>
        </dd>
    </dl>

    <hr>

    <dl>
      <dd><a name="q"></a></dd>

      <dd><a name="q"></a></dd>
      <dt>$Q</dt>
        <dd>
        This is one of the named indexes belonging to $Quota.
        <br>See also:
        <a href="#index">Index</a>,
        <a href="#o">$O</a> and
        <a href="#quota">$Quota</a>.
        </dd>

      <dd><a name="quota"></a></dd>
      <dt>$Quota <a href="../files/quota.html">(More...) </a></dt>
        <dd>
        This <a href="#metadata">metadata</a> file stores information
        about file quotas.
        </dd>
    </dl>

    <hr>

    <dl>
      <dd><a name="r"></a></dd>

      <dd><a name="r"></a></dd>
      <dt>$R</dt>
        <dd>
        This is the named index belonging to $Reparse.
        <br>See also:
        <a href="#index">Index</a>,
        <a href="#reparse">$Reparse</a>.
        </dd>

      <dd><a name="rcrd_record"></a></dd>
      <dt>RCRD Record</dt>
        <dd>
        This record is used in the $LogFile.  Each represents
        an atomic transaction that is to be performed.
        <br>See also:
        <a href="#logfile">$LogFile</a> and
        <a href="#transaction">Transaction</a>
        </dd>

      <dd><a name="record"></a></dd>
      <dt>Record</dt>
        <dd>
        There are several record types in NTFS.
        FILE Record are used in the $MFT, INDX Records in indexes,
        RCRD and RSTR Records in the $LogFile.
        <br>See also:
        <a href="#file_record">FILE Record</a>,
        <a href="#indx_record">INDX Record</a>,
        <a href="#rcrd_record">RCRD Record</a> and
        <a href="#rstr_record">RSTR Record</a>
        </dd>

      <dd><a name="recursion"></a></dd>
      <dt>Recursion <a href="#recursion">(See Recursion)</a></dt>

      <dd><a name="reference"></a></dd>
      <dt>Reference</dt>
        <dd>
        file (are there any others?)
        </dd>

      <dd><a name="reparse"></a></dd>
      <dt>$Reparse <a href="../files/reparse.html">(More...) </a></dt>
        <dd>
        This <a href="#metadata">metadata</a> file stores information
        about reparse points.
        </dd>

      <dd><a name="reparse_point"></a></dd>
      <dt>$REPARSE_POINT <a href="../attributes/reparse_point.html">(More...) </a></dt>
        <dd>
        This <a href="#attribute">attribute</a> stores information about
        reparse points.
        </dd>

      <dd><a name="resource_fork"></a></dd>
      <dt>Resource Fork</dt>
        <dd>
        In MacOS's filesystem, HFS, files are allowed to have multiple
        data streams.  These are called resource forks.
        <br>See also:
        <a href="#hfs">HFS</a> and
        <a href="#stream">Stream</a>.
        </dd>

      <dd><a name="roll-back"></a></dd>
      <dt>Roll-back</dt>
        <dd>
        When an NTFS volume is mounted, it is checked to see if it
        is in a consistant state.  If it isn't then the $LogFile is
        consulted and transactions are undone until the disk returns
        to a consistant state.  This does not guarantee data integrity,
        only disk integrity.
        <br>See also:
        <a href="#logfile">$LogFile</a>,
        <a href="#transaction">Transaction</a> and
        <a href="#volume">Volume</a>.
        </dd>

      <dd><a name="root_directory"></a></dd>
      <dt>Root Directory <a href="#dot">(See Dot, Root Directory)</a></dt>

      <dd><a name="rstr_record"></a></dd>
      <dt>RSTR Record</dt>
        <dd>
        Two copies of this are in $LogFile. A restart area has the
        magic number 'RSTR' followed by a fixup and some other data, including
        three LSNs. A restart area has a pointer into the log area, such as the
        first and last log records written and the last checkpoint record
        written. (that is three - now which is which?)
        </dd>

      <dd><a name="runs"></a></dd>
      <dt>Runs <a href="#data_runs">(See Data Runs)</a></dt>
    </dl>

    <hr>

    <dl>
      <dd><a name="s"></a></dd>