/[ddp]/manuals/trunk/release-notes/en/release-notes.en.sgml
ViewVC logotype

Diff of /manuals/trunk/release-notes/en/release-notes.en.sgml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 2627 by robster, Thu Oct 7 16:04:25 2004 UTC revision 2628 by jfs, Sun Oct 31 23:13:21 2004 UTC
# Line 1  Line 1 
1  <!DOCTYPE debiandoc PUBLIC "-//DebianDoc//DTD DebianDoc//EN" [  <!DOCTYPE debiandoc PUBLIC "-//DebianDoc//DTD DebianDoc//EN" [
2    <!entity % dynamicdata  SYSTEM "../dynamic.ent"       > %dynamicdata;    <!entity % dynamicdata  SYSTEM "../dynamic.ent"       > %dynamicdata;
3    <!entity % shareddata   SYSTEM "../release-notes.ent" > %shareddata;    <!entity % shareddata   SYSTEM "../release-notes.ent" > %shareddata;
4    <!entity docid "$Id: release-notes.en.sgml,v 1.3 2004-10-07 16:04:25 robster Exp $">    <!entity docid "$Id: release-notes.en.sgml,v 1.4 2004-10-31 23:13:21 jfs Exp $">
5  ]>  ]>
6    
7  <debiandoc>  <debiandoc>
# Line 81  Line 81 
81  <![ %available-2.6 [  <![ %available-2.6 [
82    
83            <p>On the &arch-title; architecture a 2.6 kernel is also available,            <p>On the &arch-title; architecture a 2.6 kernel is also available,
84            this has kernel version &kernelversion-2.6;.</p>            this has kernel version &kernelversion-2.6;. Note that Debian's 2.6.8
85              kernel packages include the 2.6.8.1 kernel release and selected other
86              patches.</p>
87  ]]>  ]]>
88    
89          <sect id="newinst"><heading>What's New in the Installation System?</heading>          <sect id="newinst"><heading>What's New in the Installation System?</heading>
# Line 100  Line 102 
102    
103            <p>For full details of the new Debian installation system, users            <p>For full details of the new Debian installation system, users
104            are advised to read the Debian installation guide included on the            are advised to read the Debian installation guide included on the
105            first CD or at <url id="&url-install-manual;"></p>            first CD or at <url id="&url-install-manual;">.</p>
106    
107  <![ %i386 [  <![ %i386 [
108    
# Line 126  Line 128 
128                disk image.<p></item>                disk image.<p></item>
129    
130              </taglist>              </taglist>
131    <!-- FJP: I feel the info about floppies should be removed from this table as
132              floppies are no longer the most used installation method. -->
133    
134            <p>The kernel config files for these flavors can be found in their            <p>The kernel config files for these flavors can be found in their
135            respective directories in a file named 'kernel-config'.</p>            respective directories in a file named 'kernel-config'.</p>
136    
137  ]]>  ]]>
138    
139    <!-- FJP: Maybe a short description of available installation methods could be
140              added here: floppy, CD (netinst/business-card/full set), netboot,
141              hd-media, USB-stick. -->
142    
143  <![ %available-2.6 [  <![ %available-2.6 [
144            <p>An installer using a 2.6 based kernel is available for            <p>An installer using a 2.6 based kernel is available for
145            &arch-title;. For more details on how to use it please consult the            &arch-title;. For more details on how to use it please consult the
# Line 175  Line 183 
183    
184          </example></p>          </example></p>
185    
186          <p>or on the Internet at: <url id="&url-install-manual;"></p>          <p>or on the Internet at: <url id="&url-install-manual;">.</p>
187    
188          <p>The old &debian; installation system called          <p>The old &debian; installation system called
189          <prgn>boot-floppies</prgn> has been replaced by a new componentized and          <prgn>boot-floppies</prgn> has been replaced by a new componentized and
# Line 201  release: architectures: Line 209  release: architectures:
209    
210          <sect1 id="syntax"><heading>Important program syntax changes</heading>          <sect1 id="syntax"><heading>Important program syntax changes</heading>
211            <p>Debian attempts to avoid changing upstream packages, therefore            <p>Debian attempts to avoid changing upstream packages, therefore
212            changes in the original packages will be present in &debian;</p>            changes in the original packages will be present in &debian;.</p>
213    <!-- FJP: The previous para does not seem logical; should maybe be rewritten -->
214    
215            <p><em>No changes yet reported.</em></p>            <p><em>No changes yet reported.</em></p>
216    
# Line 222  release: architectures: Line 231  release: architectures:
231            <tt>dpkg --get-selections \*</tt>.</p>            <tt>dpkg --get-selections \*</tt>.</p>
232    
233            <p>It's wise to inform all users in advance of any upgrades you're            <p>It's wise to inform all users in advance of any upgrades you're
234            planning, although users accessing your system via ssh (at least)            planning, although users accessing your system via SSH (at least)
235            shouldn't notice much during the upgrade, and may want to continue            shouldn't notice much during the upgrade, and may want to continue
236            working. If you wish to take extra precautions, back up or unmount            working. If you wish to take extra precautions, back up or unmount
237            user's partitions (<file>/home</file>) before upgrading. A reboot            user's partitions (<file>/home</file>) before upgrading. A reboot
# Line 238  release: architectures: Line 247  release: architectures:
247            because each of those services may well be terminated during the            because each of those services may well be terminated during the
248            upgrade, which can result in an <em/inaccessible/ system that is            upgrade, which can result in an <em/inaccessible/ system that is
249            only half-upgraded.</p>            only half-upgraded.</p>
250    <!-- FJP: Not only xdm, but also gdm, kdm, ...
251              Maybe s/by <prgn/xdm//by display managers like <prgn/xdm/, <prgn/gdm/ or <prgn/kdm// -->
252    
253          <sect1><heading>Disabling APT Pinning</heading>          <sect1><heading>Disabling APT Pinning</heading>
254    
255            <p>If you have configured APT to install certain packages from a            <p>If you have configured APT to install certain packages from a
256            distribution other than stable (e.g from testing) you may have to            distribution other than stable (e.g from testing), you may have to
257            change your APT pinning configuration (stored in            change your APT pinning configuration (stored in
258            <file>/etc/apt/preferences</file> to allow the upgrade of packages to            <file>/etc/apt/preferences</file>) to allow the upgrade of packages to
259            the versions in the new stable release. Further information on APT            the versions in the new stable release. Further information on APT
260            pinning can be found in <manref name="apt_preferences" section="5">.</p>            pinning can be found in <manref name="apt_preferences" section="5">.</p>
261    <!-- FJP: Couldn't the advise to hold such packages prevent the upgrade of e.g.
262              libc6 if the package depends on the old version! -->
263    
264          </sect1>          </sect1>
265    
# Line 304  release: architectures: Line 317  release: architectures:
317          <sect1><heading>Special Considerations for SSH Users</heading>          <sect1><heading>Special Considerations for SSH Users</heading>
318    
319            <p>The commercial SSH located in the <package/ssh/ package before            <p>The commercial SSH located in the <package/ssh/ package before
320            release 2.2 or in the <package/ssh-nonfree/ in release 2.2 has            release 2.2 or in the <package/ssh-nonfree/ package in release 2.2 has
321            been replaced by the DFSG free <package/ssh/ package (OpenSSH) in            been replaced by the DFSG free <package/ssh/ package (OpenSSH) in
322            this release. The commercial SSH collection is no longer present.            this release. The commercial SSH collection is no longer present.
323            The <package/ssh/ package includes a Debconf question which will            The <package/ssh/ package includes a Debconf question which will
# Line 353  release: architectures: Line 366  release: architectures:
366             <file>/etc/apt/sources.list</file> to use other mirrors,             <file>/etc/apt/sources.list</file> to use other mirrors,
367             preferably a mirror that is network-wise closest to you.</p>             preferably a mirror that is network-wise closest to you.</p>
368    
369             <p>Otherwise, Debian HTTP or FTP mirror addresses can be found at  <!-- FJP: Why is 'default configuration' relevant here? We are talking about
370              upgrading existing installations; we really have no idea what
371              apt-sources users will have set up here (maybe just a Woody CD-set).
372              Note: D-I sets the default configuration to a mirror based on
373              the selected country and not the 'main' servers. -->
374    
375               <p>Debian HTTP or FTP mirror addresses can be found at
376             <url id="&url-debian-mirrors;"> (look at the "Full list of             <url id="&url-debian-mirrors;"> (look at the "Full list of
377             mirrors" section). HTTP mirrors are generally speedier than ftp             mirrors" section). HTTP mirrors are generally speedier than FTP
378             mirrors.</p>             mirrors.</p>
379    <!-- FJP: 'Otherwise' does not refer back to anything here, so I deleted it
380              (unless the intention was to refer to local intr_a_net HTTP
381              servers in the previous para). -->
382    
383             <p>For example, suppose your closest Debian mirror is             <p>For example, suppose your closest Debian mirror is
384             <tt>&url-debian-mirror-eg;/</tt>. When inspecting that mirror             <tt>&url-debian-mirror-eg;/</tt>. When inspecting that mirror
# Line 388  release: architectures: Line 410  release: architectures:
410             (<tt/#/) in front of them.</p>             (<tt/#/) in front of them.</p>
411    
412             <p>Any package needed for installation that is fetched from the             <p>Any package needed for installation that is fetched from the
413             network is stored in the <file>/var/cache/apt/archives</file>             network is stored in <file>/var/cache/apt/archives</file>
414             (and the <file>partial/</file> subdirectory, during download), so             (and the <file>partial/</file> subdirectory, during download), so
415             you must make sure you have enough space before attempting to             you must make sure you have enough space before attempting to
416             start the installation. With a reasonably extended Debian             start the installation. With a reasonably extended Debian
# Line 431  release: architectures: Line 453  release: architectures:
453    
454          <sect1 id="cdroms"><heading>Adding APT CD-ROM Sources</heading>          <sect1 id="cdroms"><heading>Adding APT CD-ROM Sources</heading>
455    
456    <!-- FJP: Are these instructions also valid for adding DVD's? -->
457    
458            <p>See above if you need to first install the latest version of            <p>See above if you need to first install the latest version of
459            <package/apt/ and <package/dpkg/ packages, as described above.</p>            <package/apt/ and <package/dpkg/ packages, as described above.</p>
460    <!-- FJP: See above [...], as described above is a bit double.
461              Also, I don't think the need to update the package tools and how
462              to do that has been descibed 'above' yet. -->
463    
464            <p>If you want to use CDs <em/only/, comment out the existing            <p>If you want to use CDs <em/only/, comment out the existing
465            "<tt/deb/" lines in <file>/etc/apt/sources.list</file> by placing            "<tt/deb/" lines in <file>/etc/apt/sources.list</file> by placing
# Line 441  release: architectures: Line 468  release: architectures:
468            <p>Make sure there is a line in <file>/etc/fstab</file> that            <p>Make sure there is a line in <file>/etc/fstab</file> that
469            enables mounting your CD-ROM drive at the <file>/cdrom</file>            enables mounting your CD-ROM drive at the <file>/cdrom</file>
470            mount point (the exact <file>/cdrom</file> mount point is required            mount point (the exact <file>/cdrom</file> mount point is required
471            for <prgn/apt-cdrom/).For example, if <file>/dev/hdc</file> is            for <prgn/apt-cdrom/). For example, if <file>/dev/hdc</file> is
472            your CD-ROM drive, <file>/etc/fstab</file> should contain a line            your CD-ROM drive, <file>/etc/fstab</file> should contain a line
473            like:            like:
474    
# Line 492  release: architectures: Line 519  release: architectures:
519    
520            <p>Next ensure that the APT source entries (in            <p>Next ensure that the APT source entries (in
521            <file>/etc/apt/sources.list</file>) refer to the <tt>'stable'</tt>            <file>/etc/apt/sources.list</file>) refer to the <tt>'stable'</tt>
522            distribution and does not refer to it by its codename (e.g.            distribution and do not refer to it by its codename (e.g.
523            <tt>&oldreleasename;</tt>).            <tt>&oldreleasename;</tt>).
524    
525            <p>It is strongly recommended that you use the            <p>It is strongly recommended that you use the
# Line 520  release: architectures: Line 547  release: architectures:
547            <p>Provided that you have a working APT configuration as described            <p>Provided that you have a working APT configuration as described
548            above this will install the &oldreleasename; version of            above this will install the &oldreleasename; version of
549            <prgn>aptitude</prgn>.</p>            <prgn>aptitude</prgn>.</p>
550    <!-- FJP: Will it really? Haven't we have just instructed users to point
551              everything to the new release? -->
552    
553            <p>First <prgn>aptitude</prgn> needs to fetch a list of new and            <p>First <prgn>aptitude</prgn> needs to fetch a list of new and
554            updated packages for the new release. This is done by executing:</p>            updated packages for the new release. This is done by executing:</p>
# Line 529  release: architectures: Line 558  release: architectures:
558            </example></p>            </example></p>
559    
560            <p>Once <prgn>aptitude</prgn> has information on all the available            <p>Once <prgn>aptitude</prgn> has information on all the available
561            packages the system is almost ready to be fully upgraded.</p>            packages, the system is almost ready to be fully upgraded.</p>
562    <!-- FJP: Why 'almost'? The next command will perform the upgrade.
563              'Almost' implies the user needs to do something else first... -->
564    
565            <p><example>            <p><example>
566            aptitude -f --with-suggests --with-recommends dist-upgrade            aptitude -f --with-suggests --with-recommends dist-upgrade
# Line 625  release: architectures: Line 656  release: architectures:
656            split in that release; go back and read <ref id="renames"> and            split in that release; go back and read <ref id="renames"> and
657            <ref id="splits"> to see the list of packages split in this            <ref id="splits"> to see the list of packages split in this
658            release.</p>            release.</p>
659    <!-- FJP: Why should the Release Notes of the previous release be consulted? -->
660    <!-- FJP: 'go back and read'? This info comes later in this doc. -->
661    
662            <p>Read            <p>Read
663            <file>/usr/share/doc/xfree86-common/README.Debian-upgrade</file> for            <file>/usr/share/doc/xfree86-common/README.Debian-upgrade</file> for
664            more info on the upgrade of the X window system packages. This is            more info on the upgrade of the X window system packages. This is
# Line 650  release: architectures: Line 683  release: architectures:
683           <p>To upgrade your kernel you must first choose the kernel most           <p>To upgrade your kernel you must first choose the kernel most
684           apropriate for your subarchitecture. A list of kernels available for           apropriate for your subarchitecture. A list of kernels available for
685           you to install can be found with:           you to install can be found with:
686    <!-- FJP: s/subarchitecture/subarchitecture and processor/ ??? -->
687    
688           <example>           <example>
689    
# Line 683  release: architectures: Line 717  release: architectures:
717          including the Debian Guide, Debian New Maintainers Guide, and Debian          including the Debian Guide, Debian New Maintainers Guide, and Debian
718          FAQ are available, and many more. For full details of the resources          FAQ are available, and many more. For full details of the resources
719          available see the DDP website at <url          available see the DDP website at <url
720          id="&url-ddp;"></p>          id="&url-ddp;">.</p>
721    
722          <p>Documentation for individual packages is installed into          <p>Documentation for individual packages is installed into
723          <file>/usr/share/doc/<var>package</var></file>, this may include          <file>/usr/share/doc/<var>package</var></file>, this may include
# Line 704  release: architectures: Line 738  release: architectures:
738        <sect1 id="lists">        <sect1 id="lists">
739          <heading>Mailing lists</heading>          <heading>Mailing lists</heading>
740          <p>The mailing lists of most interest to Debian users are the          <p>The mailing lists of most interest to Debian users are the
741          debian-user (English) and other debian-user-<var/language/ lists          debian-user list (English) and other debian-user-<var/language/ lists
742          (for other languages). For information on these lists and details of          (for other languages). For information on these lists and details of
743          how to subscribe see <url id="&url-debian-list-archives;">. Please          how to subscribe see <url id="&url-debian-list-archives;">. Please
744          check the archives for answers to your question prior to posting and          check the archives for answers to your question prior to posting and
# Line 736  release: architectures: Line 770  release: architectures:
770          information on reported bugs at our own Bug Tracking System (BTS)          information on reported bugs at our own Bug Tracking System (BTS)
771          browseable at <url id="&url-bts;" name="bugs.debian.org">, this is          browseable at <url id="&url-bts;" name="bugs.debian.org">, this is
772          consistent with Debian's open development.</p>          consistent with Debian's open development.</p>
773    <!-- FJP: I propose to replace the last sentence by:
774            Consistent with Debian's 'open development' philosophy and as a
775            service to our users, we provide all the information on reported bugs
776            at our own Bug Tracking System (BTS). The BTS is browseable at
777            <url id="&url-bts;" name="bugs.debian.org">.
778    -->
779    
780          <p>If you find a bug in the distribution or in packaged software          <p>If you find a bug in the distribution or in packaged software
781          that is part of it, please report it so that it can be properly          that is part of it, please report it so that it can be properly
# Line 744  release: architectures: Line 784  release: architectures:
784          can get in contact with submitters should they need more          can get in contact with submitters should they need more
785          information.</p>          information.</p>
786    
787          <p>You can submit a bug report either using the programs          <p>You can submit a bug report using the program
788          <package>reportbug</package> and <package>bug</package>          <package>reportbug</package> or manually using email.
         (available in their apropriate packages) or manually using email.  
789          You can read more about the Bug Tracking System and how to use it by          You can read more about the Bug Tracking System and how to use it by
790          reading the reference cards (available at          reading the reference cards (available at
791          <file>/usr/share/doc/debian</file> in any installed system) or          <file>/usr/share/doc/debian</file> in any installed system) or
792          online at the <url id="&url-bts;" name="Bug Tracking          online at the <url id="&url-bts;" name="Bug Tracking
793          System">.</p>          System">.</p>
794    <!-- FJP: The 'bug' program and package are obsolete. -->
795    
796        </sect>        </sect>
797    
798        <sect id="contributing">        <sect id="contributing">
# Line 856  release: architectures: Line 896  release: architectures:
896          None reported yet!          None reported yet!
897          </example> </p>          </example> </p>
898        </sect>        </sect>
899    
900        <sect id="removed"><heading>Removed packages</heading>        <sect id="removed"><heading>Removed packages</heading>
901          <sect1 id="nomaintainer">          <sect1 id="nomaintainer">
902            <heading>Packages removed because of no maintainer</heading>            <heading>Packages removed because of no maintainer</heading>
# Line 869  release: architectures: Line 910  release: architectures:
910    
911            <p>The alternatives field lists any packages that might replace            <p>The alternatives field lists any packages that might replace
912            the removed package.</p>            the removed package.</p>
913    <!-- FJP: Which 'alternatives field'? -->
914    
915            <p><example>            <p><example>
916            aethera (152941)            aethera (152941)
# Line 1126  release: architectures: Line 1168  release: architectures:
1168            zebra (208786)            zebra (208786)
1169            </example></p>            </example></p>
1170          </sect1>          </sect1>
1171    
1172          <sect1 id="no-upstream">          <sect1 id="no-upstream">
1173          <heading>Packages lacking upstream</heading>          <heading>Packages lacking upstream</heading>
1174            <p>These are packages which have been removed because they lack an            <p>These are packages which have been removed because they lack an
# Line 1137  release: architectures: Line 1180  release: architectures:
1180    
1181            <p>The alternatives field lists any packages that might replace            <p>The alternatives field lists any packages that might replace
1182            the removed package.</p>            the removed package.</p>
1183    <!-- FJP: Which 'alternatives field'? -->
1184    
1185            <p><example>            <p><example>
1186            admwebuser (182238)            admwebuser (182238)
# Line 1278  release: architectures: Line 1322  release: architectures:
1322            </example></p>            </example></p>
1323          </sect1>          </sect1>
1324          <sect1 id="removed-other">          <sect1 id="removed-other">
1325    
1326          <heading>Packages removed for other reasons</heading>          <heading>Packages removed for other reasons</heading>
1327            <p>The reason for the removal of the package is listed below the            <p>The reason for the removal of the package is listed below the
1328            name of the package. The number associated with the bug is            name of the package. The number associated with the bug is
# Line 1285  release: architectures: Line 1330  release: architectures:
1330            the package was removed. To use this number visit the <url            the package was removed. To use this number visit the <url
1331            id="&url-bts;" name="Bug Tracking System"> and do a query based on            id="&url-bts;" name="Bug Tracking System"> and do a query based on
1332            the bugnumber.</p>            the bugnumber.</p>
1333    <!-- FJP: The 'reason for removal' seems to be missing in the list. -->
1334    
1335            <p>The alternatives field lists any packages that might replace            <p>The alternatives field lists any packages that might replace
1336            the removed package.</p>            the removed package.</p>
1337    <!-- FJP: Which 'alternatives field'? -->
1338    
1339            <p><example>            <p><example>
1340    

Legend:
Removed from v.2627  
changed lines
  Added in v.2628

  ViewVC Help
Powered by ViewVC 1.1.5