doc-el commit 948:5ab32b787749 - Merge from manolis
freebsd-doc-el at lists.hellug.gr
freebsd-doc-el at lists.hellug.gr
Fri Oct 24 01:23:54 EEST 2008
changeset: 948:5ab32b787749
user: keramida
date: 2008-10-24 01:14 +0300
details: http://hg.hellug.gr/freebsd/doc-el/?cmd=changeset;node=5ab32b787749
description:
Merge from manolis
diffs (truncated from 1243 to 300 lines):
diff -r 505cc3a21ff9 -r 5ab32b787749 el_GR.ISO8859-7/books/handbook/cutting-edge/chapter.sgml
--- a/el_GR.ISO8859-7/books/handbook/cutting-edge/chapter.sgml Fri Oct 24 00:57:16 2008 +0300
+++ b/el_GR.ISO8859-7/books/handbook/cutting-edge/chapter.sgml Fri Oct 24 01:14:29 2008 +0300
@@ -106,16 +106,16 @@
<para>ÕðÜñ÷ïõí äýï êëÜäïé áíÜðôõîçò óôï &os;, ôï &os.current; êáé ôï
&os.stable;. Óôçí åíüôçôá áõôÞ, èá åîçãÞóïõìå êÜðïéá ðñÜãìáôá ó÷åôéêÜ
- ìå áõôïýò ôïõò êëÜäïõò, êáé èá ðåñéãñÜøïõìå ðùò ìðïñåßôå íá êñáôÞóåôå
+ ìå áõôïýò ôïõò êëÜäïõò, êáé èá ðåñéãñÜøïõìå ðùò ìðïñåßôå íá äéáôçñÞóåôå
ôï óýóôçìá óáò åíçìåñùìÝíï óå êÜðïéïí áðü áõôïýò. Èá ìéëÞóïõìå áñ÷éêÜ
ãéá ôï &os.current; êáé Ýðåéôá ãéá ôï &os.stable;.</para>
<sect2 id="current">
- <title>Ðáñáêïëïõèþíôáò ôï Current óôï &os;</title>
+ <title>Ðáñáêïëïõèþíôáò ôï &os.current;</title>
- <para>Êáèþò äéáâÜæåôå áõôü ôï êåßìåíï, íá Ý÷åôå õðüøéí óáò, üôé ôï
+ <para>Êáèþò äéáâÜæåôå áõôü ôï êåßìåíï, íá Ý÷åôå õðüøéí óáò üôé ôï
&os.current; åßíáé ðñÜãìáôé ç <quote>êüøç ôïõ îõñáöéïý</quote> óôçí
- áíÜðôõîç ôïõ &os;. Ïé ÷ñÞóôåò ôïõ &os.current; áíáìÝíåôáé íá Ý÷ïõí
+ áíÜðôõîç ôïõ &os;. Ïé ÷ñÞóôåò ôïõ &os.current; áíáìÝíåôáé íá Ý÷ïõí
áõîçìÝíåò ôå÷íéêÝò ãíþóåéò, êáé íá åßíáé éêáíïß íá åðéëýïõí äýóêïëá
ðñïâëÞìáôá ôïõ óõóôÞìáôïò ôïõò, ÷ùñßò âïÞèåéá. Áí åßóôå êáéíïýñéïò
óôï &os;, ìÜëëïí èá ðñÝðåé íá ôï îáíáóêåöôåßôå ðñéí ôï
@@ -131,12 +131,11 @@
äåí åßíáé óßãïõñï üôé èá ðåñéëáìâÜíïíôáé óôçí åðüìåíç åðßóçìç
Ýêäïóç ôïõ ëïãéóìéêïý. Áí êáé ðïëëÜ ìÝëç ôçò ïìÜäáò áíÜðôõîçò ôïõ
&os; ìåôáãëùôôßæïõí êáèçìåñéíÜ ôïí ðçãáßï êþäéêá ôïõ &os.current;,
- õðÜñ÷ïõí ÷ñïíéêÝò ðåñßïäïé ðïõ ï ðçãáßïò êþäéêáò äåí ìðïñåß íá
- ìåôáãëùôôéóôåß. Ôá ðñïâëÞìáôá áõôÜ ãåíéêÜ åðéëýïíôáé üóï ðéï
- ãñÞãïñá ãßíåôáé, áëëÜ ôï áí ôï &os.current; èá óáò öÝñåé ôçí
- êáôáóôñïöÞ Þ êÜðïéï ðïëõðüèçôï ÷áñáêôçñéóôéêü, åßíáé ðåñéóóüôåñï
- èÝìá ôçò ÷ñïíéêÞò óôéãìÞò ðïõ èá åðéëÝîåôå íá áíáêôÞóåôå ôïí
- ðçãáßï êþäéêá!</para>
+ õðÜñ÷ïõí ÷ñïíéêÝò ðåñßïäïé ðïõ ç ìåôáãëþôôéóç ôïõ åßíáé áäýíáôç.
+ Ôá ðñïâëÞìáôá áõôÜ ãåíéêÜ åðéëýïíôáé üóï ðéï ãñÞãïñá ãßíåôáé, áëëÜ
+ ôï áí ôï &os.current; èá óáò öÝñåé ôçí êáôáóôñïöÞ Þ êÜðïéï
+ ðïëõðüèçôï ÷áñáêôçñéóôéêü, åßíáé ðåñéóóüôåñï èÝìá ôçò ÷ñïíéêÞò
+ óôéãìÞò ðïõ èá åðéëÝîåôå íá áíáêôÞóåôå ôïí ðçãáßï êþäéêá!</para>
</sect3>
<sect3>
@@ -153,12 +152,12 @@
</listitem>
<listitem>
- <para>ÌÝëç ôçò êïéíüôçôáò ôïõ &os; ðïõ åßíáé åíåñãïß äïêéìáóôÝò
+ <para>ÌÝëç ôçò êïéíüôçôáò ôïõ &os; ðïõ åßíáé åíåñãïß testers
êáé åßíáé ðñüèõìïé íá áíáëþóïõí ôï ÷ñüíï ôïõò ãéá íá ëýóïõí
ðñïâëÞìáôá, þóôå íá åîáóöáëßóïõí üôé ôï &os.current;
- ðáñáìÝíåé üóï ôï äõíáôü ðéï óùóôü. ÓõíÞèùò, ôá ìÝëç áõôÜ
- êÜíïõí åðßóçò ôïðéêÝò ðñïôÜóåéò ãéá áëëáãÝò êáé ãéá ôçí ãåíéêÞ
- êáôåýèõíóç ôïõ &os;, êáé ðïõ óôÝëíïõí patches ãéá ôçí
+ èá ðáñáìåßíåé üóï ôï äõíáôüí ðéï óùóôü. ÓõíÞèùò, ôá ìÝëç áõôÜ
+ êÜíïõí ðñïôÜóåéò ãéá ôïðéêÝò áëëáãÝò êáé ãéá ôçí ãåíéêÞ
+ êáôåýèõíóç ôïõ &os;, êáé óôÝëíïõí patches ãéá ôçí
ðñáãìáôïðïßçóç ôïõò.</para>
</listitem>
@@ -177,13 +176,12 @@
<orderedlist>
<listitem>
- <para>Äåí åßíáé Ýíáò ãñÞãïñïò ôñüðïò íá ðÜñåôå ôìÞìáôá êþäéêá ôá
- ïðïßá äåí Ý÷ïõí êõêëïöïñÞóåé áêüìá óå êÜðïéá Ýêäïóç, ìå ôçí
+ <para>Äåí åßíáé Ýíáò ãñÞãïñïò ôñüðïò íá ðÜñåôå êþäéêá ï
+ ïðïßïò äåí Ý÷åé êõêëïöïñÞóåé áêüìá óå êÜðïéá Ýêäïóç, ìå ôçí
åëðßäá üôé ðåñéÝ÷åé êÜðïéá íÝá åêðëçêôéêÞ äõíáôüôçôá êáé
- èÝëåôå íá åßóôå ï ðñþôïò óôçí ðåñéï÷Þ ðïõ ôç ÷ñçóéìïðïéåß.
- Áí åßóôå ðñÜãìáôé ï ðñþôïò ðïõ ôçí ÷ñçóéìïðïéåß, èá åßóôå
- åðßóçò êáé ï ðñþôïò ðïõ èá óõíáíôÞóåôå ôá íÝá ðñïâëÞìáôá êáé
- bugs.</para>
+ èÝëåôå íá åßóôå ï ðñþôïò ðïõ ôç ÷ñçóéìïðïéåß. Áí åßóôå
+ ðñÜãìáôé ï ðñþôïò ðïõ ôçí ÷ñçóéìïðïéåß, èá åßóôå åðßóçò êáé ï
+ ðñþôïò ðïõ èá óõíáíôÞóåôå ôá íÝá ðñïâëÞìáôá êáé bugs.</para>
</listitem>
<listitem>
@@ -222,211 +220,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>
-
- <orderedlist>
- <indexterm>
- <primary><command>cvsup</command></primary>
- </indexterm>
- <indexterm>
- <primary><command>cron</command></primary>
- </indexterm>
- <indexterm>
- <primary>-CURRENT</primary>
- <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>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>
- </listitem>
-
- <indexterm>
- <primary>-CURRENT</primary>
- <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
- <application><link linkend="cvsup">CVSup</link></application>
- for anybody with a 9600 bps modem or faster connection.
- </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>
-
- <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>
- </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>
- </listitem>
- </orderedlist>
- </sect3>
- </sect2>
-
- <sect2 id="stable">
- <title>Staying Stable with &os;</title>
-
- <sect3>
- <title>What Is &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>
- </sect3>
-
- <sect3>
- <title>Who Needs &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>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>
- </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>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>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>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>
- </sect3>
-
- <sect3>
- <title>Using &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>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>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>
- </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
More information about the Freebsd-doc-el
mailing list