- Reduce the misuse of role attribute; role="directory" should actually be
class="directory" - Add constraint to enforce this
This commit is contained in:
Gabor Kovesdan
parent
843e63283c
commit
a6684b4306
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/projects/xml-tools/; revision=41366
75 changed files with 337 additions and 331 deletions
de_DE.ISO8859-1/books/handbook
el_GR.ISO8859-7/books/handbook
advanced-networking
audit
disks
eresources
network-servers
ports
security
en_US.ISO8859-1
es_ES.ISO8859-1
articles
books/handbook
advanced-networking
geom
install
jails
mail
security
fr_FR.ISO8859-1
articles/nanobsd
books/handbook
advanced-networking
geom
install
jails
kernelconfig
mail
mirrors
ppp-and-slip
security
x11
hu_HU.ISO8859-2/books/handbook/firewalls
it_IT.ISO8859-15
articles/committers-guide
books/handbook
geom
install
jails
kernelconfig
linuxemu
mirrors
network-servers
ja_JP.eucJP/books/handbook
mn_MN.UTF-8/books/handbook
nl_NL.ISO8859-1/books/handbook
pl_PL.ISO8859-2/books/handbook
advanced-networking
audit
disks
geom
linuxemu
mirrors
network-servers
ports
ru_RU.KOI8-R
articles/committers-guide
books
fdp-primer/the-website
handbook
share/xml
zh_CN.GB2312/books/handbook/audit
zh_TW.Big5
articles
books
fdp-primer/the-website
handbook
advanced-networking
audit
disks
geom
jails
kernelconfig
linuxemu
mirrors
ports
|
|
@ -108,7 +108,7 @@
|
|||
— Master Boot Records, <acronym>BSD</acronym>-Label usw.
|
||||
— durch die Nutzung von Datenträgern (Providern) oder
|
||||
den besonderen Dateien in <filename
|
||||
role="directory">/dev</filename>. Verschiedene Software
|
||||
class="directory">/dev</filename>. Verschiedene Software
|
||||
<acronym>RAID</acronym>-Konfigurationen unterstützend, wird
|
||||
GEOM Ihnen transparenten Zugriff auf das Betriebssystem und
|
||||
System-Dienstprogramme gewähren.</para>
|
||||
|
|
@ -187,7 +187,7 @@
|
|||
existiert. Falls dieser Datenträger eine Root-Partition
|
||||
werden soll, dann nutzen Sie zeitweise einen anderen
|
||||
Mount-Punkt, beispielsweise <filename
|
||||
role="directory">/mnt</filename>:</para>
|
||||
class="directory">/mnt</filename>:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>mkdir /mnt</userinput></screen>
|
||||
</step>
|
||||
|
|
|
|||
|
|
@ -1313,7 +1313,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
|
|||
identifiziert und angelegt haben, müssen Sie dem
|
||||
<application>LPD</application>-System mitteilen, welche
|
||||
Gerätedatei im Verzeichnis <filename
|
||||
role="directory">/dev</filename> es für die
|
||||
class="directory">/dev</filename> es für die
|
||||
Datenübertragung zum Drucker verwenden soll.</para>
|
||||
|
||||
<para>Geben Sie die Gerätedatei durch das Attribut
|
||||
|
|
|
|||
|
|
@ -2908,7 +2908,7 @@ subnet 192.168.4.0 netmask 255.255.255.0 {
|
|||
<filename>pxeboot</filename>, not the kernel. There are other
|
||||
interesting possibilities, like loading
|
||||
<filename>pxeboot</filename> from a &os; CD-ROM
|
||||
<filename role="directory">/boot</filename> directory (as
|
||||
<filename class="directory">/boot</filename> directory (as
|
||||
&man.pxeboot.8; can load a <filename>GENERIC</filename> kernel,
|
||||
this makes it possible to use <acronym>PXE</acronym> to boot
|
||||
from a remote CD-ROM).</para>
|
||||
|
|
|
|||
|
|
@ -232,7 +232,7 @@
|
|||
<title>Audit Configuration</title>
|
||||
|
||||
<para>All configuration files for security audit are found in
|
||||
<filename role="directory">/etc/security</filename>. The following
|
||||
<filename class="directory">/etc/security</filename>. The following
|
||||
files must be present before the audit daemon is started:</para>
|
||||
|
||||
<itemizedlist>
|
||||
|
|
|
|||
|
|
@ -3898,7 +3898,7 @@ device crypto</screen>
|
|||
<para>The following example will describe how to generate a
|
||||
key file, which will be used as part of the Master Key for
|
||||
the encrypted provider mounted under
|
||||
<filename role="directory">/private</filename>. The key
|
||||
<filename class="directory">/private</filename>. The key
|
||||
file will provide some random data used to encrypt the
|
||||
Master Key. The Master Key will be protected by a
|
||||
passphrase as well. Provider's sector size will be 4kB big.
|
||||
|
|
@ -3970,7 +3970,7 @@ Filesystem Size Used Avail Capacity Mounted on
|
|||
<title>Unmounting and Detaching the Provider</title>
|
||||
|
||||
<para>Once the work on the encrypted partition is done, and
|
||||
the <filename role="directory">/private</filename> partition
|
||||
the <filename class="directory">/private</filename> partition
|
||||
is no longer needed, it is prudent to consider unmounting
|
||||
and detaching the <command>geli</command> encrypted
|
||||
partition from the kernel.</para>
|
||||
|
|
|
|||
|
|
@ -1585,7 +1585,7 @@
|
|||
|
||||
<para>Σημαντικές ειδήσεις σχετικές με την
|
||||
<quote>Συλλογή των Ports</quote> (<filename
|
||||
role="directory">/usr/ports</filename>) που απευθυνόνται σε
|
||||
class="directory">/usr/ports</filename>) που απευθυνόνται σε
|
||||
όσους αναπτύσσουν ή μεταφέρουν λογισμικό στο &os; αλλά και στους
|
||||
τελικούς χρήστες. Περιλαμβάνονται ειδήσεις σχετικές με
|
||||
αλλαγές στην αρχιτεκτονική και την υποδομή, νέες δυνατότητες
|
||||
|
|
|
|||
|
|
@ -3104,7 +3104,7 @@ dhcpd_ifaces="dc0"</programlisting>
|
|||
<hostid>org.</hostid>, as <hostid>org.</hostid> is more specific
|
||||
than the root zone. The layout of each part of a hostname is
|
||||
much like a file system: the
|
||||
<filename role="directory">/dev</filename> directory falls
|
||||
<filename class="directory">/dev</filename> directory falls
|
||||
within the root, and so on.</para>
|
||||
</sect2>
|
||||
|
||||
|
|
@ -3188,7 +3188,7 @@ dhcpd_ifaces="dc0"</programlisting>
|
|||
</row>
|
||||
|
||||
<row>
|
||||
<entry><filename role="directory">/etc/namedb</filename></entry>
|
||||
<entry><filename class="directory">/etc/namedb</filename></entry>
|
||||
<entry>Directory where BIND zone information resides.</entry>
|
||||
</row>
|
||||
|
||||
|
|
@ -3202,10 +3202,10 @@ dhcpd_ifaces="dc0"</programlisting>
|
|||
|
||||
<para>Depending on how a given zone is configured on the server,
|
||||
the files related to that zone can be found in the <filename
|
||||
role="directory">master</filename>, <filename
|
||||
role="directory">slave</filename>, or <filename
|
||||
role="directory">dynamic</filename> subdirectories of the
|
||||
<filename role="directory">/etc/namedb</filename> directory.
|
||||
class="directory">master</filename>, <filename
|
||||
class="directory">slave</filename>, or <filename
|
||||
class="directory">dynamic</filename> subdirectories of the
|
||||
<filename class="directory">/etc/namedb</filename> directory.
|
||||
These files contain the <acronym>DNS</acronym> information that
|
||||
will be given out by the name server in response to queries.</para>
|
||||
</sect2>
|
||||
|
|
@ -3253,7 +3253,7 @@ dhcpd_ifaces="dc0"</programlisting>
|
|||
|
||||
<para>Configuration files for <application>named</application>
|
||||
currently reside in
|
||||
<filename role="directory">/etc/namedb</filename> directory and
|
||||
<filename class="directory">/etc/namedb</filename> directory and
|
||||
will need modification before use, unless all that is needed is
|
||||
a simple resolver. This is where most of the configuration will
|
||||
be performed.</para>
|
||||
|
|
@ -3262,7 +3262,7 @@ dhcpd_ifaces="dc0"</programlisting>
|
|||
<title>Using <command>make-localhost</command></title>
|
||||
|
||||
<para>To configure a master zone for the localhost visit the
|
||||
<filename role="directory">/etc/namedb</filename> directory
|
||||
<filename class="directory">/etc/namedb</filename> directory
|
||||
and run the following command:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>sh make-localhost</userinput></screen>
|
||||
|
|
|
|||
|
|
@ -679,7 +679,7 @@ docbook =
|
|||
</note>
|
||||
|
||||
<para>Σιγουρευθείτε ότι το
|
||||
<filename role="directory">/usr/ports</filename>
|
||||
<filename class="directory">/usr/ports</filename>
|
||||
είναι άδειο πριν εκτελέσετε το <application>csup</application> για
|
||||
πρώτη φορά! Εάν έχετε ήδη ανακτήσει τη Συλλογή των Ports μέσω
|
||||
κάποιας άλλης πηγής, το <application>csup</application>
|
||||
|
|
|
|||
|
|
@ -2693,7 +2693,7 @@ kadmind5_server_enable="YES"</programlisting>
|
|||
|
||||
<para>This is done because the applications for
|
||||
<acronym>MIT</acronym> kerberos installs binaries in the
|
||||
<filename role="directory">/usr/local</filename>
|
||||
<filename class="directory">/usr/local</filename>
|
||||
hierarchy.</para>
|
||||
</sect2>
|
||||
|
||||
|
|
|
|||
|
|
@ -79,11 +79,11 @@
|
|||
</note>
|
||||
|
||||
<para>The scripts that control all of this live in either
|
||||
<filename role="directory">/a/portbuild/scripts/</filename> or.
|
||||
<filename role="directory">/a/portbuild/admin/scripts/</filename>.
|
||||
<filename class="directory">/a/portbuild/scripts/</filename> or.
|
||||
<filename class="directory">/a/portbuild/admin/scripts/</filename>.
|
||||
These are the checked-out copies from the Subversion repository at
|
||||
<ulink url="http://svnweb.freebsd.org/base/projects/portbuild/">
|
||||
<filename role="directory">base/projects/portbuild/</filename>
|
||||
<filename class="directory">base/projects/portbuild/</filename>
|
||||
</ulink>.</para>
|
||||
|
||||
<para>Typically, incremental builds are done that use previous
|
||||
|
|
|
|||
|
|
@ -1613,7 +1613,7 @@
|
|||
|
||||
<para>Important news for developers, porters, and users
|
||||
of the <quote>Ports Collection</quote> (<filename
|
||||
role="directory">/usr/ports</filename>), including
|
||||
class="directory">/usr/ports</filename>), including
|
||||
architecture/infrastructure changes, new capabilities,
|
||||
critical upgrade instructions, and release engineering
|
||||
information. This is a low-volume mailing list,
|
||||
|
|
|
|||
|
|
@ -806,7 +806,7 @@ Certificate information:
|
|||
the server, and the verification step will be repeated on the
|
||||
next connection. Accepting the certificate permanently will
|
||||
store the authentication credentials in
|
||||
<filename role="directory">~/.subversion/auth/</filename> and
|
||||
<filename class="directory">~/.subversion/auth/</filename> and
|
||||
the user will not be asked to verify the fingerprint again until
|
||||
the certificate expires.</para>
|
||||
|
||||
|
|
|
|||
|
|
@ -120,7 +120,7 @@
|
|||
<listitem>
|
||||
<para>La partición que contiene los ficheros de
|
||||
configuración, que puede montarse bajo
|
||||
<filename role="directory">/cfg</filename> durante el
|
||||
<filename class="directory">/cfg</filename> durante el
|
||||
funcionamiento del sistema.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
|
@ -128,20 +128,20 @@
|
|||
<para>Estas particiones se montan normalmente en modo de
|
||||
sólo lectura.</para>
|
||||
|
||||
<para>Los directorios <filename role="directory">/etc</filename>
|
||||
y <filename role="directory">/var</filename> son discos
|
||||
<para>Los directorios <filename class="directory">/etc</filename>
|
||||
y <filename class="directory">/var</filename> son discos
|
||||
&man.md.4; (malloc).</para>
|
||||
|
||||
<para>La partición de los ficheros de configuración
|
||||
permanece bajo el
|
||||
directorio <filename role="directory">/cfg</filename>. Este
|
||||
directorio <filename class="directory">/cfg</filename>. Este
|
||||
directorio contiene ficheros que usa el
|
||||
directorio <filename role="directory">/etc</filename> y se
|
||||
directorio <filename class="directory">/etc</filename> y se
|
||||
monta en modo de sólo lectura inmediatamente
|
||||
después del arranque; por lo tanto, es necesario que
|
||||
los ficheros que se modifiquen
|
||||
en <filename role="directory">/etc</filename> se copien
|
||||
en <filename role="directory">/cfg</filename> si se desea que
|
||||
en <filename class="directory">/etc</filename> se copien
|
||||
en <filename class="directory">/cfg</filename> si se desea que
|
||||
los cambios perduren después del reinicio del
|
||||
sistema.</para>
|
||||
|
||||
|
|
@ -158,13 +158,13 @@
|
|||
|
||||
<note>
|
||||
<para>La partición que contiene el
|
||||
directorio <filename role="directory">/cfg</filename>
|
||||
directorio <filename class="directory">/cfg</filename>
|
||||
debería montarse únicamente en el arranque y
|
||||
mientras se sobreescriben los ficheros de
|
||||
configuración.</para>
|
||||
|
||||
<para>No es buena idea montar siempre el
|
||||
directorio <filename role="directory">/cfg</filename>,
|
||||
directorio <filename class="directory">/cfg</filename>,
|
||||
especialmente si el
|
||||
sistema <application>NanoBSD</application> se ejecuta en un
|
||||
dispositivo de almacenamiento masivo que pueda verse
|
||||
|
|
@ -181,7 +181,7 @@
|
|||
<para>Una imagen de <application>NanoBSD</application> se genera
|
||||
usando el sencillo script de
|
||||
shell <filename>nanobsd.sh</filename>, ubicado en el
|
||||
directorio <filename role="directory"><replaceable>/usr</replaceable>/src/tools/tools/nanobsd</filename>.
|
||||
directorio <filename class="directory"><replaceable>/usr</replaceable>/src/tools/tools/nanobsd</filename>.
|
||||
El script crea una imagen que se deberá copiar al medio
|
||||
de almacenamiento mediante la utilidad &man.dd.1;.</para>
|
||||
|
||||
|
|
@ -327,7 +327,7 @@ customize_cmd cust_foo</programlisting>
|
|||
<para>A continuación vemos un ejemplo más útil
|
||||
de función personalizada, que cambia el tamaño por
|
||||
omisión del directorio
|
||||
<filename role="directory">/etc</filename> de 5MB a 30MB:</para>
|
||||
<filename class="directory">/etc</filename> de 5MB a 30MB:</para>
|
||||
|
||||
<programlisting>cust_etc_size () (
|
||||
cd ${NANO_WORLDDIR}/conf
|
||||
|
|
@ -357,7 +357,7 @@ customize_cmd cust_etc_size</programlisting>
|
|||
<listitem>
|
||||
<para><literal>cust_install_files</literal> : Instala ficheros
|
||||
de configuración desde el
|
||||
directorio <filename role="directory">nanobsd/files</filename>,
|
||||
directorio <filename class="directory">nanobsd/files</filename>,
|
||||
que contiene scripts útiles para la
|
||||
administración del sistema.</para>
|
||||
</listitem>
|
||||
|
|
@ -494,7 +494,7 @@ customize_cmd cust_nobeastie</programlisting>
|
|||
nueva en su sistema <application>NanoBSD</application> en
|
||||
funcionamiento dispone de los scripts <filename>updatep1</filename>
|
||||
y <filename>updatep2</filename>, ubicados en el directorio
|
||||
<filename role="directory">/root</filename>. La
|
||||
<filename class="directory">/root</filename>. La
|
||||
elección de uno u otro script depende de qué
|
||||
partición esté ejecutando el sistema,
|
||||
la primera o la segunda.</para>
|
||||
|
|
|
|||
|
|
@ -250,7 +250,7 @@
|
|||
|
||||
<para>Esto asociará por completo el repositorio
|
||||
<application>Perforce</application> al directorio
|
||||
<filename role="directory">Root</filename>
|
||||
<filename class="directory">Root</filename>
|
||||
del cliente. <emphasis>NO USE ESTE VALOR POR DEFECTO</emphasis>.
|
||||
El repositorio de &os; es enorme e intentar asociarlo y
|
||||
sincronizarse con dicho repositorio tardará muchísimo y
|
||||
|
|
@ -258,7 +258,7 @@
|
|||
sólamente la sección del repositorio en la que va a
|
||||
trabajar. Por ejemplo, hay un árbol para el proyecto
|
||||
smpng en <filename
|
||||
role="directory">//depot/projects/smpng</filename>. Una
|
||||
class="directory">//depot/projects/smpng</filename>. Una
|
||||
asociación en ese caso sería algo así:</para>
|
||||
|
||||
<programlisting>//depot/projects/smpng/... //<replaceable>cliente</replaceable>/...</programlisting>
|
||||
|
|
@ -355,7 +355,7 @@
|
|||
<para>Puede sincronizarse parte del árbol o del cliente
|
||||
especificando una ruta relativa a la orden <quote>sync</quote>.
|
||||
Por ejemplo, para sincronizar sólo el directorio
|
||||
<filename role="directory">ufs</filename>
|
||||
<filename class="directory">ufs</filename>
|
||||
del proyecto <literal>smpng</literal> ejecute lo
|
||||
siguiente:</para>
|
||||
|
||||
|
|
@ -393,7 +393,7 @@
|
|||
es un único árbol plano. Se accede a cada fichero a
|
||||
través de una
|
||||
sencilla ruta bajo el directorio <filename
|
||||
role="directory">//depot</filename>, tanto si se trata de un
|
||||
class="directory">//depot</filename>, tanto si se trata de un
|
||||
fichero de nueva creación como si proviene de una
|
||||
ramificación.
|
||||
Esto supone una gran diferencia con respecto a sistemas como CVS,
|
||||
|
|
@ -912,7 +912,7 @@
|
|||
servidor de CVS sobre cambios realizados en la rama HEAD, y dichos
|
||||
cambios se entregan a <application>Perforce</application> dentro del
|
||||
árbol <filename
|
||||
role="directory">//depot/vendor/freebsd/...</filename>.
|
||||
class="directory">//depot/vendor/freebsd/...</filename>.
|
||||
De este modo este árbol permite la ramificación y
|
||||
la integración de proyectos derivados. Cualquier proyecto
|
||||
que implique la modificación del código fuente de
|
||||
|
|
@ -969,7 +969,7 @@
|
|||
<para>La mayoría de los proyectos de &os; dentro del programa
|
||||
<quote>Google Summer of Code</quote> están en
|
||||
<filename
|
||||
role="directory">//depot/projects/soc2005/<replaceable>nombre_del_proyecto</replaceable>/...</filename>
|
||||
class="directory">//depot/projects/soc2005/<replaceable>nombre_del_proyecto</replaceable>/...</filename>
|
||||
en el servidor &os; de <application>Perforce</application>.</para>
|
||||
|
||||
<para>Entre las responsabilidades del mentor del proyecto
|
||||
|
|
|
|||
|
|
@ -3172,7 +3172,7 @@ subnet 192.168.4.0 netmask 255.255.255.0 {
|
|||
núcleo, lo hace <filename>pxeboot</filename>.
|
||||
Existen otras posibilidades interesantes, como cargar
|
||||
<filename>pxeboot</filename> desde el directorio
|
||||
<filename role="directory">/boot</filename>
|
||||
<filename class="directory">/boot</filename>
|
||||
de una unidad de CD-ROM de &os; (ya que &man.pxeboot.8; puede
|
||||
cargar un núcleo
|
||||
<filename>GENERIC</filename> surge la posibilidad de utilizar
|
||||
|
|
@ -3522,7 +3522,7 @@ options BOOTP_NFSROOT # NFS mount root filesystem using BOOTP info
|
|||
método de configuración distinto del que se
|
||||
utiliza en <filename>clone_root</filename> y en los <quote>
|
||||
scripts</quote> del sistema de <filename
|
||||
role="directory">/etc</filename>, que resultan ser un tanto
|
||||
class="directory">/etc</filename>, que resultan ser un tanto
|
||||
confusos. No obstante se pueden utilizar a modo de referencia,
|
||||
excepto si se prefiere utilizar el método que se describe
|
||||
en ellos, en cuyo caso se necesitará modificar y
|
||||
|
|
|
|||
|
|
@ -100,7 +100,7 @@
|
|||
<para>GEOM permite el acceso y control de clases —sectores de
|
||||
arranque maestros (MBR), etiquetas <acronym>BSD</acronym>, etc— por
|
||||
medio del uso de proveedores, o de los ficheros especiales de
|
||||
<filename role="directory">/dev</filename>.
|
||||
<filename class="directory">/dev</filename>.
|
||||
Capaz de trabajar con varias configuraciones de <acronym>RAID</acronym>
|
||||
por software, GEOM proporcionará transparentemente acceso al
|
||||
sistema operativo y las utilidades del mismo.</para>
|
||||
|
|
@ -171,7 +171,7 @@
|
|||
<step><para>Asegúrese de que existe un punto de montaje adecuado.
|
||||
Si este volumen se convertirá en una partición raíz,
|
||||
utilice temporalmente otro punto de montaje, como <filename
|
||||
role="directory">/mnt</filename>.</para>
|
||||
class="directory">/mnt</filename>.</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>mkdir /mnt</userinput></screen>
|
||||
</step>
|
||||
|
|
@ -209,7 +209,7 @@ XXX: What message? Put it inside the screen output above.
|
|||
<step><para>Aademás del dispositivo <filename>st0</filename>,
|
||||
este proceso debería haber creado otros dos
|
||||
dispositivos en el directorio
|
||||
<filename role="directory">/dev/stripe</filename>, incluyendo
|
||||
<filename class="directory">/dev/stripe</filename>, incluyendo
|
||||
<filename>st0a</filename> y <filename>st0c</filename>.
|
||||
Ahora se debe crear un sistema de ficheros en el dispositivo
|
||||
<filename>st0a</filename> usando la siguiente orden
|
||||
|
|
@ -273,7 +273,7 @@ XXX: What message? Put it inside the screen output above.
|
|||
particiones. Una debería ser una partición de intercambio,
|
||||
de dos veces el tamaño de la <acronym>RAM</acronym>, y todo el
|
||||
espacio restante se dedicará al sistema de ficheros raíz
|
||||
(<filename role="directory">/</filename>).
|
||||
(<filename class="directory">/</filename>).
|
||||
Es posible tener particiones aparte para otros puntos de montajes; sin
|
||||
embargo, esto multiplicará por diez el nivel de dificultad, debido
|
||||
a la alteración manual de las opciones de &man.bsdlabel.8; y
|
||||
|
|
@ -300,7 +300,7 @@ Done.</screen>
|
|||
|
||||
<note>
|
||||
<para>Esta orden debería haber creado en el directorio
|
||||
<filename role="directory">/dev/mirror</filename> los nodos de
|
||||
<filename class="directory">/dev/mirror</filename> los nodos de
|
||||
dispositivo <filename>gm0</filename>, <filename>gm0s1</filename>,
|
||||
<filename>gm0s1a</filename>, y <filename>gm0s1c</filename>.</para>
|
||||
</note>
|
||||
|
|
@ -332,7 +332,7 @@ Done.</screen>
|
|||
información y un puñado de números. Esto es bueno.
|
||||
Examine la pantalla por si hay algún mensaje de error y monte el
|
||||
dispositivo en el punto de montaje
|
||||
<filename role="directory">/mnt</filename>:</para>
|
||||
<filename class="directory">/mnt</filename>:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>mount /dev/mirror/gm0s1a /mnt</userinput></screen>
|
||||
|
||||
|
|
|
|||
|
|
@ -4901,7 +4901,7 @@ Please press any key to reboot.</screen>
|
|||
<screen>&prompt.root; <userinput>mount /dev/fd0 /mnt</userinput></screen>
|
||||
|
||||
<para>Una vez montado el disquete entre en el directorio
|
||||
<filename role="directory">/mnt</filename> :</para>
|
||||
<filename class="directory">/mnt</filename> :</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /mnt</userinput></screen>
|
||||
|
||||
|
|
|
|||
|
|
@ -281,11 +281,11 @@ no es necesario en &os; 6.0 y versiones posteriores.</para></footnote>
|
|||
<para>El mejor punto de partida es la elección del punto
|
||||
del sistema de ficheros del servidor donde estará
|
||||
físicamente ubicada la jaula. <filename
|
||||
role="directory">/usr/jail/<replaceable>nombredelajaula</replaceable></filename>
|
||||
class="directory">/usr/jail/<replaceable>nombredelajaula</replaceable></filename>
|
||||
es un buen sitio. <replaceable>nombredelajaula</replaceable>
|
||||
es el nombre de máquina que identifica a la jaula. El
|
||||
sistema de ficheros <filename
|
||||
role="directory">/usr/</filename> suele tener espacio
|
||||
class="directory">/usr/</filename> suele tener espacio
|
||||
suficiente para albergar el sistema de ficheros de la jaula que,
|
||||
cuando se trata de jaulas <quote>completas</quote>, es
|
||||
esencialmente lo necesario para alojar todos y cada uno de
|
||||
|
|
@ -308,10 +308,10 @@ no es necesario en &os; 6.0 y versiones posteriores.</para></footnote>
|
|||
<application>make</application> se instalan todos los ficheros
|
||||
de configuración necesarios. En pocas palabras,
|
||||
instala cada fichero instalable que haya en
|
||||
<filename role="directory">/usr/src/etc/</filename> en el
|
||||
directorio <filename role="directory">/etc</filename> de la
|
||||
<filename class="directory">/usr/src/etc/</filename> en el
|
||||
directorio <filename class="directory">/etc</filename> de la
|
||||
jaula, es decir, en
|
||||
<filename role="directory">$D/etc/</filename>.</para>
|
||||
<filename class="directory">$D/etc/</filename>.</para>
|
||||
</callout>
|
||||
|
||||
<callout arearefs="jaildevfs">
|
||||
|
|
@ -661,10 +661,10 @@ jail_<replaceable>www</replaceable>_devfs_ruleset="<replaceable>www_ruleset</rep
|
|||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Cada jaula se montará bajo <filename
|
||||
role="directory">/home/j</filename>.</para>
|
||||
class="directory">/home/j</filename>.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><filename role="directory">/home/j/mroot</filename>
|
||||
<para><filename class="directory">/home/j/mroot</filename>
|
||||
será la plantilla para cada jaula y la
|
||||
partición de sólo lectura para todas las
|
||||
jaulas.</para>
|
||||
|
|
@ -672,29 +672,29 @@ jail_<replaceable>www</replaceable>_devfs_ruleset="<replaceable>www_ruleset</rep
|
|||
<listitem>
|
||||
<para>Se creará un directorio vacío para
|
||||
cada jaula bajo el directorio <filename
|
||||
role="directory">/home/j</filename>.</para>
|
||||
class="directory">/home/j</filename>.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Cada jaula tendrá un directorio <filename
|
||||
role="directory">/s</filename> que estará enlazado
|
||||
class="directory">/s</filename> que estará enlazado
|
||||
con la parte de lectura-escritura del sistema.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Cada jaula tendrá su propio sistema en modo
|
||||
lectura-escritura basado en <filename
|
||||
role="directory">/home/j/skel</filename>.</para>
|
||||
class="directory">/home/j/skel</filename>.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Cada parte de lectura-escritura correspondiente a cada
|
||||
jaula se creará en <filename
|
||||
role="directory">/home/js</filename>.</para>
|
||||
class="directory">/home/js</filename>.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<note>
|
||||
<para>Se asume que las jaulas se instalarán bajo
|
||||
la partición <filename
|
||||
role="directory">/home</filename>. Por supuesto esto no
|
||||
class="directory">/home</filename>. Por supuesto esto no
|
||||
es en absoluto obligatorio, pero hay que tener en cuenta que
|
||||
debe hacerse el mismo cambio en cada uno de los ejemplos que
|
||||
se muestran más adelante.</para>
|
||||
|
|
@ -775,7 +775,7 @@ jail_<replaceable>www</replaceable>_devfs_ruleset="<replaceable>www_ruleset</rep
|
|||
ficheros de sólo lectura. Por favor,
|
||||
asegúrese de que los enlaces simbólicos
|
||||
se crean en las ubicaciones correctas: <filename
|
||||
role="directory">s/</filename>. Si se usan directorios
|
||||
class="directory">s/</filename>. Si se usan directorios
|
||||
reales o directorios erróneos la instalación
|
||||
no funcionará.</para>
|
||||
|
||||
|
|
@ -871,12 +871,12 @@ jail_www_devfs_enable="YES"</programlisting>
|
|||
<para>: La razón por la que
|
||||
<varname>jail_<replaceable>nombre</replaceable>_rootdir</varname>
|
||||
contiene <filename
|
||||
role="directory">/usr/home</filename> y no
|
||||
<filename role="directory">/home</filename> es que la ruta
|
||||
class="directory">/usr/home</filename> y no
|
||||
<filename class="directory">/home</filename> es que la ruta
|
||||
física del directorio<filename
|
||||
role="directory">/home</filename> en una instalación
|
||||
class="directory">/home</filename> en una instalación
|
||||
de &os; por omisión es <filename
|
||||
role="directory">/usr/home</filename>. La variable
|
||||
class="directory">/usr/home</filename>. La variable
|
||||
<varname>jail_<replaceable>nombre</replaceable>_rootdir</varname>
|
||||
<emphasis>no</emphasis> debe apuntar a una ruta que
|
||||
contenga un enlace simbólico porque sería
|
||||
|
|
@ -959,7 +959,7 @@ jail_www_devfs_enable="YES"</programlisting>
|
|||
<para>El primer paso es actualizar el servidor que aloja
|
||||
las jaulas de la forma habitual. Después creamos
|
||||
una plantilla de sólo lectura temporal en <filename
|
||||
role="directory">/home/j/mroot2</filename>.</para>
|
||||
class="directory">/home/j/mroot2</filename>.</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>mkdir /home/j/mroot2</userinput>
|
||||
&prompt.root; <userinput>cd /usr/src</userinput>
|
||||
|
|
@ -1008,7 +1008,7 @@ jail_www_devfs_enable="YES"</programlisting>
|
|||
<note>
|
||||
<para>Los sistemas de ficheros de lectura-escritura
|
||||
cuelgan del sistema de sólo lectura <filename
|
||||
role="directory">/s</filename> y por tanto deben
|
||||
class="directory">/s</filename> y por tanto deben
|
||||
desmontarse antes.</para>
|
||||
</note>
|
||||
</step>
|
||||
|
|
|
|||
|
|
@ -2031,7 +2031,7 @@ sasl_pwcheck_program="/usr/local/sbin/pwcheck"</programlisting>
|
|||
<screen>&prompt.user; <userinput>mail</userinput></screen>
|
||||
|
||||
<para>El contenido de la carpeta de usuario en el directorio
|
||||
<filename role="directory">/var/mail</filename> se leen
|
||||
<filename class="directory">/var/mail</filename> se leen
|
||||
automáticamente.
|
||||
Si la carpeta se encuentra vacía la aplicación termina
|
||||
su ejecución con un mensaje que indica que no ha podido
|
||||
|
|
@ -2179,7 +2179,7 @@ EOT</screen>
|
|||
|
||||
<para><application>mutt</application> lee automáticamente el
|
||||
contenido de la carpeta de correo del usuario dentro del directorio
|
||||
<filename role="directory">/var/mail</filename> y muestra por pantalla
|
||||
<filename class="directory">/var/mail</filename> y muestra por pantalla
|
||||
su contenido. Si el directorio está vacío
|
||||
<application>mutt</application>
|
||||
quedará a la espera de los comandos que pueda pasarle el
|
||||
|
|
@ -2302,7 +2302,7 @@ EOT</screen>
|
|||
|
||||
<para>El directorio por defecto que <application>pine</application>
|
||||
intenta abrir es <filename
|
||||
role="directory">inbox</filename>. Para ver el índice de
|
||||
class="directory">inbox</filename>. Para ver el índice de
|
||||
todos los mensajes recibidos pulse la tecla
|
||||
<keycap>I</keycap> o seleccione la opción de menú
|
||||
denominada
|
||||
|
|
|
|||
|
|
@ -5333,7 +5333,7 @@ drwxr-xr-x 2 robert robert 512 Nov 10 11:54 public_html</programlisting>
|
|||
|
||||
<para>Después de la instalación un administrador debe
|
||||
actualizar la base de datos alojada en local en
|
||||
<filename role="directory">/var/db/portaudit</filename>
|
||||
<filename class="directory">/var/db/portaudit</filename>
|
||||
mediante:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>portaudit -F</userinput></screen>
|
||||
|
|
|
|||
|
|
@ -143,19 +143,19 @@
|
|||
seule.</para>
|
||||
|
||||
<para>Les répertoires <filename
|
||||
role="directory">/etc</filename> et <filename
|
||||
role="directory">/var</filename> sont des disques &man.md.4;
|
||||
class="directory">/etc</filename> et <filename
|
||||
class="directory">/var</filename> sont des disques &man.md.4;
|
||||
(malloc).</para>
|
||||
|
||||
<para>La partition de configuration est montée sur le
|
||||
répertoire <filename role="directory">/cfg</filename>.
|
||||
répertoire <filename class="directory">/cfg</filename>.
|
||||
Elle contient les fichiers du répertoire <filename
|
||||
role="directory">/etc</filename> et est brièvement
|
||||
class="directory">/etc</filename> et est brièvement
|
||||
montée en lecture seule juste après le
|
||||
démarrage du système, par conséquent il
|
||||
est nécessaire de recopier les fichiers modifiés
|
||||
de <filename role="directory">/etc</filename> vers le
|
||||
répertoire <filename role="directory">/cfg</filename>
|
||||
de <filename class="directory">/etc</filename> vers le
|
||||
répertoire <filename class="directory">/cfg</filename>
|
||||
si l'on souhaite que les changements soient encore effectifs
|
||||
après le redémarrage du système.</para>
|
||||
|
||||
|
|
@ -172,11 +172,11 @@
|
|||
|
||||
<note>
|
||||
<para>La partition qui abrite <filename
|
||||
role="directory">/cfg</filename> doit être
|
||||
class="directory">/cfg</filename> doit être
|
||||
montée uniquement au démarrage et lors de la
|
||||
copie des fichiers de configuration.</para>
|
||||
|
||||
<para>Garder <filename role="directory">/cfg</filename>
|
||||
<para>Garder <filename class="directory">/cfg</filename>
|
||||
monté en permanence n'est pas une bonne idée,
|
||||
en particulier si le système
|
||||
<application>NanoBSD</application> tourne sur un
|
||||
|
|
@ -195,7 +195,7 @@
|
|||
créée à l'aide d'une simple
|
||||
procédure <filename>nanobsd.sh</filename>, qui peut
|
||||
être trouvée dans le répertoire <filename
|
||||
role="directory"><replaceable>/usr</replaceable>/src/tools/tools/nanobsd</filename>.
|
||||
class="directory"><replaceable>/usr</replaceable>/src/tools/tools/nanobsd</filename>.
|
||||
Ce programme crée une image, qui peut être
|
||||
copiée sur le support de stockage à l'aide de
|
||||
&man.dd.1;.</para>
|
||||
|
|
@ -352,7 +352,7 @@ customize_cmd cust_foo</programlisting>
|
|||
|
||||
<para>Un exemple plus utile de fonction de personnalisation
|
||||
est le suivant, qui change la taille par défaut du
|
||||
répertoire <filename role="directory">/etc</filename>
|
||||
répertoire <filename class="directory">/etc</filename>
|
||||
de 5Mo à 30Mo:</para>
|
||||
|
||||
<programlisting>cust_etc_size () (
|
||||
|
|
@ -384,7 +384,7 @@ customize_cmd cust_etc_size</programlisting>
|
|||
<listitem>
|
||||
<para><literal>cust_install_files</literal> —
|
||||
Installe les fichiers du répertoire <filename
|
||||
role="directory">nanobsd/Files</filename>, qui contient
|
||||
class="directory">nanobsd/Files</filename>, qui contient
|
||||
des programmes utiles pour l'administration
|
||||
système.</para>
|
||||
</listitem>
|
||||
|
|
@ -508,7 +508,7 @@ customize_cmd cust_nobeastie</programlisting>
|
|||
possible d'utiliser la procédure
|
||||
<filename>updatep1</filename> ou <filename>updatep2</filename>
|
||||
située dans le répertoire <filename
|
||||
role="directory">/root</filename>, en fonction de la partition
|
||||
class="directory">/root</filename>, en fonction de la partition
|
||||
qui est en cours d'utilisation sur le système.</para>
|
||||
|
||||
<para>En fonction des services disponibles sur la machine qui
|
||||
|
|
|
|||
|
|
@ -2131,7 +2131,7 @@ Success, response: OK, Success (0x20)</screen>
|
|||
les objets entrant seront stockés doit être
|
||||
créé. Le chemin d'accès par
|
||||
défaut du répertoire racine est <filename
|
||||
role="directory">/var/spool/obex</filename>. Le serveur OBEX
|
||||
class="directory">/var/spool/obex</filename>. Le serveur OBEX
|
||||
enregistrera automatiquement le service OBEX Object Push
|
||||
auprès du “daemon” SDP local. L'exemple
|
||||
ci-dessous montre comment démarrer le serveur
|
||||
|
|
@ -2508,7 +2508,7 @@ net.link.ether.bridge_ipfw=1</programlisting>
|
|||
<listitem>
|
||||
<para>Des fichiers de démarrage du système
|
||||
existent dans le répertoire <filename
|
||||
role="directory">/etc</filename> pour détecter et
|
||||
class="directory">/etc</filename> pour détecter et
|
||||
supporter le démarrage d'un système sans disque
|
||||
dur.</para>
|
||||
</listitem>
|
||||
|
|
@ -2811,7 +2811,7 @@ subnet 192.168.4.0 netmask 255.255.255.0 {
|
|||
intéressantes, comme le chargement de
|
||||
<filename>pxeboot</filename> à partir du
|
||||
répertoire <filename
|
||||
role="directory">/boot</filename> d'un CD-ROM &os;
|
||||
class="directory">/boot</filename> d'un CD-ROM &os;
|
||||
(comme &man.pxeboot.8; peut charger un noyau
|
||||
<filename>GENERIC</filename> cela rend possible
|
||||
l'utilisation de <acronym>PXE</acronym> pour
|
||||
|
|
@ -2909,7 +2909,7 @@ margaux:ha=0123456789ab:tc=.def100
|
|||
où vous avez installé
|
||||
<application>Etherboot</application>, puis rendez-vous dans
|
||||
le répertoire <filename
|
||||
role="directory">src</filename> de l'arborescence
|
||||
class="directory">src</filename> de l'arborescence
|
||||
<application>Etherboot</application> et tapez:</para>
|
||||
|
||||
<screen>
|
||||
|
|
@ -2977,7 +2977,7 @@ margaux:ha=0123456789ab:tc=.def100
|
|||
<para>Créez un répertoire à partir
|
||||
duquel <application>tftpd</application> proposera les
|
||||
fichiers, e.g. <filename
|
||||
role="directory">/tftpboot</filename>.</para>
|
||||
class="directory">/tftpboot</filename>.</para>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
|
|
@ -3004,7 +3004,7 @@ margaux:ha=0123456789ab:tc=.def100
|
|||
</procedure>
|
||||
|
||||
<para>Le répertoire <filename
|
||||
role="directory">tftpboot</filename> peut être
|
||||
class="directory">tftpboot</filename> peut être
|
||||
placé n'importe où sur le serveur.
|
||||
Assurez-vous que son emplacement est défini dans les
|
||||
fichiers <filename>inetd.conf</filename> et
|
||||
|
|
@ -3161,14 +3161,14 @@ options BOOTP_NFSROOT # NFS mount root filesystem using BOOTP info
|
|||
|
||||
<para>Les fichiers <filename>README</filename> dans le
|
||||
répertoire <filename
|
||||
role="directory">/usr/share/examples/diskless</filename>
|
||||
class="directory">/usr/share/examples/diskless</filename>
|
||||
contiennent beaucoup d'information de fond, mais, avec les
|
||||
autres exemples du répertoire <filename
|
||||
role="directory">diskless</filename>, ils documentent une
|
||||
class="directory">diskless</filename>, ils documentent une
|
||||
méthode de configuration qui est distincte de celle
|
||||
utilisée par <filename>clone_root</filename> et les
|
||||
procédures de démarrage du système de
|
||||
<filename role="directory">/etc</filename>, ce qui est un
|
||||
<filename class="directory">/etc</filename>, ce qui est un
|
||||
peu à l'origine de confusions. Utilisez-les comme
|
||||
référence uniquement, à moins que
|
||||
vous préfériez la méthode qu'ils
|
||||
|
|
@ -3337,7 +3337,7 @@ host margaux {
|
|||
configurée pour exécuter X, you devrez
|
||||
ajuster le fichier de configuration de
|
||||
<application>XDM</application>, qui envoie le journal
|
||||
d'erreurs sur <filename role="directory">/usr</filename>
|
||||
d'erreurs sur <filename class="directory">/usr</filename>
|
||||
par défaut.</para>
|
||||
</sect4>
|
||||
|
||||
|
|
@ -3353,7 +3353,7 @@ host margaux {
|
|||
<para>Dans cette situation, il y a parfois des
|
||||
problèmes avec les fichiers spéciaux de
|
||||
périphériques dans <filename
|
||||
role="directory">/dev</filename>, en raison de
|
||||
class="directory">/dev</filename>, en raison de
|
||||
différences de taille sur les entiers. Une
|
||||
solution à ce problème est d'exporter un
|
||||
répertoire à partir du serveur non-&os;, de
|
||||
|
|
@ -3478,7 +3478,7 @@ host margaux {
|
|||
<para>Pour de la documentation sur
|
||||
<application>isdn4bsd</application>, consultez le
|
||||
répertoire <filename
|
||||
role="directory">/usr/share/examples/isdn/</filename> sur
|
||||
class="directory">/usr/share/examples/isdn/</filename> sur
|
||||
votre système &os; ou sur la <ulink
|
||||
url="http://www.freebsd-support.de/i4b/">page web
|
||||
d'isdn4bsd</ulink> qui propose également des astuces,
|
||||
|
|
|
|||
|
|
@ -96,7 +96,7 @@
|
|||
Boot Records</quote>), labels <acronym>BSD</acronym>, etc.
|
||||
— par l'intermédiaire d'interfaces, ou de fichiers
|
||||
spéciaux du répertoire <filename
|
||||
role="directory">/dev</filename>. En supportant plusieurs
|
||||
class="directory">/dev</filename>. En supportant plusieurs
|
||||
configurations <acronym>RAID</acronym> logicielles, GEOM offrira
|
||||
un accès transparent au système d'exploitation et
|
||||
à ses utilitaires.</para>
|
||||
|
|
@ -176,7 +176,7 @@
|
|||
<para>Assurez-vous de l'existence d'un point de montage. Si
|
||||
ce volume doit devenir une partition racine, utilisez alors un
|
||||
autre point de montage comme <filename
|
||||
role="directory">/mnt</filename>.</para>
|
||||
class="directory">/mnt</filename>.</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>mkdir /mnt</userinput></screen>
|
||||
</step>
|
||||
|
|
@ -212,7 +212,7 @@ XXX: What message? Put it inside the screen output above.
|
|||
<para>Cette opération doit avoir créé
|
||||
deux autres périphériques dans le
|
||||
répertoire <filename
|
||||
role="directory">/dev/stripe</filename> en plus du
|
||||
class="directory">/dev/stripe</filename> en plus du
|
||||
périphérique <devicename>st0</devicename>:
|
||||
<devicename>st0a</devicename> et
|
||||
<devicename>st0c</devicename>. A ce stade, un système de fichiers
|
||||
|
|
@ -285,7 +285,7 @@ XXX: What message? Put it inside the screen output above.
|
|||
partitions. Une partition sera la partition de pagination d'une
|
||||
taille double à celle de la <acronym>RAM</acronym> et
|
||||
l'espace restant sera alloué au système de
|
||||
fichiers racine (<filename role="directory">/</filename>). Il
|
||||
fichiers racine (<filename class="directory">/</filename>). Il
|
||||
est possible d'avoir des partitions séparées pour
|
||||
les autres points de montage, cependant cela augmentera
|
||||
énormément le niveau de difficulté en
|
||||
|
|
@ -317,7 +317,7 @@ Done.</screen>
|
|||
<para>Cette commande devrait créer le fichier
|
||||
spécial de périphérique
|
||||
<devicename>gm0</devicename> sous le répertoire
|
||||
<filename role="directory">/dev/mirror</filename>.</para>
|
||||
<filename class="directory">/dev/mirror</filename>.</para>
|
||||
</note>
|
||||
|
||||
<para>Installez un label <command>fdisk</command> et un code de
|
||||
|
|
@ -350,7 +350,7 @@ Done.</screen>
|
|||
d'informations et de nombres. C'est bon signe. Contrôlez
|
||||
l'affichage à la recherche de messages d'erreur et montez
|
||||
le périphérique sur le point de montage <filename
|
||||
role="directory">/mnt</filename>:</para>
|
||||
class="directory">/mnt</filename>:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>mount /dev/mirror/gm0s1a /mnt</userinput></screen>
|
||||
|
||||
|
|
@ -513,7 +513,7 @@ ggate0
|
|||
|
||||
<para>A partir d'ici, on peut accéder au
|
||||
périphérique par l'intermédiaire du point
|
||||
de montage <filename role="directory">/mnt</filename>.</para>
|
||||
de montage <filename class="directory">/mnt</filename>.</para>
|
||||
|
||||
<note>
|
||||
<para>Il est à noter que toutes ces opérations
|
||||
|
|
|
|||
|
|
@ -799,7 +799,7 @@ pqb0.0.1.4.0 PQB0 PCI EIDE</screen>
|
|||
sur votre média d'installation dans le répertoire
|
||||
<filename>floppies/</filename> et peuvent également être
|
||||
téléchargées par FTP depuis le
|
||||
répertoire <filename role="directory">floppies</filename>,
|
||||
répertoire <filename class="directory">floppies</filename>,
|
||||
<literal>ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<replaceable><arch></replaceable>/<replaceable><version></replaceable>-RELEASE/floppies/</literal>.
|
||||
Remplacez <replaceable><arch></replaceable> et
|
||||
<replaceable><version></replaceable> avec
|
||||
|
|
|
|||
|
|
@ -328,10 +328,10 @@
|
|||
où l'environnement jail se trouvera dans le
|
||||
système de fichiers de la machine hôte. Un bon
|
||||
choix peut être <filename
|
||||
role="directory">/usr/jail/<replaceable>jailname</replaceable></filename>,
|
||||
class="directory">/usr/jail/<replaceable>jailname</replaceable></filename>,
|
||||
où <replaceable>jailname</replaceable> est le nom de
|
||||
machine identifiant l'environnement jail. Le système
|
||||
de fichiers <filename role="directory">/usr/</filename>
|
||||
de fichiers <filename class="directory">/usr/</filename>
|
||||
dispose généralement de suffisamment d'espace
|
||||
pour le système de fichiers de l'environnement jail,
|
||||
qui est pour les environnements <quote>complets</quote>,
|
||||
|
|
@ -356,10 +356,10 @@
|
|||
configuration nécessaires. Ou pour faire simple, cette
|
||||
commande installe tous les fichiers installables du
|
||||
répertoire <filename
|
||||
role="directory">/usr/src/etc/</filename> vers le
|
||||
répertoire <filename role="directory">/etc</filename>
|
||||
class="directory">/usr/src/etc/</filename> vers le
|
||||
répertoire <filename class="directory">/etc</filename>
|
||||
de l'environnement jail: <filename
|
||||
role="directory">$D/etc/</filename>.</para>
|
||||
class="directory">$D/etc/</filename>.</para>
|
||||
</callout>
|
||||
|
||||
<callout arearefs="jaildevfs">
|
||||
|
|
|
|||
|
|
@ -352,7 +352,7 @@
|
|||
</indexterm>
|
||||
|
||||
<para>Le nouveau noyau sera copié dans le répertoire
|
||||
<filename role="directory">/boot/kernel</filename> avec le nom
|
||||
<filename class="directory">/boot/kernel</filename> avec le nom
|
||||
<filename>/boot/kernel/kernel</filename> et l'ancien noyau sera renommé en
|
||||
<filename>/boot/kernel.old/kernel</filename>. Maintenant, arrêtez
|
||||
le système et redémarrez pour utiliser votre
|
||||
|
|
|
|||
|
|
@ -1507,7 +1507,7 @@ freefall MX 20 who.cdrom.com</programlisting>
|
|||
la configuration se fait à un haut niveau d'abstraction.
|
||||
Les fichiers de configuration &man.m4.1; se trouvent dans le
|
||||
répertoire <filename
|
||||
role="directory">/usr/src/usr.sbin/sendmail/cf</filename>.</para>
|
||||
class="directory">/usr/src/usr.sbin/sendmail/cf</filename>.</para>
|
||||
|
||||
<para>Si vous n'avez pas installé toutes les sources du
|
||||
système, l'ensemble des fichiers de configuration de
|
||||
|
|
@ -1521,7 +1521,7 @@ freefall MX 20 who.cdrom.com</programlisting>
|
|||
|
||||
<para>Cette extraction ne donne lieu qu'à une centaine de
|
||||
kilo-octets. Le fichier <filename>README</filename> dans le
|
||||
répertoire <filename role="directory">cf</filename>
|
||||
répertoire <filename class="directory">cf</filename>
|
||||
pourra faire office d'une introduction à la configuration
|
||||
&man.m4.1;.</para>
|
||||
|
||||
|
|
@ -1534,7 +1534,7 @@ freefall MX 20 who.cdrom.com</programlisting>
|
|||
|
||||
<para>Tout d'abord, vous devez créer votre fichier
|
||||
<filename>.mc</filename>. Le répertoire <filename
|
||||
role="directory">/usr/src/usr.sbin/sendmail/cf/cf</filename>
|
||||
class="directory">/usr/src/usr.sbin/sendmail/cf/cf</filename>
|
||||
contient quelques exemples. En supposant que vous avez
|
||||
appelé votre fichier <filename>foo.mc</filename>, tout ce
|
||||
dont vous avez besoin de faire pour le convertir en un fichier
|
||||
|
|
@ -1738,7 +1738,7 @@ hostname=_HOSTNAME_</programlisting>
|
|||
<para><filename role="package">mail/ssmtp</filename> dispose
|
||||
d'autres options. Consultez le fichier de configuration
|
||||
d'exemple dans le répertoire <filename
|
||||
role="directory">/usr/local/etc/ssmtp</filename> ou la page de
|
||||
class="directory">/usr/local/etc/ssmtp</filename> ou la page de
|
||||
manuel de <application>ssmtp</application> pour quelques
|
||||
exemples et plus d'informations.</para>
|
||||
|
||||
|
|
@ -2084,7 +2084,7 @@ sasl_pwcheck_program="/usr/local/sbin/pwcheck"</programlisting>
|
|||
<screen>&prompt.user; <userinput>mail</userinput></screen>
|
||||
|
||||
<para>Le contenu de la boîte aux lettres de l'utilisateur
|
||||
dans <filename role="directory">/var/mail</filename> est
|
||||
dans <filename class="directory">/var/mail</filename> est
|
||||
automatiquement lu par l'utilitaire <command>mail</command>.
|
||||
Si la boîte est vide, l'utilitaire rend la main avec un
|
||||
message indiquant qu'aucun courrier électronique ne
|
||||
|
|
@ -2241,7 +2241,7 @@ EOT</screen>
|
|||
|
||||
<para><application>mutt</application> lira automatiquement le
|
||||
contenu de la boîte aux lettres de l'utilisateur dans
|
||||
<filename role="directory">/var/mail</filename> et en affiche
|
||||
<filename class="directory">/var/mail</filename> et en affiche
|
||||
le contenu le cas échéant. Si aucun message
|
||||
n'est trouvé dans cette boîte, alors
|
||||
<application>mutt</application> attendra une commande de
|
||||
|
|
@ -2381,7 +2381,7 @@ EOT</screen>
|
|||
|
||||
<para>Le répertoire ouvert par défaut par
|
||||
<application>pine</application> est <filename
|
||||
role="directory">inbox</filename>. Pour afficher l'index des
|
||||
class="directory">inbox</filename>. Pour afficher l'index des
|
||||
messages, appuyez sur <keycap>I</keycap>, ou
|
||||
sélectionnez l'option <guimenuitem>MESSAGE
|
||||
INDEX</guimenuitem> comme montré ci-dessous:</para>
|
||||
|
|
|
|||
|
|
@ -2691,11 +2691,11 @@ doc/zh_*</screen>
|
|||
<application>Portsnap</application> ne met pas à jour
|
||||
le catalogue des logiciels portés directement dans le
|
||||
répertoire <filename
|
||||
role="directory">/usr/ports</filename>; le logiciel travaille
|
||||
class="directory">/usr/ports</filename>; le logiciel travaille
|
||||
plutôt par défaut sur une version
|
||||
compressée de l'arborescence des logiciels
|
||||
portés dans le répertoire <filename
|
||||
role="directory">/var/db/portsnap</filename>. Cette copie
|
||||
class="directory">/var/db/portsnap</filename>. Cette copie
|
||||
compressée est ensuite utilisée pour mettre
|
||||
à jour le catalogue des logiciels portés.</para>
|
||||
|
||||
|
|
@ -2704,8 +2704,8 @@ doc/zh_*</screen>
|
|||
installé à partir du catalogue des logiciels
|
||||
portés de &os;, alors l'emplacement par défaut
|
||||
pour son instantané compressé sera <filename
|
||||
role="directory">/usr/local/portsnap</filename> au lieu de
|
||||
<filename role="directory">/var/db/portsnap</filename>.</para>
|
||||
class="directory">/usr/local/portsnap</filename> au lieu de
|
||||
<filename class="directory">/var/db/portsnap</filename>.</para>
|
||||
</note>
|
||||
</sect2>
|
||||
|
||||
|
|
@ -2754,8 +2754,8 @@ doc/zh_*</screen>
|
|||
instantané compressé de
|
||||
l'intégralité de l'arborescence des logiciels
|
||||
portés dans <filename
|
||||
role="directory">/var/db/portsnap</filename> (ou <filename
|
||||
role="directory">/usr/local/portsnap</filename> si
|
||||
class="directory">/var/db/portsnap</filename> (ou <filename
|
||||
class="directory">/usr/local/portsnap</filename> si
|
||||
<application>Portsnap</application> a été
|
||||
installé à partir du catalogue des logiciels
|
||||
portés). Au début de l'année 2006, cela
|
||||
|
|
@ -2768,7 +2768,7 @@ doc/zh_*</screen>
|
|||
été récupéré, une copie
|
||||
utilisable de l'arborescence des logiciels portés peut
|
||||
être extraite dans le répertoire <filename
|
||||
role="directory">/usr/ports</filename>. Cela est
|
||||
class="directory">/usr/ports</filename>. Cela est
|
||||
nécessaire même si une arborescence a
|
||||
déjà été créée dans
|
||||
ce répertoire (par exemple en utilisant
|
||||
|
|
@ -2782,7 +2782,7 @@ doc/zh_*</screen>
|
|||
|
||||
<note>
|
||||
<para>Dans l'installation par défaut de &os; <filename
|
||||
role="directory">/usr/ports</filename> n'est pas
|
||||
class="directory">/usr/ports</filename> n'est pas
|
||||
créé. Si vous utilisez &os; 6.0-RELEASE,
|
||||
ce répertoire doit être créé avant
|
||||
d'utiliser la commande <command>portsnap</command>. Sur les
|
||||
|
|
@ -2802,7 +2802,7 @@ doc/zh_*</screen>
|
|||
des logiciels portés ait été
|
||||
récupéré puis décompressé
|
||||
dans le répertoire <filename
|
||||
role="directory">/usr/ports</filename>, la mise à jour
|
||||
class="directory">/usr/ports</filename>, la mise à jour
|
||||
du catalogue se divise en deux étapes: la
|
||||
récupération (<emphasis>fetch</emphasis>) des
|
||||
mises à jour de l'instantané, et leur
|
||||
|
|
@ -2860,7 +2860,7 @@ doc/zh_*</screen>
|
|||
<command>portsnap</command> de mettre à jour son
|
||||
instantané compressé et les fichiers
|
||||
<filename>INDEX</filename> du répertoire <filename
|
||||
role="directory">/usr/ports</filename>, et enverra un courrier
|
||||
class="directory">/usr/ports</filename>, et enverra un courrier
|
||||
électronique si un logiciel porté
|
||||
installé n'est pas à jour:</para>
|
||||
|
||||
|
|
|
|||
|
|
@ -144,9 +144,9 @@
|
|||
|
||||
<para>Avant de configurer PPP sur votre machine, vérifiez
|
||||
que <command>pppd</command> est bien dans le répertoire
|
||||
<filename role="directory">/usr/sbin</filename> et que le
|
||||
<filename class="directory">/usr/sbin</filename> et que le
|
||||
répertoire <filename
|
||||
role="directory">/etc/ppp</filename> existe.</para>
|
||||
class="directory">/etc/ppp</filename> existe.</para>
|
||||
|
||||
<para>La commande <command>pppd</command> peut fonctionner selon
|
||||
deux modes:</para>
|
||||
|
|
@ -886,17 +886,17 @@ ppp_profile="adsl"</programlisting>
|
|||
logiciel porté place un ensemble de fichiers de
|
||||
configuration très bien commentés dans le
|
||||
répertoire <filename
|
||||
role="directory"><replaceable>PREFIX</replaceable>/etc/mpd/</filename>.
|
||||
class="directory"><replaceable>PREFIX</replaceable>/etc/mpd/</filename>.
|
||||
Notez qu'ici <replaceable>PREFIX</replaceable>
|
||||
représente le répertoire dans lequel les
|
||||
logiciels portés sont installés, par
|
||||
défaut le répertoire <filename
|
||||
role="directory">/usr/local/</filename>. Un guide complet
|
||||
class="directory">/usr/local/</filename>. Un guide complet
|
||||
pour la configuration de <application>mpd</application> est
|
||||
disponible dans le format HTML, une fois que le logiciel a
|
||||
été installé. Il se trouve dans le
|
||||
répertoire <filename
|
||||
role="directory"><replaceable>PREFIX</replaceable>/share/doc/mpd/</filename>.
|
||||
class="directory"><replaceable>PREFIX</replaceable>/share/doc/mpd/</filename>.
|
||||
Voici un exemple de configuration pour se connecter à
|
||||
un service ADSL à l'aide de
|
||||
<application>mpd</application>. La configuration est
|
||||
|
|
|
|||
|
|
@ -3330,7 +3330,7 @@ VII. References<co id="co-ref"/></programlisting>
|
|||
aidera à déterminer la révision. Pour
|
||||
les logiciels portés, le numéro de version est
|
||||
listé après le nom du logiciel dans <filename
|
||||
role="directory">/var/db/pkg</filename>. Si le
|
||||
class="directory">/var/db/pkg</filename>. Si le
|
||||
système ne se synchronise pas avec le
|
||||
référentiel <acronym>CVS</acronym> &os; et ne
|
||||
recompile pas les sources quotidiennement, il y a des
|
||||
|
|
|
|||
|
|
@ -969,8 +969,8 @@ EndSection</programlisting>
|
|||
d'<application>&xfree86;</application> 4.3.0. Depuis
|
||||
<application>&xfree86;</application> 4.3.0, toutes les polices
|
||||
sous X11 se trouvant dans les répertoires <filename
|
||||
role="directory">/usr/local/lib/X11/fonts/</filename> et
|
||||
<filename role="directory">~/.fonts/</filename> sont
|
||||
class="directory">/usr/local/lib/X11/fonts/</filename> et
|
||||
<filename class="directory">~/.fonts/</filename> sont
|
||||
automatiquement disponibles pour l'anticrénelage avec
|
||||
les applications compatibles Xft. Toutes les applications ne
|
||||
sont pas compatibles Xft, mais de nombreuses ont
|
||||
|
|
@ -1014,9 +1014,9 @@ EndSection</programlisting>
|
|||
<para>Comme précisé précédemment,
|
||||
l'ensemble des polices de caractères du
|
||||
répertoire <filename
|
||||
role="directory">/usr/local/lib/X11/fonts/</filename> comme du
|
||||
class="directory">/usr/local/lib/X11/fonts/</filename> comme du
|
||||
répertoire <filename
|
||||
role="directory">~/.fonts/</filename> sont disponibles pour
|
||||
class="directory">~/.fonts/</filename> sont disponibles pour
|
||||
les applications compatibles Xft. Si vous désirez
|
||||
ajouter un autre répertoire en dehors des ces deux
|
||||
là, ajoutez une ligne similaire à la suivante au
|
||||
|
|
|
|||
|
|
@ -358,7 +358,7 @@
|
|||
kiadásokban alapértelmezés szerint
|
||||
található egy <filename>pf.conf</filename>
|
||||
állomány az <filename
|
||||
role="directory">/etc</filename>
|
||||
class="directory">/etc</filename>
|
||||
könyvtárban.</para>
|
||||
</note>
|
||||
|
||||
|
|
|
|||
|
|
@ -280,25 +280,25 @@
|
|||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>ncvs@ - a proposito di <filename
|
||||
role="directory">/home/ncvs</filename>, il repository dei
|
||||
class="directory">/home/ncvs</filename>, il repository dei
|
||||
src</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>pcvs@ - a proposito di <filename
|
||||
role="directory">/home/pcvs</filename>, il repository dei
|
||||
class="directory">/home/pcvs</filename>, il repository dei
|
||||
port</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>dcvs@ - a proposito di <filename
|
||||
role="directory">/home/dcvs</filename>, il repository dei
|
||||
class="directory">/home/dcvs</filename>, il repository dei
|
||||
doc</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>projcvs@ - a proposito di <filename
|
||||
role="directory">/home/projcvs</filename>, il repository dei
|
||||
class="directory">/home/projcvs</filename>, il repository dei
|
||||
progetti di terze parti</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
|
|
|||
|
|
@ -91,7 +91,7 @@
|
|||
<para>GEOM permette l'accesso e il controllo alle classi — Master Boot
|
||||
Records, <acronym>BSD</acronym> labels, ecc — attraverso l'uso
|
||||
di forniture o di di files speciali in <filename
|
||||
role="directory">/dev</filename>. Mediante il supporto di vari
|
||||
class="directory">/dev</filename>. Mediante il supporto di vari
|
||||
software di configurazione<acronym>RAID</acronym> , GEOM fornisce un
|
||||
accesso "trasparente" al sistema operativo
|
||||
e alle utilità di sistema.</para>
|
||||
|
|
@ -167,7 +167,7 @@
|
|||
<para>Assicurati che esiste una appropriato mount point. Se il volume
|
||||
in questione diventerà una partizione di root, allora usa
|
||||
temporaneamente un mount point diverso,ad esempio <filename
|
||||
role="directory">/mnt</filename>:</para>
|
||||
class="directory">/mnt</filename>:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>mkdir /mnt</userinput></screen>
|
||||
</step>
|
||||
|
|
@ -199,7 +199,7 @@
|
|||
|
||||
<step>
|
||||
<para>Questa procedura dovrebbe aver creato altri due device in
|
||||
<filename role="directory">/dev/stripe</filename> in aggiunta a
|
||||
<filename class="directory">/dev/stripe</filename> in aggiunta a
|
||||
<devicename>st0</devicename>. Nella fattispecie
|
||||
<devicename>st0a</devicename> e <devicename>st0c</devicename>.
|
||||
Ora bisogna creare un filesystem nel device
|
||||
|
|
@ -261,7 +261,7 @@
|
|||
<para>Comincia installando &os; sul primo disco creando solamente due
|
||||
partizioni. Una dovrebbe essere una partizione di swap, pari al doppio
|
||||
della <acronym>RAM</acronym> presente nel sistema e il resto dello spazio
|
||||
dedicato al filesystem di root (<filename role="directory">/</filename>).
|
||||
dedicato al filesystem di root (<filename class="directory">/</filename>).
|
||||
È possibile creare partizioni separate per gli altri mount points,
|
||||
aumentando parecchio la difficoltà di realizzazione del progetto;
|
||||
questo è dovuto alla necessità di alterare manualmente i
|
||||
|
|
@ -290,7 +290,7 @@ Done.</screen>
|
|||
<para>Questo comando dovrebbe ora avere creato i nodi di
|
||||
device<devicename>gm0</devicename>,<devicename>gm0s1</devicename>,
|
||||
<devicename>gm0s1a</devicename> e <devicename>gm0s1c</devicename> nella
|
||||
directory <filename role="directory">/dev/mirror</filename>.</para>
|
||||
directory <filename class="directory">/dev/mirror</filename>.</para>
|
||||
</note>
|
||||
|
||||
<para>Crea una label generica e un codice di boot nel device
|
||||
|
|
@ -319,7 +319,7 @@ Done.</screen>
|
|||
<para>Questo dovrebbe causare la visualizzazione di un bel pò di
|
||||
numeri e informazioni varie da parte del sistema. È corretto.
|
||||
Esamina bene lo schermo per vedere se ci sono messaggi di errore e monta
|
||||
il device in <filename role="directory">/mnt</filename>:</para>
|
||||
il device in <filename class="directory">/mnt</filename>:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>mount /dev/mirror/gm0s1a /mnt</userinput></screen>
|
||||
|
||||
|
|
|
|||
|
|
@ -3261,9 +3261,9 @@ To change any of these settings later, edit /etc/rc.conf
|
|||
specifica il file di <filename>log</filename>; di default; comunque,
|
||||
quando viene usato <literal>syslogd</literal> tutte le attività
|
||||
di log saranno inviate al demone di log del sistema. La directory
|
||||
<filename role="directory">/host</filename> è usata per
|
||||
<filename class="directory">/host</filename> è usata per
|
||||
montare un filesystem esportato da un host remoto, mentre
|
||||
la directory <filename role="directory">/net</filename> è
|
||||
la directory <filename class="directory">/net</filename> è
|
||||
usata per montare un filesystem esportato da un indirizzo
|
||||
<acronym>IP</acronym>. Il file <filename>/etc/amd.map</filename>
|
||||
definisce le opzioni di default per le esportazioni
|
||||
|
|
@ -4916,7 +4916,7 @@ Please press any key to reboot.</screen>
|
|||
<screen>&prompt.root; <userinput>mount /dev/fd0 /mnt</userinput></screen>
|
||||
|
||||
<para>Adesso che hai il tuo floppy montato, portati nella directory
|
||||
<filename role="directory">/mnt</filename>:</para>
|
||||
<filename class="directory">/mnt</filename>:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /mnt</userinput></screen>
|
||||
|
||||
|
|
|
|||
|
|
@ -267,10 +267,10 @@
|
|||
il miglior punto in cui iniziare. Questo sarà il punto
|
||||
in cui la jail risiederà fisicamente nel file system del
|
||||
sistema host. Una buona scelta può essere
|
||||
<filename role="directory">/usr/jail/<replaceable>nomejail</replaceable></filename>,
|
||||
<filename class="directory">/usr/jail/<replaceable>nomejail</replaceable></filename>,
|
||||
dove <replaceable>nomejail</replaceable> è il nome host
|
||||
che identifica la jail. Il file system
|
||||
<filename role="directory">/usr/</filename> in genere ha abbastanza
|
||||
<filename class="directory">/usr/</filename> in genere ha abbastanza
|
||||
spazio vuoto per il file system delle jail, che per una
|
||||
jail <quote>completa</quote> è, in pratica, una replica di
|
||||
ogni file presente in una installazione base di &os;</para>
|
||||
|
|
@ -290,10 +290,10 @@
|
|||
<application>make</application> installa ogni file di
|
||||
configuazione richiesto. In parole povere, installa ogni
|
||||
file di
|
||||
<filename role="directory">/usr/src/etc/</filename> nella
|
||||
directory <filename role="directory">/etc</filename>
|
||||
<filename class="directory">/usr/src/etc/</filename> nella
|
||||
directory <filename class="directory">/etc</filename>
|
||||
dell'ambiente jail:
|
||||
<filename role="directory">$D/etc/</filename>.</para>
|
||||
<filename class="directory">$D/etc/</filename>.</para>
|
||||
</callout>
|
||||
|
||||
<callout arearefs="jaildevfs">
|
||||
|
|
@ -613,41 +613,41 @@ jail_<replaceable>www</replaceable>_devfs_ruleset="<replaceable>www_ruleset</rep
|
|||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Ogni jail sarà montata sotto la directory
|
||||
<filename role="directory">/home/j</filename>.</para>
|
||||
<filename class="directory">/home/j</filename>.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><filename role="directory">/home/j/mroot</filename> è
|
||||
<para><filename class="directory">/home/j/mroot</filename> è
|
||||
il template per ogni jail e la partizione in sola lettura per
|
||||
tutte le jail.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Una directory vuota sarà creata per ogni jail sotto
|
||||
la directory <filename role="directory">/home/j</filename>.</para>
|
||||
la directory <filename class="directory">/home/j</filename>.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Ogni jail avrà una directory <filename
|
||||
role="directory">/s</filename>, che sarà linkata
|
||||
class="directory">/s</filename>, che sarà linkata
|
||||
alla porzione del sistema in lettura e scrittura.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Ogni jail ha il suo sistema in lettura e scrittura in
|
||||
<filename role="directory">/home/j/skel</filename>.</para>
|
||||
<filename class="directory">/home/j/skel</filename>.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Ogni spazio di jail (la porzione in lettura e scrittura di
|
||||
ogni jail) sarà creato in <filename
|
||||
role="directory">/home/js</filename>.</para>
|
||||
class="directory">/home/js</filename>.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<note>
|
||||
<para>Si assume che le jail siano posizionate sotto la partizione
|
||||
<filename role="directory">/home</filename>. Di sicuro, questo
|
||||
<filename class="directory">/home</filename>. Di sicuro, questo
|
||||
può essere modificato con qualcosa di diverso, ma questo
|
||||
cambiamento dovrà essere tenuto in considerazione
|
||||
negli esempi più avanti.</para>
|
||||
|
|
@ -725,7 +725,7 @@ jail_<replaceable>www</replaceable>_devfs_ruleset="<replaceable>www_ruleset</rep
|
|||
<para>Ora, linkiamo in modo simbolico il file system in lettura
|
||||
e scrittura nel file system di sola lettura. Assicuriamoci
|
||||
che i link simbolici siano creati nelle posizioni corrette in
|
||||
<filename role="directory">s/</filename>. La creazione di
|
||||
<filename class="directory">s/</filename>. La creazione di
|
||||
directory in posti sbagliati causerà un fallimento
|
||||
durante l'installazione.</para>
|
||||
|
||||
|
|
@ -821,12 +821,12 @@ jail_www_devfs_enable="YES"</programlisting>
|
|||
<para>La ragione del perchè la variabile
|
||||
<varname>jail_<replaceable>nome</replaceable>_rootdir</varname>
|
||||
è settata a <filename
|
||||
role="directory">/usr/home</filename> invece di
|
||||
<filename role="directory">/home</filename> è che
|
||||
class="directory">/usr/home</filename> invece di
|
||||
<filename class="directory">/home</filename> è che
|
||||
il percorso reale della directory <filename
|
||||
role="directory">/home</filename> in una installazione
|
||||
class="directory">/home</filename> in una installazione
|
||||
standard di &os; è <filename
|
||||
role="directory">/usr/home</filename>. La variabile
|
||||
class="directory">/usr/home</filename>. La variabile
|
||||
<varname>jail_<replaceable>nome</replaceable>_rootdir</varname>
|
||||
<emphasis>non</emphasis> deve essere settata a un percorso
|
||||
che include link simbolici, altrimenti la jail
|
||||
|
|
@ -906,7 +906,7 @@ jail_www_devfs_enable="YES"</programlisting>
|
|||
<para>Il primo passo è aggiornare il sistema host nella
|
||||
maniera usuale. Quindi creiamo un template temporaneo
|
||||
in sola lettura in <filename
|
||||
role="directory">/home/j/mroot2</filename>.</para>
|
||||
class="directory">/home/j/mroot2</filename>.</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>mkdir /home/j/mroot2</userinput>
|
||||
&prompt.root; <userinput>cd /usr/src</userinput>
|
||||
|
|
@ -955,7 +955,7 @@ jail_www_devfs_enable="YES"</programlisting>
|
|||
<note>
|
||||
<para>I sistemi in lettura e scrittura sono attaccati al
|
||||
sistema in sola lettura
|
||||
(<filename role="directory">/s</filename>) e devono essere
|
||||
(<filename class="directory">/s</filename>) e devono essere
|
||||
smontati.</para>
|
||||
</note>
|
||||
</step>
|
||||
|
|
|
|||
|
|
@ -290,7 +290,7 @@
|
|||
|
||||
<step>
|
||||
<para>Entra nella directory <filename
|
||||
role="directory">/usr/src</filename>:</para>
|
||||
class="directory">/usr/src</filename>:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /usr/src</userinput></screen>
|
||||
</step>
|
||||
|
|
|
|||
|
|
@ -443,7 +443,7 @@ multi on</programlisting>
|
|||
poterli usare. Se hai scelto di mettere gli
|
||||
eseguibili di <application>&mathematica;</application>
|
||||
nella directory
|
||||
<filename role="directory">/usr/local/bin</filename>,
|
||||
<filename class="directory">/usr/local/bin</filename>,
|
||||
troverai in questa directory dei link simbolici chiamati
|
||||
<filename>math</filename>, <filename>mathematica</filename>,
|
||||
<filename>Mathematica</filename>, e
|
||||
|
|
|
|||
|
|
@ -2400,7 +2400,7 @@ doc/zh_*</screen>
|
|||
|
||||
<note>
|
||||
<para>Nell'installazione di default la directory
|
||||
<filename role="directory">/usr/ports</filename>
|
||||
<filename class="directory">/usr/ports</filename>
|
||||
non viene creata. Se usi &os; 6.0-RELEASE,
|
||||
la directory dovrebbe essere creata prima di
|
||||
usare <command>portsnap</command>. Su versioni
|
||||
|
|
|
|||
|
|
@ -3715,7 +3715,7 @@ dhcpd_ifaces="dc0"</programlisting>
|
|||
</row>
|
||||
|
||||
<row>
|
||||
<entry><filename role="directory">/etc/namedb</filename></entry>
|
||||
<entry><filename class="directory">/etc/namedb</filename></entry>
|
||||
|
||||
<entry>Directory dove risiedono le
|
||||
informazioni di zona di BIND.</entry>
|
||||
|
|
@ -3734,10 +3734,10 @@ dhcpd_ifaces="dc0"</programlisting>
|
|||
A seconda di come certe zone sono configurate
|
||||
sul server, i file relativi a quelle zone possono essere
|
||||
trovate nelle sottodirectory <filename
|
||||
role="directory">master</filename>, <filename
|
||||
role="directory">slave</filename>, or <filename
|
||||
role="directory">dynamic</filename> della directory
|
||||
<filename role="directory">/etc/namedb</filename>.
|
||||
class="directory">master</filename>, <filename
|
||||
class="directory">slave</filename>, or <filename
|
||||
class="directory">dynamic</filename> della directory
|
||||
<filename class="directory">/etc/namedb</filename>.
|
||||
Questi file contengono le informazioni <acronym>DNS</acronym>
|
||||
che saranno distribuite dal name server in risposta alle query.</para>
|
||||
</sect2>
|
||||
|
|
@ -3786,7 +3786,7 @@ dhcpd_ifaces="dc0"</programlisting>
|
|||
</indexterm>
|
||||
|
||||
<para>I file di configurazione per <application>named</application>
|
||||
al corrente risiedono nella directory <filename role="directory">
|
||||
al corrente risiedono nella directory <filename class="directory">
|
||||
/etc/named</filename> e necessiteranno di modifiche prima
|
||||
dell'uso, a meno che non si voglia un semplice resolver.
|
||||
Qui è dove la maggior pare della configurazione viene
|
||||
|
|
@ -3796,7 +3796,7 @@ dhcpd_ifaces="dc0"</programlisting>
|
|||
<title>Usando <command>make-localhost</command></title>
|
||||
|
||||
<para>Per configurare una zona master per il localhost
|
||||
visita la directory <filename role="directory">/etc/namedb</filename>
|
||||
visita la directory <filename class="directory">/etc/namedb</filename>
|
||||
ed esegui il seguente comando:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>sh make-localhost</userinput></screen>
|
||||
|
|
|
|||
|
|
@ -1250,7 +1250,7 @@
|
|||
に関する重要なニュースと案内</emphasis></para>
|
||||
|
||||
<para><quote>Ports Collection</quote> (<filename
|
||||
role="directory">/usr/ports</filename>) の開発者、
|
||||
class="directory">/usr/ports</filename>) の開発者、
|
||||
作成者およびユーザへの重要なニュース。
|
||||
アーキテクチャ/インフラストラクチャの変更、新しい機能、
|
||||
重要なアップグレードの案内、
|
||||
|
|
@ -1268,7 +1268,7 @@
|
|||
のバグに関する議論</emphasis></para>
|
||||
|
||||
<para><quote>Ports Collection</quote> (<filename
|
||||
role="directory">/usr/ports</filename>) の障害報告や
|
||||
class="directory">/usr/ports</filename>) の障害報告や
|
||||
新たな ports や変更についての提案についての議論。
|
||||
これは技術的なメーリングリストなので、
|
||||
厳密に技術的な内容のみが扱われます。</para>
|
||||
|
|
|
|||
|
|
@ -811,7 +811,7 @@ Certificate information:
|
|||
一時的な認証であれば、サーバとの一回のセッションで有効期限が切れるため、
|
||||
次回の接続時にはもう一度検証が行われます。
|
||||
恒常的な認証を選んだ場合には、認証のための証明書が
|
||||
<filename role="directory">~/.subversion/auth/</filename> に保存され、
|
||||
<filename class="directory">~/.subversion/auth/</filename> に保存され、
|
||||
有効期限が切れるまでは、フィンガープリントの確認は求められません。</para>
|
||||
|
||||
<para>ファイアウォールまたは他の問題のため、<acronym>HTTPS</acronym>
|
||||
|
|
|
|||
|
|
@ -1514,7 +1514,7 @@
|
|||
тухай чухал мэдээнүүд болон зааврууд</emphasis></para>
|
||||
|
||||
<para><quote>Портын цуглуулгын</quote> (<filename
|
||||
role="directory">/usr/ports</filename>) хөгжүүлэгчид, порт хийгчид
|
||||
class="directory">/usr/ports</filename>) хөгжүүлэгчид, порт хийгчид
|
||||
болон хэрэглэгчдэд зориулсан архитектур/дэд бүтцийн өөрчлөлтүүд,
|
||||
шинэ боломжууд, маш чухал шинэчлэх зааврууд болон хувилбар
|
||||
инженерчлэлийн мэдээлэл зэрэг чухал мэдээнүүд. Энэ нь бага
|
||||
|
|
|
|||
|
|
@ -757,7 +757,7 @@ Certificate information:
|
|||
Түр зуурын сертификат нь сервертэй хийх нэг удаагийн
|
||||
сессээр дуусгавар болох бөгөөд дараагийн удаа шалгах
|
||||
алхам дахин хийгдэх болно. Сертификатыг бүрмөсөн зөвшөөрснөөр
|
||||
нэвтрэх эрхийг <filename role="directory">~/.subversion/auth/</filename>
|
||||
нэвтрэх эрхийг <filename class="directory">~/.subversion/auth/</filename>
|
||||
санд хадгалж сертификатын хугацаа дуустал хэрэглэгчээс
|
||||
хурууны хээг дахин шалгахыг асуудаггүй.</para>
|
||||
|
||||
|
|
|
|||
|
|
@ -1761,7 +1761,7 @@
|
|||
|
||||
<para>Belangrijk nieuws voor ontwikkelaars, porters en gebruikers
|
||||
van de <quote>Portscollectie</quote> (<filename
|
||||
role="directory">/usr/ports</filename>), waaronder veranderingen
|
||||
class="directory">/usr/ports</filename>), waaronder veranderingen
|
||||
aan de architectuur/infrastructuur, nieuwe mogelijkheden,
|
||||
kritische opwaardeerinstructies, en uitgave-informatie. Dit is
|
||||
een mailinglijst met een laag volume, bedoeld voor
|
||||
|
|
|
|||
|
|
@ -294,9 +294,9 @@
|
|||
beginpunt. Hier zal de jail fysiek te vinden zijn binnen
|
||||
het bestandssysteem van het host systeem. Een goede keuze
|
||||
kan <filename
|
||||
role="directory">/usr/jail<replaceable>jailnaam</replaceable></filename>
|
||||
class="directory">/usr/jail<replaceable>jailnaam</replaceable></filename>
|
||||
zijn, waar <replaceable>jailnaam</replaceable> de naam is van de
|
||||
jail. Het <filename role="directory">/usr</filename>
|
||||
jail. Het <filename class="directory">/usr</filename>
|
||||
bestandssysteem heeft meestal genoeg ruimte voor het jail
|
||||
bestandssysteem, wat voor een <quote>complete</quote> jail
|
||||
betekend dat het eigenlijk een replica is van elk bestand
|
||||
|
|
@ -321,10 +321,10 @@
|
|||
<application>make</application> installeert elk benodigd
|
||||
configuratie bestand. In simpelere termen, het installeert
|
||||
alle installeerbare bestanden in
|
||||
<filename role="directory">/usr/src/etc</filename> naar de
|
||||
<filename role="directory">/etc</filename> directory van
|
||||
<filename class="directory">/usr/src/etc</filename> naar de
|
||||
<filename class="directory">/etc</filename> directory van
|
||||
de jail omgeving:
|
||||
<filename role="directory">$D/etc</filename>.</para>
|
||||
<filename class="directory">$D/etc</filename>.</para>
|
||||
</callout>
|
||||
|
||||
<callout arearefs="jaildevfs">
|
||||
|
|
@ -672,11 +672,11 @@ jail_<replaceable>www</replaceable>_devfs_ruleset="<replaceable>www_ruleset</rep
|
|||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Elke jail zal gekopeld worden onder de <filename
|
||||
role="directory">/home/j</filename> directory.</para>
|
||||
class="directory">/home/j</filename> directory.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><filename role="directory">/home/j/mroot</filename> is
|
||||
<para><filename class="directory">/home/j/mroot</filename> is
|
||||
de template voor elke jail en tevens de alleen-lezen
|
||||
partitie voor elke jail.</para>
|
||||
</listitem>
|
||||
|
|
@ -684,12 +684,12 @@ jail_<replaceable>www</replaceable>_devfs_ruleset="<replaceable>www_ruleset</rep
|
|||
<listitem>
|
||||
<para>Voor elke jail zal een lege directory structuur
|
||||
gemaakt worden, welke valt onder de <filename
|
||||
role="directory">/home/j</filename> directory.</para>
|
||||
class="directory">/home/j</filename> directory.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Elke jail heeft een <filename
|
||||
role="directory">/s</filename> directory, welke
|
||||
class="directory">/s</filename> directory, welke
|
||||
gekoppeld zal worden aan het beschrijfbare gedeelte van
|
||||
het systeem.</para>
|
||||
</listitem>
|
||||
|
|
@ -697,20 +697,20 @@ jail_<replaceable>www</replaceable>_devfs_ruleset="<replaceable>www_ruleset</rep
|
|||
<listitem>
|
||||
<para>Elke jail zal zijn eigen beschrijfbaar systeem hebben
|
||||
welke gebaseerd is op <filename
|
||||
role="directory">/home/j/skel</filename>.</para>
|
||||
class="directory">/home/j/skel</filename>.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Elke jail ruimte (het beschrijfbare gedeelte van de
|
||||
jail), wordt gecreeërd in de <filename
|
||||
role="directory">/home/js</filename> directory.</para>
|
||||
class="directory">/home/js</filename> directory.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<note>
|
||||
<para>De voorbeelden gaan er vanuit dat de jails geplaatst
|
||||
worden in <filename
|
||||
role="directory">/home</filename> partitie. Dit kan
|
||||
class="directory">/home</filename> partitie. Dit kan
|
||||
uiteraard aangepast worden, maar dan moeten de
|
||||
voorbeelden hieronder ook worden aangepast naar de plek
|
||||
die gebruikt zal worden.</para>
|
||||
|
|
@ -793,7 +793,7 @@ jail_<replaceable>www</replaceable>_devfs_ruleset="<replaceable>www_ruleset</rep
|
|||
<para>Nu moet er een symbolische link gemaakt worden tussen
|
||||
het beschrijfbare bestandssysteem en het alleen-lezen
|
||||
bestandssysteem, zorg ervoor dat de links gemaakt worden
|
||||
in de juiste <filename role="directory">/s</filename>
|
||||
in de juiste <filename class="directory">/s</filename>
|
||||
directory. Als hier echte directories worden gemaakt
|
||||
of de directories worden op de verkeerde plak aangemaakt
|
||||
zal dit resulteren in een mislukte installatie:</para>
|
||||
|
|
@ -891,13 +891,13 @@ jail_www_devfs_enable="YES"</programlisting>
|
|||
<para>De reden dat de
|
||||
<varname>jail_<replaceable>name</replaceable>_rootdir</varname>
|
||||
variabele verwijst naar de <filename
|
||||
role="directory">/usr/home</filename> directory in
|
||||
class="directory">/usr/home</filename> directory in
|
||||
plaats van naar <filename
|
||||
role="directory">/home</filename> komt doordat het
|
||||
class="directory">/home</filename> komt doordat het
|
||||
fysieke pad van de <filename
|
||||
role="directory">/home</filename> directory op een
|
||||
class="directory">/home</filename> directory op een
|
||||
standaard &os; installatie verwijst naar <filename
|
||||
role="directory">/usr/home</filename>. De
|
||||
class="directory">/usr/home</filename>. De
|
||||
<varname>jail_<replaceable>name</replaceable>_rootdir</varname>
|
||||
variabele mag <emphasis>niet</emphasis> ingesteld
|
||||
worden op een symbolische link, omdat dan de jail
|
||||
|
|
@ -980,7 +980,7 @@ jail_www_devfs_enable="YES"</programlisting>
|
|||
<para>De eerste stap is het upgraden van het host systeem
|
||||
zelf, waarna een nieuwe alleen-lezen template gemaakt
|
||||
wordt in <filename
|
||||
role="directory">/home/j/mroot2</filename>.</para>
|
||||
class="directory">/home/j/mroot2</filename>.</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>mkdir /home/j/mroot2</userinput>
|
||||
&prompt.root; <userinput>cd /usr/src</userinput>
|
||||
|
|
@ -1030,7 +1030,7 @@ jail_www_devfs_enable="YES"</programlisting>
|
|||
<note>
|
||||
<para>Het beschrijfbare gedeelte van de jail is
|
||||
gekoppeld aan het alleen-lezen gedeelte
|
||||
(<filename role="directory">/s</filename>) en moet
|
||||
(<filename class="directory">/s</filename>) en moet
|
||||
derhalve eerst ontkoppeld worden.</para>
|
||||
</note>
|
||||
</step>
|
||||
|
|
|
|||
|
|
@ -2877,7 +2877,7 @@ subnet 192.168.4.0 netmask 255.255.255.0 {
|
|||
<filename>pxeboot</filename>, not the kernel. There are other
|
||||
interesting possibilities, like loading
|
||||
<filename>pxeboot</filename> from a &os; CD-ROM
|
||||
<filename role="directory">/boot</filename> directory (as
|
||||
<filename class="directory">/boot</filename> directory (as
|
||||
&man.pxeboot.8; can load a <filename>GENERIC</filename> kernel,
|
||||
this makes it possible to use <acronym>PXE</acronym> to boot
|
||||
from a remote CD-ROM).</para>
|
||||
|
|
|
|||
|
|
@ -167,7 +167,7 @@ requirements. -->
|
|||
<para>Support for Event Auditing is installed with
|
||||
the normal <maketarget>installworld</maketarget> process. An
|
||||
administrator may confirm this by viewing the contents
|
||||
of <filename role="directory">/etc/security</filename>. Files
|
||||
of <filename class="directory">/etc/security</filename>. Files
|
||||
beginning with the word <emphasis>audit</emphasis> should be present.
|
||||
For example, <filename>audit_event</filename>.</para>
|
||||
|
||||
|
|
@ -194,7 +194,7 @@ requirements. -->
|
|||
<title>Audit Configuration</title>
|
||||
|
||||
<para>All configuration files for security audit are found in
|
||||
<filename role="directory">/etc/security</filename>. The following
|
||||
<filename class="directory">/etc/security</filename>. The following
|
||||
files must be present before the audit daemon is started:</para>
|
||||
|
||||
<itemizedlist>
|
||||
|
|
@ -451,10 +451,10 @@ naflags:lo</programlisting>
|
|||
percentage of free space for audit file systems. This
|
||||
relates to the file system where audit logs are stored.
|
||||
For example, if the <option>dir</option> specifies
|
||||
<filename role="directory">/var/audit</filename> and
|
||||
<filename class="directory">/var/audit</filename> and
|
||||
<option>minfree</option> is set to twenty (20), warning
|
||||
messages will be generated when the
|
||||
<filename role="directory">/var</filename> file system grows
|
||||
<filename class="directory">/var</filename> file system grows
|
||||
to eighty (80) percent full.</para>
|
||||
|
||||
<para>The <option>naflags</option> option specifies audit
|
||||
|
|
|
|||
|
|
@ -3798,7 +3798,7 @@ device crypto</screen>
|
|||
<para>The following example will describe how to generate a
|
||||
key file, which will be used as part of the Master Key for
|
||||
the encrypted provider mounted under
|
||||
<filename role="directory">/private</filename>. The key
|
||||
<filename class="directory">/private</filename>. The key
|
||||
file will provide some random data used to encrypt the
|
||||
Master Key. The Master Key will be protected by a
|
||||
passphrase as well. Provider's sector size will be 4kB big.
|
||||
|
|
@ -3870,7 +3870,7 @@ Filesystem Size Used Avail Capacity Mounted on
|
|||
<title>Unmounting and Detaching the Provider</title>
|
||||
|
||||
<para>Once the work on the encrypted partition is done, and
|
||||
the <filename role="directory">/private</filename> partition
|
||||
the <filename class="directory">/private</filename> partition
|
||||
is no longer needed, it is prudent to consider unmounting
|
||||
and detaching the <command>geli</command> encrypted
|
||||
partition from the kernel.</para>
|
||||
|
|
|
|||
|
|
@ -87,7 +87,7 @@
|
|||
<para>GEOM permits access and control to classes — Master Boot
|
||||
Records, <acronym>BSD</acronym> labels, etc — through the
|
||||
use of providers, or the special files in
|
||||
<filename role="directory">/dev</filename>. Supporting various
|
||||
<filename class="directory">/dev</filename>. Supporting various
|
||||
software <acronym>RAID</acronym> configurations, GEOM will
|
||||
transparently provide access to the operating system and
|
||||
operating system utilities.</para>
|
||||
|
|
@ -157,7 +157,7 @@
|
|||
<step><para>Ensure that a suitable mount point exists. If this
|
||||
volume will become a root partition, then temporarily use
|
||||
another mount point such as <filename
|
||||
role="directory">/mnt</filename>:</para>
|
||||
class="directory">/mnt</filename>:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>mkdir /mnt</userinput></screen>
|
||||
</step>
|
||||
|
|
@ -186,7 +186,7 @@ XXX: What message? Put it inside the screen output above.
|
|||
</step>
|
||||
|
||||
<step><para>This process should have created two other devices
|
||||
in the <filename role="directory">/dev/stripe</filename>
|
||||
in the <filename class="directory">/dev/stripe</filename>
|
||||
directory in addition to the <devicename>st0</devicename> device.
|
||||
Those include <devicename>st0a</devicename> and
|
||||
<devicename>st0c</devicename>. A file system must now be created
|
||||
|
|
@ -248,7 +248,7 @@ XXX: What message? Put it inside the screen output above.
|
|||
<para>Begin by installing &os; on the first disk with only two
|
||||
partitions. One should be a swap partition, double the
|
||||
<acronym>RAM</acronym> size and all remaining space devoted to
|
||||
the root (<filename role="directory">/</filename>) file system.
|
||||
the root (<filename class="directory">/</filename>) file system.
|
||||
It is possible to have separate partitions for other mount points;
|
||||
however, this will increase the difficulty level ten fold due to
|
||||
manual alteration of the &man.bsdlabel.8; and &man.fdisk.8;
|
||||
|
|
@ -277,7 +277,7 @@ Done.</screen>
|
|||
<note>
|
||||
<para>This command should have created the
|
||||
<devicename>gm0</devicename>, device node under the
|
||||
<filename role="directory">/dev/mirror</filename>
|
||||
<filename class="directory">/dev/mirror</filename>
|
||||
directory.</para>
|
||||
</note>
|
||||
|
||||
|
|
@ -305,7 +305,7 @@ Done.</screen>
|
|||
<para>This should have caused the system to spit out some
|
||||
information and a bunch of numbers. This is good. Examine the
|
||||
screen for any error messages and mount the device to the
|
||||
<filename role="directory">/mnt</filename> mount point:</para>
|
||||
<filename class="directory">/mnt</filename> mount point:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>mount /dev/mirror/gm0s1a /mnt</userinput></screen>
|
||||
|
||||
|
|
@ -443,7 +443,7 @@ OK? <userinput>boot</userinput></screen>
|
|||
<screen>&prompt.root; <userinput>mount /dev/ggate0 /mnt</userinput></screen>
|
||||
|
||||
<para>From here on, the device may be accessed through the
|
||||
<filename role="directory">/mnt</filename> mount point.</para>
|
||||
<filename class="directory">/mnt</filename> mount point.</para>
|
||||
|
||||
<note>
|
||||
<para>It should be pointed out that this will fail if the device
|
||||
|
|
|
|||
|
|
@ -410,7 +410,7 @@ multi on</programlisting>
|
|||
<para>The shell scripts that
|
||||
<application>&mathematica;</application> created during
|
||||
installation have to be modified before you can use them. If
|
||||
you chose <filename role="directory">/usr/local/bin</filename>
|
||||
you chose <filename class="directory">/usr/local/bin</filename>
|
||||
as the directory to place the
|
||||
<application>&mathematica;</application> executables in, you
|
||||
will find symlinks in this directory to files called
|
||||
|
|
|
|||
|
|
@ -2433,7 +2433,7 @@ doc/zh_*</screen>
|
|||
|
||||
<note>
|
||||
<para>In the default installation
|
||||
<filename role="directory">/usr/ports</filename> is not
|
||||
<filename class="directory">/usr/ports</filename> is not
|
||||
created. If you run &os; 6.0-RELEASE, it should be created before
|
||||
<command>portsnap</command> is used. On more recent
|
||||
versions of &os; or <application>Portsnap</application>,
|
||||
|
|
|
|||
|
|
@ -3080,7 +3080,7 @@ dhcpd_ifaces="dc0"</programlisting>
|
|||
<hostid>org.</hostid>, as <hostid>org.</hostid> is more specific
|
||||
than the root zone. The layout of each part of a hostname is
|
||||
much like a file system: the
|
||||
<filename role="directory">/dev</filename> directory falls
|
||||
<filename class="directory">/dev</filename> directory falls
|
||||
within the root, and so on.</para>
|
||||
</sect2>
|
||||
|
||||
|
|
@ -3164,7 +3164,7 @@ dhcpd_ifaces="dc0"</programlisting>
|
|||
</row>
|
||||
|
||||
<row>
|
||||
<entry><filename role="directory">/etc/namedb</filename></entry>
|
||||
<entry><filename class="directory">/etc/namedb</filename></entry>
|
||||
<entry>Directory where BIND zone information resides.</entry>
|
||||
</row>
|
||||
|
||||
|
|
@ -3178,10 +3178,10 @@ dhcpd_ifaces="dc0"</programlisting>
|
|||
|
||||
<para>Depending on how a given zone is configured on the server,
|
||||
the files related to that zone can be found in the <filename
|
||||
role="directory">master</filename>, <filename
|
||||
role="directory">slave</filename>, or <filename
|
||||
role="directory">dynamic</filename> subdirectories of the
|
||||
<filename role="directory">/etc/namedb</filename> directory.
|
||||
class="directory">master</filename>, <filename
|
||||
class="directory">slave</filename>, or <filename
|
||||
class="directory">dynamic</filename> subdirectories of the
|
||||
<filename class="directory">/etc/namedb</filename> directory.
|
||||
These files contain the <acronym>DNS</acronym> information that
|
||||
will be given out by the name server in response to queries.</para>
|
||||
</sect2>
|
||||
|
|
@ -3229,7 +3229,7 @@ dhcpd_ifaces="dc0"</programlisting>
|
|||
|
||||
<para>Configuration files for <application>named</application>
|
||||
currently reside in
|
||||
<filename role="directory">/etc/namedb</filename> directory and
|
||||
<filename class="directory">/etc/namedb</filename> directory and
|
||||
will need modification before use, unless all that is needed is
|
||||
a simple resolver. This is where most of the configuration will
|
||||
be performed.</para>
|
||||
|
|
@ -3238,7 +3238,7 @@ dhcpd_ifaces="dc0"</programlisting>
|
|||
<title>Using <command>make-localhost</command></title>
|
||||
|
||||
<para>To configure a master zone for the localhost visit the
|
||||
<filename role="directory">/etc/namedb</filename> directory
|
||||
<filename class="directory">/etc/namedb</filename> directory
|
||||
and run the following command:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>sh make-localhost</userinput></screen>
|
||||
|
|
|
|||
|
|
@ -624,7 +624,7 @@ docbook =
|
|||
CVSup</link>.</para>
|
||||
|
||||
<para>Bardzo ważnym jest, aby upewnić się, że katalog
|
||||
<filename role="directory">/usr/ports</filename> jest pusty
|
||||
<filename class="directory">/usr/ports</filename> jest pusty
|
||||
nim po raz pierwszy uruchomimy <application>CVSup</application>!
|
||||
Jeśli posiadamy już kolekcję portów pozyskaną z innego źródła
|
||||
<application>CVSup</application> nie usunie nieużywanych
|
||||
|
|
@ -717,7 +717,7 @@ docbook =
|
|||
bądź najnowszą wersję programu <application>Portsnap</application>.
|
||||
Przy pierwszym uruchomieniu programu &man.portsnap.8; zostanie
|
||||
automatycznie utworzony katalog <filename
|
||||
role="directory">/usr/ports</filename>. W starszych wersjach programu
|
||||
class="directory">/usr/ports</filename>. W starszych wersjach programu
|
||||
wymagane jest własnoręczne utworzenie katalogu:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>mkdir /usr/ports</userinput></screen>
|
||||
|
|
@ -725,7 +725,7 @@ docbook =
|
|||
|
||||
<step>
|
||||
<para>Pobierz skompresowaną migawkę kolekcji portów do katalogu
|
||||
<filename role="directory">/var/db/portsnap</filename>. Można następnie
|
||||
<filename class="directory">/var/db/portsnap</filename>. Można następnie
|
||||
zakończyć połączenie z Internetem, jeśli jest taka potrzeba.</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>portsnap fetch</userinput></screen>
|
||||
|
|
@ -734,13 +734,13 @@ docbook =
|
|||
<step>
|
||||
<para>Jeśli uruchamiany <application>Portsnap</application> po raz
|
||||
pierwszy należy rozpakować migawkę do katalogu
|
||||
<filename role="directory">/usr/ports</filename>:
|
||||
<filename class="directory">/usr/ports</filename>:
|
||||
</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>portsnap extract</userinput></screen>
|
||||
|
||||
<para>Jeśli posiadamy już kolekcję portów w <filename
|
||||
role="directory">/usr/ports</filename> i jedynie ją aktualizujemy,
|
||||
class="directory">/usr/ports</filename> i jedynie ją aktualizujemy,
|
||||
wpisujemy polecenie:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>portsnap update</userinput></screen>
|
||||
|
|
@ -1250,7 +1250,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
|
|||
portów jest <application>Portmanager</application>, dostępny z portu
|
||||
<filename role="package">sysutils/portmanager</filename>:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd <filename role="directory">/usr/ports/sysutils/portmanager</filename></userinput>
|
||||
<screen>&prompt.root; <userinput>cd <filename class="directory">/usr/ports/sysutils/portmanager</filename></userinput>
|
||||
&prompt.root; <userinput>make install clean</userinput></screen>
|
||||
|
||||
<para>Wszystkie zainstalowane porty mogą zostać zaktualizowane
|
||||
|
|
|
|||
|
|
@ -254,17 +254,17 @@
|
|||
репозитория, которую требуется поправить:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para>ncvs@ - ÒÅÐÏÚÉÔÏÒÉÊ <filename role="directory">
|
||||
<listitem><para>ncvs@ - ÒÅÐÏÚÉÔÏÒÉÊ <filename class="directory">
|
||||
/home/ncvs</filename>, основные исходные тексты
|
||||
</para></listitem>
|
||||
|
||||
<listitem><para>pcvs@ - ÒÅÐÏÚÉÔÏÒÉÊ <filename role="directory">
|
||||
<listitem><para>pcvs@ - ÒÅÐÏÚÉÔÏÒÉÊ <filename class="directory">
|
||||
/home/pcvs</filename>, порты</para></listitem>
|
||||
|
||||
<listitem><para>dcvs@ - ÒÅÐÏÚÉÔÏÒÉÊ <filename role="directory">
|
||||
<listitem><para>dcvs@ - ÒÅÐÏÚÉÔÏÒÉÊ <filename class="directory">
|
||||
/home/dcvs</filename>, документация</para></listitem>
|
||||
|
||||
<listitem><para>projcvs@ - ÒÅÐÏÚÉÔÏÒÉÊ <filename role="directory">
|
||||
<listitem><para>projcvs@ - ÒÅÐÏÚÉÔÏÒÉÊ <filename class="directory">
|
||||
/home/projcvs</filename>, прочие проекты</para></listitem>
|
||||
</itemizedlist>
|
||||
</note>
|
||||
|
|
@ -2450,7 +2450,7 @@ docs:Documentation Bug:freebsd-doc:</programlisting>
|
|||
</itemizedlist>
|
||||
|
||||
<para>Вы можете воспользоваться скриптом <command>rmport</command>
|
||||
ÉÚ ËÁÔÁÌÏÇÁ <filename role="directory">ports/Tools/scripts</filename>.
|
||||
ÉÚ ËÁÔÁÌÏÇÁ <filename class="directory">ports/Tools/scripts</filename>.
|
||||
Этот скрипт написал &a.vd;, и он же его поддерживает, так что
|
||||
вопросы, исправления и замечания по поводу <command>rmport</command>
|
||||
следует посылать непосредственно ему.</para>
|
||||
|
|
|
|||
|
|
@ -98,7 +98,7 @@
|
|||
</step>
|
||||
|
||||
<step>
|
||||
<para>ðÅÒÅÊÄÉÔÅ × ËÁÔÁÌÏÇ <filename role="directory">www/en</filename>
|
||||
<para>ðÅÒÅÊÄÉÔÅ × ËÁÔÁÌÏÇ <filename class="directory">www/en</filename>
|
||||
É ÚÁÐÕÓÔÉÔÅ ËÏÍÁÎÄÕ &man.make.1; <maketarget>all</maketarget> ÄÌÑ
|
||||
ÓÏÚÄÁÎÉÑ Web-ÓÔÒÁÎÉÃ.</para>
|
||||
|
||||
|
|
|
|||
|
|
@ -2444,7 +2444,7 @@ subnet 192.168.4.0 netmask 255.255.255.0 {
|
|||
<filename>pxeboot</filename>, а не ядро. Существуют другие
|
||||
интересные возможности, такие как загрузка
|
||||
<filename>pxeboot</filename> из каталога
|
||||
<filename role="directory">/boot</filename> &os; CD-ROM
|
||||
<filename class="directory">/boot</filename> &os; CD-ROM
|
||||
(поскольку &man.pxeboot.8; может загружать
|
||||
<filename>GENERIC</filename> ядро, это делает возможной
|
||||
загрузку с удаленного CD-ROM).</para>
|
||||
|
|
|
|||
|
|
@ -237,7 +237,7 @@ requirements. -->
|
|||
|
||||
|
||||
<para>Все конфигурационные файлы системы аудита находятся в каталоге
|
||||
<filename role="directory">/etc/security</filename>. ðÅÒÅÄ ÚÁÐÕÓËÏÍ
|
||||
<filename class="directory">/etc/security</filename>. ðÅÒÅÄ ÚÁÐÕÓËÏÍ
|
||||
демона аудита там должны находиться следующие файлы:</para>
|
||||
|
||||
<itemizedlist>
|
||||
|
|
@ -518,10 +518,10 @@ naflags:lo</programlisting>
|
|||
значение свободного дискового пространства на разделе, в
|
||||
который сохраняются файлы журналов аудита. Например, если
|
||||
значение параметра <option>dir</option> установлено в
|
||||
<filename role="directory">/var/audit</filename>, Á ÐÁÒÁÍÅÔÒ
|
||||
<filename class="directory">/var/audit</filename>, Á ÐÁÒÁÍÅÔÒ
|
||||
<option>minfree</option> равен двадцати (20), то предупреждающее
|
||||
сообщение будет выдано, когда раздел <filename
|
||||
role="directory">/var</filename> ÂÕÄÅÔ ÚÁÐÏÌÎÅÎ ÎÁ
|
||||
class="directory">/var</filename> ÂÕÄÅÔ ÚÁÐÏÌÎÅÎ ÎÁ
|
||||
восемьдесят (80%) процентов.</para>
|
||||
|
||||
<para>Параметр <option>naflags</option> определяет классы
|
||||
|
|
|
|||
|
|
@ -444,7 +444,7 @@ multi on</programlisting>
|
|||
<application>&mathematica;</application> создала во
|
||||
время установки, должны быть изменены перед тем, как
|
||||
вы сможете использовать их. Если вы выбрали
|
||||
<filename role="directory">/usr/local/bin</filename> ×
|
||||
<filename class="directory">/usr/local/bin</filename> ×
|
||||
качестве директории для помещения исполняемых файлов
|
||||
<application>&mathematica;</application>, то вы обнаружите
|
||||
в этом каталоге ссылки на файлы <filename>math</filename>,
|
||||
|
|
|
|||
|
|
@ -2413,7 +2413,7 @@ doc/zh_*</screen>
|
|||
|
||||
<note>
|
||||
<para>В конфигурации установки по умолчанию каталог
|
||||
<filename role="directory">/usr/ports</filename> ÎÅ ÓÏÚÄÁÎ.
|
||||
<filename class="directory">/usr/ports</filename> ÎÅ ÓÏÚÄÁÎ.
|
||||
Если вы используете &os; 6.0-RELEASE,
|
||||
создайте его самостоятельно перед первым запуском
|
||||
утилиты <command>portsnap</command>.
|
||||
|
|
|
|||
|
|
@ -10,6 +10,12 @@
|
|||
</rule>
|
||||
</pattern>
|
||||
|
||||
<pattern name="Check filenames">
|
||||
<rule context="//filename">
|
||||
<report test="@role = 'directory'">Filename (<xsl:value-of select="."/>) has role="directory"; use class="directory"</report>
|
||||
</rule>
|
||||
</pattern>
|
||||
|
||||
<pattern name="Check cross-reference validity">
|
||||
<rule context="//link">
|
||||
<assert test="* or normalize-space()">Link (<xsl:value-of select="@linkend"/>) element must have a content; or use xref to auto-generate the linking text.</assert>
|
||||
|
|
|
|||
|
|
@ -163,7 +163,7 @@ requirements. -->
|
|||
|
||||
<para>对于事件审计的支持， 已经随标准的 <maketarget>installworld</maketarget>
|
||||
过程完成。 管理员可以通过查看
|
||||
<filename role="directory">/etc/security</filename> 的内容来确认这一点。
|
||||
<filename class="directory">/etc/security</filename> 的内容来确认这一点。
|
||||
您应能看到一些名字以 <emphasis>audit</emphasis> 开头的文件，
|
||||
例如 <filename>audit_event</filename>。</para>
|
||||
|
||||
|
|
|
|||
|
|
@ -78,7 +78,7 @@
|
|||
<screen>&prompt.user; <userinput>cvs -d <replaceable>path-to-repository</replaceable> init</userinput></screen>
|
||||
|
||||
<para>這命令告訴 <application>CVS</application> 建立
|
||||
<filename role="directory">CVSROOT</filename> 的目錄，這個目錄裡放置了所有的組態檔。</para>
|
||||
<filename class="directory">CVSROOT</filename> 的目錄，這個目錄裡放置了所有的組態檔。</para>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
|
|
@ -100,27 +100,27 @@
|
|||
<sect2>
|
||||
<title>取回原始檔案</title>
|
||||
|
||||
<para>現在你需要從 FreeBSD 儲存庫中取回 <filename role="directory">CVSROOT</filename> 目錄，
|
||||
<para>現在你需要從 FreeBSD 儲存庫中取回 <filename class="directory">CVSROOT</filename> 目錄，
|
||||
從 FreeBSD 匿名的 CVS 映射站來取回會是最簡單的方法。請查閱 <ulink
|
||||
url="&url.books.handbook;/anoncvs.html">在 handbook 中的相關章節</ulink>來
|
||||
獲得更多資訊。我們假設取回的檔案存放在相同目錄下的
|
||||
<filename role="directory">CVSROOT-freebsd</filename> 目錄中。</para>
|
||||
<filename class="directory">CVSROOT-freebsd</filename> 目錄中。</para>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>複製 FreeBSD 的命令稿</title>
|
||||
|
||||
<para>接下來我們要複製 FreeBSD <filename role="directory">CVSROOT</filename> 裡的檔案到你
|
||||
<para>接下來我們要複製 FreeBSD <filename class="directory">CVSROOT</filename> 裡的檔案到你
|
||||
的儲存庫中。如果你是孰悉於 <application>CVS</application>，你也許會想你
|
||||
可以直接匯入這些命令稿，試圖更容易的同時和更新的版本同步；不過，事實是
|
||||
<application>CVS</application> 在這個部份有缺點：當匯入檔案到
|
||||
<filename role="directory">CVSROOT</filename> 時，它並不會更新組態檔。為了要認出這些檔案
|
||||
<filename class="directory">CVSROOT</filename> 時，它並不會更新組態檔。為了要認出這些檔案
|
||||
，你還需要在匯入它們後一一重新提交，這就失去了
|
||||
<literal>cvs import</literal> 的價值。因此，建議的方法是僅複製這些命令
|
||||
稿過去。</para>
|
||||
|
||||
<para>若上述內容對你沒有意義是不重要的—因為最後的結果都是一樣的。
|
||||
首先匯出你的 <filename role="directory">CVSROOT</filename>，然後複製剛剛取回的 FreeBSD
|
||||
首先匯出你的 <filename class="directory">CVSROOT</filename>，然後複製剛剛取回的 FreeBSD
|
||||
檔案到本地的目錄中（尚未變動過）：</para>
|
||||
|
||||
<screen>&prompt.user; <userinput>cvs -d <replaceable>path-to-your-repository</replaceable> checkout CVSROOT</userinput>
|
||||
|
|
@ -240,7 +240,7 @@
|
|||
，（像是 $FreeBSD$）。在此檔案中所有符合一行一個的檔
|
||||
案名稱將不會被檢查。你可以在此檔案中為不需要修正版標頭的檔案新增一
|
||||
個正規運算式。為了安裝這些命令稿，最好的方法是排除
|
||||
<filename role="directory">CVSROOT/</filename> 會受到標頭的檢查。</para>
|
||||
<filename class="directory">CVSROOT/</filename> 會受到標頭的檢查。</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
|
@ -389,7 +389,7 @@
|
|||
<listitem>
|
||||
<para><literal>@LOG_FILE_MAP</literal> - 以你所需要的來修改這個
|
||||
陣列，每個設定值應該符合被提交的目錄，而提交的日誌訊息會以
|
||||
<filename role="directory">commitlogs</filename> 的名稱儲存在每個被設定的目錄下。</para>
|
||||
<filename class="directory">commitlogs</filename> 的名稱儲存在每個被設定的目錄下。</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
|
@ -413,7 +413,7 @@
|
|||
述（如以 <literal>^ports/</literal> 為開頭的每一行等）。此外，註解
|
||||
掉以 <literal>^CVSROOT/</literal> 為開頭的行列，然後新增一行只有
|
||||
<literal>^CVSROOT/</literal>。等到關鍵字展開的命令稿安裝好後，你可
|
||||
以在 <filename role="directory">CVSROOT</filename> 目錄中的檔案裡加上標頭，然後再恢
|
||||
以在 <filename class="directory">CVSROOT</filename> 目錄中的檔案裡加上標頭，然後再恢
|
||||
復剛剛註解的行列，但在你還沒有提交前則只保持這樣。</para>
|
||||
</step>
|
||||
|
||||
|
|
@ -454,7 +454,7 @@
|
|||
</procedure>
|
||||
|
||||
<para>現在，在細心的檢視過後，你可以提交你的修改了。確定你先前有在
|
||||
<filename>avail</filename> 中允許你自己存取 <filename role="directory">CVSROOT</filename>
|
||||
<filename>avail</filename> 中允許你自己存取 <filename class="directory">CVSROOT</filename>
|
||||
目錄，因為如果沒有這樣做的話你會把你自己鎖在外面。完整確認過後請執行下
|
||||
列命令：</para>
|
||||
|
||||
|
|
@ -479,7 +479,7 @@
|
|||
<title>FreeBSD 的特殊設定</title>
|
||||
|
||||
<para>FreeBSD 專案自己使用一個有點不同的設定，那就是同時也使用 FreeBSD
|
||||
<filename role="directory">CVSROOT</filename> 中的 <filename>freebsd</filename> 子目錄。因
|
||||
<filename class="directory">CVSROOT</filename> 中的 <filename>freebsd</filename> 子目錄。因
|
||||
為大量的提交者必須在相同的群組中，因此專案寫了一個簡單的 wrapper 來確認提
|
||||
交者可以正確的提交，並設定儲存庫的群組名稱。</para>
|
||||
|
||||
|
|
@ -537,7 +537,7 @@
|
|||
|
||||
<step>
|
||||
<para>接下來是建立 wrapper 來確認你在提交時是在正確的群組中。
|
||||
在你的 <filename role="directory">CVSROOT</filename> 中的
|
||||
在你的 <filename class="directory">CVSROOT</filename> 中的
|
||||
<filename>cvswrap.c</filename> 要能夠使用。</para>
|
||||
|
||||
<para>在你完成編輯並加入正確的路徑後我們要來編譯原始碼：</para>
|
||||
|
|
|
|||
|
|
@ -102,22 +102,22 @@
|
|||
|
||||
<listitem>
|
||||
<para>一個設定檔分割區，在運行環境中，
|
||||
可以將其掛載(mount)到 <filename role="directory">/cfg</filename> 目錄下。</para>
|
||||
可以將其掛載(mount)到 <filename class="directory">/cfg</filename> 目錄下。</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>這些分割區，在預設情況下是以唯讀方式掛載。</para>
|
||||
|
||||
<para><filename role="directory">/etc</filename> 和
|
||||
<filename role="directory">/var</filename> 目錄均為
|
||||
<para><filename class="directory">/etc</filename> 和
|
||||
<filename class="directory">/var</filename> 目錄均為
|
||||
&man.md.4;(malloc)磁碟。</para>
|
||||
|
||||
<para>設定檔的分割區則是在
|
||||
<filename role="directory">/cfg</filename> 目錄。
|
||||
它包含了用於 <filename role="directory">/etc</filename>
|
||||
<filename class="directory">/cfg</filename> 目錄。
|
||||
它包含了用於 <filename class="directory">/etc</filename>
|
||||
目錄的檔案，在啟動之後暫時以唯讀方式掛載。 因此，若想要重開機保留新的設定，
|
||||
那麼要記得從 <filename role="directory">/etc</filename> 把改過的檔案複製回
|
||||
<filename role="directory">/cfg</filename> 目錄才行。</para>
|
||||
那麼要記得從 <filename class="directory">/etc</filename> 把改過的檔案複製回
|
||||
<filename class="directory">/cfg</filename> 目錄才行。</para>
|
||||
|
||||
<example>
|
||||
<title>把修改過 <filename>/etc/resolv.conf</filename> 設定保存起來</title>
|
||||
|
|
@ -131,9 +131,9 @@
|
|||
|
||||
<note>
|
||||
<para>只有在系統啟動過程中，以及需要修改設定檔的時候，才需要掛載含有
|
||||
<filename role="directory">/cfg</filename> 的那個分割區。</para>
|
||||
<filename class="directory">/cfg</filename> 的那個分割區。</para>
|
||||
|
||||
<para>一直都掛載 <filename role="directory">/cfg</filename>
|
||||
<para>一直都掛載 <filename class="directory">/cfg</filename>
|
||||
不是一個好主意，特別是當您把 <application>NanoBSD</application>
|
||||
放在不適合進行大量寫入動作的分割區時
|
||||
(比如：由於檔案系統的同步化會定期在系統碟內寫入資料)。</para>
|
||||
|
|
@ -145,7 +145,7 @@
|
|||
|
||||
<para><application>NanoBSD</application> 映像檔是透過使用非常簡單的
|
||||
<filename>nanobsd.sh</filename> shell script 來打造的，這個 script 可以在
|
||||
<filename role="directory"><replaceable>/usr</replaceable>/src/tools/tools/nanobsd</filename>
|
||||
<filename class="directory"><replaceable>/usr</replaceable>/src/tools/tools/nanobsd</filename>
|
||||
目錄中找到。 這個 script 建立的映像檔，可以用 &man.dd.1; 工具來複製到隨身碟上。</para>
|
||||
|
||||
<para>打造
|
||||
|
|
@ -262,7 +262,7 @@
|
|||
customize_cmd cust_foo</programlisting>
|
||||
|
||||
<para>下面舉更實際點的例子，它會把預設的
|
||||
<filename role="directory">/etc</filename> 目錄大小，從 5MB 調整為 30MB：</para>
|
||||
<filename class="directory">/etc</filename> 目錄大小，從 5MB 調整為 30MB：</para>
|
||||
|
||||
<programlisting>cust_etc_size()(
|
||||
cd ${NANO_WORLDDIR}/conf
|
||||
|
|
@ -285,7 +285,7 @@ customize_cmd cust_etc_size</programlisting>
|
|||
|
||||
<listitem>
|
||||
<para><literal>cust_install_files</literal> —
|
||||
從 <filename role="directory">nanobsd/Files</filename>
|
||||
從 <filename class="directory">nanobsd/Files</filename>
|
||||
目錄中安裝檔案，這包含一些實用的系統管理 script 。</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
|
@ -385,7 +385,7 @@ customize_cmd cust_nobeastie</programlisting>
|
|||
|
||||
<para>要在正在運行的
|
||||
<application>NanoBSD</application> 系統中安裝新的映像檔，可以使用位於
|
||||
<filename role="directory">/root</filename> 目錄的
|
||||
<filename class="directory">/root</filename> 目錄的
|
||||
<filename>updatep1</filename> 或
|
||||
<filename>updatep2</filename> script ，
|
||||
實際上要用哪一個 script，則取決於正在運行的系統是位於哪個分割區而定。</para>
|
||||
|
|
|
|||
|
|
@ -201,10 +201,10 @@ ifconfig_re0="inet 192.168.0.2 netmask 255.255.255.0"</programlisting>
|
|||
image 檔的過程相當簡單。</para>
|
||||
|
||||
<para>首先是把 &os; 安裝光碟或者安裝用的 <acronym>ISO</acronym> image
|
||||
檔丟到 <filename role="directory">/cdrom</filename>。
|
||||
檔丟到 <filename class="directory">/cdrom</filename>。
|
||||
為維持所有例子的一致，本文假設都是用 &os; 7.0-RELEASE
|
||||
<acronym>ISO</acronym>。 而把 ISO image 檔掛載到 <filename
|
||||
role="directory">/cdrom</filename> 目錄相當簡單，
|
||||
class="directory">/cdrom</filename> 目錄相當簡單，
|
||||
就是用 &man.mdconfig.8;：</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>mdconfig -a -t vnode -u 10 -f <replaceable>7.0-RELEASE-amd64-disc1.iso</replaceable></userinput>
|
||||
|
|
@ -218,7 +218,7 @@ ifconfig_re0="inet 192.168.0.2 netmask 255.255.255.0"</programlisting>
|
|||
<note>
|
||||
<para>上述的 <command>make</command> 指令要在
|
||||
<application>mfsBSD</application> 的最上層目錄執行，比方說 <filename
|
||||
role="directory">~/mfsbsd-1.0-beta1/</filename>。</para>
|
||||
class="directory">~/mfsbsd-1.0-beta1/</filename>。</para>
|
||||
</note>
|
||||
</sect2>
|
||||
|
||||
|
|
@ -276,9 +276,9 @@ ifconfig_re0="inet 192.168.0.2 netmask 255.255.255.0"</programlisting>
|
|||
&os;</ulink> 章節有相當詳盡的介紹，所以這邊主要要介紹的是如何建立
|
||||
RAID-1 系統以及 <application>ZFS</application>。
|
||||
這邊會介紹建立以 &man.gmirror.8; 做成的小型 mirrored 檔案系統：
|
||||
<filename role="directory">/</filename> (根目錄), <filename
|
||||
role="directory">/usr</filename> 以及 <filename
|
||||
role="directory">/var</filename>，而硬碟的其餘剩餘空間則通通以
|
||||
<filename class="directory">/</filename> (根目錄), <filename
|
||||
class="directory">/usr</filename> 以及 <filename
|
||||
class="directory">/var</filename>，而硬碟的其餘剩餘空間則通通以
|
||||
&man.zpool.8; 做成 <application>ZFS</application> 的 mirrored 檔案系統
|
||||
。 請注意：必須要先把 &os; 作業系統裝好並開完機後，才能進行設定
|
||||
<application>ZFS</application> 檔案系統。</para>
|
||||
|
|
@ -315,10 +315,10 @@ ifconfig_re0="inet 192.168.0.2 netmask 255.255.255.0"</programlisting>
|
|||
<para>現在手動修改該硬碟的 label，至於如何建立分割區(partitions)
|
||||
請參閱 &man.bsdlabel.8; 說明。
|
||||
分割區分別建立：<literal>a</literal> 是給 <filename
|
||||
role="directory">/</filename> (根目錄)，
|
||||
class="directory">/</filename> (根目錄)，
|
||||
<literal>b</literal> 給 swap，
|
||||
<literal>d</literal> 給 <filename role="directory">/var</filename>，
|
||||
<literal>e</literal> 給 <filename role="directory">/usr</filename>，
|
||||
<literal>d</literal> 給 <filename class="directory">/var</filename>，
|
||||
<literal>e</literal> 給 <filename class="directory">/usr</filename>，
|
||||
最後，會在稍後步驟把 <literal>f</literal> 給
|
||||
<application>ZFS</application> 使用。</para>
|
||||
</callout>
|
||||
|
|
@ -363,7 +363,7 @@ ifconfig_re0="inet 192.168.0.2 netmask 255.255.255.0"</programlisting>
|
|||
<guimenuitem>Options</guimenuitem> 按 <keycap>Enter</keycap>。
|
||||
然後以方向鍵移動到 <literal>Install Root</literal> 處，按
|
||||
<keycap>Space</keycap> 鍵然後改為 <filename
|
||||
role="directory">/mnt</filename>，再按 <keycap>Enter</keycap>
|
||||
class="directory">/mnt</filename>，再按 <keycap>Enter</keycap>
|
||||
鍵以將修改值存起來，然後按 <keycap>q</keycap> 鍵即可離開這個
|
||||
<guimenuitem>Options</guimenuitem> 畫面。</para>
|
||||
|
||||
|
|
@ -409,7 +409,7 @@ ifconfig_re0="inet 192.168.0.2 netmask 255.255.255.0"</programlisting>
|
|||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>把 <literal>GENERIC</literal> kernel 複製到
|
||||
<filename role="directory">/boot/kernel</filename>
|
||||
<filename class="directory">/boot/kernel</filename>
|
||||
目錄：</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cp -Rp /boot/GENERIC/* /boot/kernel</userinput></screen>
|
||||
|
|
|
|||
|
|
@ -85,7 +85,7 @@
|
|||
</step>
|
||||
|
||||
<step>
|
||||
<para>切到 <filename role="directory">www/en</filename> 目錄，然後打
|
||||
<para>切到 <filename class="directory">www/en</filename> 目錄，然後打
|
||||
&man.make.1; <maketarget>all</maketarget> 來產生網頁。</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd en</userinput>
|
||||
|
|
|
|||
|
|
@ -3647,7 +3647,7 @@ subnet 192.168.4.0 netmask 255.255.255.0 {
|
|||
<filename>pxeboot</filename>, not the kernel. There are other
|
||||
interesting possibilities, like loading
|
||||
<filename>pxeboot</filename> from a &os; CD-ROM
|
||||
<filename role="directory">/boot</filename> directory (as
|
||||
<filename class="directory">/boot</filename> directory (as
|
||||
&man.pxeboot.8; can load a <filename>GENERIC</filename> kernel,
|
||||
this makes it possible to use <acronym>PXE</acronym> to boot
|
||||
from a remote CD-ROM).</para>
|
||||
|
|
|
|||
|
|
@ -168,7 +168,7 @@ requirements. -->
|
|||
<para>Support for Event Auditing is installed with
|
||||
the normal <maketarget>installworld</maketarget> process. An
|
||||
administrator may confirm this by viewing the contents
|
||||
of <filename role="directory">/etc/security</filename>. Files
|
||||
of <filename class="directory">/etc/security</filename>. Files
|
||||
beginning with the word <emphasis>audit</emphasis> should be present.
|
||||
For example, <filename>audit_event</filename>.</para>
|
||||
|
||||
|
|
@ -195,7 +195,7 @@ requirements. -->
|
|||
<title>Audit Configuration</title>
|
||||
|
||||
<para>All configuration files for security audit are found in
|
||||
<filename role="directory">/etc/security</filename>. The following
|
||||
<filename class="directory">/etc/security</filename>. The following
|
||||
files must be present before the audit daemon is started:</para>
|
||||
|
||||
<itemizedlist>
|
||||
|
|
@ -452,10 +452,10 @@ naflags:lo</programlisting>
|
|||
percentage of free space for audit file systems. This
|
||||
relates to the file system where audit logs are stored.
|
||||
For example, if the <option>dir</option> specifies
|
||||
<filename role="directory">/var/audit</filename> and
|
||||
<filename class="directory">/var/audit</filename> and
|
||||
<option>minfree</option> is set to twenty (20), warning
|
||||
messages will be generated when the
|
||||
<filename role="directory">/var</filename> file system grows
|
||||
<filename class="directory">/var</filename> file system grows
|
||||
to eighty (80) percent full.</para>
|
||||
|
||||
<para>The <option>naflags</option> option specifies audit
|
||||
|
|
|
|||
|
|
@ -3683,7 +3683,7 @@ device crypto</screen>
|
|||
<para>The following example will describe how to generate a
|
||||
key file, which will be used as part of the Master Key for
|
||||
the encrypted provider mounted under
|
||||
<filename role="directory">/private</filename>. The key
|
||||
<filename class="directory">/private</filename>. The key
|
||||
file will provide some random data used to encrypt the
|
||||
Master Key. The Master Key will be protected by a
|
||||
passphrase as well. Provider's sector size will be 4kB big.
|
||||
|
|
@ -3755,7 +3755,7 @@ Filesystem Size Used Avail Capacity Mounted on
|
|||
<title>Unmounting and Detaching the Provider</title>
|
||||
|
||||
<para>Once the work on the encrypted partition is done, and
|
||||
the <filename role="directory">/private</filename> partition
|
||||
the <filename class="directory">/private</filename> partition
|
||||
is no longer needed, it is prudent to consider unmounting
|
||||
and detaching the <command>geli</command> encrypted
|
||||
partition from the kernel.</para>
|
||||
|
|
|
|||
|
|
@ -78,7 +78,7 @@
|
|||
<sect1 id="GEOM-intro">
|
||||
<title>GEOM 導論</title>
|
||||
|
||||
<para>GEOM 透過 privoder(即 <filename role="directory">/dev/</filename>
|
||||
<para>GEOM 透過 privoder(即 <filename class="directory">/dev/</filename>
|
||||
下的特殊裝置檔案) 來操控 classes(如 Master Boot Records、
|
||||
<acronym>BSD</acronym> labels 等) 。GEOM 支援多種軟體
|
||||
<acronym>RAID</acronym> 配置，透過 GEOM 存取時，
|
||||
|
|
@ -142,9 +142,9 @@
|
|||
</step>
|
||||
|
||||
<step><para>確定掛載點(mount point)存在。
|
||||
如果想用分散連結(striping)的空間做為根目錄(root partition，即 <filename role="directory">/</filename> )，
|
||||
如果想用分散連結(striping)的空間做為根目錄(root partition，即 <filename class="directory">/</filename> )，
|
||||
則先用個暫時的掛載點，如
|
||||
<filename role="directory">/mnt</filename>：</para>
|
||||
<filename class="directory">/mnt</filename>：</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>mkdir /mnt</userinput></screen>
|
||||
</step>
|
||||
|
|
@ -173,7 +173,7 @@ XXX: What message? Put it inside the screen output above.
|
|||
</step>
|
||||
|
||||
<step><para>除了先前建立的 <devicename>st0</devicename> ，這個步驟還會在
|
||||
<filename role="directory">/dev/stripe</filename> 下新增兩個裝置：
|
||||
<filename class="directory">/dev/stripe</filename> 下新增兩個裝置：
|
||||
<devicename>st0a</devicename> 和 <devicename>st0c</devicename>。
|
||||
利用 <command>newfs</command> 指令可以在
|
||||
<devicename>st0a</devicename> 建立檔案系統：</para>
|
||||
|
|
@ -224,7 +224,7 @@ XXX: What message? Put it inside the screen output above.
|
|||
|
||||
<para>首先我們假設 &os; 安裝在第一個磁碟上，且只有兩個分割區(partition)。
|
||||
其中一個是交換分割區(swap partition，大小為 <acronym>RAM</acronym>
|
||||
的兩倍)，而剩下的全用於根目錄(即 <filename role="directory">/</filename>，
|
||||
的兩倍)，而剩下的全用於根目錄(即 <filename class="directory">/</filename>，
|
||||
root file system)。當然要在不同掛載點(mount point) 切出更多分割區
|
||||
(partition) 也可以，不過難度會大幅提升，因為必須手動操作 &man.bsdlabel.8;
|
||||
和 &man.fdisk.8; 工具。</para>
|
||||
|
|
@ -248,7 +248,7 @@ Done.</screen>
|
|||
<screen>&prompt.root; <userinput>gmirror load</userinput></screen>
|
||||
|
||||
<note>
|
||||
<para>這動作應該會在 <filename role="directory">/dev/mirror</filename>
|
||||
<para>這動作應該會在 <filename class="directory">/dev/mirror</filename>
|
||||
下建立 <devicename>gm0</devicename> 裝置結點(device node)。</para>
|
||||
</note>
|
||||
|
||||
|
|
@ -274,12 +274,12 @@ Done.</screen>
|
|||
|
||||
<para>系統會印出許多資訊和一大堆數字，這是正常的。
|
||||
確認是否有認何錯誤，接著就可以將這個裝置掛載到
|
||||
<filename role="directory">/mnt</filename> 掛載點(mount mount)：</para>
|
||||
<filename class="directory">/mnt</filename> 掛載點(mount mount)：</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>mount /dev/mirror/gm0s1a /mnt</userinput></screen>
|
||||
|
||||
<para>接著將原本開機磁碟的資料搬移到新的檔案系統
|
||||
(<filename role="directory">/mnt</filename>)。範例是用
|
||||
(<filename class="directory">/mnt</filename>)。範例是用
|
||||
&man.dump.8; 和 &man.restore.8; ，不過用 &man.dd.1; 也可以。</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>dump -L -0 -f- / |(cd /mnt && restore -r -v -f-)</userinput></screen>
|
||||
|
|
|
|||
|
|
@ -217,9 +217,9 @@
|
|||
<callout arearefs="jailpath">
|
||||
<para>首先就是先為 jail 找個家。 該路徑是在 host 系統中的 jail
|
||||
實體位置。 習慣是放在 <filename
|
||||
role="directory">/usr/jail/<replaceable>jailname</replaceable></filename>，
|
||||
class="directory">/usr/jail/<replaceable>jailname</replaceable></filename>，
|
||||
<replaceable>jailname</replaceable> 請替換為該 jail 的 hostname
|
||||
以便辨別。 通常 <filename role="directory">/usr</filename>
|
||||
以便辨別。 通常 <filename class="directory">/usr</filename>
|
||||
會有足夠空間來存放 jail 檔案系統，對於 <quote>complete</quote> jail
|
||||
而言，它通常包括了 &os; 預設安裝 base system 所有檔案的拷貝檔。</para>
|
||||
</callout>
|
||||
|
|
@ -234,9 +234,9 @@
|
|||
<para>使用 <maketarget>distribution</maketarget> 這個
|
||||
<application>make</application> target 來裝所有會用到的設定檔。
|
||||
簡單來說該動作就是把 <filename
|
||||
role="directory">/usr/src/etc/</filename> 複製到 jail 環境內的
|
||||
<filename role="directory">/etc</filename>，也就是
|
||||
<filename role="directory">$D/etc/</filename>。</para>
|
||||
class="directory">/usr/src/etc/</filename> 複製到 jail 環境內的
|
||||
<filename class="directory">/etc</filename>，也就是
|
||||
<filename class="directory">$D/etc/</filename>。</para>
|
||||
</callout>
|
||||
|
||||
<callout arearefs="jaildevfs">
|
||||
|
|
@ -497,35 +497,35 @@ jail_<replaceable>www</replaceable>_devfs_ruleset="<replaceable>www_ruleset</rep
|
|||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>每個 jail 都會掛載到 <filename
|
||||
role="directory">/home/j</filename> 底下的其中一個目錄。</para>
|
||||
class="directory">/home/j</filename> 底下的其中一個目錄。</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><filename role="directory">/home/j/mroot</filename> 則是每個
|
||||
<para><filename class="directory">/home/j/mroot</filename> 則是每個
|
||||
jail 共用的模版，並對於所有 jail 而言都是唯讀。</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>每個 jail 在 <filename role="directory">/home/j</filename>
|
||||
<para>每個 jail 在 <filename class="directory">/home/j</filename>
|
||||
底下都有一個相對應的空目錄。</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>每個 jail 都會有 <filename
|
||||
role="directory">/s</filename> 目錄，
|
||||
class="directory">/s</filename> 目錄，
|
||||
該目錄會連到系統的可讀寫部分。</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>每個 jail 都會在 <filename
|
||||
role="directory">/home/j/skel</filename> 目錄建立自屬的可讀寫空間
|
||||
class="directory">/home/j/skel</filename> 目錄建立自屬的可讀寫空間
|
||||
。</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>每個 jailspace (各 jail 可讀寫的部分) 都建在 <filename
|
||||
role="directory">/home/js</filename>>。</para>
|
||||
class="directory">/home/js</filename>>。</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<note>
|
||||
<para>這邊假設所有 jail 都放在
|
||||
<filename role="directory">/home</filename> 分割區。 當然，
|
||||
<filename class="directory">/home</filename> 分割區。 當然，
|
||||
也可以依自身需求更改，但接下來的例子中，
|
||||
也要記得修改相對應的地方。</para>
|
||||
</note>
|
||||
|
|
@ -588,7 +588,7 @@ jail_<replaceable>www</replaceable>_devfs_ruleset="<replaceable>www_ruleset</rep
|
|||
<step>
|
||||
<para>現在把可讀寫的檔案系統以 symlink 方式連到唯讀的檔案系統。
|
||||
請確認 symbolic link 是否有正確連到 <filename
|
||||
role="directory">s/</filename> 目錄，若目錄建立方式不對，
|
||||
class="directory">s/</filename> 目錄，若目錄建立方式不對，
|
||||
或指向位置不對，可能會導致安裝失敗。</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /home/j/mroot</userinput>
|
||||
|
|
@ -671,11 +671,11 @@ jail_www_devfs_enable="YES"</programlisting>
|
|||
<warning>
|
||||
<para>之所以要把
|
||||
<varname>jail_<replaceable>name</replaceable>_rootdir</varname>
|
||||
從 <filename role="directory">/home</filename> 改為 <filename
|
||||
role="directory">/usr/home</filename> 的原因在於 &os;
|
||||
從 <filename class="directory">/home</filename> 改為 <filename
|
||||
class="directory">/usr/home</filename> 的原因在於 &os;
|
||||
預設安裝的 <filename
|
||||
role="directory">/home</filename> 目錄其實只是指向 <filename
|
||||
role="directory">/usr/home</filename> 的 symbolic link。 而
|
||||
class="directory">/home</filename> 目錄其實只是指向 <filename
|
||||
class="directory">/usr/home</filename> 的 symbolic link。 而
|
||||
<varname>jail_<replaceable>name</replaceable>_rootdir</varname>
|
||||
變數須為 <emphasis>實體目錄</emphasis> 而非 symbolic link，
|
||||
否則 jail 會拒絕啟動。 可以用 &man.realpath.1;
|
||||
|
|
@ -740,7 +740,7 @@ jail_www_devfs_enable="YES"</programlisting>
|
|||
<procedure>
|
||||
<step>
|
||||
<para>首先是照一般方式來升級 host system，再新增臨時的唯讀模版
|
||||
<filename role="directory">/home/j/mroot2</filename>：</para>
|
||||
<filename class="directory">/home/j/mroot2</filename>：</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>mkdir /home/j/mroot2</userinput>
|
||||
&prompt.root; <userinput>cd /usr/src</userinput>
|
||||
|
|
@ -785,7 +785,7 @@ jail_www_devfs_enable="YES"</programlisting>
|
|||
&prompt.root; <userinput>umount /home/j/www</userinput></screen>
|
||||
|
||||
<note>
|
||||
<para>可讀寫空間(<filename role="directory">/s</filename>)
|
||||
<para>可讀寫空間(<filename class="directory">/s</filename>)
|
||||
是掛載在唯讀檔案系統底下，故要先卸載。</para>
|
||||
</note>
|
||||
</step>
|
||||
|
|
|
|||
|
|
@ -306,7 +306,7 @@ ath_hal(4) - Atheros Hardware Access Layer (HAL)</programlisting>
|
|||
|
||||
<step>
|
||||
<para>出ち勧<EFBFBD> <filename
|
||||
role="directory">/usr/src</filename> 目錄：</para>
|
||||
class="directory">/usr/src</filename> 目錄：</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /usr/src</userinput></screen>
|
||||
</step>
|
||||
|
|
|
|||
|
|
@ -395,7 +395,7 @@ multi on</programlisting>
|
|||
<para>The shell scripts that
|
||||
<application>&mathematica;</application> created during
|
||||
installation have to be modified before you can use them. If
|
||||
you chose <filename role="directory">/usr/local/bin</filename>
|
||||
you chose <filename class="directory">/usr/local/bin</filename>
|
||||
as the directory to place the
|
||||
<application>&mathematica;</application> executables in, you
|
||||
will find symlinks in this directory to files called
|
||||
|
|
|
|||
|
|
@ -2430,7 +2430,7 @@ doc/zh_*</screen>
|
|||
|
||||
<note>
|
||||
<para>In the default installation
|
||||
<filename role="directory">/usr/ports</filename> is not
|
||||
<filename class="directory">/usr/ports</filename> is not
|
||||
created. If you run &os; 6.0-RELEASE, it should be created before
|
||||
<command>portsnap</command> is used. On more recent
|
||||
versions of &os; or <application>Portsnap</application>,
|
||||
|
|
|
|||
|
|
@ -267,7 +267,7 @@ lsof: /usr/ports/sysutils/lsof</screen>
|
|||
<screen>&prompt.root; <userinput>echo /usr/ports/*/*lsof*</userinput>
|
||||
/usr/ports/sysutils/lsof</screen>
|
||||
|
||||
<para>請注意，這也會顯示 <filename role="directory">/usr/ports/distfiles</filename> 目錄內有符合檔名的檔案。</para>
|
||||
<para>請注意，這也會顯示 <filename class="directory">/usr/ports/distfiles</filename> 目錄內有符合檔名的檔案。</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
|
@ -559,7 +559,7 @@ docbook =
|
|||
</note>
|
||||
|
||||
<para>第一次跑 <application>CVSup</application> 之前，請先確認
|
||||
<filename role="directory">/usr/ports</filename>
|
||||
<filename class="directory">/usr/ports</filename>
|
||||
是乾淨的！ 若你已經裝了 Ports Collection ，但又自行加上其他 patch
|
||||
檔，那麼 <application>CVSup</application>
|
||||
並不會刪除你自行加上的 patch 檔，這樣可能會導致要安裝某些軟體時，
|
||||
|
|
@ -643,7 +643,7 @@ docbook =
|
|||
|
||||
<step>
|
||||
<para>若 <filename
|
||||
role="directory">/usr/ports</filename> 目錄不存在的話，
|
||||
class="directory">/usr/ports</filename> 目錄不存在的話，
|
||||
就建立一下吧：</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>mkdir /usr/ports</userinput></screen>
|
||||
|
|
@ -651,7 +651,7 @@ docbook =
|
|||
|
||||
<step>
|
||||
<para>接下來，下載壓縮的 Ports Collection 定期更新檔到
|
||||
<filename role="directory">/var/db/portsnap</filename> 目錄。
|
||||
<filename class="directory">/var/db/portsnap</filename> 目錄。
|
||||
完成下載後，要斷線與否都可以。</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>portsnap fetch</userinput></screen>
|
||||
|
|
@ -659,13 +659,13 @@ docbook =
|
|||
|
||||
<step>
|
||||
<para>若是第一次跑 <application>Portsnap</application> 的話，
|
||||
則需要先解壓到 <filename role="directory">/usr/ports</filename>：
|
||||
則需要先解壓到 <filename class="directory">/usr/ports</filename>：
|
||||
</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>portsnap extract</userinput></screen>
|
||||
|
||||
<para>若已有 <filename
|
||||
role="directory">/usr/ports</filename> 而且只是想更新而已，
|
||||
class="directory">/usr/ports</filename> 而且只是想更新而已，
|
||||
那麼就照下面作：</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>portsnap update</userinput></screen>
|
||||
|
|
@ -1133,7 +1133,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
|
|||
也可以用來輕鬆升級已裝的軟體。 該工具可從 <filename
|
||||
role="package">ports-mgmt/portmanager</filename> port 安裝：</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd <filename role="directory">/usr/ports/ports-mgmt/portmanager</filename></userinput>
|
||||
<screen>&prompt.root; <userinput>cd <filename class="directory">/usr/ports/ports-mgmt/portmanager</filename></userinput>
|
||||
&prompt.root; <userinput>make install clean</userinput></screen>
|
||||
|
||||
<para>所有已裝的軟體，都可以輕鬆用類似下列指令來升級：</para>
|
||||
|
|
|
|||
Loading…
Reference in a new issue