[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

release-notes changes on www-master



Hi,

For some reason the attached patches came into existence on the www-master
copy of etch release-notes but were never committed.

 Makefile.common                |    2 
 fi/release-notes.fi.sgml       |  301 +++++++++++++++++++++++++++------
 ja/release-notes.ja.sgml       |    2 
 pl/release-notes.pl.sgml       |  254 ++++++++++++++++++++++------
 pt/release-notes.pt.sgml       |  299 ++++++++++++++++++++++++++-------
 ro/release-notes.ro.sgml       |  371 +++++++++++++++++++++++++++++++----------
 ru/release-notes.ru.sgml       |   12 -
 sv/release-notes.sv.sgml       |   12 -
 zh_TW/release-notes.zh_TW.sgml |  288 +++++++++++++++++++++++++++----
 9 files changed, 1239 insertions(+), 302 deletions(-)

-- 
     2. That which causes joy or happiness.
? dynamic_alpha.ent
? dynamic_amd64.ent
? dynamic_arm.ent
? dynamic_hppa.ent
? dynamic_i386.ent
? dynamic_ia64.ent
? dynamic_mips.ent
? dynamic_mipsel.ent
? dynamic_powerpc.ent
? dynamic_s390.ent
? dynamic_sparc.ent
? release-notes-alpha
? release-notes-amd64
? release-notes-arm
? release-notes-hppa
? release-notes-i386
? release-notes-ia64
? release-notes-mips
? release-notes-mipsel
? release-notes-powerpc
? release-notes-s390
? release-notes-sparc
? ca/body.tmp
? ca/head.tmp
? ca/release-notes.ca.ps
? ca/release-notes.ca.txt
? cs/body.tmp
? cs/head.tmp
? cs/release-notes.cs.ps
? cs/release-notes.cs.txt
? de/body.tmp
? de/head.tmp
? de/release-notes.de.ps
? de/release-notes.de.txt
? en/body.tmp
? en/head.tmp
? en/release-notes.en.ps
? en/release-notes.en.txt
? es/body.tmp
? es/head.tmp
? es/release-notes.es.ps
? es/release-notes.es.txt
? fi/body.tmp
? fi/head.tmp
? fi/release-notes.fi.ps
? fi/release-notes.fi.txt
? fr/body.tmp
? fr/head.tmp
? fr/release-notes.fr.ps
? fr/release-notes.fr.txt
? it/body.tmp
? it/head.tmp
? it/release-notes.it.ps
? it/release-notes.it.txt
? ja/body.tmp
? ja/head.tmp
? ja/release-notes.ja.ps
? ja/release-notes.ja.txt
? nl/body.tmp
? nl/head.tmp
? nl/release-notes.nl.ps
? nl/release-notes.nl.txt
? pl/body.tmp
? pl/head.tmp
? pl/release-notes.pl.ps
? pl/release-notes.pl.txt
? pt/body.tmp
? pt/head.tmp
? pt/release-notes.pt.ps
? pt/release-notes.pt.txt
? pt_BR/body.tmp
? pt_BR/head.tmp
? pt_BR/release-notes.pt_BR.html
? pt_BR/release-notes.pt_BR.ps
? pt_BR/release-notes.pt_BR.txt
? ro/body.tmp
? ro/head.tmp
? ro/release-notes.ro.ps
? ro/release-notes.ro.txt
? ru/body.tmp
? ru/head.tmp
? ru/release-notes.ru.ps
? ru/release-notes.ru.txt
? sv/body.tmp
? sv/head.tmp
? sv/release-notes.sv.ps
? sv/release-notes.sv.txt
? zh_TW/body.tmp
? zh_TW/head.tmp
? zh_TW/release-notes.zh_TW.html
? zh_TW/release-notes.zh_TW.ps
? zh_TW/release-notes.zh_TW.txt
Index: Makefile.common
===================================================================
RCS file: /cvs/debian-doc/ddp/manuals.sgml/release-notes/Makefile.common,v
retrieving revision 1.14
diff -u -r1.14 Makefile.common
--- Makefile.common	9 Nov 2006 14:33:51 -0000	1.14
+++ Makefile.common	1 Sep 2008 17:25:30 -0000
@@ -77,7 +77,7 @@
 
 $(manual).$(currentlang).ps $(manual).$(currentlang).dvi $(manual).$(currentlang).pdf: \
   $(manual).$(currentlang).%: $(sources)
-	debiandoc2latex$* -l $(currentlang) $<
+	debiandoc2latex$* -v -l $(currentlang) $<
 
 ps dvi pdf info: %: $(manual).$(currentlang).%
 
Index: fi/release-notes.fi.sgml
===================================================================
RCS file: /cvs/debian-doc/ddp/manuals.sgml/release-notes/fi/release-notes.fi.sgml,v
retrieving revision 1.5
diff -u -r1.5 release-notes.fi.sgml
--- fi/release-notes.fi.sgml	11 Apr 2007 16:25:05 -0000	1.5
+++ fi/release-notes.fi.sgml	1 Sep 2008 17:25:30 -0000
@@ -2,7 +2,7 @@
 
   <!ENTITY % dynamicdata SYSTEM "../en/../dynamic.ent"> %dynamicdata;
   <!ENTITY % shareddata SYSTEM "../en/../release-notes.ent"> %shareddata;
-  <!ENTITY docid "$Id: release-notes.fi.sgml,v 1.5 2007-04-11 16:25:05 tale Exp $">
+  <!ENTITY docid "$Id: release-notes.en.sgml,v 1.312 2007/08/16 22:24:38 jseidel Exp $">
 ]>
 <debiandoc>
  <book>
@@ -305,6 +305,11 @@
      Apus on poistettu; myöskään ei tueta Applen arkkitehtuurin muunnosta 
      Nubus.
    </p>
+   <p>
+     Keyboards of iBooks and Powerbooks on &arch-title; are now fully 
+     supported (in X) and (contrary to <tt>&oldreleasename;</tt>) no custom 
+     made xmodmaps are required anymore.
+   </p>
   </sect>
    ]]>
 
@@ -898,10 +903,63 @@
      suoraan asennusrompulta.
    </p>
    <p>
-     Pulmasta ilmoittivat erilaisten järjestelmien käyttäjät (nimittäin 
-     Enterprise 450, Blade 2000, Fire V240, Enterprise 250 ja Blade 100 tätä 
-     kirjoitettaessa), joten vian uskotaan olevan tyypillinen näille 
-     malleille. Ilmoita jos havaitset vastaavia vikoja muilla laitteilla.
+     The problem was reported by users of various systems (namely, 
+     Enterprise 450, Blade 2000, Fire V240, Enterprise 250, Blade 100 and 
+     Enterprise 220R at the time of writing), so it is believed to be 
+     generic. Please let us know if you observe similar issues with your 
+     hardware.
+   </p>
+  </sect>
+  <sect id="sparc_qlogic_firmware">
+   <heading>
+     Issues with booting from qla2xxx on &arch-title;
+   </heading>
+   <p>
+     It has been reported by several users that the installation system 
+     fails to recognize hard disks on machines which have the hard disks 
+     connected to a QLogic fibre-channel SCSI controller. This includes the 
+     Sun Fire 280R servers. The qla2xxx driver loads, but it cannot load 
+     firmware, which makes it useless.
+   </p>
+   <p>
+     The explanation for this problem is that the QLogic controller firmware 
+     is not free, and it had to be moved to a separate non-free package 
+     (<url id="http://packages.debian.org/firmware-qlogic"; 
+     name="firmware-qlogic">) which is not used by the installation system.
+   </p>
+   <p>
+     There is no straightforward solution, unfortunately; one has to first 
+     provide the firmware image to the installation system, and then later 
+     do the same in the installed system. To get the installer to load the 
+     firmware, one has to have network connectivity while the machine is 
+     being installed in order to download the 
+     <package>firmware-qlogic</package> udeb package with wget, install it 
+     with udpkg, and then reload the qla2xxx module. After the installation 
+     is complete, mount the new root partition, chroot to it, fetch the 
+     <package>firmware-qlogic</package> deb package, install it with dpkg, 
+     and then run <prgn>update-initramfs</prgn> in order to include it in 
+     the initial ramdisk image used by the kernel.
+   </p>
+   <p>
+     Alternatively, install from an older installation CD (where that 
+     non-free firmware was still integrated) and then upgrade.
+   </p>
+  </sect>
+  <sect id="solard-used-hd">
+   <heading>
+     Size of harddisk not detected correctly
+   </heading>
+   <p>
+     If a hard disk has previously used under Solaris, the partitioner may 
+     not detect the size of the drive correctly. Creating a new partition 
+     table does not fix this issue. What does help, is to "zero" the first 
+     few sectors of the drive:
+    <example>
+# dd if=/dev/zero of=/dev/hd<var>X</var> bs=512 count=2; sync
+           </example>
+   </p>
+   <p>
+     Note that this will make any existing data on that disk inaccessible.
    </p>
   </sect>
    ]]>
@@ -1241,9 +1299,10 @@
       saattaa rikkoa järjestelmän pahasti.
     </p>
     <p>
-      Tärkeitä kopioitavia ovat hakemistopuut <file>/etc</file>, 
-      <file>/var/lib/dpkg</file> ja komennon <tt>dpkg --get-selections 
-      "*"</tt> tuloste (lainausmerkit ovat tärkeitä).
+      The main things you'll want to back up are the contents of 
+      <file>/etc</file>, <file>/var/lib/dpkg</file>, 
+      <file>/var/lib/aptitude/pkgstates</file> and the output of <tt>dpkg 
+      --get-selections "*"</tt> (the quotes are important).
     </p>
     <p>
       Asennusprosessi ei itse muokkaa mitään 
@@ -1417,14 +1476,14 @@
      Järjestelmän tilan tarkistaminen
    </heading>
    <p>
-     Tässä luvussa kuvattu päivitysprosessi on suunniteltu päivittämään 
-     "puhdas" &oldreleasename; jossa ei ole kolmannen osapuolen 
-     paketteja. Erityisesti on tunnettuja pulmia hakemistoon 
-     <file>/usr/X11R6/bin/</file> ohjelmia asentavien kolmannen osapuolen 
-     pakettien kanssa koska on siirrytty X.Org:n käyttöön (<ref 
-     id="xorg">). Saatat haluta poistaa kolmannen osapuolen paketit 
-     järjestelmästä ennen päivitystä jotta päivitysprosessin luotettavuus 
-     paranisi.
+     The upgrade process described in this chapter has been designed for 
+     upgrades from "pure" &oldreleasename; systems without third-party 
+     packages. In particular, there are known problems with third-party 
+     packages which install programs under <file>/usr/X11R6/bin/</file> 
+     causing problems with upgrades due to the X.Org transition (<ref 
+     id="xorg">). For greatest reliability of the upgrade process, you may 
+     wish to remove third-party packages from your system before you begin 
+     upgrading.
    </p>
    <p>
      Tässä oletetaan myös, että järjestelmä on päivitetty viimeisimpään 
@@ -1854,6 +1913,12 @@
 Tarvitsee noutaa xx.xMB/yyyMB arkistoista. Levytilaa kuluu AAAMB purkamisen jälkeen.
 Noutaisi tai asentaisi tai poistaisi paketteja.
        </example>
+      <footnote><p>Running this command at the beginning of the upgrade 
+      process may give an error, for the reasons described in the next 
+      sections. In that case you will need to wait until you've done the 
+      minimal system upgrade as in <ref id="minimal_upgrade"> and upgraded 
+      your kernel as in <ref id="upgrading_kernel"> before running this 
+      command to estimate the disk space. </p></footnote>
     </p>
     <p>
       Jos riittävää tilaa päivitykseen ei ole, muista vapauttaa tilaa 
@@ -2038,9 +2103,8 @@
        Päivitys järjestelmässä jossa ei ole mitään X-tukea asennettuna
      </heading>
      <p>
-       Jos järjestelmässä ei ole X:ää lainkaan, ei pitäisi tarvita 
-       ylimääräisiä aptitude install -komentoja, ja voidaan siirtyä 
-       seuraavaan vaiheeseen.
+       On a system with no X, no additional <tt>aptitude install</tt> 
+       command should be required, and you can move on to the next step.
      </p>
     </sect2>
    </sect1>
@@ -2199,7 +2263,7 @@
           </example>
       poistamaan joitakin kiusaa tekeviä paketteja, tai
      <example>
-# aptitude --fix-broken install
+# aptitude -f install
 # dpkg --configure --pending
           </example>
     </p>
@@ -2573,12 +2637,12 @@
       käynnistyskomentotiedostot eivät voi vielä käyttää niitä.
     </p>
     <p>
-      Tavalliset oireet ovat käynnistyksen epäonnistuminen koska 
-      juuritiedostojärjestelmää ei voi liittää ja päädytään 
-      virheenjäljityskomentotulkkiin, mutta kun myöhemmint tarkistetaan, 
-      kaikki tarvittavat laitteet ovat hakemistossa <file>/dev</file>. Ilmiö 
-      on havaittu kun juuritiedostojärjestelmä on USB-levyllä tai 
-      RAID-pakalla.
+      The usual symptoms are that the boot will fail because the root file 
+      system cannot be mounted and you are dropped into a debug shell, but 
+      that when you check afterwards, all devices that are needed are 
+      present in <file>/dev</file>. This has been observed in cases where 
+      the root file system is on a USB disk or on RAID, especially if lilo 
+      is used.
     </p>
     <p>
       Vian voi kiertää käynnistyksen parametrilla 
@@ -2586,6 +2650,19 @@
       joutua säätämään.
     </p>
    </sect1>
+    ]]><![ %powerpc [
+
+   <sect1 id="pcilynx-broken">
+    <heading>
+      PCILynx FireWire driver is broken
+    </heading>
+    <p>
+      The PCILynx driver is horribly broken and might result in driver 
+      crashes on PowerPC. We encourage users who need FireWire to avail 
+      themselves of one of the cheap OHCI1394 cards and blacklist PCILynx 
+      driver.
+    </p>
+   </sect1>
     ]]>
 
   </sect>
@@ -2657,11 +2734,11 @@
       ajuria ei ole muistilevyssä, järjestelmä ei ehkä käynnisty.
     </p>
     <p>
