doc-el commit 929:36e6f49755c0 - Continuing translation of 'cutt...
freebsd-doc-el at lists.hellug.gr
freebsd-doc-el at lists.hellug.gr
Fri Oct 24 01:23:27 EEST 2008
changeset: 929:36e6f49755c0
user: Manolis Kiagias <sonicy at otenet.gr>
date: 2008-10-20 15:22 +0300
details: http://hg.hellug.gr/freebsd/doc-el/?cmd=changeset;node=36e6f49755c0
description:
Continuing translation of 'cutting-edge' chapter
diffs (206 lines):
diff -r 467d80a61bec -r 36e6f49755c0 el_GR.ISO8859-7/books/handbook/cutting-edge/chapter.sgml
--- a/el_GR.ISO8859-7/books/handbook/cutting-edge/chapter.sgml Mon Oct 20 15:22:22 2008 +0300
+++ b/el_GR.ISO8859-7/books/handbook/cutting-edge/chapter.sgml Mon Oct 20 15:22:58 2008 +0300
@@ -222,29 +222,33 @@
</indexterm>
<orderedlist>
<listitem>
- <para>Join the &a.current.name; and the &a.cvsall.name; lists. This is not
- just a good idea, it is <emphasis>essential</emphasis>. If
- you are not on the <emphasis>&a.current.name;</emphasis> list,
- you will not see the comments that people are
- making about the current state of the system and thus will
- probably end up stumbling over a lot of problems that others
- have already found and solved. Even more importantly, you
- will miss out on important bulletins which may be critical
- to your system's continued health.</para>
+ <para>Ãñáöôåßôå óôéò ëßóôåò &a.current.name; êáé &a.cvsall.name;.
+ Äåí åßíáé áðëþò êáëÞ éäåÜ, åßíáé <emphasis>âáóéêü</emphasis> íá
+ ôï êÜíåôå. Áí äåí åßóôå ãñáììÝíïò óôç ëßóôá
+ <emphasis>&a.current.name;</emphasis>, äåí èá âëÝðåôå ôá ó÷üëéá
+ ðïõ ãñÜöïõí üóïé ôï ÷ñçóéìïðïéïýí ó÷åôéêÜ ìå ôçí ôñÝ÷ïõóá
+ êáôÜóôáóç ôïõ óõóôÞìáôïò, êáé Ýôóé ðéèáíþò èá êáôáëÞîåôå íá
+ áíôéìåôùðßæåôå ðïëëÜ ðñïâëÞìáôá ðïõ Üëëïé Ý÷ïõí Þäç áíáêáëýøåé
+ êáé ëýóåé. Áêüìá ðéï óçìáíôéêü åßíáé üôé èá ÷Üíåôå óçìáíôéêÝò
+ áíáêïéíþóåéò ïé ïðïßåò ìðïñåß íá åßíáé êñßóéìåò ãéá ôçí
+ äéáôÞñçóç ôïõ óõóôÞìáôïò óáò óå õãéÞ êáôÜóôáóç.</para>
- <para>The &a.cvsall.name; list will allow you to see the
- commit log entry for each change as it is made along with
- any pertinent information on possible side-effects.</para>
+ <para>Ç ëßóôá &a.cvsall.name; èá óáò åðéôñÝðåé íá âëÝðåôå ôéò
+ êáôá÷ùñÞóåéò óôï commit log ãéá êÜèå áëëáãÞ ðïõ ãßíåôáé, êáèþò
+ êáé ðëçñïöïñßåò ãéá ðéèáíÝò ðáñåíÝñãåéò ðïõ ìðïñåß íá
+ Ý÷åé.</para>
- <para>To join these lists, or one of the others available
- go to &a.mailman.lists.link; and click on the list that
- you wish to subscribe to. Instructions on the rest of
- the procedure are available there.</para>
+ <para>Ãéá íá ãñáöôåßôå óå áõôÝò, Þ óå ïðïéåóäÞðïôå Üëëåò áðü ôéò
+ õðÜñ÷ïõóåò ëßóôåò, åðéóêåöèåßôå ôçí ôïðïèåóßá
+ &a.mailman.lists.link; êáé åðéëÝîôå ôç ëßóôá óôçí ïðïßá èÝëåôå
+ íá ãßíåôå óõíäñïìçôÞò. Ïäçãßåò ãéá ôçí õðüëïéðç äéáäéêáóßá
+ èá âñåßôå åðéôüðïõ.</para>
</listitem>
<listitem>
- <para>Grab the sources from a &os; <link linkend="mirrors">mirror
- site</link>. You can do this in one of two ways:</para>
+ <para>ÁíáêôÞóôå ôïí ðçãáßï êþäéêá áðü Ýíá
+ <link linkend="mirrors">mirror site</link> ôïõ &os;. Áõôü
+ ìðïñåß íá ãßíåé ìå äýï ôñüðïõò:</para>
<orderedlist>
<indexterm>
@@ -259,17 +263,22 @@
</indexterm>
<listitem>
- <para>Use the <link linkend="cvsup">cvsup</link> program
- with the <filename>supfile</filename> named <filename>standard-supfile</filename>
- available from <filename>/usr/share/examples/cvsup</filename>.
- This is the most recommended
- method, since it allows you to grab the entire
- collection once and then only what has changed from then
- on. Many people run <command>cvsup</command> from
- <command>cron</command> and keep their
- sources up-to-date automatically. You have to
- customize the sample <filename>supfile</filename> above, and configure
- <link linkend="cvsup">cvsup</link> for your environment.</para>
+ <para>×ñçóéìïðïéÞóôå ôï ðñüãñáììá <link
+ linkend="cvsup">cvsup</link> óå óõíäõáóìü ìå ôï
+ <filename>supfile</filename> ìå ôçí ïíïìáóßá
+ <filename>standard-supfile</filename> ôï ïðïßï èá âñåßôå
+ óôïí êáôÜëïãï
+ <filename>/usr/share/examples/cvsup</filename>.
+ ÁõôÞ åßíáé êáé ç ðëÝïí óõíéóôþìåíç ìÝèïäïò, êáèþò óáò
+ åðéôñÝðåé íá áíáêôÞóåôå üëç ôç óõëëïãÞ óå ìéá êßíçóç, êáé
+ óôéò åðüìåíåò áíáíåþóåéò èá ðáßñíåôå ìüíï ôéò áëëáãÝò.
+ Ðïëëïß ÷ñÞóôåò åêôåëïýí ôï <command>cvsup</command> ìÝóù
+ ôïõ <command>cron</command> þóôå íá êñáôÜíå ôïí ðçãáßï
+ êþäéêá ôïõ óõóôÞìáôïò ôïõò ðÜíôá áíáíåùìÝíï áõôüìáôá. Èá
+ ðñÝðåé íá ðñïóáñìüóåôå ôï õðüäåéãìá ôïõ
+ <filename>supfile</filename> ðïõ äßíïõìå ðáñáðÜíù, êáé íá
+ ñõèìßóåôå ôï <link linkend="cvsup">cvsup</link> ãéá ôï
+ ðåñéâÜëëïí óáò.</para>
</listitem>
<indexterm>
@@ -277,69 +286,75 @@
<secondary>Syncing with CTM</secondary>
</indexterm>
<listitem>
- <para>Use the <application><link
- linkend="ctm">CTM</link></application> facility. If you
- have very bad connectivity (high price connections or
- only email access) <application>CTM</application> is an option.
- However, it is a lot of hassle and can give you broken files.
- This leads to it being rarely used, which again increases
- the chance of it not working for fairly long periods of
- time. We recommend using
+ <para>×ñçóéìïðïéÞóôå ôçí õðçñåóßá <application><link
+ linkend="ctm">CTM</link></application>. Áí Ý÷åôå ðïëý êáêÞ
+ óõíäåóéìüôçôá (õøçëü êüóôïò óýíäåóçò Þ ðñüóâáóç ìüíï ìÝóù
+ email) ôï <application>CTM</application> áðïôåëåß ãéá óáò
+ ìéá åíáëëáêôéêÞ ëýóç. Ìðïñåß ùóôüóï íá óáò äçìéïõñãÞóåé
+ äéÜöïñïõò ìðåëÜäáò êáé íá êáôáëÞîåôå ìå ÷áëáóìÝíá áñ÷åßá.
+ Ãéá ôï ëüãï áõôü, ôï <application>CTM</application>
+ ÷ñçóéìïðïéåßôáé óðÜíéá, êÜôé ôï ïðïßï áõîÜíåé áêüìá
+ ðåñéóóüôåñï ôçí ðéèáíüôçôá íá ìç äïõëåýåé óùóôÜ ãéá ìåãÜëá
+ ÷ñïíéêÜ äéáóôÞìáôá. Óáò óõíéóôïýìå íá ÷ñçóéìïðïéÞóåôå ôï
<application><link linkend="cvsup">CVSup</link></application>
- for anybody with a 9600 bps modem or faster connection.
- </para>
+ áí ôï modem óáò åßíáé ôá÷ýôçôáò 9600 bps Þ
+ ôá÷ýôåñï.</para>
</listitem>
</orderedlist>
</listitem>
<listitem>
- <para>If you are grabbing the sources to run, and not just
- look at, then grab <emphasis>all</emphasis> of &os.current;, not
- just selected portions. The reason for this is that various
- parts of the source depend on updates elsewhere, and trying
- to compile just a subset is almost guaranteed to get you
- into trouble.</para>
+ <para>Áí óêïðåýåôå íá áíáêôÞóåôå ôïí ðçãáßï êþäéêá ãéá êáíïíéêÞ
+ ÷ñÞóç (åêôÝëåóç) êáé ü÷é áðëþò ãéá íá ôïí äåßôå, ôüôå
+ áíáêôÞóôå <emphasis>ïëüêëçñï</emphasis> ôï &os.current; êáé ü÷é
+ êÜðïéá åðéëåãìÝíá ôìÞìáôá. Ï ëüãïò ãéá ôï ðáñáðÜíù åßíáé üôé
+ äéÜöïñá êïììÜôéá ôïõ êþäéêá åîáñôþíôáé áðü áíáíåþóåéò óå Üëëá,
+ êáé áí ðñïóðáèÞóåôå íá ìåôáãëùôôßóåôå áðëþò Ýíá õðïóýíïëï ôïõ,
+ ôï ðéï ðéèáíü åßíáé íá óõíáíôÞóåôå ðñüâëçìá.</para>
<indexterm>
<primary>-CURRENT</primary>
<secondary>compiling</secondary>
</indexterm>
- <para>Before compiling &os.current;, read the
- <filename>Makefile</filename> in <filename>/usr/src</filename>
- carefully. You should at least <link
- linkend="makeworld">install a new kernel and rebuild the world</link> the first time through
- as part of the upgrading process. Reading the &a.current;
- and <filename>/usr/src/UPDATING</filename> will keep you up-to-date on other bootstrapping procedures
- that sometimes become necessary as we move toward the next
- release.</para>
+ <para>Ðñéí ìåôáãëùôôßóåôå ôï &os.current;, äéáâÜóôå ðñïóåêôéêÜ ôï
+ <filename>Makefile</filename> óôïí êáôÜëïãï
+ <filename>/usr/src</filename>. Èá ðñÝðåé íá <link
+ linkend="makeworld">ìåôáãëùôôßóåôå ôïí ðõñÞíá êáé üëï ôï âáóéêü óýóôçìá (world)</link> ôçí ðñþôç öïñÜ, ùò ìÝñïò ôçò äéáäéêáóßáò áíáâÜèìéóçò.
+ ÄéáâÜæïíôáò ôç ëßóôá &a.current;
+ êáé ôï <filename>/usr/src/UPDATING</filename> èá åßóôå
+ åíçìåñùìÝíïé ãéá íÝåò äéáäéêáóßåò üóï áöïñÜ ôçí åêêßíçóç óôï íÝï
+ óáò óýóôçìá, ðïõ ïñéóìÝíåò öïñÝò åßíáé áðáñáßôçôåò üóï åñ÷üìáóôå
+ ðéï êïíôÜ óå ìéá íÝá åðßóçìç Ýêäïóç.</para>
</listitem>
-
+
<listitem>
- <para>Be active! If you are running &os.current;, we want
- to know what you have to say about it, especially if you
- have suggestions for enhancements or bug fixes. Suggestions
- with accompanying code are received most
- enthusiastically!</para>
+ <para>Ãßíåôå åíåñãü ìÝëïò! Áí ÷ñçóéìïðïéåßôå ôï &os.current;,
+ èÝëïõìå íá îÝñïõìå ôç ãíþìç óáò ãéá áõôü, åéäéêÜ áí Ý÷åôå
+ ðñïôÜóåéò ãéá âåëôéþóåéò Þ äéïñèþóåéò ëáèþí. ÐñïôÜóåéò ðïõ
+ óõíïäåýïíôáé êáé áðü êþäéêá ãßíïíôáé äåêôÝò ìå
+ åíèïõóéáóìü!</para>
</listitem>
</orderedlist>
</sect3>
</sect2>
-
+
<sect2 id="stable">
- <title>Staying Stable with &os;</title>
+ <title>×ñçóéìïðïéþíôáò ôï &os;-STABLE</title>
<sect3>
- <title>What Is &os.stable;?</title>
+ <title>Ôé Åßíáé ôï &os.stable;;</title>
<indexterm><primary>-STABLE</primary></indexterm>
- <para>&os.stable; is our development branch from which major releases
- are made. Changes go into this branch at a different pace, and
- with the general assumption that they have first gone into
- &os.current; for testing. This is <emphasis>still</emphasis>
- a development branch, however, and this means that at any given time,
- the sources for &os.stable; may or may not be suitable for any
- particular purpose. It is simply another engineering development
- track, not a resource for end-users.</para>
+ <para>Ôï &os.stable; åßíáé Ýíáò êëÜäïò áíÜðôõîçò áðü ôïí ïðïßï
+ ðñïêýðôïõí ïé <quote>ìåãÜëåò</quote> (major) åêäüóåéò. Ïé áëëáãÝò
+ åéóÜãïíôáé óå áõôü ôïí êëÜäï ìå äéáöïñåôéêü ñõèìü, êáé ìå ôç ãåíéêÞ
+ ðáñáäï÷Þ üôé Ý÷ïõí ðñþôá ðåñÜóåé áðü ôï &os.current; ãéá äïêéìÞ.
+ Ùóôüóï, <emphasis>äåí ðáýåé</emphasis> íá åßíáé Ýíáò êëÜäïò
+ áíÜðôõîçò, êáé áõôü óçìáßíåé üôé ï êþäéêá ôïõ &os.stable; ìðïñåß
+ ìéá äåäïìÝíç ÷ñïíéêÞ óôéãìÞ íá åßíáé áêáôÜëëçëïò ãéá óõãêåêñéìÝíåò
+ åöáñìïãÝò. Ðñüêåéôáé ãéá ìéá áêüìá ãñáììÞ áíÜðôõîçò ãéá ôïõò
+ ðñïãñáììáôéóôÝò, ü÷é áðáñáßôçôá êáôÜëëçëç ãéá ôïõò ôåëéêïýò
+ ÷ñÞóôåò.</para>
</sect3>
<sect3>
More information about the Freebsd-doc-el
mailing list