path: root/polish/CD/releases/index.wml

#use wml::debian::cdimage title="Informacje wydania obrazów płyt Debian" BARETITLE=true
#use wml::debian::translation-check translation="981a8578736a09678fc193cac33fe0f2ff036381"

<p>Ta strona zawiera historyczne informacje <q>z ostatniej chwili</q>
odnoszące się do obrazów płyt Debiana.</p>


<p>Informacje nt. problemów związanych z instalacją dla wydań następujących
po wymienionych poniżej są dostępne na stronie <q>informacji o instalacji</q>
dla każdego wydania. Dla bieżącego wydania stabilnego są one dostępne
<a href="$(HOME)/releases/stable/debian-installer/">tutaj</a>.</p>

<p>
<strong>Poniższa lista nie będzie już aktualizowana.</strong>
</p>

<hrline />

<dl>
# ------------------------------------------------------------
  <release-notes title="Oficjalny Debian 4.0 rev2" version="4.0 rev2">
    <p>Brak znanych problemów.</p>
  </release-notes>

# ------------------------------------------------------------
  <release-notes title="Oficjalny Debian 4.0 rev1" version="4.0 rev1">
    <p>Brak znanych problemów.</p>
  </release-notes>

# ------------------------------------------------------------
  <release-notes title="Oficjalny Debian 4.0 rev0" version="4.0 rev0">
    <p>Jeśli instalacja jest przeprowadzana z płyty i wybrano również
    serwer lustrzany do pobierania pakietów z sieci, istnieje możliwość,
    że po instalacji wpisy w pliku <tt>/etc/apt/sources.list</tt>
    będą odnosić się do <q>sarge</q>, zamiast do <q>etch</q>.<br />
    Może to się zdarzyć tylko w przypadku, jeśli wybrany serwer
    zawiera nie uaktualnione dane i wskazuje sarge jako wydanie
    stabilne. Użytkownicy instalujący etch z płyt wkrótce po ukazaniu
    się wydania powinni sprawdzić zawartość pliku <tt>sources.list</tt>
    i zastąpić wpisy <q>sarge</q> na <q>etch</q>.</p>
  </release-notes>

  <dt><strong>Starsze uwagi:</strong></dt>
  <dd><p>Poniższe uwagi są dostępne tylko w języku angielskim.</p></dd>

# ------------------------------------------------------------
  <release-notes title="Official Debian 3.1 rev6a" version="3.1 rev6a">
    <p>No known problems.</p>
  </release-notes>

# ------------------------------------------------------------
  <release-notes title="Official Debian 3.1 rev6" version="3.1 rev6">
    <p>A bug was discovered in the 3.1r6 installation CD/DVD images:
    installations would fail immediately due to a missing <q>oldstable</q>
    symbolic link. However, the update CD/DVD images work correctly.</p>
    <p>This issue was resolved in the 3.1r6a images.</p>
  </release-notes>

# ------------------------------------------------------------
  <release-notes title="Official Debian 3.1 rev5" version="3.1 rev5">

    <p>During installations for the architectures i386, hppa, ia64 and
    s390, the installer may select an incorrect kernel for your system.<br />
    You can work around this issue by booting the installer with the parameter
    <tt>debconf/priority=medium</tt>. This will result in a full list of
    available kernels being shown, from which you can manually select the flavor
    that is appropriate for your system.</p>

    <p>Apologies for any inconvenience this may cause; we expect to fix
    this issue for r6.</p>

  </release-notes>

# ------------------------------------------------------------
  <release-notes title="Official Debian 3.1 rev4" version="3.1 rev4">
    <p>No known problems.</p>
  </release-notes>

# ------------------------------------------------------------
  <release-notes title="Official Debian 3.1 rev3" version="3.1 rev3">

    <p>CD#1 contains extra files that should have been deleted, but
    were missed when releasing 3.1r3. This causes two problems:</p>

    <ul>
      <li>The kernel installed using these images will, in some cases,
      not be the latest kernel on the CD, but rather the previous
      version. Update the kernel specifically after installation and
      all should be fine.</li>

      <li>As the extra files on CD#1 take up extra space, some of the
      normal installation tasks will no longer fit there. If you want
      to install all the tasks from CD only, you will need to use CD#2
      as well.</li>
    </ul>

    <p>Apologies for any hassle this may cause; we expect to fix this
    issue for r4. DVD images and network installs should not be
    affected.</p>

  </release-notes>

# ------------------------------------------------------------
  <release-notes title="Official Debian 3.1 rev2" version="3.1 rev2">
    <p>No known problems.</p>
  </release-notes>

# ------------------------------------------------------------
  <release-notes title="Official Debian 3.1 rev1" version="3.1 rev1">
    <p>No known problems.</p>
  </release-notes>