-      Käytettäessä <tt>lasi700</tt>- tai <tt>zalon7xx</tt>-moduuleita 
-      kiintolevyajureina, on tuo moduuli lisättävä tiedostoon 
-      <file>/etc/initramfs-tools/modules</file> ja tehtävä käynnistyksen 
-      muistilevy uudestaan ennen kuin järjestelmä käynnistetään 
-      uudelleen. Käynnistyksen muistilevy voidaan tehdä komennolla:
+      If your system uses the <tt>lasi700</tt>, <tt>53c700</tt> or 
+      <tt>zalon7xx</tt> module to access your hard disks, you will need to 
+      include that module in <file>/etc/initramfs-tools/modules</file> and 
+      regenerate the initrd before you reboot your system. The initrd can be 
+      regenerated using:
      <example>
 # update-initramfs -u -k all
           </example>
@@ -2848,7 +2925,24 @@
       siitä olisi etsittävä apua pulmatilanteissa.
     </p>
    </sect1>
+    <![ %sparc [
+
+   <sect1 id="networkdrivers">
+    <heading>
+      Conflict between tulip and dmfe drivers
+    </heading>
+    <p>
+      On some Netras (e.g. on Netra X1) udev loads both tulip and dmfe 
+      drivers, which claim support for the same PCI IDs (<url 
+      id="http://bugs.debian.org/334104"; name="#334104">). The tulip driver 
+      is correct one for Netra. If this happens, you should blacklist the 
+      dmfe driver and reboot, and/or remove both dmfe and tulip (modprobe 
+      -r) and then modprobe tulip only.
+    </p>
+   </sect1>
   </sect>
+   ]]>
+
   <sect id="for_next">
    <heading>
      Valmistautuminen seuraavaan julkaisuun
@@ -2888,9 +2982,10 @@
      </item>
      <item>
       <p>
-        Siirrä kaikki ytimen asetukset tiedostosta 
-        <file>/etc/network/options</file> tiedostoon 
-        <file>/etc/sysctl.conf</file>.
+        Move any configuration options from 
+        <file>/etc/network/options</file> to 
+        <file>/etc/sysctl.conf</file>. Please see 
+        <file>/usr/share/doc/netbase/README.Debian</file> for details.
       </p>
      </item>
      <item>
@@ -2904,6 +2999,48 @@
     </list>
    </p>
   </sect>
+  <sect id="deprecated">
+   <heading>
+     Deprecated packages
+   </heading>
+   <p>
+     With the release of <tt>Lenny</tt> a bigger number of server packages 
+     will be deprecated, thus updating to newer versions of those now will 
+     save you from trouble when updating to <tt>Lenny</tt>.
+   </p>
+   <p>
+     This includes the following packages:
+   </p>
+   <p>
+    <list>
+     <item>
+      <p>
+        apache (1.x), successor is apache2
+      </p>
+     </item>
+     <item>
+      <p>
+        bind8, successor is bind9
+      </p>
+     </item>
+     <item>
+      <p>
+        php4, successor is php5
+      </p>
+     </item>
+     <item>
+      <p>
+        postgresql-7.4, successor is postgresql-8.1
+      </p>
+     </item>
+     <item>
+      <p>
+        exim 3, successor is exim4
+      </p>
+     </item>
+    </list>
+   </p>
+  </sect>
   <sect id="obsolete">
    <heading>
      Vanhentuneet paketit
@@ -3063,8 +3200,6 @@
       id="http://www.debian.org/devel/debian-installer/errata"; 
       name="Debianin asentimen errata-sivulta">.
     </p>
-    <p>
-    </p>
    </sect1>
     <![ %i386 [
 
@@ -3236,6 +3371,20 @@
    </sect1>
     ]]>
 
+   <sect1 id="no-sound">
+    <heading>
+      Sound stops working
+    </heading>
+    <p>
+      In rare cases the sound might stop working after the upgrade. If this 
+      happens, go through the alsa checklist: run <prgn>alsaconf</prgn> as 
+      root user, add your user to the <tt>audio</tt> group, use alsamixer 
+      and make sure levels are up and it is unmuted, make sure arts or 
+      esound stopped, make sure OSS modules unloaded, make sure speakers are 
+      on, check whether the command <tt>cat /dev/urandom > /dev/dsp</tt> 
+      works for root.
+    </p>
+   </sect1>
   </sect>
    <![ %defaulted-2.4 [
 
@@ -3433,18 +3582,26 @@
      Sivulta <url id="http://wiki.debian.org/Xorg69To7";> voit lukea lisää 
      yksityiskohtia ja muita asioita.
    </p>
+   <p>
+     If you experience problems with X.Org after restarting, it might be 
+     also worth to restart the font server by running <tt>/etc/init.d/xfs 
+     restart</tt>. This happens due to <file>/etc/X11/fs/xfs.options</file> 
+     containing a line with <tt>no-restart-on-upgrade</tt>, but the font 
+     paths have changed.
+   </p>
   </sect>
   <sect id="xorg-8bit">
    <heading>
      Useissa sovelluksissa ei ole tukea 8-bittisille näytöille
    </heading>
    <p>
-     Kun on päivitetty X.Orgiin ja uusimpiin kirjastoihin, lakkaavat vain 
-     8-bittisiin väreihin pystyät X-päätteet toimimasta. Tämä koska Cairo 2D 
-     -vektorigrafiikkakirjastossa (<package>libcairo2</package>) ei ole 
-     8-bittisen pseudovärin tukea. Tätä kirjastoa käyttävät GNOME- ja 
-     Xfce-työpöytäympäristöt sekä monet Gtk2+-työkalupakilla käännetyt 
-     työpöytäsovellukset, kuten <package>abiword</package>.
+     After the upgrade to the X.Org and the latest libraries, X terminals 
+     which can only represent colors 8 bits depth will not work. This is 
+     because the Cairo 2D vector graphics library 
+     (<package>libcairo2</package>) doesn't have 8-bit pseudocolor 
+     support. This library is used by the GNOME and Xfce desktops as well as 
+     by many desktop applications compiled with the Gtk2+ toolkit, such as 
+     <package>abiword</package>.
    </p>
    <p>
      Koneet joihin tämän tiedetään vaikuttavan ovat jotkin Sun-koneet ja 
@@ -3760,6 +3917,36 @@
           </example>
    </p>
   </sect>
+  <sect id="motd">
+   <heading>
+     Message of the day
+   </heading>
+   <p>
+     <file>/etc/motd</file> is now a symlink to <file>/var/run/motd</file> 
+     which is rebuilt by <prgn>/etc/init.d/bootmisc.sh</prgn> from a 
+     template, <prgn>/etc/motd.tail</prgn>, at each reboot. It means that 
+     changes made to <file>/etc/motd</file> will be lost. Changes made into 
+     <file>/etc/motd.tail</file> are not automatically applied to 
+     <file>/etc/motd</file> other than at reboot.
+   </p>
+   <p>
+     Also, the EDITMOTD variable at <file>/etc/default/rcS</file> no longer 
+     has any effect. If you wish to disable updating of the motd, or want to 
+     maintain your own content for the message of the day you just have to 
+     point the <file>/etc/motd</file> symlink to a different file such as 
+     <file>/etc/motd.static</file> and make your changes there.
+   </p>
+  </sect>
+  <sect id="no-unicode">
+   <heading>
+     Not default support for unicode in emacs21*
+   </heading>
+   <p>
+     Emacs21 and emacs21-nox are not configured to use Unicode by 
+     default. For more information and a workaround please see <url 
+     id="http://bugs.debian.org/419490"; name="Bug #419490">.
+   </p>
+  </sect>
  </chapt>
  <chapt id="moreinfo">
   <heading>
@@ -3817,16 +4004,18 @@
       IRC
     </heading>
     <p>
-      Debianilla on käyttäjien tukeen ja auttamiseen tarkoitettu IRC-kanava 
-      OFTC-IRC-verkossa, joka tarjoaa tiedonvälitystä yhteistyötä tekevälle 
-      vapaiden ohjelmien yhteisölle. Pääset kanavalle menemällä 
-      haluamallassi IRC-asiakasohjelmalla palvelimelle &debian-irc-server; 
-      ja liittymällä kanavalle #debian.
+      Debian has an IRC channel dedicated to the support and aid of Debian 
+      users located on the OFTC IRC network. To access the channel, point 
+      your favorite IRC client at &debian-irc-server; and join #debian.
+    </p>
+    <p>
+      Please follow the channel guidelines, respecting other users 
+      fully. The guidelines are available at the <url 
+      id="http://wiki.debian.org/DebianIRC"; name="Debian Wiki">.
     </p>
     <p>
-      Noudata kanavan ohjeistusta ja kunnioita muiden käyttäjien 
-      mielipiteitä. Lisää tietoa OFTC:stä löytyy projektin <url 
-      id="&url-irc-host;" name="seittisivustolta">.
+      For more information on OFTC please visit the <url id="&url-irc-host;" 
+      name="website">.
     </p>
    </sect1>
   </sect>
@@ -3852,12 +4041,12 @@
      kehittävät voivat tarvittaessa pyytää lisätietoja.
    </p>
    <p>
-     Vikailmoitus voidaan lähettää ohjelmalla <package>reportbug</package> 
-     tai lähettämällä suoraan sähköpostia. Lisää tietoja 
-     vianseurantajärjestelmästä ja sen käyttöohjeita voi lukea hakemiston 
-     <file>/usr/share/doc/debian</file> ohjetiedostoista mikäli 
-     <package>doc-debian</package> on asennettu tai netistä osoitteesta <url 
-     id="&url-bts;" name="Vianseurantajärjestelmä">.
+     You can submit a bug report using the program <prgn>reportbug</prgn> or 
+     manually using email. You can read more about the Bug Tracking System 
+     and how to use it by reading the reference cards (available at 
+     <file>/usr/share/doc/debian</file> if you have 
+     <package>doc-debian</package> installed) or online at the <url 
+     id="&url-bts;" name="Bug Tracking System">.
    </p>
   </sect>
   <sect id="contributing">
Index: ja/release-notes.ja.sgml
===================================================================
RCS file: /cvs/debian-doc/ddp/manuals.sgml/release-notes/ja/release-notes.ja.sgml,v
retrieving revision 1.29
diff -u -r1.29 release-notes.ja.sgml
--- ja/release-notes.ja.sgml	25 Aug 2007 16:40:02 -0000	1.29
+++ ja/release-notes.ja.sgml	1 Sep 2008 17:25:31 -0000
@@ -2,7 +2,7 @@
 
   <!ENTITY % dynamicdata SYSTEM "../en/../dynamic.ent"> %dynamicdata;
   <!ENTITY % shareddata SYSTEM "../en/../release-notes.ent"> %shareddata;
-  <!ENTITY docid "$Id: release-notes.ja.sgml,v 1.29 2007-08-25 16:40:02 jseidel Exp $">
+  <!ENTITY docid "$Id: release-notes.en.sgml,v 1.312 2007/08/16 22:24:38 jseidel Exp $">
 ]>
 <debiandoc>
  <book>
Index: pl/release-notes.pl.sgml
===================================================================
RCS file: /cvs/debian-doc/ddp/manuals.sgml/release-notes/pl/release-notes.pl.sgml,v
retrieving revision 1.2
diff -u -r1.2 release-notes.pl.sgml
--- pl/release-notes.pl.sgml	25 Jun 2007 19:55:46 -0000	1.2
+++ pl/release-notes.pl.sgml	1 Sep 2008 17:25:31 -0000
@@ -2,7 +2,7 @@
 
   <!ENTITY % dynamicdata SYSTEM "../en/../dynamic.ent"> %dynamicdata;
   <!ENTITY % shareddata SYSTEM "../en/../release-notes.ent"> %shareddata;
-  <!ENTITY docid "$Id: release-notes.pl.sgml,v 1.2 2007-06-25 19:55:46 jseidel Exp $">
+  <!ENTITY docid "$Id: release-notes.en.sgml,v 1.312 2007/08/16 22:24:38 jseidel Exp $">
 ]>
 <debiandoc>
  <book>
@@ -301,6 +301,11 @@
      Apple G5 powermac). Zostało wycofane wsparcie dla Apple Apus; 
      podarchitektura Apple Nubus również nie jest wspierana.
    </p>
+   <p>
+     Keyboards of iBooks and Powerbooks on &arch-title; are now fully 
+     supported (in X) and (contrary to <tt>&oldreleasename;</tt>) no custom 
+     made xmodmaps are required anymore.
+   </p>
   </sect>
    ]]>
 
@@ -922,16 +927,17 @@
      instalacyjny.
    </p>
    <p>
-     Niestety, nie ma na to bezpośredniego rozwiązania; konieczne jest 
-     najpierw udostępnienie firmware'u systemowi instalacyjnemu, a potem tak 
-     samo instalowanemu systemowi. Aby wymusić załadowanie firmware'u przez 
-     instalator, najpierw trzeba mieć połączenie sieciowe do maszyny z 
-     zainstalowanym pakietem firmware-qlogic udeb, ściągnąć go za pomocą 
-     wget, zainstalować poprzez udpkg i przeładować moduł qla2xxx. Po 
-     zakończeniu instalacji, trzeba zamontować nową partycję root, 
-     "chrootować" na nią, ściągnąć pakiet firmware-qlogic, zainstalować za 
-     pomocą dpkg i wykonać update-initramfs w celu włączenia jej do 
-     inicjalnego ramdysku używanego przez jądro.
+     There is no straightforward solution, unfortunately; one has to first 
+     provide the firmware image to the installation system, and then later 
+     do the same in the installed system. To get the installer to load the 
+     firmware, one has to have network connectivity while the machine is 
+     being installed in order to download the 
+     <package>firmware-qlogic</package> udeb package with wget, install it 
+     with udpkg, and then reload the qla2xxx module. After the installation 
+     is complete, mount the new root partition, chroot to it, fetch the 
+     <package>firmware-qlogic</package> deb package, install it with dpkg, 
+     and then run <prgn>update-initramfs</prgn> in order to include it in 
+     the initial ramdisk image used by the kernel.
    </p>
    <p>
      Alternatywą jest instalacja ze starej płyty instalacyjnej (gdzie 
@@ -939,6 +945,23 @@
      aktualizacji.
    </p>
   </sect>
+  <sect id="solard-used-hd">
+   <heading>
+     Size of harddisk not detected correctly
+   </heading>
+   <p>
+     If a hard disk has previously used under Solaris, the partitioner may 
+     not detect the size of the drive correctly. Creating a new partition 
+     table does not fix this issue. What does help, is to "zero" the first 
+     few sectors of the drive:
+    <example>
+# dd if=/dev/zero of=/dev/hd<var>X</var> bs=512 count=2; sync
+           </example>
+   </p>
+   <p>
+     Note that this will make any existing data on that disk inaccessible.
+   </p>
+  </sect>
    ]]>
 
   <sect id="inst-new">
@@ -1285,9 +1308,10 @@
       w czasie aktualizacji mogą spowodować poważne uszkodzenie systemu.
     </p>
     <p>
