doc-el commit 952:7c7964e7b1b8 - Tranlated 24.4.6 - 24.4.7 (cutt...
freebsd-doc-el at lists.hellug.gr
freebsd-doc-el at lists.hellug.gr
Mon Oct 27 18:39:55 EET 2008
changeset: 952:7c7964e7b1b8
user: Manolis Kiagias <sonicy at otenet.gr>
date: 2008-10-24 13:19 +0300
details: http://hg.hellug.gr/freebsd/doc-el/?cmd=changeset;node=7c7964e7b1b8
description:
Tranlated 24.4.6 - 24.4.7 (cutting-edge)
diffs (truncated from 330 to 300 lines):
diff -r b0a616875b2c -r 7c7964e7b1b8 el_GR.ISO8859-7/books/handbook/cutting-edge/chapter.sgml
--- a/el_GR.ISO8859-7/books/handbook/cutting-edge/chapter.sgml Fri Oct 24 01:31:51 2008 +0300
+++ b/el_GR.ISO8859-7/books/handbook/cutting-edge/chapter.sgml Fri Oct 24 13:19:44 2008 +0300
@@ -885,20 +885,22 @@
</sect2>
<sect2>
- <title>Remove <filename>/usr/obj</filename></title>
+ <title>ÄéáãñÜøôå ôï <filename>/usr/obj</filename></title>
- <para>As parts of the system are rebuilt they are placed in
- directories which (by default) go under
- <filename>/usr/obj</filename>. The directories shadow those under
- <filename>/usr/src</filename>.</para>
+ <para>Êáèþò ãßíåôáé ç åðáíáìåôáãëþôôéóç, ôìÞìáôá ôïõ óõóôÞìáôïò
+ ôïðïèåôïýíôáé áðü ðñïåðéëïãÞ óå õðïêáôáëüãïõò ôïõ
+ <filename>/usr/obj</filename>. Ïé õðïêáôÜëïãïé áõôïß áíôéãñÜöïõí ôç
+ äïìÞ ðïõ áêïëïõèåßôáé óôï <filename>/usr/src</filename>.</para>
- <para>You can speed up the <command>make buildworld</command> process, and
- possibly save yourself some dependency headaches by removing this
- directory as well.</para>
+ <para>Ìðïñåßôå íá åðéôá÷ýíåôå ôç äéáäéêáóßá ôïõ
+ <command>make buildworld</command> êáé åðßóçò íá ãëõôþóåôå áðü êÜðïéá
+ ðéèáíÜ ðñïâëÞìáôá, áí äéáãñÜøåôå êáé áõôü ôïí êáôÜëïãï.</para>
- <para>Some files below <filename>/usr/obj</filename> may have the
- immutable flag set (see &man.chflags.1; for more information)
- which must be removed first.</para>
+ <para>ÊÜðïéá áñ÷åßá óå õðïêáôáëüãïõò ôïõ <filename>/usr/obj</filename>
+ ìðïñåß íá Ý÷ïõí ÷áñáêôçñéóôåß ùò immutable ìÝóù ôïõ áíôßóôïé÷ïõ flag
+ (ãéá ðåñéóóüôåñåò ëåðôïìÝñåéåò äåßôå ôï &man.chflags.1;). Ðñéí
+ äéáãñÜøåôå áõôÜ ôá áñ÷åßá, èá ðñÝðåé ðñþôá íá êáôáñãÞóåôå áõôü ôï
+ flag.</para>
<screen>&prompt.root; <userinput>cd /usr/obj</userinput>
&prompt.root; <userinput>chflags -R noschg *</userinput>
@@ -906,165 +908,189 @@
</sect2>
<sect2 id="cutting-edge-compilebase">
- <title>Recompile the Base System</title>
+ <title>Åðáíáìåôáãëùôôßóôå ôï Âáóéêü Óýóôçìá</title>
<sect3>
- <title>Saving the Output</title>
+ <title>Áðïèçêåýóôå ôçí ¸îïäï</title>
- <para>It is a good idea to save the output you get from running
- &man.make.1; to another file. If something goes wrong you will
- have a copy of the error message. While this might not help you
- in diagnosing what has gone wrong, it can help others if you post
- your problem to one of the &os; mailing lists.</para>
+ <para>Êáèþò åêôåëåßôáé ç &man.make.1;, åßíáé êáëÞ éäÝá ç Ýîïäïò ôçò
+ íá áðïèçêåýåôáé óå êÜðïéï Üëëï áñ÷åßï. Áí êÜôé ðÜåé óôñáâÜ, èá
+ Ý÷åôå Ýíá áíôßãñáöï ôïõ ìçíýìáôïò ëÜèïõò. Áí êáé áõôü ßóùò äåí óáò
+ âïçèÞóåé íá âñåßôå ôé ðÞãå óôñáâÜ, ìðïñåß íá äéåõêïëýíåé Üëëïõò áí
+ óôåßëåôå ôï ìÞíõìá óáò óå ìéá áðü ôéò ëßóôåò çëåêôñïíéêïý
+ ôá÷õäñïìåßïõ ôïõ &os;.</para>
- <para>The easiest way to do this is to use the &man.script.1;
- command, with a parameter that specifies the name of the file to
- save all output to. You would do this immediately before
- rebuilding the world, and then type <userinput>exit</userinput>
- when the process has finished.</para>
+ <para>Ï åõêïëüôåñïò ôñüðïò ãéá íá ãßíåé áõôü åßíáé ÷ñçóéìïðïéþíôáò ôçí
+ åíôïëÞ &man.script.1;, ìå ìéá ðáñÜìåôñï ðïõ íá êáèïñßæåé ôï üíïìá
+ ôïõ áñ÷åßïõ óôï ïðïßï èá áðïèçêåõôåß ç Ýîïäïò. Èá ðñÝðåé íá
+ ôï åêôåëÝóåôå áìÝóùò ðñéí îåêéíÞóåôå ôçí ìåôáãëþôôéóç ôïõ âáóéêïý
+ óõóôÞìáôïò, êáé íá ãñÜøåôå <userinput>exit</userinput> ìüëéò
+ ç äéáäéêáóßá ïëïêëçñùèåß.</para>
<screen>&prompt.root; <userinput>script /var/tmp/mw.out</userinput>
-Script started, output file is /var/tmp/mw.out
+Script started, output file is /var/tmp/mw.out
&prompt.root; <userinput>make TARGET</userinput>
-<emphasis>… compile, compile, compile …</emphasis>
+<emphasis>… ìåôáãëþôôéóç, ìåôáãëþôôéóç, ìåôáãëþôôéóç …</emphasis>
&prompt.root; <userinput>exit</userinput>
Script done, …</screen>
- <para>If you do this, <emphasis>do not</emphasis> save the output
- in <filename>/tmp</filename>. This directory may be cleared
- next time you reboot. A better place to store it is in
- <filename>/var/tmp</filename> (as in the previous example) or
- in <username>root</username>'s home directory.</para>
+ <para>Áí áðïöáóßóåôå íá áðïèçêåýóåôå ôçí Ýîïäï,
+ <emphasis>ìç ÷ñçóéìïðïéÞóåôå</emphasis> ãéá áõôü ôï óêïðü ôïí
+ êáôÜëïãï <filename>/tmp</filename>. Ôá ðåñéå÷üìåíá áõôïý ôïõ
+ êáôáëüãïõ ðéèáíþò íá äéáãñáöïýí ôçí åðüìåíç öïñÜ ðïõ èá åêêéíÞóåôå.
+ ¸íáò êáëýôåñïò êáôÜëïãïò ãéá ôçí áðïèÞêåõóç ôïõ åßíáé ï
+ <filename>/var/tmp</filename> (üðùò óôï ðñïçãïýìåíï ðáñÜäåéãìá) Þ
+ ï ðñïóùðéêüò êáôÜëïãïò ôïõ <username>root</username>.</para>
</sect3>
<sect3 id="make-buildworld">
- <title>Compile the Base System</title>
+ <title>Ìåôáãëùôôßóôå ôï Âáóéêü Óýóôçìá</title>
- <para>You must be in the <filename>/usr/src</filename>
- directory:</para>
+ <para>Èá ðñÝðåé íá âñßóêåóôå óôïí êáôÜëïãï
+ <filename>/usr/src</filename>:</para>
<screen>&prompt.root; <userinput>cd /usr/src</userinput></screen>
- <para>(unless, of course, your source code is elsewhere, in which
- case change to that directory instead).</para>
+ <para>(åêôüò áí öõóéêÜ Ý÷åôå áðïèçêåýóåé ôïí ðçãáßï êþäéêá óå êÜðïéï
+ Üëëï êáôÜëïãï, ïðüôå áðëþò ìåôáêéíçèåßôå óå áõôüí).</para>
<indexterm><primary><command>make</command></primary></indexterm>
- <para>To rebuild the world you use the &man.make.1; command. This
- command reads instructions from the <filename>Makefile</filename>,
- which describes how the programs that comprise &os; should be
- rebuilt, the order in which they should be built, and so on.</para>
+ <para>Ãéá íá åðáíáìåôáãëùôôßóåôå ôï âáóéêü óýóôçìá, ÷ñçóéìïðïéÞóôå
+ ôçí åíôïëÞ &man.make.1;. Ç åíôïëÞ áõôÞ äéáâÜæåé ôéò ó÷åôéêÝò
+ ïäçãßåò áðü ôï áñ÷åßï <filename>Makefile</filename>, ôï ïðïßï
+ ðåñéãñÜöåé ìå ðïéï ôñüðï ðñÝðåé íá ìåôáãëùôôéóôïýí ôá ðñïãñÜììáôá
+ áðü ôá ïðïßá áðïôåëåßôáé ôï &os;, ôç óåéñÜ ìå ôçí ïðïßá ðñÝðåé íá
+ ãßíåé ç ìåôáãëþôôéóç. ê.ï.ê.</para>
- <para>The general format of the command line you will type is as
- follows:</para>
+ <para>Ç ãåíéêÞ ìïñöÞ ôçò åíôïëÞ ðïõ èá ðëçêôñïëïãÞóåôå åßíáé ç
+ ðáñáêÜôù:</para>
<screen>&prompt.root; <userinput>make -<replaceable>x</replaceable> -D<replaceable>VARIABLE</replaceable> <replaceable>target</replaceable></userinput></screen>
- <para>In this example, <option>-<replaceable>x</replaceable></option>
- is an option that you would pass to &man.make.1;. See the
- &man.make.1; manual page for an example of the options you can
- pass.</para>
+ <para>Óôï ðáñÜäåéãìá áõôü, ôï
+ <option>-<replaceable>x</replaceable></option> åßíáé ìéá åðéëïãÞ
+ ðïõ èÝëåôå íá äþóåôå óôçí &man.make.1;. Äåßôå ôçí óåëßäá manual ôïõ
+ &man.make.1; ãéá ðåñéóóüôåñá ðáñáäåßãìáôá äõíáôþí åðéëïãþí.</para>
- <para><option>-D<replaceable>VARIABLE</replaceable></option>
- passes a variable to the <filename>Makefile</filename>. The
- behavior of the <filename>Makefile</filename> is controlled by
- these variables. These are the same variables as are set in
- <filename>/etc/make.conf</filename>, and this provides another
- way of setting them.</para>
+ <para>Ç åðéëïãÞ <option>-D<replaceable>VARIABLE</replaceable></option>
+ ðåñíÜåé ìéá ìåôáâëçôÞ óôï <filename>Makefile</filename>.
+ Ç óõìðåñéöïñÜ ôïõ <filename>Makefile</filename> åëÝã÷åôáé áðü
+ ôÝôïéïõ åßäïõò ìåôáâëçôÝò. Ðñüêåéôáé ãéá ôéò ßäéåò ìåôáâëçôÝò ðïõ
+ êáèïñßæïíôáé êáé óôï <filename>/etc/make.conf</filename>, êáé áõôüò
+ åßíáé Ýíáò áêüìá ôñüðïò êáèïñéóìïý ôïõò.</para>
<screen>&prompt.root; <userinput>make -DNO_PROFILE <replaceable>target</replaceable></userinput></screen>
- <para>is another way of specifying that profiled libraries should
- not be built, and corresponds with the</para>
+ <para>Ôï ðáñáðÜíù äåß÷íåé Ýíá áêüìá ôñüðï íá êáèïñßóåôå üôé äåí èÝëåôå
+ íá ìåôáãëùôôéóôïýí ïé âéâëéïèÞêåò ìå ðëçñïöïñßåò profiling, êáé
+ áíôéóôïé÷åß ìå ôçí ðáñáêÜôù ãñáììÞ óôï
+ <filename>/etc/make.conf</filename>:</para>
<programlisting>NO_PROFILE= true # Avoid compiling profiled libraries</programlisting>
- <para>line in <filename>/etc/make.conf</filename>.</para>
+ <para>Ôï <replaceable>target</replaceable> äçëþíåé óôï &man.make.1;
+ ôé èÝëåôå íá êÜíåôå. Óå êÜèå <filename>Makefile</filename> ïñßæåôáé
+ Ýíáò áñéèìüò äéáöïñåôéêþí <quote>targets</quote>, êáé ç åðéëïãÞ ðïõ
+ èá êÜíåôå, êáèïñßæåé ôé áêñéâþò èá ãßíåé.</para>
- <para><replaceable>target</replaceable> tells &man.make.1; what
- you want to do. Each <filename>Makefile</filename> defines a
- number of different <quote>targets</quote>, and your choice of
- target determines what happens.</para>
+ <para>ÊÜðïéá áðü ôá targets ðïõ êáèïñßæïíôáé óôï
+ <filename>Makefile</filename>, äåí ðñïïñßæïíôáé ãéá Üìåóç åêôÝëåóç
+ áðü ôï ÷ñÞóôç. Áíôß ãéá áõôü, ÷ñçóéìïðïéïýíôáé áðü ôç äéáäéêáóßá
+ ìåôáãëþôôéóçò ãéá íá ìïéñáóôåß ï áñéèìüò ôùí âçìÜôùí ðïõ áðáéôïýíôáé
+ ãéá ôç ìåôáãëþôôéóç ôïõ óõóôÞìáôïò, óå Ýíá áñéèìü
+ õðü-âçìÜôùí.</para>
- <para>Some targets are listed in the
- <filename>Makefile</filename>, but are not meant for you to run.
- Instead, they are used by the build process to break out the
- steps necessary to rebuild the system into a number of
- sub-steps.</para>
-
- <para>Most of the time you will not need to pass any parameters to
- &man.make.1;, and so your command like will look like
- this:</para>
+ <para>Óôéò ðåñéóóüôåñåò ðåñéðôþóåéò äåí èá ÷ñåéáóôåß íá äþóåôå êáìßá
+ ðáñÜìåôñï óôï &man.make.1;, êáé Ýôóé ç åíôïëÞ óáò èá ìïéÜæåé ìå ôçí
+ ðáñáêÜôù:</para>
<screen>&prompt.root; <userinput>make <replaceable>target</replaceable></userinput></screen>
- <para>Where <replaceable>target</replaceable> will be one of
- many build options. The first target should always be
- <makevar>buildworld</makevar>.</para>
+ <para>¼ðïõ ôï <replaceable>target</replaceable> èá åßíáé ìéá áðü ôéò
+ ðïëëÝò åðéëïãÝò ìåôáãëþôôéóçò. Ôï ðñþôï target èá ðñÝðåé ðÜíôá íá
+ åßíáé ôï <makevar>buildworld</makevar>.</para>
- <para>As the names imply, <maketarget>buildworld</maketarget>
- builds a complete new tree under <filename>/usr/obj</filename>,
- and <maketarget>installworld</maketarget>, another target, installs this tree on
- the current machine.</para>
+ <para>¼ðùò åííïåßôáé êáé áðü ôï üíïìá, ôï
+ <maketarget>buildworld</maketarget> ìåôáãëùôôßæåé Ýíá ðëÞñåò äÝíôñï
+ ìÝóá óôïí êáôÜëïãï <filename>/usr/obj</filename>, åíþ ôï
+ <maketarget>installworld</maketarget>, åãêáèéóôÜ áõôü ôï äÝíôñï óôï
+ ôñÝ÷ïí ìç÷Üíçìá.</para>
- <para>Having separate options is very useful for two reasons. First, it allows you
- to do the build safe in the knowledge that no components of
- your running system will be affected. The build is
- <quote>self hosted</quote>. Because of this, you can safely
- run <maketarget>buildworld</maketarget> on a machine running
- in multi-user mode with no fear of ill-effects. It is still
- recommended that you run the
- <maketarget>installworld</maketarget> part in single user
- mode, though.</para>
+ <para>Ç ýðáñîç äéáöïñåôéêþí åðéëïãþí, åßíáé ÷ñÞóéìç ãéá äýï ëüãïõò.
+ Ðñþôá áðü üëá, óáò åðéôñÝðåé íá åêôåëÝóåôå ôç äéáäéêáóßá
+ ìåôáãëþôôéóçò ìå áóöÜëåéá, ãíùñßæïíôáò üôé äåí ðñüêåéôáé íá
+ åðçñåáóôåß êáíÝíá ôìÞìá ôïõ ôñÝ÷ïíôïò óõóôÞìáôïò óáò. Ç äéáäéêáóßá
+ ìåôáãëþôôéóçò åßíáé <quote>self hosted</quote>, áðïìïíùìÝíç áðü ôçí
+ õðüëïéðç ëåéôïõñãßá ôïõ ìç÷áíÞìáôïò. Ìðïñåßôå Ýôóé íá åêôåëÝóåôå
+ ôï <maketarget>buildworld</maketarget> óå Ýíá ìç÷Üíçìá ðïõ âñßóêåôáé
+ óå êáíïíéêÞ ëåéôïõñãßá (ðïëëáðëþí ÷ñçóôþí) ÷ùñßò íá õðÜñ÷åé öüâïò
+ ðáñåíåñãåéþí. Ùóôüóï, óõíßóôáôáé íá åêôåëÝóåôå ôï
+ <maketarget>installworld</maketarget> óå êáôÜóôáóç ëåéôïõñãßáò
+ åíüò ÷ñÞóôç.</para>
- <para>Secondly, it allows you to use NFS mounts to upgrade
- multiple machines on your network. If you have three machines,
- <hostid>A</hostid>, <hostid>B</hostid> and <hostid>C</hostid> that you want to upgrade, run <command>make
- buildworld</command> and <command>make installworld</command> on
- <hostid>A</hostid>. <hostid>B</hostid> and <hostid>C</hostid> should then NFS mount <filename>/usr/src</filename>
- and <filename>/usr/obj</filename> from <hostid>A</hostid>, and you can then run
- <command>make installworld</command> to install the results of
- the build on <hostid>B</hostid> and <hostid>C</hostid>.</para>
+ <para>Ï äåýôåñïò ëüãïò åßíáé üôé óáò åðéôñÝðåé íá ÷ñçóéìïðïéÞóåôå
+ ðñïóáñôÞóåéò NFS ãéá íá áíáâáèìßóåôå ðïëëÜ ìç÷áíÞìáôá ôïõ äéêôýïõ
+ óáò. Áí Ý÷åôå ôñßá ìç÷áíÞìáôá, ôá
+ <hostid>A</hostid>, <hostid>B</hostid> êáé <hostid>C</hostid>
+ ôá ïðïßá èÝëåôå íá áíáâáèìßóåôå, åêôåëÝóôå ôï
+ <command>make buildworld</command> êáé ôï
+ <command>make installworld</command> óôï ìç÷Üíçìá
+ <hostid>A</hostid>. Ôï <hostid>B</hostid> êáé ôï
+ <hostid>C</hostid> ìðïñïýí íá ðñïóáñôÞóïõí ôïí êáôÜëïãï
+ <filename>/usr/src</filename> êáé ôïí
+ <filename>/usr/obj</filename> áðü ôïí <hostid>A</hostid> ìÝóù NFS,
+ êáé Ýðåéôá ìðïñåßôå íá åêôåëÝóåôå ôï
+ <command>make installworld</command> ãéá íá åãêáôáóôÞóåôå ôï
+ Ýôïéìï ðëÝïí óýóôçìá óôïí <hostid>B</hostid> êáé
+ <hostid>C</hostid>.</para>
- <para>Although the <maketarget>world</maketarget> target still exists,
- you are strongly encouraged not to use it.</para>
+ <para>Áí êáé õðÜñ÷åé áêüìá ôï target <maketarget>world</maketarget>,
+ äåí óõíßóôáôáé ðëÝïí ç ÷ñÞóç ôïõ.</para>
- <para>Run</para>
+ <para>ÅêôåëÝóôå ôçí åíôïëÞ:</para>
<screen>&prompt.root; <userinput>make buildworld</userinput></screen>
- <para>It is possible to specify a <option>-j</option> option to
- <command>make</command> which will cause it to spawn several
- simultaneous processes. This is most useful on multi-CPU machines.
- However, since much of the compiling process is IO bound rather
- than CPU bound it is also useful on single CPU machines.</para>
+ <para>Ìðïñåßôå íá êáèïñßóåôå ôçí åðéëïãÞ <option>-j</option> óôçí
+ <command>make</command> þóôå íá åêôåëåóôåß óå ðïëëáðëÝò äéåñãáóßåò.
+ Áõôü åßíáé ðåñéóóüôåñï ÷ñÞóéìï óå ìç÷áíÞìáôá ìå ðïëëïýò
+ åðåîåñãáóôÝò, ùóôüóï êáèþò ôï ìåãáëýôåñï ìÝñïò ôçò äéáäéêáóßáò
+ ìåôáãëþôôéóçò êáèõóôåñåß åîáéôßáò ôïõ óêëçñïý äßóêïõ (IO bound)
+ êáé ü÷é ôçò CPU, ìðïñåß íá óáò öáíåß ÷ñÞóéìï áêüìá êáé óå ìç÷áíÞìáôá
+ ìå Ýíá åðåîåñãáóôÞ.</para>
- <para>On a typical single-CPU machine you would run:</para>
-
+ <para>Óå Ýíá ôõðéêü ìç÷Üíçìá ìå ìéá CPU, èá ìðïñïýóáôå íá
+ äþóåôå:</para>
+
<screen>&prompt.root; <userinput>make -j4 buildworld</userinput></screen>
- <para>&man.make.1; will then have up to 4 processes running at any one
- time. Empirical evidence posted to the mailing lists shows this
- generally gives the best performance benefit.</para>
+ <para>Ìå ôçí ðáñáðÜíù åíôïëÞ, ôï &man.make.1; èá ÷ñçóéìïðïéåß ìÝ÷ñé
+ 4 äéåñãáóßåò êÜèå ÷ñïíéêÞ óôéãìÞ. Áðü ôçí åìðåéñßá ðïõ Ý÷ïõìå
+ êáé ìÝóù äçìïóéåýóåùí óôéò ëßóôåò, öáßíåôáé üôé ãåíéêÜ áõôü äßíåé
+ ôçí êáëýôåñç áðüäïóç.</para>
- <para>If you have a multi-CPU machine and you are using an SMP
- configured kernel try values between 6 and 10 and see how they speed
- things up.</para>
+ <para>Áí Ý÷åôå ìç÷Üíçìá ìå ðïëëïýò åðåîåñãáóôÝò, êáé ÷ñçóéìïðïéåßôå
+ ðõñÞíá ìå äõíáôüôçôá SMP, äïêéìÜóôå ôéìÝò ìåôáîý ôïõ 6 êáé ôïõ 10
More information about the Freebsd-doc-el
mailing list