doc-el commit 960:334e589ba731 - Complete translation of entire ...
freebsd-doc-el at lists.hellug.gr
freebsd-doc-el at lists.hellug.gr
Mon Oct 27 18:40:23 EET 2008
changeset: 960:334e589ba731
user: Manolis Kiagias <sonicy at otenet.gr>
date: 2008-10-25 21:08 +0300
details: http://hg.hellug.gr/freebsd/doc-el/?cmd=changeset;node=334e589ba731
description:
Complete translation of entire 24.4 section (cutting-edge)
diffs (298 lines):
diff -r 6a9adc0c2a1d -r 334e589ba731 el_GR.ISO8859-7/books/handbook/cutting-edge/chapter.sgml
--- a/el_GR.ISO8859-7/books/handbook/cutting-edge/chapter.sgml Sat Oct 25 20:07:15 2008 +0300
+++ b/el_GR.ISO8859-7/books/handbook/cutting-edge/chapter.sgml Sat Oct 25 21:08:27 2008 +0300
@@ -1607,142 +1607,164 @@
<qandaentry>
<question>
- <para>Can interrupted builds be resumed?</para>
+ <para>Ìðïñþ íá óõíå÷ßóù ìéá ìåôáãëþôôéóç ðïõ äéÝêïøá;</para>
</question>
<answer>
- <para>This depends on how far through the process you got before
- you found a problem.</para>
+ <para>Áõôü åîáñôÜôáé áðü ôï ðüóï Ý÷åôå ðñï÷ùñÞóåé óôç äéáäéêáóßá
+ ìÝ÷ñé ðïõ âñÞêáôå ôï ðñüâëçìá.</para>
- <para><emphasis>In general</emphasis> (and this is not a hard and
- fast rule) the <command>make buildworld</command> process builds new
- copies of essential tools (such as &man.gcc.1;, and
- &man.make.1;) and the system libraries. These tools and
- libraries are then installed. The new tools and libraries are
- then used to rebuild themselves, and are installed again. The
- entire system (now including regular user programs, such as
- &man.ls.1; or &man.grep.1;) is then rebuilt with the new
- system files.</para>
+ <para><emphasis>Óå ãåíéêÝò ãñáììÝò</emphasis> (êáé áõôüò äåí
+ åßíáé êáíüíáò ðïõ éó÷ýåé ðÜíôá), ç äéåñãáóßá ôïõ
+ <command>make buildworld</command> ìåôáãëùôôßæåé íÝá áíôßãñáöá
+ âáóéêþí åñãáëåßùí (üðùò ôá &man.gcc.1;, êáé &man.make.1;) êáèþò
+ êáé ôùí âéâëéïèçêþí óõóôÞìáôïò. ¸ðåéôá åãêáèéóôïýíôáé áõôÜ
+ ôá åñãáëåßá êáé ïé âéâëéïèÞêåò. Ôá íÝá åñãáëåßá êáé
+ âéâëéïèÞêåò ÷ñçóéìïðïéïýíôáé Ýðåéôá ãéá íá åðáíáìåôáãëùôôßóïõí
+ ôïõò åáõôïýò ôïõ, êáé åãêáèßóôáíôáé îáíÜ. Ïëüêëçñï ôï óýóôçìá
+ (ôï ïðïßï ôþñá ðåñéëáìâÜíåé êáé ôá óõíçèéóìÝíá ðñïãñÜììáôá
+ ÷ñÞóôç üðùò ôï &man.ls.1; Þ ôï &man.grep.1;)
+ åðáíáìåôáãëùôôßæåôå ÷ñçóéìïðïéþíôáò ôá íÝá áñ÷åßá ôïõ
+ óõóôÞìáôïò.</para>
- <para>If you are at the last stage, and you know it (because you
- have looked through the output that you were storing) then you
- can (fairly safely) do:</para>
+ <para>Áí âñßóêåóôå óôï ôåëåõôáßï óôÜäéï, ôï ïðïßï èá ôï ãíùñßæåôå
+ êïéôÜæïíôáò ôçí Ýîïäï ðïõ Ý÷åôå áðïèçêåýóåé, åßíáé ó÷åôéêÜ
+ áóöáëÝò íá êÜíåôå:</para>
<screen><emphasis>… fix the problem …</emphasis>
&prompt.root; <userinput>cd /usr/src</userinput>
&prompt.root; <userinput>make -DNO_CLEAN all</userinput></screen>
- <para>This will not undo the work of the previous
+ <para>Ìå ôïí ôñüðï áõôü äåí èá áíáéñÝóåôå ôçí åñãáóßá ðïõ Ý÷åé
+ ãßíåé áðü ôï ðñïçãïýìåíï
<command>make buildworld</command>.</para>
- <para>If you see the message:</para>
+ <para>Áí äåßôå ôï ìÞíõìá:</para>
<screen>--------------------------------------------------------------
Building everything..
--------------------------------------------------------------</screen>
- <para>in the <command>make buildworld</command> output then it is
- probably fairly safe to do so.</para>
-
- <para>If you do not see that message, or you are not sure, then it
- is always better to be safe than sorry, and restart the build
- from scratch.</para>
+ <para>óôçí Ýîïäï ôçò åíôïëÞò <command>make buildworld</command>,
+ ôüôå åßíáé ìÜëëïí áóöáëÝò íá ðñï÷ùñÞóåôå ìå áõôü ôïí
+ ôñüðï.</para>
+
+ <para>Áí äåí äåßôå áõôü ôï ìÞíõìá, Þ áí äåí åßóôå óßãïõñïò, ôüôå
+ åßíáé êáëýôåñá íá êÜíåôå ðëÞñç ìåôáãëþôôéóç ðáñÜ íá ìåôáíéþíåôå
+ áñãüôåñá.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
- <para>How can I speed up making the world?</para>
+ <para>Ðùò ìðïñþ íá åðéôá÷ýíù ôç ìåôáãëþôôéóç ôïõ âáóéêïý
+ óõóôÞìáôïò;</para>
</question>
<answer>
<itemizedlist>
<listitem>
- <para>Run in single user mode.</para>
+ <para>ÅêôåëÝóôå ôçí óå êáôÜóôáóç åíüò ÷ñÞóôç.</para>
</listitem>
-
+
<listitem>
- <para>Put the <filename>/usr/src</filename> and
- <filename>/usr/obj</filename> directories on separate
- file systems held on separate disks. If possible, put these
- disks on separate disk controllers.</para>
+ <para>ÂÜëôå ôïõò êáôáëüãïõò <filename>/usr/src</filename>
+ êáé <filename>/usr/obj</filename> óå äéáöïñåôéêÜ óõóôÞìáôá
+ áñ÷åßùí ôá ïðïßá âñßóêïíôáé êáé óå äéáöïñåôéêïýò öõóéêïýò
+ äßóêïõò. Áí åßíáé äõíáôüí, âÜëôå áõôïýò ôïõò äßóêïõò óå
+ ÷ùñéóôïýò åëåãêôÝò.</para>
</listitem>
-
+
<listitem>
- <para>Better still, put these file systems across multiple
- disks using the &man.ccd.4; (concatenated disk
- driver) device.</para>
+ <para>Áêüìá êáëýôåñá, ìïéñÜóôå áõôÜ ôá óõóôÞìáôá áñ÷åßùí
+ óå ðïëëáðëïýò äßóêïõò, ÷ñçóéìïðïéþíôáò ôï ðñüãñáììá
+ ïäÞãçóçò &man.ccd.4; (concatenated disk driver, ïäÞãçóçò
+ óõíåíùìÝíùí äßóêùí).</para>
</listitem>
-
+
<listitem>
- <para>Turn off profiling (set <quote>NO_PROFILE=true</quote> in
- <filename>/etc/make.conf</filename>). You almost certainly
- do not need it.</para>
+ <para>ÁðåíåñãïðïéÞóôå ôï profiling (èÝóôå ôçí ìåôáâëçôÞ
+ <quote>NO_PROFILE=true</quote> óôï
+ <filename>/etc/make.conf</filename>). Åßíáé ó÷åäüí óßãïõñï
+ üôé äåí ôï ÷ñåéÜæåóôå.</para>
</listitem>
-
+
<listitem>
- <para>Also in <filename>/etc/make.conf</filename>, set
- <makevar>CFLAGS</makevar> to something like <option>-O
- -pipe</option>. The optimization <option>-O2</option> is much
- slower, and the optimization difference between
- <option>-O</option> and <option>-O2</option> is normally
- negligible. <option>-pipe</option> lets the compiler use
- pipes rather than temporary files for communication, which
- saves disk access (at the expense of memory).</para>
+ <para>Óôï áñ÷åßï <filename>/etc/make.conf</filename>, èÝóôå
+ ôï <makevar>CFLAGS</makevar> óå êÜôé üðùò
+ <option>-O -pipe</option>. Ç âåëôéóôïðïßçóç
+ <option>-O2</option> ÷ñåéÜæåôáé áñêåôÜ ðåñéóóüôåñï ÷ñüíï,
+ êáé ç äéáöïñÜ áðüäïóçò ìåôáîý
+ <option>-O</option> êáé <option>-O2</option> åßíáé óõíÞèùò
+ áìåëçôÝá. Ôï <option>-pipe</option> åðéôñÝðåé óôïí
+ ìåôáãëùôôéóôÞ íá ÷ñçóéìïðïéÞóåé pipes ãéá åðéêïéíùíßá áíôß
+ ãéá ðñïóùñéíÜ áñ÷åßá. Áõôü êáôáíáëþíåé ðåñéóóüôåñç ìíÞìç,
+ áëëÜ ÷ñçóéìïðïéåß ëéãüôåñï ôï óêëçñü äßóêï.</para>
</listitem>
-
+
<listitem>
- <para>Pass the <option>-j<replaceable>n</replaceable></option> option to &man.make.1; to
- run multiple processes in parallel. This usually helps
- regardless of whether you have a single or a multi processor
- machine.</para>
+ <para>×ñçóéìïðïéÞóôå ôçí åðéëïãÞ
+ <option>-j<replaceable>n</replaceable></option> óôï
+ &man.make.1; þóôå íá åêôåëïýíôáé ðáñÜëëçëá ðïëëáðëÝò
+ äéåñãáóßåò ìåôáãëþôôéóçò. Áõôü óõíÞèùò âïçèÜåé áêüìá êáé
+ óå ðåñßðôùóç ðïõ Ý÷åôå ìç÷Üíçìá ìå Ýíá åðåîåñãáóôÞ.</para>
</listitem>
-
- <listitem><para>The file system holding
- <filename>/usr/src</filename> can be mounted (or remounted)
- with the <option>noatime</option> option. This prevents the
- file system from recording the file access time. You probably
- do not need this information anyway.</para>
-
+
+ <listitem>
+ <para>Ìðïñåßôå íá ðñïóáñôÞóåôå (Þ íá åðáíáðñïóáñôÞóåôå) ôï
+ óýóôçìá áñ÷åßùí óôï ïðïßï åßíáé áðïèçêåõìÝíï ôï
+ <filename>/usr/src</filename> ìå ôçí åðéëïãÞ
+ <option>noatime</option>. Áõôü áðïôñÝðåé ôçí êáôáãñáöÞ
+ çìåñïìçíßáò / þñáò ðñüóâáóçò óôï óýóôçìá áñ÷åßùí. ÊáôÜ
+ ðéèáíüôçôá äåí ÷ñåéÜæåóôå áõôÞ ôçí ðëçñïöïñßá Ýôóé êáé
+ áëëéþò.</para>
+
<screen>&prompt.root; <userinput>mount -u -o noatime /usr/src</userinput></screen>
-
+
<warning>
- <para>The example assumes <filename>/usr/src</filename> is
- on its own file system. If it is not (if it is a part of
- <filename>/usr</filename> for example) then you will
- need to use that file system mount point, and not
- <filename>/usr/src</filename>.</para>
+ <para>Ôï ðáñÜäåéãìá ðñïõðïèÝôå üôé Ý÷åôå ôï
+ <filename>/usr/src</filename> óôï äéêü ôïõ óýóôçìá
+ áñ÷åßùí. Áí áõôü äåí óõìâáßíåé (áí åßíáé ìÝñïò ôïõ
+ <filename>/usr</filename> ãéá ðáñÜäåéãìá) èá ÷ñåéáóôåß
+ íá ÷ñçóéìïðïéÞóåôå áõôü ôï óçìåßï ðñïóÜñôçóçò, êáé ü÷é
+ ôï <filename>/usr/src</filename>.</para>
</warning>
</listitem>
-
+
<listitem>
- <para>The file system holding <filename>/usr/obj</filename> can
- be mounted (or remounted) with the <option>async</option>
- option. This causes disk writes to happen asynchronously.
- In other words, the write completes immediately, and the
- data is written to the disk a few seconds later. This
- allows writes to be clustered together, and can be a
- dramatic performance boost.</para>
+ <para>Ìðïñåßôå íá ðñïóáñôÞóåôå (Þ íá åðáíáðñïóáñôÞóåôå) ôï
+ óýóôçìá áñ÷åßùí ðïõ ðåñéÝ÷åé ôï
+ <filename>/usr/obj</filename> ìå ôçí åðéëïãÞ
+ <option>async</option>. Ìå ôïí ôñüðï áõôü, ïé åããñáöÝò óôï
+ äßóêï èá ãßíïíôáé áóýã÷ñïíá. Ìå Üëëá ëüãéá, ïé åããñáöÝò
+ ïëïêëçñþíïíôáé Üìåóá, åíþ ç ðñáãìáôéêÞ åããñáöÞ óôï äßóêï
+ ãßíåôáé ëßãá äåõôåñüëåðôá áñãüôåñá. Áõôü åðéôñÝðåé ôçí
+ ïìáäïðïßçóç ôùí åããñáöþí, ôï ïðïßï ìðïñåß íá ðñïóöÝñåé
+ äñáìáôéêÞ âåëôßùóç áðüäïóçò.</para>
<warning>
- <para>Keep in mind that this option makes your file system
- more fragile. With this option there is an increased
- chance that, should power fail, the file system will be in
- an unrecoverable state when the machine restarts.</para>
-
- <para>If <filename>/usr/obj</filename> is the only thing on
- this file system then it is not a problem. If you have
- other, valuable data on the same file system then ensure
- your backups are fresh before you enable this
- option.</para>
+ <para>Íá Ý÷åôå õðüøéí óáò üôé áõôÞ ç åðéëïãÞ ìðïñåß íá
+ êÜíåé ôï óýóôçìá áñ÷åßùí óáò ðïëý ðéï åõáßóèçôï. Ìå ôçí
+ åðéëïãÞ áõôÞ, õðÜñ÷åé áõîçìÝíç ðéèáíüôçôá ôï óýóôçìá
+ áñ÷åßùí ìåôÜ áðü åðáíåêêßíçóç íá âñåèåß óå ìç
+ åðéóêåõÜóéìç êáôÜóôáóç áí õðÜñîåé äéáêïðÞ
+ ñåýìáôïò.</para>
+
+ <para>Áí ôï óýóôçìá áñ÷åßùí ðåñéÝ÷åé ìüíï ôï
+ <filename>/usr/obj</filename>, ôï ðáñáðÜíù äåí åßíáé
+ ðñüâëçìá. Áí ùóôüóï Ý÷åôå êáé Üëëá ðïëýôéìá äåäïìÝíá
+ óôï ßäéï óýóôçìá áñ÷åßùí, óéãïõñåõôåßôå üôé Ý÷åôå
+ åíçìåñùìÝíá áíôßãñáöá áóöáëåßáò ðñéí åíåñãïðïéÞóåôå áõôÞ
+ ôçí åðéëïãÞ.</para>
</warning>
-
+
<screen>&prompt.root; <userinput>mount -u -o async /usr/obj</userinput></screen>
-
+
<warning>
- <para>As above, if <filename>/usr/obj</filename> is not on
- its own file system, replace it in the example with the
- name of the appropriate mount point.</para>
+ <para>¼ðùò êáé ðñïçãïõìÝíùò, áí ôï
+ <filename>/usr/obj</filename> äåí åßíáé óýóôçìá áñ÷åßùí
+ áðü ìüíï ôïõ, áíôéêáôáóôÞóôå ôï óôï ðáñÜäåéãìá ìå ôï
+ üíïìá ôïõ ðñáãìáôéêïý óçìåßïõ ðñïóÜñôçóçò.</para>
</warning>
</listitem>
</itemizedlist>
@@ -1751,13 +1773,12 @@
<qandaentry>
<question>
- <para>What do I do if something goes wrong?</para>
+ <para>Ôé íá êÜíù áí êÜôé ðÜåé óôñáâÜ;</para>
</question>
<answer>
- <para>Make absolutely sure your environment has no
- extraneous cruft from earlier builds. This is simple
- enough.</para>
+ <para>Óéãïõñåõôåßôå üôé ôï ðåñéâÜëëïí óáò äåí Ý÷åé õðïëåßììáôá
+ áðü ðñïçãïýìåíåò ìåôáãëùôôßóåéò. Áõôü åßíáé áñêåôÜ áðëü.</para>
<screen>&prompt.root; <userinput>chflags -R noschg /usr/obj/usr</userinput>
&prompt.root; <userinput>rm -rf /usr/obj/usr</userinput>
@@ -1765,16 +1786,16 @@
&prompt.root; <userinput>make cleandir</userinput>
&prompt.root; <userinput>make cleandir</userinput></screen>
- <para>Yes, <command>make cleandir</command> really should
- be run twice.</para>
+ <para>Íáé, èá ðñåÝðåé íá åêôåëÝóåôå ôï
+ <command>make cleandir</command> äýï öïñÝò.</para>
- <para>Then restart the whole process, starting
- with <command>make buildworld</command>.</para>
+ <para>ÅðáíåêêéíÞóôå Ýðåéôá üëç ôç äéáäéêáóßá, îåêéíþíôáò ìå ôï
+ <command>make buildworld</command>.</para>
- <para>If you still have problems, send the error and the
- output of <command>uname -a</command> to &a.questions;.
- Be prepared to answer other questions about your
- setup!</para>
+ <para>Áí Ý÷åôå áêüìá ðñïâëÞìáôá, óôåßëôå ôï ìÞíõìá ëÜèïõò êáé ôçí
+ Ýîïäï ôïõ <command>uname -a</command> óôçí &a.questions;. Íá
+ åßóôå ðñïåôïéìáóìÝíïé íá áðáíôÞóåôå åðéðëÝïí åñùôÞóåéò ó÷åôéêÜ
+ ìå ôçí åãêáôÜóôáóç óáò!</para>
</answer>
</qandaentry>
</qandaset>
More information about the Freebsd-doc-el
mailing list