-      Najważniejsze do zachowania są katalogi <file>/etc</file>, 
-      <file>/var/lib/dpkg</file> oraz wyjście polecenia <tt>dpkg 
-      --get-selections "*"</tt> (cudzysłowy są ważne).
+      The main things you'll want to back up are the contents of 
+      <file>/etc</file>, <file>/var/lib/dpkg</file>, 
+      <file>/var/lib/aptitude/pkgstates</file> and the output of <tt>dpkg 
+      --get-selections "*"</tt> (the quotes are important).
     </p>
     <p>
       Proces aktualizacji nie wprowadza modyfikacji w katalogu 
@@ -1459,12 +1483,14 @@
      Sprawdzenie statusu systemu
    </heading>
    <p>
-     Proces aktualizacji opisany w tym rozdziale został zaprojektowany dla 
-     upgrade'u z "czystego" systemu &oldreleasename;, bez pakietów spoza 
-     Debiana. Są znane problemy z takimi pakietami, które instalują programy 
-     w <file>/usr/X11R6/bin/</file>, ze względu na przejście na środowisko 
-     X.org (<ref id="xorg">). W celu zwiększenia niezawodności być może 
-     najprościej jest usunąć te pakiety, zanim rozpoczniesz upgrade.
+     The upgrade process described in this chapter has been designed for 
+     upgrades from "pure" &oldreleasename; systems without third-party 
+     packages. In particular, there are known problems with third-party 
+     packages which install programs under <file>/usr/X11R6/bin/</file> 
+     causing problems with upgrades due to the X.Org transition (<ref 
+     id="xorg">). For greatest reliability of the upgrade process, you may 
+     wish to remove third-party packages from your system before you begin 
+     upgrading.
    </p>
    <p>
      Zakładamy również, że aktualizujemy system z najnowszego 
@@ -1892,6 +1918,12 @@
 Potrzebne ściągnięcie xx.xMB/yyyMB archiwów. Po rozpakowaniu zostanie użyte AAAMB.
 Zostaną ściągnięte/zainstalowane/usunięte pakiety.
        </example>
+      <footnote><p>Running this command at the beginning of the upgrade 
+      process may give an error, for the reasons described in the next 
+      sections. In that case you will need to wait until you've done the 
+      minimal system upgrade as in <ref id="minimal_upgrade"> and upgraded 
+      your kernel as in <ref id="upgrading_kernel"> before running this 
+      command to estimate the disk space. </p></footnote>
     </p>
     <p>
       Jeśli nie ma wystarczającej przestrzeni na upgrade, musisz przedtem 
@@ -2073,8 +2105,8 @@
        Aktualizacja systemu bez X-ów
      </heading>
      <p>
-       Dla systemów bez X-ów nie jest konieczne wykonywanie żadnej 
-       dodatkowej komendy, można od razu przejść do następnego kroku.
+       On a system with no X, no additional <tt>aptitude install</tt> 
+       command should be required, and you can move on to the next step.
      </p>
     </sect2>
    </sect1>
@@ -2227,7 +2259,7 @@
           </example>
       aby wyeliminować jakieś przeszkadzające pakiety lub
      <example>
-# aptitude --fix-broken install
+# aptitude -f install
 # dpkg --configure --pending
           </example>
     </p>
@@ -2599,12 +2631,12 @@
       zbyt późno, aby były przydatne dla skrtyptu bootowania.
     </p>
     <p>
-      Symptomem zwykle jest wtedy błąd bootowania ze względu na niemożność 
-      zamontowania filesystemu root i następuje przejście do powłoki 
-      debugowania. Sprawdzając tam urządzenia stwierdzasz, że wszystkie 
-      wymagane pliki są jednak utworzone w katalogu <file>/dev</file>. Było 
-      to obserwowane w przypadkach, gdy filesystem root był założony na 
-      urządzeniach USB lub RAID.
+      The usual symptoms are that the boot will fail because the root file 
+      system cannot be mounted and you are dropped into a debug shell, but 
+      that when you check afterwards, all devices that are needed are 
+      present in <file>/dev</file>. This has been observed in cases where 
+      the root file system is on a USB disk or on RAID, especially if lilo 
+      is used.
     </p>
     <p>
       Rozwiązaniem tego problemu jest użycie parametru bootowania 
@@ -2612,6 +2644,19 @@
       być zmieniona.
     </p>
    </sect1>
+    ]]><![ %powerpc [
+
+   <sect1 id="pcilynx-broken">
+    <heading>
+      PCILynx FireWire driver is broken
+    </heading>
+    <p>
+      The PCILynx driver is horribly broken and might result in driver 
+      crashes on PowerPC. We encourage users who need FireWire to avail 
+      themselves of one of the cheap OHCI1394 cards and blacklist PCILynx 
+      driver.
+    </p>
+   </sect1>
     ]]>
 
   </sect>
@@ -2683,10 +2728,11 @@
       nie zostaną dodane, bootowanie może się nie powieść.
     </p>
     <p>
-      Jeśli system używa modułów <tt>lasi700</tt> lub <tt>zalon7xx</tt> do 
-      sterowania dyskami, powinieneś dodać te moduły do pliku 
-      <file>/etc/initramfs-tools/modules</file> i zregenerować initrd przed 
-      rebootem systemu. Initrd można zregenerować za pomocą:
+      If your system uses the <tt>lasi700</tt>, <tt>53c700</tt> or 
+      <tt>zalon7xx</tt> module to access your hard disks, you will need to 
+      include that module in <file>/etc/initramfs-tools/modules</file> and 
+      regenerate the initrd before you reboot your system. The initrd can be 
+      regenerated using:
      <example>
 # update-initramfs -u -k all
           </example>
@@ -2869,7 +2915,24 @@
       prosimy przeczytać w razie problemów.
     </p>
    </sect1>
+    <![ %sparc [
+
+   <sect1 id="networkdrivers">
+    <heading>
+      Conflict between tulip and dmfe drivers
+    </heading>
+    <p>
+      On some Netras (e.g. on Netra X1) udev loads both tulip and dmfe 
+      drivers, which claim support for the same PCI IDs (<url 
+      id="http://bugs.debian.org/334104"; name="#334104">). The tulip driver 
+      is correct one for Netra. If this happens, you should blacklist the 
+      dmfe driver and reboot, and/or remove both dmfe and tulip (modprobe 
+      -r) and then modprobe tulip only.
+    </p>
+   </sect1>
   </sect>
+   ]]>
+
   <sect id="for_next">
    <heading>
      Przygotowanie do nowej edycji
@@ -2908,8 +2971,10 @@
      </item>
      <item>
       <p>
-        Przenieś wszystkie zmienne konfiguracji jądra z pliku 
-        <file>/etc/network/options</file> do <file>/etc/sysctl.conf</file>.
+        Move any configuration options from 
+        <file>/etc/network/options</file> to 
+        <file>/etc/sysctl.conf</file>. Please see 
+        <file>/usr/share/doc/netbase/README.Debian</file> for details.
       </p>
      </item>
      <item>
@@ -2923,6 +2988,48 @@
     </list>
    </p>
   </sect>
+  <sect id="deprecated">
+   <heading>
+     Deprecated packages
+   </heading>
+   <p>
+     With the release of <tt>Lenny</tt> a bigger number of server packages 
+     will be deprecated, thus updating to newer versions of those now will 
+     save you from trouble when updating to <tt>Lenny</tt>.
+   </p>
+   <p>
+     This includes the following packages:
+   </p>
+   <p>
+    <list>
+     <item>
+      <p>
+        apache (1.x), successor is apache2
+      </p>
+     </item>
+     <item>
+      <p>
+        bind8, successor is bind9
+      </p>
+     </item>
+     <item>
+      <p>
+        php4, successor is php5
+      </p>
+     </item>
+     <item>
+      <p>
+        postgresql-7.4, successor is postgresql-8.1
+      </p>
+     </item>
+     <item>
+      <p>
+        exim 3, successor is exim4
+      </p>
+     </item>
+    </list>
+   </p>
+  </sect>
   <sect id="obsolete">
    <heading>
      Przestarzałe pakiety
@@ -3245,6 +3352,20 @@
    </sect1>
     ]]>
 
+   <sect1 id="no-sound">
+    <heading>
+      Sound stops working
+    </heading>
+    <p>
+      In rare cases the sound might stop working after the upgrade. If this 
+      happens, go through the alsa checklist: run <prgn>alsaconf</prgn> as 
+      root user, add your user to the <tt>audio</tt> group, use alsamixer 
+      and make sure levels are up and it is unmuted, make sure arts or 
+      esound stopped, make sure OSS modules unloaded, make sure speakers are 
+      on, check whether the command <tt>cat /dev/urandom > /dev/dsp</tt> 
+      works for root.
+    </p>
+   </sect1>
   </sect>
    <![ %defaulted-2.4 [
 
@@ -3441,19 +3562,26 @@
      Prosimy przeczytać <url id="http://wiki.debian.org/Xorg69To7";>, są tam 
      opisane szczegóły i inne problemy.
    </p>
+   <p>
+     If you experience problems with X.Org after restarting, it might be 
+     also worth to restart the font server by running <tt>/etc/init.d/xfs 
+     restart</tt>. This happens due to <file>/etc/X11/fs/xfs.options</file> 
+     containing a line with <tt>no-restart-on-upgrade</tt>, but the font 
+     paths have changed.
+   </p>
   </sect>
   <sect id="xorg-8bit">
    <heading>
      Brak wsparcia dla 8-bitowych wyświetlaczy w wielu aplikacjach
    </heading>
    <p>
-     Po upgrade do Xorg i najnowszych bibliotek, X-terminale, które 
-     obsługują jedynie 8-bitowe wyświetlanie kolorów, nie zadziałają. Dzieje 
-     się tak, gdyż biblioteka graficzna Cairo 2D vector 
-     (<package>libcairo2</package>) nie zawiera wsparcia dla 8-bitowego 
-     pseudokoloru. Biblioteka ta jest używana przez GNOME i Xfce, a także 
-     przez wiele aplikacji skompilowanych przy użyciu narzędzi Gtk2+, takich 
-     jak <package>abiword</package>.
+     After the upgrade to the X.Org and the latest libraries, X terminals 
+     which can only represent colors 8 bits depth will not work. This is 
+     because the Cairo 2D vector graphics library 
+     (<package>libcairo2</package>) doesn't have 8-bit pseudocolor 
+     support. This library is used by the GNOME and Xfce desktops as well as 
+     by many desktop applications compiled with the Gtk2+ toolkit, such as 
+     <package>abiword</package>.
    </p>
    <p>
      Systemy, których dotyczy ten problem to niektóre maszyny Sun oraz 
@@ -3763,6 +3891,36 @@
           </example>
    </p>
   </sect>
+  <sect id="motd">
+   <heading>
+     Message of the day
+   </heading>
+   <p>
+     <file>/etc/motd</file> is now a symlink to <file>/var/run/motd</file> 
+     which is rebuilt by <prgn>/etc/init.d/bootmisc.sh</prgn> from a 
+     template, <prgn>/etc/motd.tail</prgn>, at each reboot. It means that 
+     changes made to <file>/etc/motd</file> will be lost. Changes made into 
+     <file>/etc/motd.tail</file> are not automatically applied to 
+     <file>/etc/motd</file> other than at reboot.
+   </p>
+   <p>
+     Also, the EDITMOTD variable at <file>/etc/default/rcS</file> no longer 
+     has any effect. If you wish to disable updating of the motd, or want to 
+     maintain your own content for the message of the day you just have to 
+     point the <file>/etc/motd</file> symlink to a different file such as 
+     <file>/etc/motd.static</file> and make your changes there.
+   </p>
+  </sect>
+  <sect id="no-unicode">
+   <heading>
+     Not default support for unicode in emacs21*
+   </heading>
+   <p>
+     Emacs21 and emacs21-nox are not configured to use Unicode by 
+     default. For more information and a workaround please see <url 
+     id="http://bugs.debian.org/419490"; name="Bug #419490">.
+   </p>
+  </sect>
  </chapt>
  <chapt id="moreinfo">
   <heading>
@@ -3855,12 +4013,12 @@
      pytań.
    </p>
    <p>
-     Możesz wysłać raport używając programu <package>reportbug</package> lub 
-     ręcznie przez mail. Prosimy przeczytać informacje o BTS i sposobie jego 
-     używania zawarte na kartach referencyjnych (dostępnych na 
-     <file>/usr/share/doc/debian</file>, jeśli masz zainstalowany pakiet 
-     <package>doc-debian</package>) lub na stronach <url id="&url-bts;" 
-     name="Systemu śledzenia błędów">.
+     You can submit a bug report using the program <prgn>reportbug</prgn> or 
+     manually using email. You can read more about the Bug Tracking System 
+     and how to use it by reading the reference cards (available at 
+     <file>/usr/share/doc/debian</file> if you have 
+     <package>doc-debian</package> installed) or online at the <url 
+     id="&url-bts;" name="Bug Tracking System">.
    </p>
   </sect>
   <sect id="contributing">
Index: pt/release-notes.pt.sgml
===================================================================
RCS file: /cvs/debian-doc/ddp/manuals.sgml/release-notes/pt/release-notes.pt.sgml,v
retrieving revision 1.23
diff -u -r1.23 release-notes.pt.sgml
--- pt/release-notes.pt.sgml	12 Apr 2007 11:06:39 -0000	1.23
+++ pt/release-notes.pt.sgml	1 Sep 2008 17:25:31 -0000
@@ -2,7 +2,7 @@
 
   <!ENTITY % dynamicdata SYSTEM "../en/../dynamic.ent"> %dynamicdata;
   <!ENTITY % shareddata SYSTEM "../en/../release-notes.ent"> %shareddata;
-  <!ENTITY docid "$Id: release-notes.pt.sgml,v 1.23 2007-04-12 11:06:39 fjp Exp $">
+  <!ENTITY docid "$Id: release-notes.en.sgml,v 1.312 2007/08/16 22:24:38 jseidel Exp $">
 ]>
 <debiandoc>
  <book>
@@ -318,6 +318,11 @@
      sub-arquitectura Apple Apus foi descontinuado; a sub-arquitectura Apple 
      Nubus também năo é suportada.
    </p>
+   <p>
+     Keyboards of iBooks and Powerbooks on &arch-title; are now fully 
+     supported (in X) and (contrary to <tt>&oldreleasename;</tt>) no custom 
+     made xmodmaps are required anymore.
+   </p>
   </sect>
    ]]>
 
@@ -931,11 +936,63 @@
      directamente com o CD de instalaçăo.
    </p>
    <p>
