doc-el commit 1086:5b3cacad803f - Translate section 19.5 & 19.6 ...
freebsd-doc-el at lists.hellug.gr
freebsd-doc-el at lists.hellug.gr
Sat Nov 29 00:02:55 EET 2008
changeset: 1086:5b3cacad803f
user: Manolis Kiagias <sonicy at otenet.gr>
date: 2008-11-23 22:50 +0200
details: http://hg.hellug.gr/freebsd/doc-el/?cmd=changeset;node=5b3cacad803f
description:
Translate section 19.5 & 19.6 ('geom' chapter)
diffstat:
1 file changed, 111 insertions(+), 106 deletions(-)
el_GR.ISO8859-7/books/handbook/geom/chapter.sgml | 217 +++++++++++-----------
diffs (285 lines):
diff -r a650695dee72 -r 5b3cacad803f el_GR.ISO8859-7/books/handbook/geom/chapter.sgml
--- a/el_GR.ISO8859-7/books/handbook/geom/chapter.sgml Sat Nov 22 19:40:39 2008 +0200
+++ b/el_GR.ISO8859-7/books/handbook/geom/chapter.sgml Sun Nov 23 22:50:48 2008 +0200
@@ -445,53 +445,55 @@
</sect1>
<sect1 id="geom-ggate">
- <title>GEOM Gate Network Devices</title>
+ <title>ÄéêôõáêÝò ÓõóêåõÝò ìÝóù GEOM Gate</title>
- <para>GEOM supports the remote use of devices, such as disks,
- CD-ROMs, files, etc. through the use of the gate utilities.
- This is similar to <acronym>NFS</acronym>.</para>
+ <para>Ôï GEOM õðïóôçñßæåé áðïìáêñõóìÝíç ÷ñÞóç óõóêåõþí, üðùò ïé óêëçñïß
+ äßóêïé, ôá CD-ROM, ôá áñ÷åßá ê.ë.ð. ÷ñçóéìïðïéþíôáò ôá âïçèçôéêÜ
+ ðñïãñÜììáôá ðýëçò (gate). Ç ëåéôïõñãßá åßíáé ðáñüìïéá ìå ôï
+ <acronym>NFS</acronym>.</para>
- <para>To begin, an exports file must be created. This file
- specifies who is permitted to access the exported resources and
- what level of access they are offered. For example, to export
- the fourth slice on the first <acronym>SCSI</acronym> disk, the
- following <filename>/etc/gg.exports</filename> is more than
- adequate:</para>
+ <para>Ãéá íá îåêéíÞóåôå, ðñÝðåé íá äçìéïõñãÞóåôå Ýíá áñ÷åßï exports. Ôï
+ áñ÷åßï áõôü êáèïñßæåé ðïéïò åðéôñÝðåôáé íá áðïêôÞóåé ðñüóâáóç óôïõò
+ êïéíü÷ñçóôïõò ðüñïõò êáé ôé åðéðÝäïõ èá åßíáé áõôÞ ç ðñüóâáóç. Ãéá
+ ðáñÜäåéãìá, ãéá íá äéáìïéñÜóåôå ôçí ôÝôáñôç êáôÜôìçóç (slice) ôïõ ðñþôïõ
+ äßóêïõ <acronym>SCSI</acronym>, åßíáé áñêåôü íá äçìéïõñãÞóåôå ôï
+ ðáñáêÜôù áñ÷åßï <filename>/etc/gg.exports</filename>:</para>
<programlisting>192.168.1.0/24 RW /dev/da0s4d</programlisting>
- <para>It will allow all hosts inside the private network access
- the file system on the <devicename>da0s4d</devicename>
- partition.</para>
+ <para>Ôï ðáñáðÜíù èá åðéôñÝøåé óå üëïõò ôïõò õðïëïãéóôÝò ôïõ éäéùôéêïý
+ óáò äéêôýïõ, íá Ý÷ïõí ðñüóâáóç ìÝóù äéêôýïõ óôï óýóôçìá áñ÷åßùí ôçò
+ êáôÜôìçóçò <devicename>da0s4d</devicename>.</para>
- <para>To export this device, ensure it is not currently mounted,
- and start the &man.ggated.8; server daemon:</para>
+ <para>Ãéá íá äéáìïéñÜóåôå áõôÞ ôç óõóêåõÞ, âåâáéùèåßôå üôé äåí åßíáé
+ ðñïóáñôçìÝíç ôç äåäïìÝíç óôéãìÞ, êáé îåêéíÞóôå ôï äáßìïíá åîõðçñåôçôÞ
+ &man.ggated.8;:</para>
<screen>&prompt.root; <userinput>ggated</userinput></screen>
- <para>Now to <command>mount</command> the device on the client
- machine, issue the following commands:</para>
+ <para>Ãéá íá ðñïóáñôÞóåôå ôçí óõóêåõÞ óôï ìç÷Üíçìá ðåëÜôç, ÷ñçóéìïðïéÞóôå
+ ôéò áêüëïõèåò åíôïëÝò:</para>
<screen>&prompt.root; <userinput>ggatec create -o rw 192.168.1.1 /dev/da0s4d</userinput>
ggate0
&prompt.root; <userinput>mount /dev/ggate0 /mnt</userinput></screen>
- <para>From here on, the device may be accessed through the
- <filename class="directory">/mnt</filename> mount point.</para>
+ <para>Áðü åäþ êáé óôï åîÞò, ìðïñåßôå íá Ý÷åôå ðñüóâáóç óôç óõóêåõÞ ìÝóù
+ ôïõ óçìåßïõ ðñïóÜñôçóçò <filename class="directory">/mnt</filename>.</para>
<note>
- <para>It should be pointed out that this will fail if the device
- is currently mounted on either the server machine or any other
- machine on the network.</para>
+ <para>ÐñÝðåé íá ôïíéóôåß üôé ç äéáäéêáóßá èá áðïôý÷åé, áí ç óõóêåõÞ
+ åßíáé ôç äåäïìÝíç óôéãìÞ ðñïóáñôçìÝíç, åßôå óôïí åîõðçñåôçôÞ, åßôå óå
+ ïðïéïäÞðïôå Üëëï õðïëïãéóôÞ óôï äßêôõï.</para>
</note>
- <para>When the device is no longer needed, it may be safely
- unmounted with the &man.umount.8; command, similar to any other
- disk device.</para>
+ <para>¼ôáí äåí ÷ñåéÜæåóôå ðëÝïí ôç óõóêåõÞ, ìðïñåßôå íá ôçí
+ áðïðñïóáñôÞóåôå ìå áóöÜëåéá, ÷ñçóéìïðïéþíôáò ôçí åíôïëÞ &man.umount.8;,
+ üðùò êÜíåôå êáé ìå ïðïéáäÞðïôå Üëëç óõóêåõÞ äßóêïõ.</para>
</sect1>
<sect1 id="geom-glabel">
- <title>Labeling Disk Devices</title>
+ <title>Äçìéïõñãþíôáò ÅôéêÝôåò (Labels) óôéò ÓõóêåõÝò Äßóêùí</title>
<indexterm>
<primary>GEOM</primary>
@@ -500,116 +502,119 @@
<primary>Disk Labels</primary>
</indexterm>
- <para>During system initialization, the &os; kernel will create
- device nodes as devices are found. This method of probing for
- devices raises some issues, for instance what if a new disk
- device is added via <acronym>USB</acronym>? It is very likely
- that a flash device may be handed the device name of
- <devicename>da0</devicename> and the original
- <devicename>da0</devicename> shifted to
- <devicename>da1</devicename>. This will cause issues mounting
- file systems if they are listed in
- <filename>/etc/fstab</filename>, effectively, this may also
- prevent the system from booting.</para>
+ <para>ÊáôÜ ôç äéÜñêåéá ôçò áñ÷éêïðïßçóçò, óôçí åêêßíçóç ôïõ óõóôÞìáôïò,
+ ï ðõñÞíáò ôïõ &os; èá äçìéïõñãÞóåé ôá áðáñáßôçôá áñ÷åßá ãéá êÜèå
+ óõóêåõÞ ðïõ áíé÷íåýåé. ÁõôÞ ç ìÝèïäïò áíß÷íåõóçò óõóêåõþí, ìðïñåß íá
+ äçìéïõñãÞóåé ðñïâëÞìáôá. Ãéá ðáñÜäåéãìá, ôé èá ãßíåé áí ðñïóèÝóïõìå Ýíá
+ íÝï äßóêï <acronym>USB</acronym>; Åßíáé áñêåôÜ ðéèáíü ìéá óõóêåõÞ
+ ìíÞìçò flash íá ðÜñåé ôï üíïìá <devicename>da0</devicename> êáé ç
+ áñ÷éêÞ <devicename>da0</devicename> íá ìåôáêéíçèåß óôï
+ <devicename>da1</devicename>. Áõôü èá ðñïêáëÝóåé ðñïâëÞìáôá óôçí
+ ðñïóÜñôçóç ôùí óõóôçìÜôùí áñ÷åßùí, áí õðÜñ÷ïõí ïé áíôßóôïé÷åò
+ êáôá÷ùñÞóåéò ôïõò óôï <filename>/etc/fstab</filename>, êáé ìðïñåß áêüìá
+ êáé íá ðáñåìðïäßóåé ôçí êáíïíéêÞ åêêßíçóç ôïõ óõóôÞìáôïò.</para>
- <para>One solution to this issue is to chain the
- <acronym>SCSI</acronym> devices in order so a new device added to
- the <acronym>SCSI</acronym> card will be issued unused device
- numbers. But what about <acronym>USB</acronym> devices which may
- replace the primary <acronym>SCSI</acronym> disk? This happens
- because <acronym>USB</acronym> devices are usually
- probed before the <acronym>SCSI</acronym> card. One solution
- is to only insert these devices after the system has been
- booted. Another method could be to use only a single
- <acronym>ATA</acronym> drive and never list the
- <acronym>SCSI</acronym> devices in
- <filename>/etc/fstab</filename>.</para>
+ <para>Ìéá ëýóç åßíáé íá ñõèìßóåôå ôéò óõóêåõÝò <acronym>SCSI</acronym> ìå
+ ôÝôïéï ôñüðï, þóôå ç áñßèìçóç ôïõò íá åßíáé óõíå÷üìåíç. ¸ôóé, êÜèå
+ öïñÜ ðïõ ðñïóèÝôåôå ìéá íÝá óõóêåõÞ óôïí åëåãêôÞ <acronym>SCSI</acronym>
+ èá åßóôå óßãïõñïò üôé èá ëÜâåé áñéèìü ðïõ äåí Ý÷åé ÷ñçóéìïðïéçèåß.
+ ÁëëÜ ôé ãßíåôáé ìå ôéò óõóêåõÝò <acronym>USB</acronym> ðïõ ìðïñåß íá
+ áíôéêáôáóôÞóïõí ôïí êýñéï <acronym>SCSI</acronym> äßóêï; Áõôü ìðïñåß
+ ðñÜãìáôé íá óõìâåß, êáèþò ïé óõóêåõÝò <acronym>USB</acronym>
+ áíé÷íåýïíôáé êáôÜ âÜóç ðñéí áðü ôïí åëåãêôÞ <acronym>SCSI</acronym>.
+ Ìéá ëýóç åßíáé íá âÜæåôå ôéò óõóêåõÝò áõôÝò, ìüíï ìåôÜ ôçí åêêßíçóç
+ ôïõ óõóôÞìáôïò. Ìéá Üëëç ìÝèïäïò åßíáé íá ÷ñçóéìïðïéåßôå ìüíï ìéá
+ óõóêåõÞ ôýðïõ <acronym>ATA</acronym> êáé íá ìçí êáôá÷ùñåßôå ðïôÝ ôïõò
+ äßóêïõò <acronym>SCSI</acronym> óôï <filename>/etc/fstab</filename>.</para>
- <para>A better solution is available. By using the
- <command>glabel</command> utility, an administrator or user may
- label their disk devices and use these labels in
- <filename>/etc/fstab</filename>. Because
- <command>glabel</command> stores the label in the last sector of
- a given provider, the label will remain persistent across reboots.
- By using this label as a device, the file system may always be
- mounted regardless of what device node it is accessed
- through.</para>
+ <para>ÕðÜñ÷åé ùóôüóï êáëýôåñç ëýóç. ×ñçóéìïðïéþíôáò ôï âïçèçôéêü
+ ðñüãñáììá <command>glabel</command>, Ýíáò äéá÷åéñéóôÞò Þ ÷ñÞóôçò, ìðïñåß
+ íá áðïäþóåé åôéêÝôåò óôéò óõóêåõÝò äßóêùí êáé íá ÷ñçóéìïðïéÞóåé áõôÝò
+ ôéò åôéêÝôåò óôï <filename>/etc/fstab</filename>. ÅðåéäÞ ç
+ <command>glabel</command> áðïèçêåýåé ôçí åôéêÝôá óôïí ôåëåõôáßï ôïìÝá
+ ôïõ êÜèå ðáñï÷Ýá (óõóêåõÞò äßóêïõ), ç åôéêÝôá äéáôçñåßôáé êáé ìåôÜ áðü
+ ôçí åðáíåêêßíçóç ôïõ óõóôÞìáôïò. ×ñçóéìïðïéþíôáò áõôÞ ôçí åôéêÝôá ùò
+ üíïìá óõóêåõÞò, èá ìðïñåßôå íá ðñïóáñôÞóåôå ðÜíôá ôï óýóôçìá áñ÷åßùí,
+ Üó÷åôá ìå ôï ðñáãìáôéêü üíïìá óõóêåõÞò ðïõ Ý÷åé áðïäïèåß óôï
+ äßóêï.</para>
<note>
- <para>This goes without saying that a label be permanent. The
- <command>glabel</command> utility may be used to create both a
- transient and permanent label. Only the permanent label will
- remain consistent across reboots. See the &man.glabel.8;
- manual page for more information on the differences between
- labels.</para>
+ <para>Äåí ÷ñåéÜæåôáé öõóéêÜ íá ôïíßóïõìå üôé áõôÞ ç åôéêÝôá èá ðñÝðåé
+ íá åßíáé ìüíéìç. Ôï âïçèçôéêü ðñüãñáììá <command>glabel</command>
+ ìðïñåß íá äçìéïõñãÞóåé ôüóï ìüíéìåò, üóï êáé ðñïóùñéíÝò åôéêÝôåò.
+ Ìüíï ïé ìüíéìåò åôéêÝôåò äéáôçñïýíôáé áíÝðáöåò ìÝôá áðü
+ åðáíåêêéíÞóåéò. Äåßôå ôç óåëßäá manual ôçò &man.glabel.8; ãéá
+ ðåñéóóüôåñåò ðëçñïöïñßåò ó÷åôéêÜ ìå ôá åßäç ôùí åôéêåôþí.</para>
</note>
<sect2>
- <title>Label Types and Examples</title>
+ <title>Åßäç Åôéêåôþí êáé Ðáñáäåßãìáôá</title>
- <para>There are two types of labels, a generic label and a
- file system label. The difference between the labels is
- the auto detection associated with permanent labels, and the
- fact that this type of label will be persistent across reboots.
- These labels are given a special directory in
- <filename class="directory">/dev</filename>, which will be named
- based on their file system type. For example,
- <acronym>UFS</acronym>2 file system labels will be created in
- the <filename class="directory">/dev/ufs</filename>
- directory.</para>
+ <para>ÕðÜñ÷ïõí äýï ôýðïé åôéêåôþí, ç ãåíéêÞ åôéêÝôá êáé ç åôéêÝôá
+ óõóôÞìáôïò áñ÷åßùí. Ç äéáöïñÜ ìåôáîý ôïõò, åßíáé ç áõôüìáôç
+ áíß÷íåõóç ðïõ ó÷åôßæåôáé ìå ôéò ìüíéìåò åôéêÝôåò, êáé ôï ãåãïíüò
+ üôé áõôïý ôïõ åßäïõò ïé åôéêÝôåò ðáñáìÝíïõí áíÝðáöåò ìåôÜ áðü ìéá
+ åðáíåêêßíçóç. Óôéò åôéêÝôåò áõôÝò ðáñá÷ùñåßôå Ýíáò åéäéêüò êáôÜëïãïò
+ ìÝóá óôïí <filename class="directory">/dev</filename>, ï ïðïßïò
+ ïíïìÜæåôáé áíÜëïãá ìå ôï åßäïò ôïõ óõóôÞìáôïò áñ÷åßùí ðïõ
+ ÷ñçóéìïðïéåßôáé. Ãéá ðáñÜäåéãìá, ïé åôéêÝôåò ðïõ áíáöÝñïíôáé óå
+ óýóôçìá áñ÷åßùí <acronym>UFS</acronym>2 èá äçìéïõñãçèïýí óôïí
+ êáôÜëïãï <filename class="directory">/dev/ufs</filename>.</para>
- <para>A generic label will go away with the next reboot. These
- labels will be created in the
- <filename class="directory">/dev/label</filename> directory and
- are perfect for experimentation.</para>
+ <para>Ç åôéêÝôá ãåíéêïý ôýðïõ åßíáé ðñïóùñéíÞ, êáé äéáãñÜöåôáé óôçí
+ åðüìåíç åðáíåêêßíçóç. Ïé åôéêÝôåò áõôÝò äçìéïõñãïýíôáé óôïí êáôÜëïãï
+ <filename class="directory">/dev/label</filename> êáé åßíáé ôÝëåéåò
+ ãéá ðåéñáìáôéóìïýò.</para>
<!-- XXXTR: How do you create a file system label without running newfs
or when there is no newfs (e.g.: cd9660)? -->
- <para>Permanent labels may be placed on the file system using the
- <command>tunefs</command> or <command>newfs</command>
- utilities. To create a permanent label for a
- <acronym>UFS</acronym>2 file system without destroying any
- data, issue the following command:</para>
+ <para>Ìðïñåßôå íá äçìéïõñãÞóåôå ìüíéìåò åôéêÝôåò óå Ýíá óýóôçìá áñ÷åßùí
+ ÷ñçóéìïðïéþíôáò ôçí åíôïëÞ <command>tunefs</command> Þ
+ <command>newfs</command>. Ãéá íá äçìéïõñãÞóåôå ìéá ìüíéìç åôéêÝôá
+ ãéá Ýíá óýóôçìá áñ÷åßùí <acronym>UFS</acronym>2, ÷ùñßò íá
+ êáôáóôñÝøåôå äåäïìÝíá, ÷ñçóéìïðïéÞóôå ôçí áêüëïõèç åíôïëÞ:</para>
<screen>&prompt.root; <userinput>tunefs -L <replaceable>home</replaceable> <replaceable>/dev/da3</replaceable></userinput></screen>
<warning>
- <para>If the file system is full, this may cause data
- corruption; however, if the file system is full then the
- main goal should be removing stale files and not adding
- labels.</para>
+ <para>Áí ôï óýóôçìá áñ÷åßùí åßíáé ãåìÜôï, ç ðáñáðÜíù åíôïëÞ ìðïñåß íá
+ ðñïêáëÝóåé êáôáóôñïöÞ äåäïìÝíùí. Ùóôüóï, áí ôï óýóôçìá áñ÷åßùí
+ åßíáé ãåìÜôï, óôü÷ïò óáò èá ðñÝðåé íá åßíáé íá äéáãñÜøåôå ôá
+ áñ÷åßá ðïõ äåí ÷ñçóéìïðïéïýíôáé êáé ü÷é íá ðñïóèÝôåôå
+ åôéêÝôåò.</para>
</warning>
- <para>A label should now exist in
- <filename class="directory">/dev/ufs</filename> which may be
- added to <filename>/etc/fstab</filename>:</para>
+ <para>Èá ðñÝðåé ôþñá íá õðÜñ÷åé ìéá åôéêÝôá óôïí êáôÜëïãï
+ <filename class="directory">/dev/ufs</filename> ç ïðïßá ìðïñåß íá
+ ðñïóôåèåß óôï <filename>/etc/fstab</filename>:</para>
<programlisting>/dev/ufs/home /home ufs rw 2 2</programlisting>
<note>
- <para>The file system must not be mounted while attempting
- to run <command>tunefs</command>.</para>
+ <para>Ôï óýóôçìá áñ÷åßùí äåí ðñÝðåé íá åßíáé ðñïóáñôçìÝíï êáèþò
+ åêôåëåßôå ôçí åíôïëÞ <command>tunefs</command>.</para>
</note>
- <para>Now the file system may be mounted like normal:</para>
+ <para>Ìðïñåßôå ôþñá íá ðñïóáñôÞóåôå ôï óýóôçìá áñ÷åßùí ìå ôï óõíÞèç
+ ôñüðï:</para>
<screen>&prompt.root; <userinput>mount /home</userinput></screen>
- <para>From this point on, so long as the
- <filename>geom_label.ko</filename> kernel module is loaded at
- boot with <filename>/boot/loader.conf</filename> or the
- <literal>GEOM_LABEL</literal> kernel option is present,
- the device node may change without any ill effect on the
- system.</para>
+ <para>Áðü åäþ êáé ðÝñá, êáé üóï ôï Üñèñùìá
+ <filename>geom_label.ko</filename> öïñôþíåôáé óôïí ðõñÞíá ìÝóù ôïõ
+ <filename>/boot/loader.conf</filename> Þ åöüóïí Ý÷åôå âÜëåé ôçí
+ åðéëïãÞ <literal>GEOM_LABEL</literal> óôïí ðõñÞíá óáò, áêüìá êáé áí
+ ôï üíïìá ôçò óõóêåõÞò áëëÜîåé, äåí èá Ý÷åé êáìéÜ äõóìåíÞ åðßäñáóç
+ óôï óýóôçìá óáò.</para>
- <para>File systems may also be created with a default label
- by using the <option>-L</option> flag with
- <command>newfs</command>. See the &man.newfs.8; manual page
- for more information.</para>
+ <para>Ìðïñåßôå åðßóçò íá äçìéïõñãÞóåôå óõóôÞìáôá áñ÷åßùí ìå
+ ðñïåðéëåãìÝíç åôéêÝôá, ÷ñçóéìïðïéþíôáò ôçí åðéëïãÞ
+ <option>-L</option> óôçí åíôïëÞ <command>newfs</command>. Äåßôå ôçí
+ óåëßäá manual &man.newfs.8; ãéá ðåñéóóüôåñåò ðëçñïöïñßåò.</para>
- <para>The following command can be used to destroy the
- label:</para>
+ <para>Ìðïñåßôå íá ÷ñçóéìïðïéÞóåôå ôçí ðáñáêÜôù åíôïëÞ ãéá íá
+ êáôáóôñÝøåôå ìéá åôéêÝôá:</para>
<screen>&prompt.root; <userinput>glabel destroy home</userinput></screen>
</sect2>
More information about the Freebsd-doc-el
mailing list