os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Made <indexterm>'s more specific by adding <filename>, <command>,

Browse source 
and <application> entities.

Submitted by:	Valentino Vaschetto <valentino.vaschetto@windriver.com>
Reviewed by:	murray
This commit is contained in:
Chern Lee 2001-07-19 01:11:52 +00:00
parent 9bb625166b
commit 4df284c246
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=9960
8 changed files with 279 additions and 103 deletions
Download patch file Download diff file Expand all files Collapse all files

116
en_US.ISO8859-1/books/handbook/disks/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/disks/chapter.sgml,v 1.36 2001/07/14 23:40:28 murray Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/disks/chapter.sgml,v 1.37 2001/07/16 15:02:50 nik Exp $
-->
<chapter id="disks">
@ -288,7 +288,10 @@
<sect2 id="disks-mount">
<title>The mount Command</title>
<indexterm><primary>filesystems</primary><secondary>mounting</secondary></indexterm>
<indexterm>
<primary>filesystems</primary>
<secondary>mounting</secondary>
</indexterm>
<para>The &man.mount.8; command is what is ultimately used to
mount filesystems.</para>
@ -414,7 +417,10 @@
<sect2 id="disks-umount">
<title>The umount Command</title>
<indexterm><primary>filesystems</primary><secondary>unmounting</secondary></indexterm>
<indexterm>
<primary>filesystems</primary>
<secondary>unmounting</secondary>
</indexterm>
<para>The umount command takes, as a parameter, one of a
mountpoint, a device name, or the <option>-a</option> or
@ -433,7 +439,10 @@
<sect1 id="disks-adding">
<title>Adding Disks</title>
<indexterm><primary>disks</primary><secondary>adding</secondary></indexterm>
<indexterm>
<primary>disks</primary>
<secondary>adding</secondary>
</indexterm>
<para><emphasis>Originally contributed by &a.obrien; 26 April
1998</emphasis></para>
@ -455,7 +464,9 @@
<indexterm><primary>partitions</primary></indexterm>
<indexterm><primary>slices</primary></indexterm>
<indexterm><primary>fdisk</primary></indexterm>
<indexterm>
<primary><command>fdisk</command></primary>
</indexterm>
<para>Because FreeBSD runs on IBM-PC compatible computers, it must
take into account the PC BIOS partitions. These are different
@ -480,7 +491,10 @@
<sect2>
<title>Using &man.sysinstall.8;</title>
<indexterm><primary>sysinstall</primary><secondary>adding disks</secondary></indexterm>
<indexterm>
<primary><application>sysinstall</application></primary>
<secondary>adding disks</secondary>
</indexterm>
<para>You may use <command>/stand/sysinstall</command> to
partition and label a new disk using its easy to use menus.
@ -603,7 +617,10 @@
<sect1 id="disks-virtual">
<title>Virtual Disks: Network, Memory, and File-Based Filesystems</title>
<indexterm><primary>virtual disks</primary></indexterm>
<indexterm><primary>disks</primary><secondary>virtual</secondary></indexterm>
<indexterm>
<primary>disks</primary>
<secondary>virtual</secondary>
</indexterm>
<para>Aside from the disks you physically insert into your computer:
floppies, CDs, hard drives, and so forth; other forms of disks
@ -612,7 +629,10 @@
<indexterm><primary>NFS</primary></indexterm>
<indexterm><primary>Coda</primary></indexterm>
<indexterm><primary>disks</primary><secondary>memory</secondary></indexterm>
<indexterm>
<primary>disks</primary>
<secondary>memory</secondary>
</indexterm>
<para>These include network filesystems such as the <link
linkend="nfs">Network Filesystem</link> and Coda, memory-based
filesystems such as <link linkend="disks-md">md</link> and
@ -621,7 +641,10 @@
<sect2 id="disks-vnconfig">
<title>vnconfig: file-backed filesystem</title>
<indexterm><primary>disks</primary><secondary>file-backed</secondary></indexterm>
<indexterm>
<primary>disks</primary>
<secondary>file-backed</secondary>
</indexterm>
<para>&man.vnconfig.8; configures and enables vnode pseudo disk
devices. A <firstterm>vnode</firstterm> is a representation
@ -665,7 +688,10 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<sect2 id="disks-md">
<title>md: Memory Filesystem</title>
<indexterm><primary>disks</primary><secondary>memory</secondary></indexterm>
<indexterm>
<primary>disks</primary>
<secondary>memory filesystem</secondary>
</indexterm>
<para>md is a simple, efficient means to do memory
filesystems.</para>
@ -689,8 +715,10 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<sect1 id="quotas">
<title>Disk Quotas</title>
<indexterm><primary>accounting</primary><secondary>disk
space</secondary></indexterm>
<indexterm>
<primary>accounting</primary>
<secondary>disk space</secondary>
</indexterm>
<indexterm><primary>disk quotas</primary></indexterm>
<para>Quotas are an optional feature of the operating system that
@ -723,7 +751,10 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
line:</para>
<programlisting>enable_quotas=<quote>YES</quote></programlisting>
<indexterm><primary>disk quotas</primary><secondary>checking</secondary></indexterm>
<indexterm>
<primary>disk quotas</primary>
<secondary>checking</secondary>
</indexterm>
<para>For finer control over your quota startup, there is an
additional configuration variable available. Normally on bootup,
the quota integrity of each file system is checked by the
@ -787,7 +818,10 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<sect2>
<title>Setting Quota Limits</title>
<indexterm><primary>disk quotas</primary><secondary>limits</secondary></indexterm>
<indexterm>
<primary>disk quotas</primary>
<secondary>limits</secondary>
</indexterm>
<para>Once you have configured your system to enable quotas, verify
that they really are enabled. An easy way to do this is to
@ -875,7 +909,10 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<sect2>
<title>Checking Quota Limits and Disk Usage</title>
<indexterm><primary>disk quotas</primary><secondary>checking</secondary></indexterm>
<indexterm>
<primary>disk quotas</primary>
<secondary>checking</secondary>
</indexterm>
<para>You can use either the <command>quota</command> or the
<command>repquota</command> commands to check quota limits and
@ -934,7 +971,10 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<sect1 id="creating-cds">
<title>Creating CDs</title>
<indexterm><primary>CDROMs</primary><secondary>creating</secondary></indexterm>
<indexterm>
<primary>CDROMs</primary>
<secondary>creating</secondary>
</indexterm>
<para><emphasis>Contributed by Mike Meyer
<email>mwm@mired.org</email>, April 2001.</emphasis></para>
@ -956,21 +996,29 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
CD.</para>
<indexterm><primary>ISO 9660</primary></indexterm>
<indexterm><primary>filesystems</primary><secondary>ISO-9660</secondary></indexterm>
<indexterm>
<primary>filesystems</primary>
<secondary>ISO-9660</secondary>
</indexterm>
<para>The ISO 9660 file system was designed to deal with these
differences. It unfortunately codifies file system limits that were
common then. Fortunately, it provides an extension mechanism that
allows properly written CDs to exceed those limits while still
working with systems that do not support those extensions.</para>
<indexterm><primary>mkisofs</primary></indexterm>
<indexterm>
<primary><command>mkisofs</command></primary>
</indexterm>
<para>The <command><link linkend="mkisofs">mkisofs</link></command>
program is used to produce a data file containing an ISO 9660 file
system. It has options that support various extensions, and is
described below. You can install it with the <filename>
/usr/ports/sysutils/mkisofs</filename> port.</para>
<indexterm><primary>CD burner</primary><secondary>ATAPI</secondary></indexterm>
<indexterm>
<primary>CD burner</primary>
<secondary>ATAPI</secondary>
</indexterm>
<para>Which tool to use to burn the CD depends on whether your CD burner
is ATAPI or something else. ATAPI CD burners use the <command><link
linkend="burncd">burncd</link></command> program that is part of
@ -988,7 +1036,10 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<screen>&prompt.root; <userinput>mkisofs <option>-o</option> <replaceable>imagefile.iso</replaceable> <replaceable>/path/to/tree</replaceable></userinput></screen>
<indexterm><primary>filesystems</primary><secondary>ISO-9660</secondary></indexterm>
<indexterm>
<primary>filesystems</primary>
<secondary>ISO-9660</secondary>
</indexterm>
<para>This command will create an <replaceable>imagefile</replaceable>
containing an ISO 9660 file system that is a copy of the tree at
<replaceable>/path/to/tree</replaceable>. In the process, it will
@ -998,8 +1049,14 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
for details of this process, and options that can be used to
control it.</para>
<indexterm><primary>filesystems</primary><secondary>HFS</secondary></indexterm>
<indexterm><primary>filesystems</primary><secondary>Joliet</secondary></indexterm>
<indexterm>
<primary>filesystems</primary>
<secondary>HFS</secondary>
</indexterm>
<indexterm>
<primary>filesystems</primary>
<secondary>Joliet</secondary>
</indexterm>
<para>A number of options are available to overcome those
restrictions. In particular, <option>-R</option> enables the
Rock Ridge extensions common to Unix systems, <option>-J</option>
@ -1015,7 +1072,10 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
from, though it may violate the ISO 9660 standard in a number of
ways.</para>
<indexterm><primary>CDROMs</primary><secondary>creating bootable</secondary></indexterm>
<indexterm>
<primary>CDROMs</primary>
<secondary>creating bootable</secondary>
</indexterm>
<para>The last option of general use is <option>-b</option>. This is
used to specify the location of the boot image for use in producing an
<quote>El Torito</quote> bootable CD. This option takes an
@ -1045,7 +1105,10 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<sect2 id="burncd">
<title>burncd</title>
<indexterm><primary>CDROMs</primary><secondary>burning</secondary></indexterm>
<indexterm>
<primary>CDROMs</primary>
<secondary>burning</secondary>
</indexterm>
<para>If you have an ATAPI CD burner, you can use the
<command>burncd</command> command to burn an ISO image onto a
CD. <command>burncd</command> is part of the base system, installed
@ -1086,7 +1149,10 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
the <option>dev</option> to use. To find the proper setting, use
the <option>-scanbus</option> flag of <command>cdrecord</command>,
which might produce results like this:</para>
<indexterm><primary>CDROMs</primary><secondary>burning</secondary></indexterm>
<indexterm>
<primary>CDROMs</primary>
<secondary>burning</secondary>
</indexterm>
<screen>&prompt.root; <userinput>cdrecord <option>-scanbus</option></userinput>
Cdrecord 1.9 (i386-unknown-freebsd4.2) Copyright (C) 1995-2000 J&ouml;rg Schilling
Using libscg version 'schily-0.1'