doc-el commit 955:df88787d57fb - Translated q1-q3 from section 2...
freebsd-doc-el at lists.hellug.gr
freebsd-doc-el at lists.hellug.gr
Mon Oct 27 18:39:59 EET 2008
changeset: 955:df88787d57fb
user: Manolis Kiagias <sonicy at otenet.gr>
date: 2008-10-25 15:27 +0300
details: http://hg.hellug.gr/freebsd/doc-el/?cmd=changeset;node=df88787d57fb
description:
Translated q1-q3 from section 24.4.14 (cutting-edge)
diffs (174 lines):
diff -r 87a0163c2a9a -r df88787d57fb el_GR.ISO8859-7/books/handbook/cutting-edge/chapter.sgml
--- a/el_GR.ISO8859-7/books/handbook/cutting-edge/chapter.sgml Sat Oct 25 00:06:37 2008 +0300
+++ b/el_GR.ISO8859-7/books/handbook/cutting-edge/chapter.sgml Sat Oct 25 15:27:25 2008 +0300
@@ -1499,96 +1499,109 @@
</sect2>
<sect2>
- <title>Questions</title>
+ <title>ÅñùôÞóåéò</title>
<qandaset>
<qandaentry>
<question>
- <para>Do I need to re-make the world for every change?</para>
+ <para>ÐñÝðåé íá ìåôáãëùôôßóù îáíÜ ôï âáóéêü óýóôçìá óå êÜèå
+ áëëáãÞ;</para>
</question>
<answer>
- <para>There is no easy answer to this one, as it depends on the
- nature of the change. For example, if you just ran <application>CVSup</application>, and
- it has shown the following files as being updated:</para>
-
+ <para>Äåí õðÜñ÷åé åýêïëç áðÜíôçóç óå áõôü ôï åñþôçìá, êáèþò
+ åîáñôÜôáé áðü ôç öýóç ôçò áëëáãÞò. Ãéá ðáñÜäåéãìá, áí
+ åêôåëÝóåôå ôï <application>CVSup</application>, êáé äåßôå üôé
+ åíçìåñþèçêáí ôá ðáñáêÜôù áñ÷åßá:</para>
+
<screen><filename>src/games/cribbage/instr.c</filename>
<filename>src/games/sail/pl_main.c</filename>
<filename>src/release/sysinstall/config.c</filename>
<filename>src/release/sysinstall/media.c</filename>
<filename>src/share/mk/bsd.port.mk</filename></screen>
- <para>it probably is not worth rebuilding the entire world.
- You could just go to the appropriate sub-directories and
- <command>make all install</command>, and that's about it. But
- if something major changed, for example
- <filename>src/lib/libc/stdlib</filename> then you should either
- re-make the world, or at least those parts of it that are
- statically linked (as well as anything else you might have added
- that is statically linked).</para>
-
- <para>At the end of the day, it is your call. You might be happy
- re-making the world every fortnight say, and let changes
- accumulate over that fortnight. Or you might want to re-make
- just those things that have changed, and be confident you can
- spot all the dependencies.</para>
-
- <para>And, of course, this all depends on how often you want to
- upgrade, and whether you are tracking &os.stable; or
- &os.current;.</para>
+ <para>Ôï ðéèáíüôåñï åßíáé üôé äåí ÷ñåéÜæåôáé íá ìåôáãëùôôßóåôå
+ îáíÜ üëï ôï âáóéêü óýóôçìá. Ìðïñåßôå áðëþò íá ìåôáâåßôå óôïõò
+ ó÷åôéêïýò õðïêáôáëüãïõò êáé íá åêôåëÝóåôå ôï
+ <command>make all install</command>, êáé èá Ý÷åôå ôåëåéþóåé.
+ Áí üìùò õðÜñ÷åé êÜðïéá óçìáíôéêÞ áëëáãÞ, ãéá ðáñÜäåéãìá ôï
+ <filename>src/lib/libc/stdlib</filename>, èá ðñÝðåé åßôå íá
+ åðáíáìåôáãëùôôßóåôå ôï âáóéêü óýóôçìá, Þ ôïõëÜ÷éóôïí áõôÜ ôá
+ êïììÜôéá ôá ïðïßá åßíáé óôáôéêÜ óõíäåäåìÝíá (üðùò êáé ïôéäÞðïôå
+ Üëëï Ý÷åôå ðñïóèÝóåé åóåßò êáé ôï ïðïßï åßíáé óôáôéêÜ
+ óõíäåäåìÝíï.</para>
+
+ <para>ÔåëéêÜ, ç áðüöáóç åßíáé äéêÞ óáò. Ìðïñåß íá åßóôå
+ éêáíïðïéçìÝíïò áí ìåôáãëùôôßæåôå ôï âáóéêü óýóôçìá êÜèå äýï
+ âäïìÜäåò, áöÞíïíôáò ôéò áëëáãÝò íá óõãêåíôñùèïýí óôç äéÜñêåéá
+ áõôïý ôïõ äéáóôÞìáôïò. ¹ ìðïñåß íá èÝëåôå íá ìåôáãëùôôßóåôå
+ ìüíï ôéò áëëáãÝò, áí Ý÷åôå ôçí ðåðïßèçóç üôé ìðïñåßôå íá
+ åíôïðßóåôå üëåò ôéò åîáñôÞóåéò ôïõò.</para>
+
+ <para>Êáé öõóéêÜ, üëá áõôÜ åîáñôþíôáé áðü ôï ðüóï óõ÷íÜ èÝëåôå íá
+ åíçìåñþíåôå ôï óýóôçìá óáò, êáé áðü ôï áí áêïëïõèåßôå ôï
+ &os.stable; Þ ôï &os.current;.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
- <para>My compile failed with lots of signal 11 (or other signal
- number) errors. What has happened?</para>
+ <para>Ç ìåôáãëþôôéóç ìïõ áðÝôõ÷å ìå ðëÞèïò ìçíõìÜôùí signal 11
+ (Þ ëÜèç ìå Üëëá óÞìáôá). Ôé Ý÷åé óõìâåß;</para>
</question>
- <indexterm><primary>signal 11</primary></indexterm>
+ <indexterm><primary>signal 11</primary></indexterm>
<answer>
+ <para>Áõôü óõíÞèùò äåß÷íåé ðñïâëÞìáôá õëéêïý. Ç äéáäéêáóßá
+ ìåôáãëþôôéóçò ôïõ âáóéêïý óõóôÞìáôïò åßíáé Ýíáò áðïôåëåóìáôéêüò
+ ôñüðïò íá äïêéìÜóåôå ôï õëéêü óáò óôá üñéá ôïõ, êáé óõ÷íÜ èá
+ äåßîåé ðñïâëÞìáôá ðïõ ó÷åôßæïíôáé ìå ôç ìíÞìç. Ôï ðéï óýíçèåò
+ óýìðôùìá, åßíáé ç áðüôïìç äéáêïðÞ ôçò ìåôáãëþôôéóçò, ìå ôïí
+ ìåôáãëùôôéóôÞ íá öáßíåôáé üôé Ý÷åé ëÜâåé êÜðïéï ìõóôçñéþäåò
+ óÞìá.</para>
- <para>This is normally indicative of hardware problems.
- (Re)making the world is an effective way to stress test your
- hardware, and will frequently throw up memory problems. These
- normally manifest themselves as the compiler mysteriously dying
- on receipt of strange signals.</para>
-
- <para>A sure indicator of this is if you can restart the make and
- it dies at a different point in the process.</para>
-
- <para>In this instance there is little you can do except start
- swapping around the components in your machine to determine
- which one is failing.</para>
+ <para>¸íá óßãïõñï óçìÜäé ãéá ôï ðáñáðÜíù, åßíáé íá åðáíåêêéíÞóåôå
+ ôç äéáäéêáóßá, êáé áõôÞ íá óôáìáôÞóåé óå äéáöïñåôéêü
+ óçìåßï.</para>
+
+ <para>Óôçí ðåñßðôùóç áõôÞ, äåí õðÜñ÷ïõí êáé ðïëëÜ ðïõ ìðïñåßôå íá
+ êÜíåôå, åêôüò áðü ôï íá áñ÷ßóåôå íá áëëÜæåôå åîáñôÞìáôá óôï
+ ìç÷Üíçìá óáò ìÝ÷ñé íá âñåßôå áõôü ðïõ åßíáé õðáßôéï.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
- <para>Can I remove <filename>/usr/obj</filename> when I have
- finished?</para>
+ <para>Ìðïñþ íá äéáãñÜøù ôï <filename>/usr/obj</filename> üôáí
+ ôåëåéþóù;</para>
</question>
-
+
<answer>
- <para>The short answer is yes.</para>
-
- <para><filename>/usr/obj</filename> contains all the object files
- that were produced during the compilation phase. Normally, one
- of the first steps in the <command>make buildworld</command> process is to
- remove this directory and start afresh. In this case, keeping
- <filename>/usr/obj</filename> around after you have finished
- makes little sense, and will free up a large chunk of disk space
- (currently about 340 MB).</para>
-
- <para>However, if you know what you are doing you can have
- <command>make buildworld</command> skip this step. This will make subsequent
- builds run much faster, since most of sources will not need to
- be recompiled. The flip side of this is that subtle dependency
- problems can creep in, causing your build to fail in odd ways.
- This frequently generates noise on the &os; mailing lists,
- when one person complains that their build has failed, not
- realizing that it is because they have tried to cut
- corners.</para>
+ <para>Ç óýíôïìç áðÜíôçóç åßíáé íáé.</para>
+
+ <para>Ôï <filename>/usr/obj</filename> ðåñéÝ÷åé üëá ôá
+ áíôéêåéìåíéêÜ áñ÷åßá ðïõ ðáñÜãïíôáé êáôÜ ôç äéÜñêåéá ôçò
+ ìåôáãëþôôéóçò. ÓõíÞèùò, Ýíá áðü ôá ðñþôá âÞìáôá óôçí
+ äéáäéêáóßá <command>make buildworld</command> åßíáé ç äéáãñáöÞ
+ áõôïý ôïõ êáôáëüãïõ êáé ç áíáäçìéïõñãßá ôïõ. Óôçí ðåñßðôùóç
+ áõôÞ, ôï íá êñáôÞóåôå ôïí êáôÜëïãï
+ <filename>/usr/obj</filename> áöïý Ý÷åôå ôåëåéþóåé, äåí Ý÷åé
+ êáé ðïëý íüçìá, åíþ áí ôïí óâÞóåôå èá êåñäßóåôå Ýíá ìåãÜëï
+ êïììÜôé åëåýèåñïõ ÷þñïõ (ôçí ðáñïýóá óôéãìÞ ðåñßðïõ
+ 340 MB).</para>
+
+ <para>¼ìùò, áí îÝñåôå ôé êÜíåôå, ìðïñåßôå íá ïäçãÞóåôå ôï
+ <command>make buildworld</command> íá ðáñáëåßøåé áõôü ôï âÞìá.
+ Áõôü èá åðéôá÷ýíåé éäéáßôåñá ôéò íÝåò ìåôáãëùôôßóåéò, êáèþò
+ ôá ðåñéóóüôåñá ôìÞìáôá ôïõ ðçãáßïõ êþäéêá äåí èá ÷ñåéÜæïíôáé
+ îáíÜ ìåôáãëþôôéóç. Ôï ìåéïíÝêôçìá åßíáé üôé ïñéóìÝíåò öïñÝò
+ åìöáíßæïíôáé ðñïâëÞìáôá ðïõ Ý÷ïõí ó÷Ýóç ìå ü÷é êáé ôüóï
+ åìöáíåßò åîáñôÞóåéò, êáé ìðïñåß íá ïäçãÞóïõí óå ìõóôçñéþäç
+ áðïôõ÷ßá ôçò ìåôáãëþôôéóçò. ÔÝôïéá ðñïâëÞìáôá óõ÷íÜ äçìéïõñãïýí
+ <quote>èüñõâï</quote> óôéò ëßóôåò ôïõ &os;, üôáí êÜðïéïò ÷ñÞóôçò
+ ðáñáðïíéÝôáé üôé ç ìåôáãëþôôéóç ôïõ áðïôõã÷Üíåé, ÷ùñßò íá
+ áíôéëáìâÜíåôáé üôé áõôü ïöåßëåôáé óôçí ðñïóðÜèåéá ôïõ íá
+ óõíôïìåýóåé ôçí äéáäéêáóßá.</para>
</answer>
</qandaentry>
More information about the Freebsd-doc-el
mailing list