-     O problema foi relatado por utilizadores de vários sistemas 
-     (nomeadamente, Enterprise 450, Blade 2000, Fire V240, Enterprise 250 e 
-     Blade 100, na altura em que isto foi escrito), portanto acredita-se ser 
-     geral. Por favor informe-nos se observar problemas semelhantes com o 
-     seu hardware.
+     The problem was reported by users of various systems (namely, 
+     Enterprise 450, Blade 2000, Fire V240, Enterprise 250, Blade 100 and 
+     Enterprise 220R at the time of writing), so it is believed to be 
+     generic. Please let us know if you observe similar issues with your 
+     hardware.
+   </p>
+  </sect>
+  <sect id="sparc_qlogic_firmware">
+   <heading>
+     Issues with booting from qla2xxx on &arch-title;
+   </heading>
+   <p>
+     It has been reported by several users that the installation system 
+     fails to recognize hard disks on machines which have the hard disks 
+     connected to a QLogic fibre-channel SCSI controller. This includes the 
+     Sun Fire 280R servers. The qla2xxx driver loads, but it cannot load 
+     firmware, which makes it useless.
+   </p>
+   <p>
+     The explanation for this problem is that the QLogic controller firmware 
+     is not free, and it had to be moved to a separate non-free package 
+     (<url id="http://packages.debian.org/firmware-qlogic"; 
+     name="firmware-qlogic">) which is not used by the installation system.
+   </p>
+   <p>
+     There is no straightforward solution, unfortunately; one has to first 
+     provide the firmware image to the installation system, and then later 
+     do the same in the installed system. To get the installer to load the 
+     firmware, one has to have network connectivity while the machine is 
+     being installed in order to download the 
+     <package>firmware-qlogic</package> udeb package with wget, install it 
+     with udpkg, and then reload the qla2xxx module. After the installation 
+     is complete, mount the new root partition, chroot to it, fetch the 
+     <package>firmware-qlogic</package> deb package, install it with dpkg, 
+     and then run <prgn>update-initramfs</prgn> in order to include it in 
+     the initial ramdisk image used by the kernel.
+   </p>
+   <p>
+     Alternatively, install from an older installation CD (where that 
+     non-free firmware was still integrated) and then upgrade.
+   </p>
+  </sect>
+  <sect id="solard-used-hd">
+   <heading>
+     Size of harddisk not detected correctly
+   </heading>
+   <p>
+     If a hard disk has previously used under Solaris, the partitioner may 
+     not detect the size of the drive correctly. Creating a new partition 
+     table does not fix this issue. What does help, is to "zero" the first 
+     few sectors of the drive:
+    <example>
+# dd if=/dev/zero of=/dev/hd<var>X</var> bs=512 count=2; sync
+           </example>
+   </p>
+   <p>
+     Note that this will make any existing data on that disk inaccessible.
    </p>
   </sect>
    ]]>
@@ -1293,9 +1350,10 @@
       extremamente danificado.
     </p>
     <p>
-      A principal informaçăo que quererá salvaguardar é o conteúdo de 
-      <file>/etc</file>, <file>/var/lib/dpkg</file> e saída de <tt>dpkg 
-      --get-selections "*"</tt> (as aspas săo importantes).
+      The main things you'll want to back up are the contents of 
+      <file>/etc</file>, <file>/var/lib/dpkg</file>, 
+      <file>/var/lib/aptitude/pkgstates</file> and the output of <tt>dpkg 
+      --get-selections "*"</tt> (the quotes are important).
     </p>
     <p>
       O processo de actualizaçăo em si năo modifica nada no seu directório 
@@ -1476,13 +1534,14 @@
      Verificar o estado do sistema
    </heading>
    <p>
-     O processo de actualizaçăo descrito neste capítulo foi desenhado para 
-     actualizaçőes de sistemas &oldreleasename; "puros" sem pacotes de 
-     terceiros. Em particular, há problemas conhecidos com pacotes de 
-     terceiros que instalam programas em <file>/usr/X11R6/bin/</file> que 
-     causam problemas devido ŕ transiçăo para X.org (<ref id="xorg">). Para 
-     uma maior fiabilidade do processo de actualizaçăo, pode querer remover 
-     pacotes de terceiros do seu sistema antes de começar a actualizaçăo.
+     The upgrade process described in this chapter has been designed for 
+     upgrades from "pure" &oldreleasename; systems without third-party 
+     packages. In particular, there are known problems with third-party 
+     packages which install programs under <file>/usr/X11R6/bin/</file> 
+     causing problems with upgrades due to the X.Org transition (<ref 
+     id="xorg">). For greatest reliability of the upgrade process, you may 
+     wish to remove third-party packages from your system before you begin 
+     upgrading.
    </p>
    <p>
      Este procedimento assume que o seu sistema foi actualizado até ao 
@@ -1932,6 +1991,12 @@
 Necessário obter xx.xMB/yyyMB de arquivos. Depois da descompressăo AAAMB serăo utilizados.
 Serăo descarregados/instalados/removidos pacotes.
        </example>
+      <footnote><p>Running this command at the beginning of the upgrade 
+      process may give an error, for the reasons described in the next 
+      sections. In that case you will need to wait until you've done the 
+      minimal system upgrade as in <ref id="minimal_upgrade"> and upgraded 
+      your kernel as in <ref id="upgrading_kernel"> before running this 
+      command to estimate the disk space. </p></footnote>
     </p>
     <p>
       Se năo tiver espaço suficiente para a actualizaçăo, certifique-se que 
@@ -2118,8 +2183,8 @@
        Actualizar um sistema sem ter instalado o suporte para X
      </heading>
      <p>
-       Num sistema sem X, năo deve ser preciso mais nenhum comando além de 
-       aptitude install, e pode prosseguir para o próximo passo.
+       On a system with no X, no additional <tt>aptitude install</tt> 
+       command should be required, and you can move on to the next step.
      </p>
     </sect2>
    </sect1>
@@ -2276,7 +2341,7 @@
           </example>
       para eliminar alguns dos pacotes que estăo a criar problemas, ou
      <example>
-# aptitude --fix-broken install
+# aptitude -f install
 # dpkg --configure --pending
           </example>
     </p>
@@ -2669,11 +2734,12 @@
       scripts de arranque actuem.
     </p>
     <p>
-      Os sintomas usuais săo que o arranque falha devido ao sistema de 
-      ficheiros raiz năo poder ser montado e vocę é deixado na shell de 
-      depuraçăo, mas quando verifica, todos os dispositivos necessários 
-      estăo presentes no <file>/dev</file>. Isto foi observado em casos em 
-      que o sistema de ficheiros raiz está num disco USB ou num RAID.
+      The usual symptoms are that the boot will fail because the root file 
+      system cannot be mounted and you are dropped into a debug shell, but 
+      that when you check afterwards, all devices that are needed are 
+      present in <file>/dev</file>. This has been observed in cases where 
+      the root file system is on a USB disk or on RAID, especially if lilo 
+      is used.
     </p>
     <p>
       Uma forma de contornar este problema é utilizar o parâmetro de 
@@ -2681,6 +2747,19 @@
       (em segundos) pode ter de ser ajustado.
     </p>
    </sect1>
+    ]]><![ %powerpc [
+
+   <sect1 id="pcilynx-broken">
+    <heading>
+      PCILynx FireWire driver is broken
+    </heading>
+    <p>
+      The PCILynx driver is horribly broken and might result in driver 
+      crashes on PowerPC. We encourage users who need FireWire to avail 
+      themselves of one of the cheap OHCI1394 cards and blacklist PCILynx 
+      driver.
+    </p>
+   </sect1>
     ]]>
 
   </sect>
@@ -2757,12 +2836,11 @@
       arranque.
     </p>
     <p>
-      Se o seu sistema utiliza o módulo <tt>lasi700</tt> ou o 
-      <tt>zalon7xx</tt> para aceder aos seus discos rígidos, vocę irá 
-      necessitar de incluir esse módulo em 
-      <file>/etc/initramfs-tools/modules</file> e gerar novamente o initrd 
-      antes de reiniciar o seu sistema. O initrd pode ser novamente gerado 
-      utilizando:
+      If your system uses the <tt>lasi700</tt>, <tt>53c700</tt> or 
+      <tt>zalon7xx</tt> module to access your hard disks, you will need to 
+      include that module in <file>/etc/initramfs-tools/modules</file> and 
+      regenerate the initrd before you reboot your system. The initrd can be 
+      regenerated using:
      <example>
 # update-initramfs -u -k all
           </example>
@@ -2946,7 +3024,24 @@
       por favor consulte-o em caso de problemas.
     </p>
    </sect1>
+    <![ %sparc [
+
+   <sect1 id="networkdrivers">
+    <heading>
+      Conflict between tulip and dmfe drivers
+    </heading>
+    <p>
+      On some Netras (e.g. on Netra X1) udev loads both tulip and dmfe 
+      drivers, which claim support for the same PCI IDs (<url 
+      id="http://bugs.debian.org/334104"; name="#334104">). The tulip driver 
+      is correct one for Netra. If this happens, you should blacklist the 
+      dmfe driver and reboot, and/or remove both dmfe and tulip (modprobe 
+      -r) and then modprobe tulip only.
+    </p>
+   </sect1>
   </sect>
+   ]]>
+
   <sect id="for_next">
    <heading>
      Preparar para o próximo lançamento
@@ -2985,9 +3080,10 @@
      </item>
      <item>
       <p>
-        Mova quaisquer valores das configuraçőes do kernel em 
-        <file>/etc/network/options</file> para 
-        <file>/etc/sysctl.conf</file>.
+        Move any configuration options from 
+        <file>/etc/network/options</file> to 
+        <file>/etc/sysctl.conf</file>. Please see 
+        <file>/usr/share/doc/netbase/README.Debian</file> for details.
       </p>
      </item>
      <item>
@@ -3001,6 +3097,48 @@
     </list>
    </p>
   </sect>
+  <sect id="deprecated">
+   <heading>
+     Deprecated packages
+   </heading>
+   <p>
+     With the release of <tt>Lenny</tt> a bigger number of server packages 
+     will be deprecated, thus updating to newer versions of those now will 
+     save you from trouble when updating to <tt>Lenny</tt>.
+   </p>
+   <p>
+     This includes the following packages:
+   </p>
+   <p>
+    <list>
+     <item>
+      <p>
+        apache (1.x), successor is apache2
+      </p>
+     </item>
+     <item>
+      <p>
+        bind8, successor is bind9
+      </p>
+     </item>
+     <item>
+      <p>
+        php4, successor is php5
+      </p>
+     </item>
+     <item>
+      <p>
+        postgresql-7.4, successor is postgresql-8.1
+      </p>
+     </item>
+     <item>
+      <p>
+        exim 3, successor is exim4
+      </p>
+     </item>
+    </list>
+   </p>
+  </sect>
   <sect id="obsolete">
    <heading>
      Pacotes obsoletos
@@ -3164,8 +3302,6 @@
       id="http://www.debian.org/devel/debian-installer/errata"; name="página 
       da errata do debian-installer">.
     </p>
-    <p>
-    </p>
    </sect1>
     <![ %i386 [
 
@@ -3336,6 +3472,20 @@
    </sect1>
     ]]>
 
