doc-el commit 935:99d545b47038 - Completed initial translation o...
freebsd-doc-el at lists.hellug.gr
freebsd-doc-el at lists.hellug.gr
Fri Oct 24 01:23:34 EEST 2008
changeset: 935:99d545b47038
user: Manolis Kiagias <sonicy at otenet.gr>
date: 2008-10-20 20:06 +0300
details: http://hg.hellug.gr/freebsd/doc-el/?cmd=changeset;node=99d545b47038
description:
Completed initial translation of section 24.2 (cutting-edge)
diffs (256 lines):
diff -r 473f5f73faf0 -r 99d545b47038 el_GR.ISO8859-7/books/handbook/cutting-edge/chapter.sgml
--- a/el_GR.ISO8859-7/books/handbook/cutting-edge/chapter.sgml Mon Oct 20 16:24:17 2008 +0300
+++ b/el_GR.ISO8859-7/books/handbook/cutting-edge/chapter.sgml Mon Oct 20 20:06:34 2008 +0300
@@ -358,90 +358,96 @@
</sect3>
<sect3>
- <title>Who Needs &os.stable;?</title>
+ <title>Ðïéïò ×ñåéÜæåôáé ôï &os.stable;;</title>
- <para>If you are interested in tracking or contributing to the
- FreeBSD development process, especially as it relates to the
- next <quote>point</quote> release of FreeBSD, then you should
- consider following &os.stable;.</para>
+ <para>Áí óáò åíäéáöÝñåé íá ðáñáêïëïõèåßôå Þ íá óõìâÜëëåôå óôçí
+ áíÜðôõîç ôïõ &os;, êáé åéäéêÜ üóï áöïñÜ ôçí åðüìåíç åðßóçìç
+ Ýêäïóç ôïõ áðü ôïí ßäéï êëÜäï (point release), åßíáé êáëÞ éäÝá íá
+ ðáñáêïëïõèåßôå ôï &os.stable;.</para>
- <para>While it is true that security fixes also go into the
- &os.stable; branch, you do not <emphasis>need</emphasis> to
- track &os.stable; to do this. Every security advisory for
- FreeBSD explains how to fix the problem for the releases it
- affects
- <footnote><para>That is not quite true. We can not continue to
- support old releases of FreeBSD forever, although we do
- support them for many years. For a complete description
- of the current security policy for old releases of
- FreeBSD, please see <ulink
- url="&url.base;/security/">http://www.FreeBSD.org/security/</ulink>.</para>
+ <para>Áí êáé åßíáé áëÞèåéá üôé ïé äéïñèþóåéò áóöÜëåéáò ãßíïíôáé êáé
+ óôïí êëÜäï &os.stable;, ùóôüóï äåí <emphasis>÷ñåéÜæåôáé</emphasis>
+ íá ðáñêïëïõèåßôå ôï &os.stable; ãéá áõôü ôï ëüãï. ÊÜèå áíáöïñÜ
+ ðñïâëÞìáôïò áóöÜëåéáò ôïõ &os; åîçãåß ðùò íá äéïñèþóåôå ôï ðñüâëçìá
+ ãéá êÜèå åðßóçìç Ýêäïóç ç ïðïßá åðçñåÜæåôáé áðü áõôü
+ <footnote><para>Áõôü âÝâáéá äåí åßíáé áðüëõôá áëçèéíü. Äåí ìðïñïýìå
+ íá óõíå÷ßóïõìå íá õðïóôçñßæïõìå ôéò ðáëéÝò åêäüóåéò ôïõ &os; ãéá
+ ðÜíôá, áí êáé ôéò õðïóôçñßæïõìå ãéá ðïëëÜ ÷ñüíéá. Ãéá ðëÞñç
+ ðåñéãñáöÞ ôçò ôñÝ÷ïõóáò ðïëéôéêÞò üóï áöïñÜ ôçí áóöÜëåéá ôùí
+ ðáëéþí åêäüóåùí ôïõ &os;, äåßôå <ulink
+ url="&url.base;/security/">http://www.FreeBSD.org/security/</ulink>.</para>
</footnote>
- , and tracking an entire development branch just
- for security reasons is likely to bring in a lot of unwanted
- changes as well.</para>
+ , êáé ç ðáñáêïëïýèçóç åíüò êëÜäïõ áíÜðôõîçò ìüíï ãéá ëüãïõò
+ áóöÜëåéáò, ðéèáíüí íá öÝñåé åðßóçò êáé Üëëåò áíåðéèýìçôåò áëëáãÝò
+ ìáæß ôçò.</para>
- <para>Although we endeavor to ensure that the &os.stable; branch
- compiles and runs at all times, this cannot be guaranteed. In
- addition, while code is developed in &os.current; before including
- it in &os.stable;, more people run &os.stable; than &os.current;, so
- it is inevitable that bugs and corner cases will sometimes be found
- in &os.stable; that were not apparent in &os.current;.</para>
+ <para>Áí êáé êáôáâÜëëïõìå êÜèå äõíáôÞ ðñïóðÜèåéá þóôå íá åîáóöáëßóïõìå
+ üôé ï êëÜäïò &os.stable; ìðïñåß íá ìåôáãëùôôéóôåß êáé íá åêôåëåóôåß
+ óå êÜèå äåäïìÝíç ÷ñïíéêÞ óôéãìÞ, äåí ìðïñïýìå ùóôüóï íá ôï
+ åããõçèïýìå. Åðéðñüóèåôá, áí êáé ï êþäéêá áíáðôýóóåôáé óôï
+ &os.current; ðñéí ðåñÜóåé óôï &os.stable;, ï êüóìïò ðïõ åêôåëåß ôï
+ &os.stable; åßíáé ðåñéóóüôåñïò, êáé Ýôóé åßíáé áíáðüöåõêôï íá
+ áíáêáëýðôïíôáé ðéï ðïëëÜ óöÜëìáôá êáé áêñáßåò ðåñéðôþóåéò óôï
+ &os.stable; ôá ïðïßá äåí Ý÷ïõí ãßíåé åìöáíÞ óôï &os.current;.</para>
- <para>For these reasons, we do <emphasis>not</emphasis> recommend that
- you blindly track &os.stable;, and it is particularly important that
- you do not update any production servers to &os.stable; without
- first thoroughly testing the code in your development
- environment.</para>
+ <para>Ãéá ôïõò ëüãïõò áõôïýò, <emphasis>äåí</emphasis> óõíéóôïýìå íá
+ ðáñáêïëïõèåßôå ôõöëÜ ôï &os.stable;, êáé åéäéêüôåñá åßíáé óçìáíôéêü
+ íá ìçí áíáâáèìßæåôå óå áõôü åîõðçñåôçôÝò óå ðáñáãùãÞ, ÷ùñßò íá
+ Ý÷åôå ðñþôá åëÝãîåé áíáëõôéêÜ ôïí êþäéêá óôï äéêü óáò ðåñéâÜëëïí
+ áíÜðôõîçò.</para>
- <para>If you do not have the resources to do this then we recommend
- that you run the most recent release of FreeBSD, and use the binary
- update mechanism to move from release to release.</para>
+ <para>Áí äåí äéáèÝôåôå ôïõò ðüñïõò ãéá íá ôï êÜíåôå áõôü, óáò
+ óõíéóôïýìå íá ÷ñçóéìïðïéåßôå ôçí ôåëåõôáßá åðßóçìç Ýêäïóç ôïõ &os;,
+ êáé íá ðçãáßíåôå áðü ôç ìéá Ýêäïóç óôçí Üëëç ìÝóù ôïõ ìç÷áíéóìïý
+ äõáäéêþí åíçìåñþóåùí.</para>
</sect3>
<sect3>
- <title>Using &os.stable;</title>
-
+ <title>×ñçóéìïðïéþíôáò ôï &os.stable;</title>
+
<indexterm>
<primary>-STABLE</primary>
<secondary>using</secondary>
</indexterm>
<orderedlist>
<listitem>
- <para>Join the &a.stable.name; list. This will keep you informed of
- build-dependencies that may appear in &os.stable;
- or any other issues requiring
- special attention. Developers will also make announcements
- in this mailing list when they are contemplating some
- controversial fix or update, giving the users a chance to
- respond if they have any issues to raise concerning the
- proposed change.</para>
+ <para>Ãñáöôåßôå óõíäñïìçôÞò óôç ëßóôá &a.stable.name;. Èá åßóôå
+ Ýôóé åíçìåñùìÝíïé ãéá åîáñôÞóåéò ìåôáãëþôôéóçò ðïõ ßóùò
+ åìöáíéóôïýí óôï &os.stable;, Þ ãéá Üëëá ðñïâëÞìáôá ðïõ ÷ñÞæïõí
+ åéäéêÞò ðñïóï÷Þò. Óôç ëßóôá áõôÞ èá âñßóêåôå åðßóçò
+ áíáêïéíþóåéò áðü ìÝëç ôçò ïìÜäáò áíÜðôõîçò üôáí óêÝöôïíôáé íá
+ óõìðåñéëÜâïõí êÜðïéá áìöéëåãüìåíç áíáíÝùóç Þ äéüñèùóç, äßíïíôáò
+ Ýôóé óôïõò ÷ñÞóôåò ôçí åõêáéñßá íá áðáíôÞóïõí ó÷åôéêÜ ìå
+ ðñïâëÞìáôá ðïõ èá ðñïêáëÝóåé ç ðñïôåéíüìåíç áëëáãÞ.</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>If you are going to install a new system and want it
- to run monthly snapshot built from &os.stable;, please
- check the <ulink url="&url.base;/snapshots/">
- Snapshots</ulink> web page for more information.
- Alternatively, it is possible to
- install the most recent &os.stable; release from the
- <link linkend="mirrors">mirror sites</link> and follow
- the instructions below to upgrade your system to the
- most up to date &os.stable; source code.</para>
+ <para>Áí ðñüêåéôáé íá åãêáôáóôÞóåôå Ýíá íÝï óýóôçìá ìå óêïðü íá
+ åêôåëåßôå ôá ìçíéáßá snapshot ôïõ &os.stable;, ðáñáêáëïýìå íá
+ åëÝãîåôå ôçí ôïðïèåóßá <ulink
+ url="&url.base;/snapshots/">Snapshots</ulink> ãéá
+ ðåñéóóüôåñåò ðëçñïöïñßåò. ÅíáëëáêôéêÜ, åßíáé äõíáôüí íá
+ åãêáôáóôÞóåôå ôï ðéï ðñüóöáôï &os.stable; áðü êÜðïéï
+ <link linkend="mirrors">mirror site</link> áêïëïõèþíôáò ôéò
+ ðáñáêÜôù ïäçãßåò þóôå íá áíáâáèìßóåôå ôï óýóôçìá óáò óôçí ðëÝïí
+ ðñüóöáôç Ýêäïóç ðçãáßïõ êþäéêá ôïõ &os.stable;.</para>
- <para>If you are already running a previous release of &os;
- and wish to upgrade via sources then you can easily do so
- from &os; <link linkend="mirrors">mirror site</link>. This can
- be done in one of two ways:</para>
+ <para>Áí äéáèÝôåôå Þäç êÜðïéá ðñïçãïýìåíç Ýêäïóç ôïõ &os; êáé
+ åðéèõìåßôå íá áíáâáèìéóôåßôå ìÝóù ôïõ ðçãáßïõ êþäéêá, ìðïñåßôå
+ åýêïëá íá ÷ñçóéìïðïéÞóåôå êÜðïéï <link
+ linkend="mirrors">mirror site</link> ôïõ &os;. ÕðÜñ÷ïõí äýï
+ ôñüðïé ãéá íá ãßíåé áõôü:</para>
<orderedlist>
<indexterm>
@@ -455,19 +461,23 @@
<secondary>syncing with <application>CVSup</application></secondary>
</indexterm>
<listitem>
- <para>Use the <link linkend="cvsup">cvsup</link> program
- with the <filename>supfile</filename> named <filename>stable-supfile</filename>
- from the directory
- <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> to 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>stable-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>
@@ -475,21 +485,21 @@
<secondary>syncing with CTM</secondary>
</indexterm>
<listitem>
- <para>Use the <application><link
- linkend="ctm">CTM</link></application> facility. If
- you do not have a fast and inexpensive connection to
- the Internet, this is the method you should consider
- using.
- </para>
+ <para>×ñçóéìïðïéÞóôå ôçí õðçñåóßá <application><link
+ linkend="ctm">CTM</link></application>. Áí äåí Ý÷åôå
+ ãñÞãïñç êáé öôçíÞ óýíäåóç ìå ôï Internet, áõôÞ åßíáé ç
+ óõíéóôþìåíç ìÝèïäïò.</para>
</listitem>
</orderedlist>
</listitem>
<listitem>
- <para>Essentially, if you need rapid on-demand access to the
- source and communications bandwidth is not a consideration,
- use <command>cvsup</command> or <command>ftp</command>.
- Otherwise, use <application>CTM</application>.</para>
+ <para>ÏõóéáóôéêÜ, áí ÷ñåéÜæåóôå ãñÞãïñç êáé êáôÜ áðáßôçóç
+ ðñüóâáóç óôïí ðçãáßï êþäéêá, êáé ôï åýñïò æþíçò ôçò óýíäåóçò
+ äåí áðïôåëåß ðñüâëçìá, ÷ñçóéìïðïéÞóôå ôï
+ <command>cvsup</command> Þ ôï <command>ftp</command>.
+ ÄéáöïñåôéêÜ, ÷ñçóéìïðïéÞóôå ôï
+ <application>CTM</application>.</para>
</listitem>
<indexterm>
@@ -497,14 +507,15 @@
<secondary>compiling</secondary>
</indexterm>
<listitem>
- <para>Before compiling &os.stable;, 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.stable; 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.stable;, äéáâÜóôå ðñïóåêôéêÜ ôï
+ <filename>Makefile</filename> óôïí êáôÜëïãï
+ <filename>/usr/src</filename>. Èá ðñÝðåé íá <link
+ linkend="makeworld">ìåôáãëùôôßóåôå ôïí ðõñÞíá êáé üëï ôï âáóéêü óýóôçìá (world)</link> ôçí ðñþôç öïñÜ, ùò ìÝñïò ôçò äéáäéêáóßáò áíáâÜèìéóçò.
+ ÄéáâÜæïíôáò ôç ëßóôá &a.stable;
+ êáé ôï <filename>/usr/src/UPDATING</filename> èá åßóôå
+ åíçìåñùìÝíïé ãéá íÝåò äéáäéêáóßåò üóï áöïñÜ ôçí åêêßíçóç óôï íÝï
+ óáò óýóôçìá, ðïõ ïñéóìÝíåò öïñÝò åßíáé áðáñáßôçôåò üóï åñ÷üìáóôå
+ ðéï êïíôÜ óå ìéá íÝá åðßóçìç Ýêäïóç.</para>
</listitem>
</orderedlist>
</sect3>
More information about the Freebsd-doc-el
mailing list