# ------------------------------------------------------------
  <release-notes title="Official Debian 3.1 rev0a" version="3.1 rev0a">
    <p>The CD's README states that the CD is an unofficial beta. The
    README is wrong, it <em>is</em> the official CD release. Sorry for
    the confusion.</p>
  </release-notes>

# ------------------------------------------------------------
  <release-notes title="Official Debian 3.1 rev0" version="3.1 rev0">
    <p>Installations from these images will
    <a href="https://lists.debian.org/debian-devel-announce/2005/06/msg00003.html">
    install an incorrect line for security updates in
    /etc/apt/sources.list</a>.</p>
  </release-notes>

# ------------------------------------------------------------
  <release-notes title="Official Debian 3.0 rev6" version="3.0 rev6">
    <p>No known problems.</p>
  </release-notes>

# ------------------------------------------------------------
  <release-notes title="Official Debian 3.0 rev5" version="3.0 rev5">
    <p>No known problems.</p>
  </release-notes>

# ------------------------------------------------------------
  <release-notes title="Official Debian 3.0 rev4" version="3.0 rev4">
    <p>No known problems.</p>
  </release-notes>

# ------------------------------------------------------------
  <release-notes title="Official Debian 3.0 rev3" version="3.0 rev3">
    <p>No known problems.</p>
  </release-notes>

# ------------------------------------------------------------
  <release-notes title="Official Debian 3.0 rev2" version="3.0 rev2">
    <p>No known problems.</p>
  </release-notes>

# ------------------------------------------------------------
  <release-notes title="Official Debian 3.0 rev1" version="3.0 rev1">
    <p>No known problems.</p>
  </release-notes>

# ------------------------------------------------------------
  <release-notes title="Official Debian 3.0 rev0" version="3.0 rev0">
    <p>The CD's README states that the CD is an unofficial beta. The
    README is wrong, it <em>is</em> the official CD release. Sorry for
    the confusion.</p>
  </release-notes>

# ------------------------------------------------------------
  <release-notes title="Official Debian 2.2 rev7" version="2.2 rev7">
    <p>No known problems.</p>
  </release-notes>

# ------------------------------------------------------------
  <release-notes title="Official Debian 2.2 rev6" version="2.2 rev6">
    <p>No known problems.</p>
  </release-notes>

# ------------------------------------------------------------
  <release-notes title="Official Debian 2.2 rev5" version="2.2 rev5">
    <p>No known problems.</p>
  </release-notes>

# ------------------------------------------------------------
  <dt><strong>Official Debian 2.2 rev4 and rev4.1</strong></dt>
    <dd>\
    <p>The original 2.2rev4 CDs for the powerpc architecture
    were not bootable. They were regenerated - the resulting
    2.2rev4.1 release does not differ from 2.2rev4 except on
    powerpc.</p>\
    </dd>
# ------------------------------------------------------------
  <dt><strong>Official Debian 2.2 rev3</strong></dt>
    <dd>
    <p>Toshiba laptops are reported to have problems booting off the CDs
    because their BIOS
    <a href="https://lists.debian.org/debian-devel-0104/msg01326.html">cannot
    handle</a> 2.88MB boot images. The easiest way to start installing
    Debian on these machines is by running <tt>boot.bat</tt> from the
    <tt>install/</tt> directory of the Binary-1 CD.</p>

    <p>Not all packages from section <q>contrib</q> are included on the CDs,
    since they depend on non-free packages that are also not on the CDs.</p>

    <p>The problems with the <tt>gpm</tt> text-mode mouse driver have still
    not been resolved. See in the <q>2.2 rev0</q> section below for more
    info.</p>

  </dd>
# ------------------------------------------------------------

  <dt><strong>Official Debian 2.2 rev2</strong></dt>
  <dd>
    <p>Not all packages from section <q>contrib</q> are included on
    the CDs, since they depend on non-free packages that are
    also not on the CDs.</p>

    <p>The problems with the <tt>gpm</tt> text-mode mouse
    driver have still not been resolved. See in the <q>2.2 rev0</q>
    section below for more info.</p>
  </dd>
# ------------------------------------------------------------

  <dt><strong>Official Debian 2.2 rev1</strong></dt>
  <dd><p>No CD images were created for the 2.2 rev1
  release.</p></dd>