+   <sect1 id="no-sound">
+    <heading>
+      Sound stops working
+    </heading>
+    <p>
+      In rare cases the sound might stop working after the upgrade. If this 
+      happens, go through the alsa checklist: run <prgn>alsaconf</prgn> as 
+      root user, add your user to the <tt>audio</tt> group, use alsamixer 
+      and make sure levels are up and it is unmuted, make sure arts or 
+      esound stopped, make sure OSS modules unloaded, make sure speakers are 
+      on, check whether the command <tt>cat /dev/urandom > /dev/dsp</tt> 
+      works for root.
+    </p>
+   </sect1>
   </sect>
    <![ %defaulted-2.4 [
 
@@ -3539,19 +3689,26 @@
      Por favor leia <url id="http://wiki.debian.org/Xorg69To7";> para mais 
      detalhes e outras questőes.
    </p>
+   <p>
+     If you experience problems with X.Org after restarting, it might be 
+     also worth to restart the font server by running <tt>/etc/init.d/xfs 
+     restart</tt>. This happens due to <file>/etc/X11/fs/xfs.options</file> 
+     containing a line with <tt>no-restart-on-upgrade</tt>, but the font 
+     paths have changed.
+   </p>
   </sect>
   <sect id="xorg-8bit">
    <heading>
      Muitas aplicaçőes sem suporte para displays de 8bit
    </heading>
    <p>
-     Após a actualizaçăo para Xorg e para as bibliotecas mais recentes, os 
-     terminais de X que apenas possam representar cor com 8bit de 
-     profundidade năo irăo funcionar. Isto deve-se ao facto da biblioteca 
-     Cairo de gráficos vectoriais em 2D (<package>libcairo2</package>) năo 
-     ter suporte para pseudo-cores de 8-bit. Esta biblioteca é utilizada 
-     pelos desktops GNOME e Xfce assim como em muitas aplicaçőes de desktop 
-     compiladas com o toolkit Gtk2+, tal como o <package>abiword</package>.
+     After the upgrade to the X.Org and the latest libraries, X terminals 
+     which can only represent colors 8 bits depth will not work. This is 
+     because the Cairo 2D vector graphics library 
+     (<package>libcairo2</package>) doesn't have 8-bit pseudocolor 
+     support. This library is used by the GNOME and Xfce desktops as well as 
+     by many desktop applications compiled with the Gtk2+ toolkit, such as 
+     <package>abiword</package>.
    </p>
    <p>
      Sistemas que se sabe serem afectados por este problema incluem algumas 
@@ -3874,6 +4031,36 @@
           </example>
    </p>
   </sect>
+  <sect id="motd">
+   <heading>
+     Message of the day
+   </heading>
+   <p>
+     <file>/etc/motd</file> is now a symlink to <file>/var/run/motd</file> 
+     which is rebuilt by <prgn>/etc/init.d/bootmisc.sh</prgn> from a 
+     template, <prgn>/etc/motd.tail</prgn>, at each reboot. It means that 
+     changes made to <file>/etc/motd</file> will be lost. Changes made into 
+     <file>/etc/motd.tail</file> are not automatically applied to 
+     <file>/etc/motd</file> other than at reboot.
+   </p>
+   <p>
+     Also, the EDITMOTD variable at <file>/etc/default/rcS</file> no longer 
+     has any effect. If you wish to disable updating of the motd, or want to 
+     maintain your own content for the message of the day you just have to 
+     point the <file>/etc/motd</file> symlink to a different file such as 
+     <file>/etc/motd.static</file> and make your changes there.
+   </p>
+  </sect>
+  <sect id="no-unicode">
+   <heading>
+     Not default support for unicode in emacs21*
+   </heading>
+   <p>
+     Emacs21 and emacs21-nox are not configured to use Unicode by 
+     default. For more information and a workaround please see <url 
+     id="http://bugs.debian.org/419490"; name="Bug #419490">.
+   </p>
+  </sect>
  </chapt>
  <chapt id="moreinfo">
   <heading>
@@ -3930,16 +4117,18 @@
       Internet Relay Chat (IRC)
     </heading>
     <p>
-      Debian tem um canal de IRC dedicado ao suporte e ajuda aos 
-      utilizadores de Debian localizado na rede de IRC OFTC, que existe para 
-      fornecer serviços interactivos a comunidades com projectos 
-      'peer-directed'. Para aceder ao canal, aponte o seu cliente de IRC 
-      favorito para &debian-irc-server; e junte-se ao #debian.
+      Debian has an IRC channel dedicated to the support and aid of Debian 
+      users located on the OFTC IRC network. To access the channel, point 
+      your favorite IRC client at &debian-irc-server; and join #debian.
+    </p>
+    <p>
+      Please follow the channel guidelines, respecting other users 
+      fully. The guidelines are available at the <url 
+      id="http://wiki.debian.org/DebianIRC"; name="Debian Wiki">.
     </p>
     <p>
-      Por favor siga as linhas de conduta do canal, respeitando os outros 
-      utilizadores. Para mais informaçăo sobre a OFTC visite <url 
-      id="&url-irc-host;"name="website">.
+      For more information on OFTC please visit the <url id="&url-irc-host;" 
+      name="website">.
     </p>
    </sect1>
   </sect>
@@ -3965,11 +4154,11 @@
      necessária informaçăo adicional.
    </p>
    <p>
-     Pode submeter um relatório de erro utilizando o programa 
-     <package>reportbug</package> ou manualmente através do email. Pode ler 
-     mais sobre o Bug Tracking System e como o utilizar lendo os cartőes de 
-     referęncia (disponíveis em <file>/usr/share/doc/debian</file> se tiver 
-     instalado o <package>doc-debian</package>) ou online em <url 
+     You can submit a bug report using the program <prgn>reportbug</prgn> or 
+     manually using email. You can read more about the Bug Tracking System 
+     and how to use it by reading the reference cards (available at 
+     <file>/usr/share/doc/debian</file> if you have 
+     <package>doc-debian</package> installed) or online at the <url 
      id="&url-bts;" name="Bug Tracking System">.
    </p>
   </sect>
Index: ro/release-notes.ro.sgml
===================================================================
RCS file: /cvs/debian-doc/ddp/manuals.sgml/release-notes/ro/release-notes.ro.sgml,v
retrieving revision 1.11
diff -u -r1.11 release-notes.ro.sgml
--- ro/release-notes.ro.sgml	7 Apr 2007 07:23:39 -0000	1.11
+++ ro/release-notes.ro.sgml	1 Sep 2008 17:25:31 -0000
@@ -2,7 +2,7 @@
 
   <!ENTITY % dynamicdata SYSTEM "../en/../dynamic.ent"> %dynamicdata;
   <!ENTITY % shareddata SYSTEM "../en/../release-notes.ent"> %shareddata;
-  <!ENTITY docid "$Id: release-notes.ro.sgml,v 1.11 2007-04-07 07:23:39 fjp Exp $">
+  <!ENTITY docid "$Id: release-notes.en.sgml,v 1.312 2007/08/16 22:24:38 jseidel Exp $">
 ]>
 <debiandoc>
  <book>
@@ -46,12 +46,11 @@
     impactului pe care îl au.
   </p>
   <p>
-    Cea mai recentă versiune a acestui document este întotdeauna disponibilă 
-    la <url id="&url-release-notes;">. Dacă versiunea pe care o citiţi este 
-    mai veche de o lună<footnote><p>versiunea este trecută pe prima pagină a 
-    variantei PDF şi în notele de subsol ale variantei HTML de pe 
-    internet</p></footnote>, probabil veţi prefera să obţineţi ultima 
-    versiune.
+    The most recent version of this document is always available at <url 
+    id="&url-release-notes;">. If the version you are reading is more than a 
+    month old<footnote><p>As listed on the front page of the PDF version and 
+    in the footer of the HTML version.</p></footnote>, you might wish to 
+    obtain the latest version.
   </p>
   <p>
     A se reţine că oferim suport şi documentăm actualizările doar pornind de 
@@ -81,15 +80,16 @@
      Contribuiţi cu rapoarte de actualizare
    </heading>
    <p>
-     Orice informaţii legate de actualizarea de la &oldreleasename; la 
-     &releasename; din partea utilizatorilor sunt binevenite. Dacă doriţi să 
-     oferiţi astfel de informaţii, vă rugăm să trimiteţi un raport de 
-     problemă cu rezultatele dumneavoastră către <url id="&url-bts;" 
-     name="sistemul de raportare a problemelor"> pentru pachetul 
-     <package>upgrade-reports</package>.
+     We welcome any information from users related to upgrades from 
+     &oldreleasename; to &releasename;. If you are willing to share 
+     information please file a bug in the <url id="&url-bts;" name="bug 
+     tracking system"> against the <package>upgrade-reports</package> 
+     package with your results. We request that you compress any attachments 
+     that are included (using <prgn>gzip</prgn>).
    </p>
    <p>
-     Vă rugăm să furnizaţi următoarele informaţii când trimiteţi raportul:
+     Please include the following information when submitting your upgrade 
+     report:
     <list>
      <item>
       <p>
@@ -105,13 +105,14 @@
      </item>
      <item>
       <p>
-        Jurnalele sesiunii, folosind pachetul <package>script</package>, aşa 
-        cum este descris în <ref id="record_session">.
+        Session logs using <prgn>script</prgn>, as described in <ref 
+        id="record_session">.
       </p>
      </item>
      <item>
       <p>
-        Jurnalele lui aptitude, aflate în <file>/var/log/aptitude</file>.
+        Your <prgn>aptitude</prgn> logs, available at 
+        <file>/var/log/aptitude</file>.
       </p>
      </item>
     </list>
@@ -317,6 +318,11 @@
      pentru sub-arhitectura Apple Apus; nu se mai suportă nici 
      sub-arhitectura Apple Nubus.
    </p>
+   <p>
+     Keyboards of iBooks and Powerbooks on &arch-title; are now fully 
+     supported (in X) and (contrary to <tt>&oldreleasename;</tt>) no custom 
+     made xmodmaps are required anymore.
+   </p>
   </sect>
    ]]>
 
@@ -347,13 +353,13 @@
      pentru plăcile video suportate.
    </p>
    <p>
-     &debian; furnizează din nou aplicaţii pentru desktop şi medii pentru 
-     desktop. Printre altele, acum &debian; include mediile de desktop GNOME 
-     2.14<footnote><p>cu unele module din GNOME 2.16</p></footnote>, KDE 
-     3.5.5a şi Xfce4.4. Aplicaţiile de productivitate au fost şi ele 
-     actualizate, inclusiv pachetele de aplicaţii de birou OpenOffice.org 
-     2.0.4a şi KOffice 1.6 cât şi GNUcash 2.0.5, GNUmeric 1.6.3 şi Abiword 
-     2.4.6.
+     &debian; again ships with several desktop applications and 
+     environments. Among others it now includes the desktop environments 
+     GNOME 2.14<footnote><p>With some modules from GNOME 
+     2.16.</p></footnote>, KDE 3.5.5a, and Xfce 4.4. Productivity 
+     applications have also been upgraded, including the office suites 
+     OpenOffice.org 2.0.4a and KOffice 1.6 as well as GNUcash 2.0.5, 
+     GNUmeric 1.6.3 and Abiword 2.4.6.
    </p>
    <p>
      Printre aplicaţiile actualizate se află şi Evolution 2.6.3 şi Gaim 
@@ -380,7 +386,7 @@
      </item>
      <item>
       <p>
-        interpretoare de limbaje: PHP 5.2, Python 2.4
+        language interpreters: Python 2.4, PHP 5.2
       </p>
      </item>
      <item>
@@ -937,11 +943,63 @@
      instalare.
    </p>
    <p>
-     Problema ne-a fost raportată de utilizatori de diverse sisteme (şi 
-     anume Enterprise 450, Blade 2000, Fire V240, Enterprise 250 şi Blade 
-     100 până în momentul redactării acestui text), deci se crede că 
-     problema este generală. Vă rugăm să ne anunţaţi dacă observaţi un 
-     comportament simlar cu hardware-ul dumneavoastră.
+     The problem was reported by users of various systems (namely, 
+     Enterprise 450, Blade 2000, Fire V240, Enterprise 250, Blade 100 and 
+     Enterprise 220R at the time of writing), so it is believed to be 
+     generic. Please let us know if you observe similar issues with your 
+     hardware.
+   </p>
+  </sect>
+  <sect id="sparc_qlogic_firmware">
+   <heading>
+     Issues with booting from qla2xxx on &arch-title;
+   </heading>
+   <p>
+     It has been reported by several users that the installation system 
+     fails to recognize hard disks on machines which have the hard disks 
+     connected to a QLogic fibre-channel SCSI controller. This includes the 
+     Sun Fire 280R servers. The qla2xxx driver loads, but it cannot load 
+     firmware, which makes it useless.
+   </p>
+   <p>
+     The explanation for this problem is that the QLogic controller firmware 
+     is not free, and it had to be moved to a separate non-free package 
+     (<url id="http://packages.debian.org/firmware-qlogic"; 
+     name="firmware-qlogic">) which is not used by the installation system.
+   </p>
+   <p>
+     There is no straightforward solution, unfortunately; one has to first 
+     provide the firmware image to the installation system, and then later 
+     do the same in the installed system. To get the installer to load the 
+     firmware, one has to have network connectivity while the machine is 
+     being installed in order to download the 
+     <package>firmware-qlogic</package> udeb package with wget, install it 
+     with udpkg, and then reload the qla2xxx module. After the installation 
+     is complete, mount the new root partition, chroot to it, fetch the 
+     <package>firmware-qlogic</package> deb package, install it with dpkg, 
+     and then run <prgn>update-initramfs</prgn> in order to include it in 
+     the initial ramdisk image used by the kernel.
+   </p>
+   <p>
+     Alternatively, install from an older installation CD (where that 
+     non-free firmware was still integrated) and then upgrade.
+   </p>
+  </sect>
+  <sect id="solard-used-hd">
+   <heading>
+     Size of harddisk not detected correctly
+   </heading>
+   <p>
+     If a hard disk has previously used under Solaris, the partitioner may 
+     not detect the size of the drive correctly. Creating a new partition 
+     table does not fix this issue. What does help, is to "zero" the first 
+     few sectors of the drive:
+    <example>
+# dd if=/dev/zero of=/dev/hd<var>X</var> bs=512 count=2; sync
+           </example>
+   </p>
+   <p>
+     Note that this will make any existing data on that disk inaccessible.
    </p>
   </sect>
    ]]>
@@ -1298,10 +1356,10 @@
       apărută în mijlocul actualizării poate afecta sever un sistem.
     </p>
     <p>
-      Lucrurile principale pe care veţi dori să le copiaţi sunt conţinutul 
-      lui <file>/etc</file>, <file>/var/lib/dpkg</file> şi rezultatul 
-      rulării <tt>dpkg --get-selections "*"</tt> (ghilimelele sunt 
-      importante).
+      The main things you'll want to back up are the contents of 
+      <file>/etc</file>, <file>/var/lib/dpkg</file>, 
+      <file>/var/lib/aptitude/pkgstates</file> and the output of <tt>dpkg 
+      --get-selections "*"</tt> (the quotes are important).
     </p>
     <p>
       Procesul de actualizare, în sine, nu modifică nimic în directorul 
@@ -1485,14 +1543,14 @@
      Verificarea stării sistemului
    </heading>
    <p>
-     Procesul de actualizare descris în acest capitol a fost conceput pentru 
-     actualizări de la sisteme &oldreleasename; "pure", fără pachete din 
-     terţe surse. În special, se ştie că sunt probleme cu pachete din terţe 
-     surse care instalează programe în <file>/usr/X11R6/bin/</file>, lucru 
-     care cauzează probleme la actualizare datorită tranziţiei X.org (<ref 
-     id="xorg">). Pentru a mări şansele de succes ale procesului de 
-     actualizare, probabil că veţi dori să ştergeţi astfel de pachete din 
-     sistem înainte să începeţi actualizarea.
+     The upgrade process described in this chapter has been designed for 
+     upgrades from "pure" &oldreleasename; systems without third-party 
+     packages. In particular, there are known problems with third-party 
+     packages which install programs under <file>/usr/X11R6/bin/</file> 
+     causing problems with upgrades due to the X.Org transition (<ref 
+     id="xorg">). For greatest reliability of the upgrade process, you may 
+     wish to remove third-party packages from your system before you begin 
+     upgrading.
    </p>
    <p>
      Se pleacă de la presupunerea că aţi actualizat până la ultima versiune 
@@ -1933,6 +1991,12 @@
 Need to get xx.xMB/yyyMB of archives. After unpacking AAAMB will be used.
 Would download/install/remove packages.
        </example>
+      <footnote><p>Running this command at the beginning of the upgrade 
+      process may give an error, for the reasons described in the next 
+      sections. In that case you will need to wait until you've done the 
+      minimal system upgrade as in <ref id="minimal_upgrade"> and upgraded 
+      your kernel as in <ref id="upgrading_kernel"> before running this 
+      command to estimate the disk space. </p></footnote>
     </p>
     <p>
       Dacă nu aveţi spaţiu suficient, asiguraţi-vă că eliberaţi destul 
@@ -2120,8 +2184,8 @@
        Actualizaţi un sistem care nu are suport pentru X instalat
      </heading>
      <p>
-       Pe un sistem fără X, nu ar trebui să fie nevoie de nici o comandă de 
-       instalare suplimentară şi puteţi trece la pasul următor.
+       On a system with no X, no additional <tt>aptitude install</tt> 
+       command should be required, and you can move on to the next step.
      </p>
     </sect2>
    </sect1>
@@ -2280,7 +2344,7 @@
           </example>
       pentru a elimina pachetele problemă, sau
      <example>
-# aptitude --fix-broken install
+# aptitude -f install
 # dpkg --configure --pending
           </example>
     </p>
@@ -2670,12 +2734,12 @@
       iniţializare să poată acţiona.
     </p>
     <p>
-      Simptomele uzuale sunt că iniţializarea va da greş deoarece sistemul 
-      de fişiere rădăcină nu poate fi montat şi sunteţi transferat într-o 
-      consolă de depanare, dar când verificaţi ulterior, toate dispozitivele 
-      necesare sunt prezente în <file>/dev</file>. Aceasta s-a observat în 
-      cazurile în care sistemul de fişiere rădăcină este pe un disk USB sau 
-      RAID.
+      The usual symptoms are that the boot will fail because the root file 
+      system cannot be mounted and you are dropped into a debug shell, but 
+      that when you check afterwards, all devices that are needed are 
+      present in <file>/dev</file>. This has been observed in cases where 
+      the root file system is on a USB disk or on RAID, especially if lilo 
+      is used.
     </p>
     <p>
       O soluţie alternativă pentru această problemă este folosirea 
@@ -2683,6 +2747,19 @@
       pentru limita de timp (în secunde) poate necesita ajustare.
     </p>
    </sect1>
+    ]]><![ %powerpc [
+
+   <sect1 id="pcilynx-broken">
+    <heading>
+      PCILynx FireWire driver is broken
+    </heading>
+    <p>
+      The PCILynx driver is horribly broken and might result in driver 
+      crashes on PowerPC. We encourage users who need FireWire to avail 
+      themselves of one of the cheap OHCI1394 cards and blacklist PCILynx 
+      driver.
+    </p>
+   </sect1>
     ]]>
 
   </sect>
@@ -2759,11 +2836,11 @@
       nu va mai putea fi iniţializat.
     </p>
     <p>
-      Dacă sistemul dumneavoastră foloseşte modulul <tt>lasi700</tt> sau 
-      <tt>zalon7xx</tt> pentru a accesa discurile fixe va trebui să 
-      includeţi acel modul în <file>/etc/initramfs-tools/modules</file> şi 
-      să regeneraţi initrd-ul înainte de reiniţializarea 
-      sistemului. Initrd-ul poate fi regenerat folosind:
+      If your system uses the <tt>lasi700</tt>, <tt>53c700</tt> or 
+      <tt>zalon7xx</tt> module to access your hard disks, you will need to 
+      include that module in <file>/etc/initramfs-tools/modules</file> and 
+      regenerate the initrd before you reboot your system. The initrd can be 
+      regenerated using:
      <example>
 # update-initramfs -u -k all
           </example>
@@ -2951,7 +3028,24 @@
       consultaţi-l în caz că aveţi probleme.
     </p>
    </sect1>
+    <![ %sparc [
+
+   <sect1 id="networkdrivers">
+    <heading>
+      Conflict between tulip and dmfe drivers
+    </heading>
+    <p>
+      On some Netras (e.g. on Netra X1) udev loads both tulip and dmfe 
+      drivers, which claim support for the same PCI IDs (<url 
+      id="http://bugs.debian.org/334104"; name="#334104">). The tulip driver 
+      is correct one for Netra. If this happens, you should blacklist the 
+      dmfe driver and reboot, and/or remove both dmfe and tulip (modprobe 
+      -r) and then modprobe tulip only.
+    </p>
+   </sect1>
   </sect>
+   ]]>
+
   <sect id="for_next">
    <heading>
      Pregătirile pentru următoarea versiune
@@ -2991,8 +3085,10 @@
      </item>
      <item>
       <p>
-        Mutaţi orice valori de configurare a nucleului din 
-        <file>/etc/network/options</file> în <file>/etc/sysctl.conf</file>.
+        Move any configuration options from 
+        <file>/etc/network/options</file> to 
+        <file>/etc/sysctl.conf</file>. Please see 
+        <file>/usr/share/doc/netbase/README.Debian</file> for details.
       </p>
      </item>
      <item>
@@ -3006,6 +3102,48 @@
     </list>
    </p>
   </sect>
+  <sect id="deprecated">
+   <heading>
+     Deprecated packages
+   </heading>
+   <p>
+     With the release of <tt>Lenny</tt> a bigger number of server packages 
+     will be deprecated, thus updating to newer versions of those now will 
+     save you from trouble when updating to <tt>Lenny</tt>.
+   </p>
+   <p>
+     This includes the following packages:
+   </p>
+   <p>
+    <list>
+     <item>
+      <p>
+        apache (1.x), successor is apache2
+      </p>
+     </item>
+     <item>
+      <p>
+        bind8, successor is bind9
+      </p>
+     </item>
+     <item>
+      <p>
+        php4, successor is php5
+      </p>
+     </item>
+     <item>
+      <p>
+        postgresql-7.4, successor is postgresql-8.1
+      </p>
+     </item>
+     <item>
+      <p>
+        exim 3, successor is exim4
+      </p>
+     </item>
+    </list>
+   </p>
+  </sect>
   <sect id="obsolete">
    <heading>
      Pachete depăşite
@@ -3150,13 +3288,21 @@
       Anumite locaţii din reţea nu pot fi contactate prin TCP
     </heading>
     <p>
-      Începând cu versiunea de nucleu 2.6.17, Linux foloseşte într-un mod 
-      agresiv scalarea ferestrelor TCP - detaliată în RFC 1323. Unele 
-      servere au un comportament defectuos şi anunţă, pentru ele însele, 
-      dimensiuni eronate ale ferestrelor TCP. A se vedea rapoartele de erori 
-      <url id="http://bugs.debian.org/381262"; name="nr. 381262"> şi <url 
-      id="http://bugs.debian.org/395066"; name="nr. 395066"> pentru mai multe 
-      informaţii.
+      Since 2.6.17, Linux aggressively uses TCP window scaling which is 
+      specified in RFC 1323. Some servers have a broken behavior, and 
+      announce wrong window sizes for themselves. For more details, please 
+      see the bug reports <url id="http://bugs.debian.org/381262"; 
+      name="#381262">, <url id="http://bugs.debian.org/395066"; 
+      name="#395066">, <url id="http://bugs.debian.org/401435"; 
+      name="#401435">.
+    </p>
+    <p>
+      There are usually two workarounds to these problems: either revert the 
+      maximum allowed TCP window sizes to a smaller value (preferable) or 
+      turn off TCP window scaling altogether (deprecated). See the example 
+      commands in the <url 
+      id="http://www.debian.org/devel/debian-installer/errata"; 
+      name="debian-installer errata page">.
     </p>
    </sect1>
     <![ %i386 [
@@ -3329,6 +3475,20 @@
    </sect1>
     ]]>
 
+   <sect1 id="no-sound">
+    <heading>
+      Sound stops working
+    </heading>
+    <p>
+      In rare cases the sound might stop working after the upgrade. If this 
+      happens, go through the alsa checklist: run <prgn>alsaconf</prgn> as 
+      root user, add your user to the <tt>audio</tt> group, use alsamixer 
+      and make sure levels are up and it is unmuted, make sure arts or 
+      esound stopped, make sure OSS modules unloaded, make sure speakers are 
+      on, check whether the command <tt>cat /dev/urandom > /dev/dsp</tt> 
+      works for root.
+    </p>
+   </sect1>
   </sect>
    <![ %defaulted-2.4 [
 
@@ -3533,19 +3693,26 @@
      Vă rugăm citiţi <url id="http://wiki.debian.org/Xorg69To7";> pentru mai 
      multe detalii şi alte probleme.
    </p>
+   <p>
+     If you experience problems with X.Org after restarting, it might be 
+     also worth to restart the font server by running <tt>/etc/init.d/xfs 
+     restart</tt>. This happens due to <file>/etc/X11/fs/xfs.options</file> 
+     containing a line with <tt>no-restart-on-upgrade</tt>, but the font 
+     paths have changed.
+   </p>
   </sect>
   <sect id="xorg-8bit">
    <heading>
      Lipsa suportului pentru afişare cu 8 biţi în multe aplicaţii
    </heading>
    <p>
-     După actualizarea Xorg la ultimele biblioteci, terminale X care pot 
-     reprezenta doar culori cu o adâncime de 9 biţi, nu vor 
-     funcţiona. Aceasta este din cauză că biblioteca pentru grafică 
-     vectorială Cairo 2D (<package>libcairo2</package>) nu are suport pentru 
-     pseudoculori în 8 biţi. Acestă bibliotecă este folosită de mediile de 
-     birou GNOME şi Xfce precum şi multe aplicaţii de birou compilate cu 
-     trusa de unelte Gtk2+, cum ar fi <package>abiword</package>.
+     After the upgrade to the X.Org and the latest libraries, X terminals 
+     which can only represent colors 8 bits depth will not work. This is 
+     because the Cairo 2D vector graphics library 
+     (<package>libcairo2</package>) doesn't have 8-bit pseudocolor 
+     support. This library is used by the GNOME and Xfce desktops as well as 
+     by many desktop applications compiled with the Gtk2+ toolkit, such as 
+     <package>abiword</package>.
    </p>
    <p>
      Sisteme cunoscute care sunt afectate includ unele calculatoare Sun şi 
@@ -3864,6 +4031,36 @@
           </example>
    </p>
   </sect>
+  <sect id="motd">
+   <heading>
+     Message of the day
+   </heading>
+   <p>
+     <file>/etc/motd</file> is now a symlink to <file>/var/run/motd</file> 
+     which is rebuilt by <prgn>/etc/init.d/bootmisc.sh</prgn> from a 
+     template, <prgn>/etc/motd.tail</prgn>, at each reboot. It means that 
+     changes made to <file>/etc/motd</file> will be lost. Changes made into 
+     <file>/etc/motd.tail</file> are not automatically applied to 
+     <file>/etc/motd</file> other than at reboot.
+   </p>
+   <p>
+     Also, the EDITMOTD variable at <file>/etc/default/rcS</file> no longer 
+     has any effect. If you wish to disable updating of the motd, or want to 
+     maintain your own content for the message of the day you just have to 
+     point the <file>/etc/motd</file> symlink to a different file such as 
+     <file>/etc/motd.static</file> and make your changes there.
+   </p>
+  </sect>
+  <sect id="no-unicode">
+   <heading>
+     Not default support for unicode in emacs21*
+   </heading>
+   <p>
+     Emacs21 and emacs21-nox are not configured to use Unicode by 
+     default. For more information and a workaround please see <url 
+     id="http://bugs.debian.org/419490"; name="Bug #419490">.
+   </p>
+  </sect>
  </chapt>
  <chapt id="moreinfo">
   <heading>
@@ -3918,16 +4115,18 @@
       IRC - Internet Relay Chat
     </heading>
     <p>
-      Debian are un canal IRC dedicat suportului şi ajutorului 
-      utilizatorilor Debian, aflat în reţeaua OFTC IRC, reţea care există 
-      pentru a furniza servicii interactive proiectelor 
-      descentralizate. Pentru a accesa canalul, mergeţi cu clientul IRC 
-      favorit la &debian-irc-server; şi intraţi pe #debian.
+      Debian has an IRC channel dedicated to the support and aid of Debian 
+      users located on the OFTC IRC network. To access the channel, point 
+      your favorite IRC client at &debian-irc-server; and join #debian.
+    </p>
+    <p>
+      Please follow the channel guidelines, respecting other users 
+      fully. The guidelines are available at the <url 
+      id="http://wiki.debian.org/DebianIRC"; name="Debian Wiki">.
     </p>
     <p>
-      Vă rugăm să urmaţi regulile canalului, respectând ceilalţi 
-      utilizatori. Pentru mai multe informaţii despre OFTC, vă rugăm să 
-      vizitaţi <url id="&url-irc-host;" name="situl web">.
+      For more information on OFTC please visit the <url id="&url-irc-host;" 
+      name="website">.
     </p>
    </sect1>
   </sect>
@@ -3954,12 +4153,12 @@
      nevoie de mai multe informaţii şi pentru a putea urmări problemele.
    </p>
    <p>
-     Puteţi trimite un raport de problemă utilizând programul 
-     <package>reportbug</package> sau manual prin poştă electronică. Puteţi 
-     citi mai multe despre sistemul de gestiune al problemelor şi despre cum 
-     să-l utilizaţi la <file>/usr/share/doc/debian</file>, dacă aveţi 
-     <package>doc-debian</package> instalat sau pe internet la <url 
-     id="&url-bts;" name="Sistemul de gestiune al problemelor">.
+     You can submit a bug report using the program <prgn>reportbug</prgn> or 
+     manually using email. You can read more about the Bug Tracking System 
+     and how to use it by reading the reference cards (available at 
+     <file>/usr/share/doc/debian</file> if you have 
+     <package>doc-debian</package> installed) or online at the <url 
+     id="&url-bts;" name="Bug Tracking System">.
    </p>
   </sect>
   <sect id="contributing">
Index: ru/release-notes.ru.sgml
===================================================================
RCS file: /cvs/debian-doc/ddp/manuals.sgml/release-notes/ru/release-notes.ru.sgml,v
retrieving revision 1.11
diff -u -r1.11 release-notes.ru.sgml
--- ru/release-notes.ru.sgml	16 Aug 2007 17:51:45 -0000	1.11
+++ ru/release-notes.ru.sgml	1 Sep 2008 17:25:31 -0000
@@ -2,7 +2,7 @@
 
   <!ENTITY % dynamicdata SYSTEM "../en/../dynamic.ent"> %dynamicdata;
   <!ENTITY % shareddata SYSTEM "../en/../release-notes.ent"> %shareddata;
-  <!ENTITY docid "$Id: release-notes.ru.sgml,v 1.11 2007-08-16 17:51:45 jseidel Exp $">
+  <!ENTITY docid "$Id: release-notes.en.sgml,v 1.312 2007/08/16 22:24:38 jseidel Exp $">
 ]>
 <debiandoc>
  <book>
@@ -3943,11 +3943,11 @@
      <file>/etc/motd</file>, ÜÔĎ ĐŇĎÉÓČĎÄÉÔ ÔĎĚŘËĎ ĐŇÉ ĐĹŇĹÚÁÇŇŐÚËĹ.
    </p>
    <p>
-     ôÁËÖĹ, ĐĹŇĹÍĹÎÎÁŃ EDITMOTD × ĆÁĘĚĹ <file>/etc/default/rcS</file> ÂĎĚŘŰĹ 
-     ÎĹ ŇÁÂĎÔÁĹÔ. ĺÓĚÉ ×Ů ČĎÔÉÔĹ ×ŮËĚŔŢÉÔŘ ĎÂÎĎ×ĚĹÎÉĹ motd ÉĚÉ ÇĎÔĎ×ÉÔŘ 
-     ÓĎĎÂÝĹÎÉĹ ÄÎŃ ÓÁÍĎÓÔĎŃÔĹĚŘÎĎ, ÔĎ ĐŇĎÓÔĎ ÉÚÍĹÎÉÔĹ ÓÉÍ×ĎĚÉŢĹÓËŐŔ ÓÓŮĚËŐ 
-     <file>/etc/motd</file> ÎÁ ÄŇŐÇĎĘ ĆÁĘĚ ×ÍĹÓÔĎ 
-     <file>/etc/motd.static</file> É ÉÚÍĹÎŃĘÔĹ ĹÇĎ ËÁË ČĎÔÉÔĹ.
+     Also, the EDITMOTD variable at <file>/etc/default/rcS</file> no longer 
+     has any effect. If you wish to disable updating of the motd, or want to 
+     maintain your own content for the message of the day you just have to 
+     point the <file>/etc/motd</file> symlink to a different file such as 
+     <file>/etc/motd.static</file> and make your changes there.
    </p>
   </sect>
   <sect id="no-unicode">
Index: sv/release-notes.sv.sgml
===================================================================
RCS file: /cvs/debian-doc/ddp/manuals.sgml/release-notes/sv/release-notes.sv.sgml,v
retrieving revision 1.16
diff -u -r1.16 release-notes.sv.sgml
--- sv/release-notes.sv.sgml	16 Aug 2007 20:01:35 -0000	1.16
+++ sv/release-notes.sv.sgml	1 Sep 2008 17:25:31 -0000
@@ -2,7 +2,7 @@
 
   <!ENTITY % dynamicdata SYSTEM "../en/../dynamic.ent"> %dynamicdata;
   <!ENTITY % shareddata SYSTEM "../en/../release-notes.ent"> %shareddata;
-  <!ENTITY docid "$Id: release-notes.sv.sgml,v 1.16 2007-08-16 20:01:35 jseidel Exp $">
+  <!ENTITY docid "$Id: release-notes.en.sgml,v 1.312 2007/08/16 22:24:38 jseidel Exp $">
 ]>
 <debiandoc>
  <book>