# ------------------------------------------------------------

  <dt><strong>Official Debian 2.2 rev0</strong></dt>
    <dd>
    <p>Not all packages from section <q>contrib</q> are included on the CDs,
    since they depend on non-free packages that are also not on the CDs.</p>

    <p><strong>i386</strong>: There are some issues with the <tt>gpm</tt>
    text-mode mouse driver while running the X Window System. The easiest
    solution is to remove the line
    <tt>repeat_type=<em>&lt;something&gt;</em></tt> from
    <tt>/etc/gpm.conf</tt>, running <q><tt>/etc/init.d/gpm&nbsp;restart</tt></q>
    and then restart X.  Other solutions are possible, ask the
    <a href="mailto:gpm@packages.debian.org">gpm maintainer</a> to supply
    more documentation.</p>

    <p><strong>i386</strong>: The previously available Binary-2 CD image had
    a one-bit problem that prevented the package <q><tt>pdksh</tt></q> from being
    installed. Repairing your own image is very easy with the 
    <a href="https://cdimage.debian.org/~costar/correct_cds/correct-i386-2.c">correct-i386-2.c</a>
    program.</p>

    <p>Thanks to <a href="mailto:kteague@sprocket.dhis.net">Ken Teague</a>
    we also have a precompiled 
    <a href="https://cdimage.debian.org/~costar/correct_cds/correct-i386-2.zip">Windows
    version</a>; usage: extract the <tt>.zip</tt> in the dir where the
    <tt>binary-i386-2.iso</tt> file is sitting, then in a DOS box change to
    that directory and give the command <q><tt>correct-i386-2
    binary-i386-2.iso</tt></q>.</p>

    <p>If you have a CD-ROM, which you obviously cannot repair, the easiest
    option to get <tt>pdksh</tt> is to 
    <a href="http://ftp.debian.org/debian/dists/potato/main/binary-i386/shells/pdksh_5.2.14-1.deb">download
    it</a> (212 kB) and install with <q><tt>dpkg -i pdksh_5.2.14-1.deb</tt></q>. 
    But you can also copy the file from the CD to a temporary directory and
    use the same 
    <a href="https://cdimage.debian.org/~costar/correct_cds/correct-i386-2.c">correct-i386-2.c</a>
    program, but then you should modify it so that <tt>POS</tt> is
    <tt>0x64de</tt>.</p>

    <p><strong>PowerPC</strong>: The powerpc Binary-1_NONUS and Binary-3 CD
    images are also plagued by a one-bit problem, preventing
    <q><tt>smbfs</tt></q> and <q><tt>gimp-manual</tt></q> respectively from being
    installed. Repaired versions are (slowly) propagating to the mirrors,
    but you can repair your own images very easily with the 
    <a href="https://cdimage.debian.org/~costar/correct_cds/correct-powerpc-1_NONUS.c">correct-powerpc-1_NONUS.c</a>
    and 
    <a href="https://cdimage.debian.org/~costar/correct_cds/correct-powerpc-3.c">correct-powerpc-3.c</a>
    programs. These also contain information on repairing the affected
    packages individually when copied from CD (which is especially useful
    for the 15MB-sized <q><tt>gimp-manual</tt></q>).</p>

    <p><strong>Sparc</strong>: The 2.2 rev0 CDs have a problem when booting
    from the Binary-1 CD. This has been solved in the 2.2 rev0a (or
    2.2_rev0_CDa) version of the sparc CDs.</p>

    <p>Sparc: If X does not start correctly, and the error message mentions
    the mouse, and you are <em>not</em> running the <tt>gpm</tt> text-mode
    mouse driver, <q><tt>rm -f /dev/gpmdata</tt></q> might help.</p>

    <p><strong>Alpha</strong>: The 2.2 rev0 CDs may prove problematic when
    booting from the Binary-1 CD. To solve that, boot with <q><tt>-flags
    i</tt></q>, then enter at the aboot prompt:
    <br />
      <tt>&nbsp;&nbsp;&nbsp;&nbsp;aboot&gt; b /linux
      initrd=/boot/root.bin root=/dev/ram</tt>
    <br />
    This problem has been corrected in the 2.2 rev0a (or 2.2_rev0_CDa)
    version of the alpha CDs.</p>
  </dd>
# ------------------------------------------------------------

  <dt><strong>Potato test-cycle-3</strong></dt>
    <dd><p>The <tt>gpm</tt> text-mode mouse driver has some problems. You
    should <strong>not</strong> run the <tt>mouse-test</tt> program, and you
    will have to do <q><tt>/etc/init.d/gpm&nbsp;stop</tt></q> before you can use
    the mouse in X.</p></dd>
# ------------------------------------------------------------

  <dt><strong>Potato test-cycle-2</strong></dt>
    <dd><p>The <tt>gpm</tt> text-mode mouse driver has some problems. You
    should <strong>not</strong> run the <tt>mouse-test</tt> program, and you
    will have to do <q><tt>/etc/init.d/gpm&nbsp;stop</tt></q> before you can use
    the mouse in X.</p></dd>
# ------------------------------------------------------------

  <dt><strong>Potato test-cycle-1</strong></dt>
    <dd><p>No relevant information</p></dd>

</dl>