@@ -3999,11 +3999,11 @@
      inte automatiskt pĺ <file>/etc/motd</file> annat än vid omstart.
    </p>
    <p>
-     För övrigt har variabeln EDITMOTD i <file>/etc/default/rcS</file> inte 
-     längre nĺgon effekt. Om du önskar att inaktivera uppdatering av motd, 
-     eller vill underhĺlla dina egna texter för dagens meddelande sĺ kan du 
-     bara peka den symboliska länken <file>/etc/motd</file> till en annan 
-     fil sĺsom <file>/etc/motd.static</file> och göra dina ändringar där.
+     Also, the EDITMOTD variable at <file>/etc/default/rcS</file> no longer 
+     has any effect. If you wish to disable updating of the motd, or want to 
+     maintain your own content for the message of the day you just have to 
+     point the <file>/etc/motd</file> symlink to a different file such as 
+     <file>/etc/motd.static</file> and make your changes there.
    </p>
   </sect>
   <sect id="no-unicode">
Index: zh_TW/release-notes.zh_TW.sgml
===================================================================
RCS file: /cvs/debian-doc/ddp/manuals.sgml/release-notes/zh_TW/release-notes.zh_TW.sgml,v
retrieving revision 1.13
diff -u -r1.13 release-notes.zh_TW.sgml
--- zh_TW/release-notes.zh_TW.sgml	13 Apr 2007 07:26:01 -0000	1.13
+++ zh_TW/release-notes.zh_TW.sgml	1 Sep 2008 17:25:31 -0000
@@ -2,7 +2,7 @@
 
   <!ENTITY % dynamicdata SYSTEM "../en/../dynamic.ent"> %dynamicdata;
   <!ENTITY % shareddata SYSTEM "../en/../release-notes.ent"> %shareddata;
-  <!ENTITY docid "$Id: release-notes.zh_TW.sgml,v 1.13 2007-04-13 07:26:01 jfs Exp $">
+  <!ENTITY docid "$Id: release-notes.en.sgml,v 1.312 2007/08/16 22:24:38 jseidel Exp $">
 ]>
 <debiandoc>
  <book>
@@ -281,6 +281,11 @@
      Apple G5 powermacsĄ^Şş¤ä´ŠĄCšďŠó Apple Apus Ľ­ĽxŞş¤ä´Š¤w¸g¤¤¤îĄAšďŠó 
      Apple Nubus ¤lĽ­Ľx¤]¤ŁŚA¤ä´ŠĄC
    </p>
+   <p>
+     Keyboards of iBooks and Powerbooks on &arch-title; are now fully 
+     supported (in X) and (contrary to <tt>&oldreleasename;</tt>) no custom 
+     made xmodmaps are required anymore.
+   </p>
   </sect>
    ]]>
 
@@ -828,9 +833,63 @@
      ­ŤˇsąŇ°ĘŞşĄAŠŇĽHľLŞk¤~ˇ|Ľżą`°őŚćĄC¸Ń¨M¤čŽ×ŹO§šĽţĽýąNž÷žšŞşšqˇ˝ĂöłŹĄAľMŤáŞ˝ąľĽÎŚw¸ËĽúşĐś}ž÷ĄC
    </p>
    <p>
-     Śł˛łŚh¤ŁŚPŞş¨t˛ÎŞş¨ĎĽÎŞĚŚ^łřšLło­Ó°ÝĂDĄ]şI¤îĽŘŤeŹ°¤îĄAĽ]§t¤F Enterprise 
-     450ĄBBlade 2000ĄBFire V240ĄBEnterprise 250 ¤Î Blade 
-     100Ą^ĄAŠŇĽHłQľřŹ°ą`¨ŁŞş°ÝĂDĄCŚpŞGŚbązŞşž÷žš¤W¤]ľo˛{¤FĂţŚüŞş°ÝĂDĄA˝ĐŞžˇ|§Ú­ĚĄC
+     The problem was reported by users of various systems (namely, 
+     Enterprise 450, Blade 2000, Fire V240, Enterprise 250, Blade 100 and 
+     Enterprise 220R at the time of writing), so it is believed to be 
+     generic. Please let us know if you observe similar issues with your 
+     hardware.
+   </p>
+  </sect>
+  <sect id="sparc_qlogic_firmware">
+   <heading>
+     Issues with booting from qla2xxx on &arch-title;
+   </heading>
+   <p>
+     It has been reported by several users that the installation system 
+     fails to recognize hard disks on machines which have the hard disks 
+     connected to a QLogic fibre-channel SCSI controller. This includes the 
+     Sun Fire 280R servers. The qla2xxx driver loads, but it cannot load 
+     firmware, which makes it useless.
+   </p>
+   <p>
+     The explanation for this problem is that the QLogic controller firmware 
+     is not free, and it had to be moved to a separate non-free package 
+     (<url id="http://packages.debian.org/firmware-qlogic"; 
+     name="firmware-qlogic">) which is not used by the installation system.
+   </p>
+   <p>
+     There is no straightforward solution, unfortunately; one has to first 
+     provide the firmware image to the installation system, and then later 
+     do the same in the installed system. To get the installer to load the 
+     firmware, one has to have network connectivity while the machine is 
+     being installed in order to download the 
+     <package>firmware-qlogic</package> udeb package with wget, install it 
+     with udpkg, and then reload the qla2xxx module. After the installation 
+     is complete, mount the new root partition, chroot to it, fetch the 
+     <package>firmware-qlogic</package> deb package, install it with dpkg, 
+     and then run <prgn>update-initramfs</prgn> in order to include it in 
+     the initial ramdisk image used by the kernel.
+   </p>
+   <p>
+     Alternatively, install from an older installation CD (where that 
+     non-free firmware was still integrated) and then upgrade.
+   </p>
+  </sect>
+  <sect id="solard-used-hd">
+   <heading>
+     Size of harddisk not detected correctly
+   </heading>
+   <p>
+     If a hard disk has previously used under Solaris, the partitioner may 
+     not detect the size of the drive correctly. Creating a new partition 
+     table does not fix this issue. What does help, is to "zero" the first 
+     few sectors of the drive:
+    <example>
+# dd if=/dev/zero of=/dev/hd<var>X</var> bs=512 count=2; sync
+           </example>
+   </p>
+   <p>
+     Note that this will make any existing data on that disk inaccessible.
    </p>
   </sect>
    ]]>
@@ -1107,9 +1166,10 @@
       Śb¤ÉŻĹązŞş¨t˛Î¤§ŤeĄA§Ú­ĚąjŻPŤŘÄłązŻŕśiŚć¤@Ś¸§šžăŞşłĆĽ÷ĄAŠÎŚÜ¤Öąz¤]Ŕł¸Ó§â¨ş¨Çľ´šď¤ŁŻŕĽXĽôŚóŽtżůŞş¸ęŽĆŠMł]Šw¸ę°TľšłĆĽ÷°_¨ÓĄC¤ÉŻĹŽÉŠŇ¨ĎĽÎŞş¤u¨ăŠM¤ÉŻĹšLľ{Ŕł¸Ó¤Łˇ|ĽX¤°ťňŽtżůĄAŚýŚb¤ÉŻĹšLľ{¤¤­YľoĽÍ¤F¤°ťňľwĹéżůť~ĽiŻŕˇ|žÉ­P¨t˛ÎÄY­Ť¨üˇlĄC
     </p>
     <p>
-      ązĽiŻŕˇ|ˇQśiŚćłĆĽ÷Şş¤şŽeĽD­nĽ]ŹA¤F <file>/etc</file> ĽŘżýŠM 
-      <file>/var/lib/dpkg</file> ĽŘżý¤¤Şş¤şŽeĄAĽH¤Î <tt>dpkg 
-      --get-selections "*"</tt>Ą]˝Đ§O§Ń¤FÂů¤Ţ¸šĄ^ŠŇżéĽXŞş¸ę°TĄC
+      The main things you'll want to back up are the contents of 
+      <file>/etc</file>, <file>/var/lib/dpkg</file>, 
+      <file>/var/lib/aptitude/pkgstates</file> and the output of <tt>dpkg 
+      --get-selections "*"</tt> (the quotes are important).
     </p>
     <p>
       ło­Ó¤ÉŻĹŞşľ{§ÇĽŚĽť¨­¨Ă¤Łˇ|­×§ďŚb <file>/home</file> 
@@ -1250,11 +1310,14 @@
      ŔËŹd¨t˛ÎŞşŞŹŞp
    </heading>
    <p>
-     Śbło­Ółš¸`¤¤ŠŇťĄŠúŞş¤ÉŻĹšLľ{ŹOąMŞůŹ°ĄyŻÂşéĄzŞş &oldreleasename; 
-     ŠŇźgŞşĄA¤]´NŹOŚb¨t˛Î¤¤¨SŚłŚw¸ËĽôŚó¨äĽŚ¨ó¤OŽMĽóĄC§óŠú˝TŞşťĄĄA¤wŞžŚbÂŕ´ŤŚÜ 
-     X.org ŽÉ (<ref id="xorg">)ĄA¨ş¨ÇąNľ{ŚĄŚw¸ËŚb 
-     <file>/usr/X11R6/bin/</file> 
-     ¤UŞş¨ó¤OŽMĽóąNˇ|Śb¤ÉŻĹšLľ{¤¤ľoĽÍ°ÝĂDĄCŹ°¤F˝TŤO¤ÉŻĹľ{§ÇŻŕĽ­śśśiŚćĄAąz¤]ł\ˇ|§ĆąćŚb¤ÉŻĹ¤§ŤeĽýąq¨t˛Î¸Ě˛ž°Ł¨ş¨Ç¨ó¤OŽMĽóĄC
+     The upgrade process described in this chapter has been designed for 
+     upgrades from "pure" &oldreleasename; systems without third-party 
+     packages. In particular, there are known problems with third-party 
+     packages which install programs under <file>/usr/X11R6/bin/</file> 
+     causing problems with upgrades due to the X.Org transition (<ref 
+     id="xorg">). For greatest reliability of the upgrade process, you may 
+     wish to remove third-party packages from your system before you begin 
+     upgrading.
    </p>
    <p>
      ŚÓŚbło­ÓšLľ{¤¤¤]°˛ł]ązŞş¨t˛Î¤w§óˇsŚÜ &oldreleasename; 
@@ -1625,6 +1688,12 @@
 Ľ˛śˇ¤U¸ü xx.xMB/yyyMB ŞşŔɎץCŚb¸ŃŔŁÁY¤§ŤáąNˇ|ĽÎąź AAAMBĄC
 ąNˇ|śiŚć ¤U¸ü/Św¸Ë/˛ž°Ł ŽMĽóĄC
        </example>
+      <footnote><p>Running this command at the beginning of the upgrade 
+      process may give an error, for the reasons described in the next 
+      sections. In that case you will need to wait until you've done the 
+      minimal system upgrade as in <ref id="minimal_upgrade"> and upgraded 
+      your kernel as in <ref id="upgrading_kernel"> before running this 
+      command to estimate the disk space. </p></footnote>
     </p>
     <p>
       ŚpŞGąz¨SŚł¨Ź°÷ŞşŞĹśĄĽi¨Ń¤ÉŻĹĄA˝ĐŚb¨ĆĽý´N˛MĽXşĎşĐŞĹśĄĄCązĽiĽHĄG
@@ -1786,8 +1855,8 @@
        ¤ÉŻĹ¨SŚłŚw¸ËĽôŚó X Şş¨t˛Î
      </heading>
      <p>
-       Śb¨SŚł X Şş¨t˛Î¤WĄA´N¨SŚłĽ˛­n°őŚćĽôŚóĂBĽ~Şş aptitude 
-       Św¸ËŤüĽO¤FĄCązĽiĽHŞ˝ąľśiŚć¤U¤@­Ó¨BĆJĄC
+       On a system with no X, no additional <tt>aptitude install</tt> 
+       command should be required, and you can move on to the next step.
      </p>
     </sect2>
    </sect1>
@@ -1917,7 +1986,7 @@
           </example>
       ¨Ó˛M°Ł¤@¨Çˇ|łyŚ¨°ÝĂDŞşŽMĽóĄAŠÎ
      <example>
-# aptitude --fix-broken install
+# aptitude -f install
 # dpkg --configure --pending
           </example>
     </p>
@@ -2253,16 +2322,31 @@
       ŤŘĽß¸Ë¸mŔÉŞşŽÉž÷¤ńś}ž÷ scripts Şş°Ę§@ÁŮşCĄC
     </p>
     <p>
-      ¤@ŻëŚÓ¨ĽĄAľLŞkĽżą`ś}ž÷Şş­ěŚ]ŚhŹOŚ]Ź°ľLŞkąž¸ü root 
-      ŔɎרt˛ÎĄAľMŤáązˇ|śi¤J¤@­Ó°Łżů¤ś­ąĄAŚýˇíązŚbľyŤáŚAśiŚćŔËŹdŽÉĄAŤoľo˛{ŠŇŚłĽ˛­nŞş¸Ë¸młŁ¤wĽX˛{Šó 
-      <file>/dev</file> ¤şĄCłoşŘąĄŞpˇ|ľoĽÍŚb root ŔɎרt˛ÎŹOŠńŚb USB ¸Ë¸mŠÎ 
-      RAID ¤WŽÉĄC
+      The usual symptoms are that the boot will fail because the root file 
+      system cannot be mounted and you are dropped into a debug shell, but 
+      that when you check afterwards, all devices that are needed are 
+      present in <file>/dev</file>. This has been observed in cases where 
+      the root file system is on a USB disk or on RAID, especially if lilo 
+      is used.
     </p>
     <p>
       ­nÁל}ło­Ó°ÝĂDŞş¤čŞkŹO¨ĎĽÎ <tt>rootdelay=<var>9</var></tt> 
       ś}ž÷°ŃźĆĄC¨ä¤¤ŞşŹíźĆĽiŻŕąoŚAĽ[ĽH˝Őžă¤~ŚćĄC
     </p>
    </sect1>
+    ]]><![ %powerpc [
+
+   <sect1 id="pcilynx-broken">
+    <heading>
+      PCILynx FireWire driver is broken
+    </heading>
+    <p>
+      The PCILynx driver is horribly broken and might result in driver 
+      crashes on PowerPC. We encourage users who need FireWire to avail 
+      themselves of one of the cheap OHCI1394 cards and blacklist PCILynx 
+      driver.
+    </p>
+   </sect1>
     ]]>
 
   </sect>
@@ -2332,10 +2416,11 @@
       initrd ¤¤ĄAązŞş¨t˛ÎĽiŻŕˇ|ľLŞkś}ž÷ĄC
     </p>
     <p>
-      ŚpŞGązŞş¨t˛ÎŹOÂÇĽŃ <tt>lasi700</tt> ŠÎ <tt>zalon7xx</tt> 
-      źŇ˛Ő¨ÓŚs¨úązŞşľwşĐĄAŚbąz­ŤˇsąŇ°ĘązŞş¨t˛Î¤§ŤeĄAązĽ˛śˇ§â¸ÓźŇ˛ŐŠń¤J 
-      <file>/etc/initramfs-tools/modules</file> ¨Ă­Ťˇs˛ŁĽÍ initrdĄCŚÓ initrd 
-      ĽiĽH§QĽÎĽH¤UŤüĽO­Ťˇs˛ŁĽÍĄG
+      If your system uses the <tt>lasi700</tt>, <tt>53c700</tt> or 
+      <tt>zalon7xx</tt> module to access your hard disks, you will need to 
+      include that module in <file>/etc/initramfs-tools/modules</file> and 
+      regenerate the initrd before you reboot your system. The initrd can be 
+      regenerated using:
      <example>
 # update-initramfs -u -k all
           </example>
@@ -2507,7 +2592,24 @@
       ¨úąoĄA­YžDšJĽôŚó°ÝĂD˝Đ¤Ł§Ť°Ńž\ĄC
     </p>
    </sect1>
+    <![ %sparc [
+
+   <sect1 id="networkdrivers">
+    <heading>
+      Conflict between tulip and dmfe drivers
+    </heading>
+    <p>
+      On some Netras (e.g. on Netra X1) udev loads both tulip and dmfe 
+      drivers, which claim support for the same PCI IDs (<url 
+      id="http://bugs.debian.org/334104"; name="#334104">). The tulip driver 
+      is correct one for Netra. If this happens, you should blacklist the 
+      dmfe driver and reboot, and/or remove both dmfe and tulip (modprobe 
+      -r) and then modprobe tulip only.
+    </p>
+   </sect1>
   </sect>
+   ]]>
+
   <sect id="for_next">
    <heading>
      ´Ŕ¤U¤@­ÓÄŔĽXŞŠĽťśiŚćˇÇłĆ
@@ -2544,8 +2646,10 @@
      </item>
      <item>
       <p>
-        ąNĽôŚóŚb <file>/etc/network/options</file> ¸ĚŞş kernel ł]Šw­Č˛žŚÜ 
-        <file>/etc/sysctl.conf</file>ĄC
+        Move any configuration options from 
+        <file>/etc/network/options</file> to 
+        <file>/etc/sysctl.conf</file>. Please see 
+        <file>/usr/share/doc/netbase/README.Debian</file> for details.
       </p>
      </item>
      <item>
@@ -2558,6 +2662,48 @@
     </list>
    </p>
   </sect>
+  <sect id="deprecated">
+   <heading>
+     Deprecated packages
+   </heading>
+   <p>
+     With the release of <tt>Lenny</tt> a bigger number of server packages 
+     will be deprecated, thus updating to newer versions of those now will 
+     save you from trouble when updating to <tt>Lenny</tt>.
+   </p>
+   <p>
+     This includes the following packages:
+   </p>
+   <p>
+    <list>
+     <item>
+      <p>
+        apache (1.x), successor is apache2
+      </p>
+     </item>
+     <item>
+      <p>
+        bind8, successor is bind9
+      </p>
+     </item>
+     <item>
+      <p>
+        php4, successor is php5
+      </p>
+     </item>
+     <item>
+      <p>
+        postgresql-7.4, successor is postgresql-8.1
+      </p>
+     </item>
+     <item>
+      <p>
+        exim 3, successor is exim4
+      </p>
+     </item>
+    </list>
+   </p>
+  </sect>
   <sect id="obsolete">
    <heading>
      łQźoąóŞşŽMĽó
@@ -2839,6 +2985,20 @@
    </sect1>
     ]]>
 
+   <sect1 id="no-sound">
+    <heading>
+      Sound stops working
+    </heading>
+    <p>
+      In rare cases the sound might stop working after the upgrade. If this 
+      happens, go through the alsa checklist: run <prgn>alsaconf</prgn> as 
+      root user, add your user to the <tt>audio</tt> group, use alsamixer 
+      and make sure levels are up and it is unmuted, make sure arts or 
+      esound stopped, make sure OSS modules unloaded, make sure speakers are 
+      on, check whether the command <tt>cat /dev/urandom > /dev/dsp</tt> 
+      works for root.
+    </p>
+   </sect1>
   </sect>
    <![ %defaulted-2.4 [
 
@@ -3019,17 +3179,26 @@
      ˝Đ°Ńž\ <url id="http://wiki.debian.org/Xorg69To7";> 
      ĽH¨úąo§óŚh¸ÔşÉ¸ę°T¤Î¨äĽŚŞş°ÝĂDĄC
    </p>
+   <p>
+     If you experience problems with X.Org after restarting, it might be 
+     also worth to restart the font server by running <tt>/etc/init.d/xfs 
+     restart</tt>. This happens due to <file>/etc/X11/fs/xfs.options</file> 
+     containing a line with <tt>no-restart-on-upgrade</tt>, but the font 
+     paths have changed.
+   </p>
   </sect>
   <sect id="xorg-8bit">
    <heading>
      ŚbŤÜŚhŔłĽÎľ{ŚĄ¤W¨Ă¤Ł¤ä´ŠĽH 8-bit ĹăĽÜ
    </heading>
    <p>
-     Śb§óˇsŚÜ Xorg ¤ÎłĚˇsŞş¨çŚĄŽwŤáĄAĽuŻŕĽH 8-bit Śâ˛`¨ÓĹăĽÜŞş X 
-     ˛×şÝž÷ąNˇ|ľLŞkšB§@ĄCłoŹOŚ]Ź° Cairo 2D ŚVśqšĎ§Î¨çŚĄŽw 
-     (<package>libcairo2</package>) ¨Ă¤Ł¤ä´Š 8-bit ŞşľęŔŔŚâąmĄCGNOME ¤Î Xfce 
-     Žŕ­ąĽH¤ÎŤÜŚh¨ĎĽÎ Gtk2+ ¤u¨ăĽ]˝sÄśŞşŽŕ­ąŔłĽÎľ{ŚĄĄAšłŹO 
-     <package>abiword</package>ĄAłŁˇ|ĽÎ¨ěło­Ó¨çŚĄŽwĄC
+     After the upgrade to the X.Org and the latest libraries, X terminals 
+     which can only represent colors 8 bits depth will not work. This is 
+     because the Cairo 2D vector graphics library 
+     (<package>libcairo2</package>) doesn't have 8-bit pseudocolor 
+     support. This library is used by the GNOME and Xfce desktops as well as 
+     by many desktop applications compiled with the Gtk2+ toolkit, such as 
+     <package>abiword</package>.
    </p>
    <p>
      ˇ|źvĹT¨ěŞş¨t˛Î¤wŞžĽ]ŹA¤F¤@¨Ç Sun ĽDž÷¤Î TektronixĄBNCDĄBIBM ¤Î SGI Şş X 
@@ -3310,6 +3479,36 @@
           </example>
    </p>
   </sect>
+  <sect id="motd">
+   <heading>
+     Message of the day
+   </heading>
+   <p>
+     <file>/etc/motd</file> is now a symlink to <file>/var/run/motd</file> 
+     which is rebuilt by <prgn>/etc/init.d/bootmisc.sh</prgn> from a 
+     template, <prgn>/etc/motd.tail</prgn>, at each reboot. It means that 
+     changes made to <file>/etc/motd</file> will be lost. Changes made into 
+     <file>/etc/motd.tail</file> are not automatically applied to 
+     <file>/etc/motd</file> other than at reboot.
+   </p>
+   <p>
+     Also, the EDITMOTD variable at <file>/etc/default/rcS</file> no longer 
+     has any effect. If you wish to disable updating of the motd, or want to 
+     maintain your own content for the message of the day you just have to 
+     point the <file>/etc/motd</file> symlink to a different file such as 
+     <file>/etc/motd.static</file> and make your changes there.
+   </p>
+  </sect>
+  <sect id="no-unicode">
+   <heading>
+     Not default support for unicode in emacs21*
+   </heading>
+   <p>
+     Emacs21 and emacs21-nox are not configured to use Unicode by 
+     default. For more information and a workaround please see <url 
+     id="http://bugs.debian.org/419490"; name="Bug #419490">.
+   </p>
+  </sect>
  </chapt>
  <chapt id="moreinfo">
   <heading>
@@ -3359,15 +3558,18 @@
       IRC(Internet Relay Chat) şô¸ô˛á¤ŃŤÇ
     </heading>
     <p>
-      OFTC IRC 
-      şô¸ôĽD­nŞşĽŘŞş´NŹOŚVŚPžŤžÉŚVŞşąMŽ×ŞŔ¸s´Ł¨Ń¤Ź°ĘŚĄŞşŞA°ČĄCŚb¨ş¸Ě Debian 
-      Śł¤@­Ó IRC ŔWšDŹOąMŞůĽÎ¨Ó¤ä´Š¨ĂŔ°§U Debian 
-      Şş¨ĎĽÎŞĚŞşĄCązĽu­n§âązşDĽÎŞş IRC ŤČ¤áşÝľ{ŚĄŤüŚV &opn-irc-server; 
-      ¨ĂĽ[¤J #debian ´NĽiĽHłs¤Wło­ÓŔWšD¤FĄC
+      Debian has an IRC channel dedicated to the support and aid of Debian 
+      users located on the OFTC IRC network. To access the channel, point 
+      your favorite IRC client at &debian-irc-server; and join #debian.
+    </p>
+    <p>
+      Please follow the channel guidelines, respecting other users 
+      fully. The guidelines are available at the <url 
+      id="http://wiki.debian.org/DebianIRC"; name="Debian Wiki">.
     </p>
     <p>
-      ˝Đżí´`¸ÓŔWšDŞşłWŠwĄA¨Ă´L­Ť˝u¤W¨äĽLŞş¨ĎĽÎŞĚĄCązĽiĽHŚb <url 
-      id="&url-irc-host;" name="website"> ¤W¨úąo§óŚh OFTC ŞşŹŰĂö¸ę°TĄC
+      For more information on OFTC please visit the <url id="&url-irc-host;" 
+      name="website">.
     </p>
    </sect1>
   </sect>
@@ -3387,12 +3589,12 @@
      ŚpŞGązŚb§Ú­ĚŞş¨t˛ÎľoŚćŠÎ¨ä¤¤ŞşŽMĽó¤¤ľo˛{¤FĽôŚó°ÝĂDĄA˝ĐŚV§Ú­ĚŚ^łřĄAłoźË§Ú­Ě¤~ŻŕŚb¤éŤáŞşľoŚćŞŠ¤¤ąNĽŚ­×´_ĄCązťÝ­nžÖŚł¤@­ÓĽż˝TŞşšq¤lślĽóŤH˝c¤~Żŕ°÷Ś^łř°ÝĂDĄAˇ|Śłło­Ó­­¨îŹOŚ]Ź°łoźË§Ú­Ě¤~ŻŕÂÇŚš°lÂÜżůť~łř§iŞşśiŽiĄAŚÓˇíś}ľo¤H­űťÝ­n§óŚh¸ę°TŞşŽÉ­Ô¤]¤~ŻŕŠM­ě°ÝĂDłř§iŞĚ¨úąołsĂ´ĄC
    </p>
    <p>
-     ązĽiĽHÂÇĽŃ <package>reportbug</package> 
-     ľ{ŚĄŠÎŹOŚŰŚć¨ĎĽÎšq¤lślĽó¨ÓśiŚćŚ^łřżůť~ĄAązĽiĽHž\ĹŞ°ŃŚŇĽd¤ůĄ]ŚpŞGązŚłŚw¸Ë 
-     <package>doc-debian</package> Şş¸ÜĄAĽiĽHŚb 
-     <file>/usr/share/doc/debian</file> ¸Ě§ä¨ěĄ^ŠÎ¨ě <url id="&url-bts;" 
-     name="żůť~°lÂܨt˛Î"> 
-     Şş˝u¤Wşô­ś¨úąo§óŚhŚpŚó¨ĎĽÎżůť~°lÂܨt˛Î¤Î¨äĽŚŞşŹŰĂö¸ę°TĄC
+     You can submit a bug report using the program <prgn>reportbug</prgn> or 
+     manually using email. You can read more about the Bug Tracking System 
+     and how to use it by reading the reference cards (available at 
+     <file>/usr/share/doc/debian</file> if you have 
+     <package>doc-debian</package> installed) or online at the <url 
+     id="&url-bts;" name="Bug Tracking System">.
    </p>
   </sect>
   <sect id="contributing">

Reply to: