Re: Release notes
On Fri, Dec 07, 2001 at 01:52:38PM +0100, Javier Fern?ndez-Sanguino Pe?a wrote:
> On Wed, Nov 21, 2001 at 08:47:41PM +0000, Rob Bradford wrote:
> > Can you grab my latest attempt at the release notes from
> > http://people.debian.org/~robster/release-notes.sgml
> >
> > These are based on teh cvs versions for potato, i need some assistance in
> > unbreaking the mess i seem to have made. Ny content suggestions would also
> > be warmly welcomed. If anyone else, preferably those who have more
> > experiance than myself would like to help (takeover?) please approach me.
> >
>
> Could we please add this to the WWW site even if currently under
> development?
> Is there anyone (besides Rob and maybe Josip) working in finishing the
> release notes?
>
> Javi
>
I attached a revision diff. I did some reorganization to keep things
in chronological order, added some comments, did a little
reformatting, and grammar/spelling/titlecasing changes etc.
--
*--v------ Installing Debian GNU/Linux 3.0 For PowerPC -----v----*
| <http://mirrors.kernel.org/debian/dists/woody/main/disks- |
| (pause for breath) powerpc/current/doc/install.en.html> |
| debian-imac: <http://debian-imac.sourceforge.net> |
| Chris Tillman tillman@azstarnet.com |
| May the Source be with you |
*----------------------------------------------------------------*
--- release-notes-orig.sgml Fri Dec 7 19:27:44 2001
+++ release-notes.sgml Sat Dec 8 00:10:16 2001
@@ -28,26 +28,26 @@
<url id="&url-release-notes;">. If your version is more than a month
old, you might wish to download the latest version.]
- <p> Previously &debian; 2.2 release ('potato') had six release
- architectures, in this release these six have been
- joined by four more indictated by an asterisk (*)
- Therefore the full list of release architectures
- are:
- </p>
- <p>
- <list>
- <item>Intel x86 (i386')</item>
- <item>Motorola 680x0 ('m68k')</item>
- <item>Alpha ('alpha')</item>
- <item>SPARC ('sparc')</item>
- <item>PowerPC ('powerpc')</item>
- <item>ARM ('arm')</item>
- <item>MIPS ('mips' (Big endian) and 'mipsel' (Little endian)) [*]</item>
- <item>Intel Itanium ('ia64') [*]</item>
- <item>HP PA-RISC ('hppa') [*]</item>
- <item>S/390 ('s390') [*]</item>
- </list>
- </p>
+ <p> Previously &debian; 2.2 release ('potato') supported six
+ computer architectures. In this release those six have
+ been joined by four more indicated by an asterisk (*) below.
+ Here is the full list of architectures for this release:
+
+ </p>
+ <p>
+ <list>
+ <item>Intel x86 ('i386')</item>
+ <item>Motorola 680x0 ('m68k')</item>
+ <item>Alpha ('alpha')</item>
+ <item>SPARC ('sparc')</item>
+ <item>PowerPC ('powerpc')</item>
+ <item>ARM ('arm')</item>
+ <item>MIPS ('mips' (Big endian) and 'mipsel' (Little endian)) [*]</item>
+ <item>Intel Itanium ('ia64') [*]</item>
+ <item>HP PA-RISC ('hppa') [*]</item>
+ <item>S/390 ('s390') [*]</item>
+ </list>
+ </p>
<![ %not-i386 [<!-- i386 doesn't have a port page --> You can read more
about port status, and port-specific information for your
@@ -55,43 +55,7 @@
pages">.
]]>
-<![ %hppa [ <p>This is the first official release of &debian; for the
- &arch-title; architecture. We feel that it has proven itself
- sufficiently to be released. However, because it has not had the
- exposure (and hence testing by users) that our other releases on
- other architectures have had, you may encounter a few bugs. Please
- use our <url id="&url-bts;" name="bug tracking system"> to report
- any problems; make sure to mention the fact that the bug is on the
- &architecture; platform.
-]]>
-<![ %s390 [ <p>This is the first official release of &debian; for the
- &arch-title; architecture. We feel that it has proven itself
- sufficiently to be released. However, because it has not had the
- exposure (and hence testing by users) that our other releases on
- other architectures have had, you may encounter a few bugs. Please
- use our <url id="&url-bts;" name="bug tracking system"> to report
- any problems; make sure to mention the fact that the bug is on the
- &architecture; platform.
-]]>
-<![ %mips [ <p>This is the first official release of &debian; for the
- &arch-title; architecture. We feel that it has proven itself
- sufficiently to be released. However, because it has not had the
- exposure (and hence testing by users) that our other releases on
- other architectures have had, you may encounter a few bugs. Please
- use our <url id="&url-bts;" name="bug tracking system"> to report
- any problems; make sure to mention the fact that the bug is on the
- &architecture; platform.
-]]>
-<![ %mipsel [ <p>This is the first official release of &debian; for the
- &arch-title; architecture. We feel that it has proven itself
- sufficiently to be released. However, because it has not had the
- exposure (and hence testing by users) that our other releases on
- other architectures have had, you may encounter a few bugs. Please
- use our <url id="&url-bts;" name="bug tracking system"> to report
- any problems; make sure to mention the fact that the bug is on the
- &architecture; platform.
-]]>
-<![ %ia64 [ <p>This is the first official release of &debian; for the
+<![ %hppa %s390 %mips %mipsel %ia64 [ <p>This is the first official release of &debian; for the
&arch-title; architecture. We feel that it has proven itself
sufficiently to be released. However, because it has not had the
exposure (and hence testing by users) that our other releases on
@@ -101,42 +65,60 @@
&architecture; platform.
]]>
- <p>&debian; &release; for the &arch-title; architecture ships with
- kernel version &kernel-version;. The 2.2 kernel series has been
- updated and developed extensively introducing several valuable
- changes both in the kernel and in other programs based on kernel
- features, along with a whole slew of new hardware drivers and bug
- fixes for existing drivers.</p> <p>A 2.4 kernel is also included in
- this release, but is not used by default. Although kernel branch is
- officially the stable kernel branch the &debian; release team feel
- it has not reached sufficient maturity for inclusion in this
- release.</p>
+ <p>&debian; &release; for the &arch-title; architecture ships
+ with kernel version &kernel-version;. The 2.2 kernel series
+ has been updated and developed extensively introducing several
+ valuable changes both in the kernel and in other programs
+ based on kernel features, along with a whole slew of new
+ hardware drivers and bug fixes for existing drivers.</p>
+
+ <p>
+ A 2.4 kernel is also included in this release for optional
+ installation by users. Although the 2.4 branch is considered
+ by the kernel developers to be a stable kernel branch, the
+ &debian; release team judged it not to have reached sufficient
+ maturity for inclusion as the default kernel in this release.
+</p>
<sect id="newinst">What's New in the Installation System?
- <p> The new <package>debootstrap</package> tool downloads &debian;
- packages and unpacks and extracts them. An improvement over the
- previous installation system that utilized a tarball containing the
- base system. </p> <p>The task system has been revamped, tasks no
- longer consist of meta packages (ie packages whose sole task is to
- depend on other packages) which were introduced into the previous
- release of Debian GNU/Linux, special headers are now used. This
- allows greater selection of tasks and its is much easier to only
- install selected components of tasks, ie not the whole thing. </p>
- <p> All configuration at install time and for later reconfiguration
- is done using Debconf, which comes in a variety of flavours. From a
- non-interactive method, to dialog to the new GNOME frontend. Debconf
- has also had its backend revamped and improved and it is now more
- flexible than ever. In short Debconf makes the world go around :)
- </p> <p> For full details of the Debian installation system users
- are advised to read the Debian installation guide. Included on the
- first CD or find it on the internet at <url
- id="http://www.debian.org/releases/3.0/i386/install";> </p>
+ <p> The new <package>debootstrap</package> tool downloads, unpacks and extracts &debian;
+ packages for the base system installation. This is an improvement over the
+ previous installation system which utilized a tarball containing the
+ base system. The installation base system can be more
+ dynamically updated with this system. </p>
+
+<p> The task system has been revamped. Tasks in the previous release
+ consisted of meta packages (packages which are simply
+ collections of other packages). The new system uses special
+ headers within the existing package system to designate any
+ tasks to which each package may belong.
+
+<!-- this isn't true, is it? We don't have any way for people to pick
+ part of a task except to pick some packages, right? -->
+ This allows greater selection of tasks and its is much easier to only
+ install selected components of tasks, ie not the whole thing.
+ </p>
+ <p>
+
+ Almost all configuration at install time and for later
+ reconfiguration is done using Debconf, which comes in a
+ variety of flavours: a non-interactive method, dialog
+ (curses-based), and a new GNOME frontend. Debconf's engine
+ has also been revamped and improved and is now more flexible
+ than ever. In short, Debconf makes the world go around :)
+ </p>
+ <p>
+
+ For full details on the Debian installation system users are
+ advised to read the Debian installation guide, included on the
+ first CD or at <url
+ id="http://www.debian.org/releases/3.0/i386/install";>
+</p>
<![ %i386 [ <p>Kernel images are available in various "flavors". These
flavors each support a different set of hardware. The flavors
- available in &debian;
- &release; for &arch-title; are:
+ available in &debian; &release; for &arch-title; are:
<taglist>
<tag>`vanilla'
@@ -161,7 +143,7 @@
made. Finally, `compact' also supports several common RAID
controllers: DAC960, and Compaq's SMART2 RAID controllers.
The `compact' flavor includes one rescue, one root and one
- driver disks.
+ driver disk.
<tag>`idepci' <item>Kernel that supports only IDE and PCI devices
(and a very small number of ISA devices). This kernel should
@@ -173,76 +155,67 @@
</taglist>
The kernel config files for these flavors can be found in their respective
- directories in a file named "kernel-config".
+ directories in a file named 'kernel-config'.
]]>
<sect id="newdistro">What's New in the Distribution?
- <p> At install time, on most platforms, the kernel used is
- &kernel-version, however a 2.4 kernel, the
- latest stable branch is included for those
- who wish to benefit from it.
- </p>
- <p>
- The Debian package management tools apt and
- dpkg have been improved considerably in this
- release. Now apt supports "pinning" in which
- the user can opt to download certain
- packages from different distributions, e.g.
- testing or unstable, whilst still tracking
- stable. Fortunately apt will automagically
- download and install apropriate dependencies
- if required from this distribution. An apt
- "pinning" howto is available here.
- </p>
- <p>
- To aid in the compilation of source
- packages, often used by people wishing to
- track stable and use packages from other
- distributions (note "pinning" supercedes
- this use, source packages however still have
- many other uses), build dependencies have
- been added. Using the "build-dep" method of
- apt-get can be used to retrieve these
- dependencies before compilation is
- commenced.
- </p>
- <p>
- To replace the ageing, yet still popular
- <package>dselect</package> many apt
- frontends have been in development during
- the woody release cycle, many of these are
- reaching a usable stable state. Interested
- users should investigate
- <package>deity</package> and
- <package>aptitude</package>
- </p>
- <p>
- This release of Debian GNU/Linux contains
- the much improved XFree86 4.1 release, this
- includes better support for a greater range
- of hardware, more autodetection support and
- also improved support for advanced
- technologies such as Xinerama and 3D
- acceleration.
- </p>
- <p>
- For the first time, Debian GNU/Linux
- includes several fully featured free
- graphical web browsers in the form of
- Mozilla, Galeon and Konqueror, this along
- with the inclusion of KDE 2.2 for the first
- time, as well as the new GNOME 1.4 release
- has increased Debian's desktop provision.
- </p>
- <p>
- Debian GNU/Linux officially now ships on 6
- binary CDs iwth a similar number of source CDs, and
- a DVD version of the distribution is now also
- available. </p>
+ <p> At install time, on most platforms, the kernel used is
+ &kernel-version, however a 2.4 kernel, the latest
+ stable branch is included for those who wish to benefit
+ from it.
+ </p>
+ <p>
+ The Debian package management tools apt and dpkg have
+ been improved considerably in this release. Now apt
+ supports "pinning" in which the user can opt to
+ download certain packages from different distributions,
+ e.g. testing or unstable, while still keeping the bulk
+ of his installation in the stable distribution. APT
+ will automagically download and install appropriate
+ dependent packages from the advanced distribution as
+ required. An apt "pinning" howto is available here.
+ </p>
+ <p>
+ Build dependencies have been added to aid in the
+ compilation of source packages. The "build-dep" apt-get
+ method can be used to retrieve all packages needed for
+ a build before compilation is commenced.
+ </p>
+ <p>
+ To replace the aging, much-maligned, yet still popular
+ <package>dselect</package>, many apt frontends have
+ been in development during the woody release
+ cycle. Many of these are reaching a usable stable
+ state. Interested users should investigate
+ <package>aptitude</package> and
+ <package>deity</package>. <package>Aptitude</package>
+ may even replace dselect as the default in the basic
+ installation.
+ </p>
+ <p>
+ This release of Debian GNU/Linux contains the much
+ improved XFree86 4.1 release, which includes
+ support for a greater range of hardware, better
+ autodetection support, and improved support for
+ advanced technologies such as Xinerama and 3D
+ acceleration.
+ </p>
+ <p>
+ For the first time, Debian GNU/Linux includes several
+ full featured free graphical web browsers in the form
+ of Mozilla, Galeon and Konqueror. With the inclusion of
+ KDE 2.2 for the first time, as well as the new GNOME
+ 1.4 release, Debian's desktop provision has been
+ radically improved.
+ </p>
+ <p>
+ The official Debian GNU/Linux distribution now ships on
+ six binary CDs with a similar number of source CDs, and a
+ DVD version of the distribution is now also available.
+ </p>
- </sect>
-<chapt id="installing">New installations
+<chapt id="installing">New Installations
<p>If you are making a new installation of Debian, you should read
the installation manual, which is available on the Official CD at:
@@ -251,11 +224,11 @@
/dists/&releasename;/main/disks-&architecture;/current/doc/install.txt (or .html)
</example>
- Or on the Internet at:
+ or on the Internet at:
<p><url id="&url-install-manual;">
<p>The Debian installation system, which is called the
- <package/boot-floppies/ (even though it is for more than just
+ <package/boot-floppies/ (even though it supports more than just
floppies), has been further streamlined and upgraded for users'
convenience.
@@ -263,29 +236,31 @@
<![ %not-mipsel [
<![ %not-ia64 [
<![ %not-hppa [
-<chapt id="upgrading">Upgrades from previous releases
+<chapt id="upgrading">Upgrades from Previous Releases
<!-- For doc-writers' convenience:
+ Debian Supported
+ release: architectures:
- Debian Supported
- release: architectures:
-
- <= 1.3.1 i386
- 2.0 i386 m68k
- 2.1 i386 m68k alpha sparc
- 2.2 i386 m68k alpha sparc powerpc arm
+ <= 1.3.1 i386
+ 2.0 i386 m68k
+ 2.1 i386 m68k alpha sparc
+ 2.2 i386 m68k alpha sparc powerpc arm
+ 3.0 + hppa s390 mips mipsel ia64
-->
- <sect id="information">Detailed changes to the system
-
- <p>We need this information, and any port specific details.</p>
+ <sect id="information">Detailed Changes to the System
+ <p>
+ ******************
+ <p>We need this information, and any port specific details.</p>
+ <p>******************
- <sect1 id="renames">Renamed packages
+ <sect1 id="renames">Renamed Packages
<p>The following packages have been renamed as shown. In most, if
not all, cases, Conflicts:, Replaces:, and Provides: fields (or even
dummy packages) have been provided so the new package will either
- get installed automatically, and/or will safely replace/remove the
+ get installed automatically, and/or will safely replace or remove the
old one.
<example>
@@ -295,7 +270,7 @@
<p>Although we have made every effort to complete this list, it may
still not be exhaustive.
- <sect1 id="splits">Split packages
+ <sect1 id="splits">Split Packages
<p>Between releases 2.2 (`potato') and 3.0 (`woody'), a number of
packages have been split into two or more packages. The reason for
@@ -307,7 +282,7 @@
<p>If you find that a familiar package is lacking some or all of its
functionality, check the list below to see if you need to install
- more packages to restore the original functionality. Failing that,
+ additional packages to restore the original functionality. Failing that,
check the changelog for the package, which can be found in
<file>/usr/doc/<var>package</var>/changelog.Debian.gz</file>.
@@ -315,18 +290,19 @@
list may not be complete):
<example>
- isdnutils -> ipppd, isdnlog, isdnutils-doc, isdnutils-xtools, isdnvboxserver,isdnvboxclient
+ isdnutils -> ipppd, isdnlog, isdnutils-doc, isdnutils-xtools,
+ isdnvboxserver, isdnvboxclient
</example>
- <sect id="backup">Necessary actions prior to the upgrade
+ <sect id="backup">Preparing for the Upgrade
<p>Before upgrading your system, it is strongly recommended that you
- make a full backup, or at least, backup any data or configuration
+ make a full backup, or at least backup any data or configuration
information you can't afford to lose. The upgrade tools and process
are quite reliable, but a hardware failure in the middle of an
upgrade could result in a severely damaged system.
- <p>The main things you'll want to save are the contents of
+ <p>The main things you'll want to back up are the contents of
<file>/etc</file>, <file>/var/lib/dpkg</file> and the output of
<tt>dpkg --get-selections</tt>.
@@ -334,81 +310,80 @@
planning, although users accessing your system via ssh (at least)
shouldn't notice much during the upgrade, and may want to continue
working. If you wish to take extra precautions, back up or unmount
- user's partitions (<file>/home</file>) before upgrading.
+ user's partitions (<file>/home</file>) before upgrading. A
+ reboot will not normally be necessary.
<p>Distribution upgrade should be done either locally from a textmode
virtual console (or a directly connected serial terminal), or remotely
via an <prgn/ssh/ link.
- <p>You should <em/not/ do the upgrade using <prgn/telnet/,
- <prgn/rlogin/, <prgn/rsh/, or from an X session managed by
- <prgn/xdm/ on the machine you are upgrading. That is because each of
- those services may well be terminated during the upgrade, which can
- result in an <em/inaccessible/ system that is only half-upgraded.
-
- <p>Running the upgrade using <prgn/emacs/ shell buffers is not
- recommended due to problems some debconf frontends in that mode.
-<!-- debconf not working in emacs shell buffers problem was fixed in woody,
- see
- http://cgi.debian.org/cgi-bin/bugreport.cgi?archive=yes&bug=60963
- -->
+ <p><em/Important/: You should <em/not/ upgrade using
+ <prgn/telnet/, <prgn/rlogin/, <prgn/rsh/, or from an X session
+ managed by <prgn/xdm/ on the machine you are upgrading. That
+ is because each of those services may well be terminated
+ during the upgrade, which can result in an <em/inaccessible/
+ system that is only half-upgraded.
+
+ <!-- <p>Running the upgrade using <prgn/emacs/ shell buffers is not
+ recommended due to problems with some debconf frontends in
+ that mode.
+
+ (debconf not working in emacs shell buffers problem
+ was fixed in woody, see
+ http://cgi.debian.org/cgi-bin/bugreport.cgi?archive=yes&bug=60963)
+ -->
+ <sect1>Checking Packages Status
<p>Regardless of the method used for upgrading, it is recommended
that you check the status of all packages first, and verify that all
- packages are in an upgradable state. This can be done with
+ packages are in an upgradable state. The following command
+ will show any packages which have a status of Half-Installed
+ or Failed-Config, and those with any error status.
<example>
-dpkg -l | pager
+# dpkg -l | grep '^.[HF][^ ]'
</example>
- or
-
+ You could also inspect the state of all packages on your
+ system using <prgn/dselect/, or with commands such as
<example>
-dpkg --get-selections > filename
+# dpkg -l | pager
</example>
- (and then inspect <file/filename/), or it can be done in
- <prgn/dselect/.
-
- <p>Any package installation operation must be run with superuser
- privileges, so either login as root or use <prgn/su/ or <prgn/sudo/
- to gain necessary access rights.
-
- <p>It is strongly recommended that you use
- <prgn>/usr/bin/script</prgn> program to record a transcript of the
- upgrade session. <footnote>In fact, it is a good idea to use
- <prgn/script/ to record any <prgn/dselect/ session, and anything
- else you do that it is desirable to record.</footnote> Then if any
- problems develop, you can have a log of what happened, and if
- needed, provide exact information in a bug report. To start the
- recording, type:
+ or
<example>
-script -a /upgrade-2.2.typescript
+# dpkg --get-selections > ~/curr-pkgs.txt
</example>
- or similar. Remember not to put the typescript file on a temporary
- directory (such as <file>/tmp</file> or <file>/var/tmp</file>).
-
<p>It is desirable to remove any holds before upgrading. If any
package that is essential for the upgrade is on hold, the upgrade
- will fail. If you changed and recompiled a package locally, and
+ will fail. You can identify packages on hold with
+
+<example>
+# dpkg -l | grep ^h
+</example>
+
+ If you changed and recompiled a package locally, and
didn't rename it or put an epoch in the version, you must put it on
hold to prevent it from being upgraded. The `hold' package state can
be changed either by using <prgn/dselect/ (in the Select menu, use
- the `H' and `G' keys to hold and unhold, respectively), or by doing:
+ the `H' and `G' keys to hold and unhold, respectively), or by
+ editing the file produced by
<example>
-dpkg --get-selections > filename
+dpkg --get-selections > ~/curr-sels.txt
</example>
- editing <file>filename</file> to change "hold" to "install" (or vice
- versa), and then, with root permissions, doing
+ to change "hold" to "install" (or vice versa), and then, with
+ root permissions, doing
<example>
-dpkg --set-selections < filename
+dpkg --set-selections < ~/curr-sels.txt
</example>
+
+ <sect1>Special Considerations for SSH Users
<p>It might be a good idea to put <package/ssh/ on `Hold' (if it's
installed), since otherwise it will be replaced by OpenSSH (the new
<package/ssh/ package) which still has a slightly incompatible
@@ -422,23 +397,17 @@
<p>Please note that the <package/ssh/ package in this release
disables root logins by default. If you rely on this feature for
- remote access to your system you should ensure that
+ remote access to your system you should ensure that the
<tt/PermitRootLogin/ option in <file>/etc/ssh/sshd_config</file> is
set to <tt/yes/ after upgrade (To ensure dpkg never updates the file
to match new defaults, you can simply modify the file locally.
Adding a blank line is enough.)
+ <sect1>Directories Possibly Needing Attention
<p>It is important that the <file>/etc/rcS.d</file> directory exists
prior to the upgrade; the installation of the <package/libc6/
package will fail otherwise.
- <p>Don't forget to mount all needed partitions (notably the root and
- <file>/usr</file> partitions) read-write, with a command like:
-
-<example>
-mount -o remount,rw /<var>mountpoint</var>
-</example>
-
<p>The <file>/usr/share/doc</file> directory (if it exists already)
should not be a symlink (e.g. to <file>/usr/doc</file>), since that
will cause some packages to break. However, symlinking
@@ -447,21 +416,38 @@
messages about <file>/usr/doc</file> directories that can't be
removed. Those are normal, and you can safely ignore them.
- <p>The recommended method of upgrading is by using <prgn/apt-get/
- directly, as described in the next section. APT is the next
- generation of Debian's packaging tools, and it enables smooth
- upgrades and easy installations.
+
+ <sect id="upgrade-process">Preparing Sources for APT
+
+ <p>The recommended method of upgrading is to use
+ <prgn/apt-get/ directly, as described here. APT's built-in
+ dependency analysis enables smooth upgrades and easy
+ installations.
<p>You should <em/not/ be doing any major package upgrades with
default access methods in <prgn/dselect/, because those, unlike the
<prgn/apt/ method, do not do any logical package ordering during the
installation, and therefore aren't as reliable. Additionally, such
- upgrades are far less tested and therefore unsupported by Debian.
+ upgrades are not well tested and are unsupported by Debian.
+
+ <p>Any package installation operation must be run with superuser
+ privileges, so either login as root or use <prgn/su/ or <prgn/sudo/
+ to gain the necessary access rights.
- <sect id="upgrade-process">Upgrade process
+ <p>Before starting the upgrade you must set up <package/apt/'s
+ configuration file for package lists,
+ <file>/etc/apt/sources.list</file>.
+
+ <p><package/apt/ will consider all packages that can be found via
+ any "<tt>deb</tt>" line, and install the package with the highest
+ version number, giving priority to the first mentioned lines (that
+ way, in case of multiple mirror locations, you'd typically first
+ name a local harddisk, then CD-ROMs, and then HTTP/FTP mirrors).
-<![ %not-sparc [ <p>If you want to upgrade using CD-ROMs, or if you are
- upgrading from a &debian; release 2.0 or earlier, you need the
+ <sect1>Upgrading from Pre-Potato Releases or Using CD-ROMs
+ <p>
+<![ %not-sparc [ If you want to upgrade using CD-ROMs, or if you are
+ upgrading from &debian; release 2.0 or earlier, you need the
versions of <package/apt/ and <package/dpkg/ available in the <url
id="&disturl;/main/upgrade-&architecture;/"> directory at your
Debian mirror, or the <file>upgrade/</file> directory on the first
@@ -481,12 +467,13 @@
]]>
<![ %sparc [
+<!-- Is this information still applicable for upgrading to woody??? -->
<p>Before upgrading the &arch-title; architecture, you need to run a
Linux kernel version 2.2.x, as described in <ref id="information">.
<p>If you want to upgrade using CD-ROMs, you need the latest
- versions of <package/apt/ and <package/dpkg/ for Debian 2.1
- (`slink'); these are versions 0.3.11 and 1.4.0.34 respectively. You
+ versions of <package/dpkg/ and <package/apt/ for Debian 2.1
+ (`slink'); these are versions 1.4.0.34 and 0.3.11 respectively. You
can check the installed versions with <tt>apt-get --version</tt> and
<tt>dpkg --version</tt>. If you do not have the newest versions
yet, they are available in the <url
@@ -502,19 +489,18 @@
</example>
]]>
- <p>If you are upgrading from &debian; version 2.1 (any point
- release) and you want to upgrade using either the network (FTP,
- HTTP) or a local packages mirror (possibly a disk partition, or an
+ <p>If you are upgrading from &debian; version 2.1 or later and
+ you want to upgrade using either the network (FTP, HTTP) or a
+ local packages mirror (possibly a disk partition, or an
NFS-mounted mirror), then you can use the <package/apt/ and
<package/dpkg/ packages that came with that Debian release. Of
- course, if <package/apt/ is not installed yet (it is not by
- default), install it now.
+ course, if <package/apt/ is not installed yet, install it now.
+<!-- Is this information still applicable for upgrading to woody??? -->
<![ %not-sparc [ <p>Please note that for upgrading with <em/multiple/ CDs
from <em/any/ Debian release you need the static versions of
<package/apt/ and <package/dpkg/ packages, as described above.
]]>
-
<p>It is recommended that you read the <manref name="apt-get"
section="8"> and the <manref name="sources.list" section="5"> man
pages at this time.
@@ -525,60 +511,51 @@
<package/man-db/ package is upgraded.
]]>
- <p>Before starting the upgrade you must set up <package/apt/'s
- configuration file for package lists,
- <file>/etc/apt/sources.list</file>.
-
- <p><package/apt/ will consider all packages that can be found via
- any "<tt>deb</tt>" line, and install the package with the highest
- version number, giving priority to the first mentioned lines (that
- way, in case of multiple mirror locations, you'd typically first
- name a local harddisk, then CD-ROMs, and then FTP/HTTP mirrors).
-
+ <sect1 id="network">Adding APT Internet Sources
- <sect1 id="network">Setting up for an upgrade over the Internet
+ <p>The default configuration is set up for installation from
+ main Debian Internet servers, but you may wish to modify
+ <file>/etc/apt/sources.list</file> to use other mirrors,
+ preferably a mirror that is network-wise closest to you.
+
+ <p>Otherwise, Debian HTTP or FTP mirror addresses can be found
+ at <url id="&url-debian-mirrors;"> (look at the "Full list of
+ mirrors" section). HTTP mirrors are generally speedier tha ftp
+ mirrors.
- <p>The default configuration is set up for installation from our
- main Internet servers, but you may wish to modify
- <file>/etc/apt/sources.list</file> to use other mirrors, preferably
- a mirror that is network-wise closest to you. In that case, first
- comment out the existing "<tt/deb/" lines in <file/sources.list/, by
- placing a hash sign (<tt/#/) in front of them.
-
- <p>Debian FTP or HTTP mirror addresses can be found at
- <url id="&url-debian-mirrors;"> (look at the "Full list of mirrors"
- section).
-
- <p>For example, your closest Debian mirror is
- <tt>ftp://alea.iacta.est/debian/</tt> When inspecting that mirror
+ <p>For example, suppose your closest Debian mirror is
+ <tt>http://mirrors.kernel.org/debian/</tt>. When inspecting that mirror
with a web browser or FTP program, you will notice that the main
- directories are like this:
+ directories are organized like this:
<example>
-ftp://alea.iacta.est/debian/dists/&releasename;/main/binary-&architecture;/...
-ftp://alea.iacta.est/debian/dists/&releasename;/contrib/binary-&architecture;/...
+http://mirrors.kernel.org/debian/dists/&releasename;/main/binary-&architecture;/...
+http://mirrors.kernel.org/debian/dists/&releasename;/contrib/binary-&architecture;/...
</example>
To use this mirror with <prgn/apt/, you add this line to your
<file/sources.list/ file:
<example>
-deb ftp://alea.iacta.est/debian &releasename; main contrib
+deb http://mirrors.kernel.org/debian &releasename; main contrib
</example>
Note that the `<tt>dists</tt>' is added implicitly, and the
- arguments after the third are used to expand the path into multiple
- directories.
+ arguments after the release name are used to expand the path
+ into multiple directories.
- <p>If the mirror also contains the non-US
-/* sections under
- ftp://alea.iacta.est/debian/debian-non-US, also add the following
+ <p>If the mirror also contains the non-US sections under
+ http://mirrors.kernel.org/debian/debian-non-US, also add the following
line:
-
+
<example>
-deb ftp://alea.iacta.est/debian/debian-non-US &releasename;/non-US main contrib
+deb http://mirrors.kernel.org/debian/debian-non-US &releasename;/non-US main contrib
</example>
+ After adding your new sources, disable the previously
+ existing "<tt/deb/" lines in <file/sources.list/, by placing a
+ hash sign (<tt/#/) in front of them.
+
<p>Any package needed for installation that is fetched from the
network is stored in the <file>/var/cache/apt/archives</file> (and
the <file>partial/</file> subdirectory, during download), so you
@@ -589,19 +566,17 @@
<![ %not-sparc [ <p>Note: if you are using the static versions of
<package/apt/ and <package/dpkg/, the hostname-lookup is broken
- (which is one reason to use slink's <package/apt/ when upgrading
+ (which is one reason to use the normal <package/apt/ when upgrading
over the network). The solution is to simply put the mirrors' IP
- address in the "<tt>deb</tt>" line. (Hint: <tt>nslookup
+ address in the "<tt>deb</tt>" line. (Hint: <tt>nslookup
some-server</tt>)
]]>
- <sect1 id="localmirror">Setting up for an upgrade from a local mirror
+ <sect1 id="localmirror">Adding APT Local Mirror Sources
- <p>Instead of using FTP or HTTP packages mirrors, you may wish to
+ <p>Instead of using HTTP or FTP packages mirrors, you may wish to
modify <file>/etc/apt/sources.list</file> to use a mirror on a local
- disk (possibly NFS-mounted). In that case, first comment out the
- existing "<tt/deb/" lines in <file/sources.list/, by placing a hash
- sign (<tt/#/) in front of them.
+ disk (possibly NFS-mounted).
<p>For example, your packages mirror may be under
<file>/var/ftp/debian/</file>, and have main directories like this:
@@ -611,7 +586,7 @@
/var/ftp/debian/dists/&releasename;/contrib/binary-&architecture;/...
</example>
- To use this with <prgn/apt/, you add this line to your
+ To use this with <prgn/apt/, add this line to your
<file/sources.list/ file:
<example>
@@ -619,8 +594,8 @@
</example>
Note that the `<tt>dists</tt>' is added implicitly, and the
- arguments after the third are used to expand the path into multiple
- directories.
+ arguments after the release name are used to expand the path
+ into multiple directories.
<p>If your local mirror contains the non-US/* sections under
<file>/var/ftp/debian-non-US</file>, also add the following line:
@@ -629,7 +604,11 @@
deb file:/var/ftp/debian-non-US &releasename;/non-US main contrib
</example>
- <sect1 id="cdroms">Setting up for an upgrade from CD-ROMs
+ After adding your new sources, disable the previously
+ existing "<tt/deb/" lines in <file/sources.list/, by placing a
+ hash sign (<tt/#/) in front of them.
+
+ <sect1 id="cdroms">Adding APT CD-ROM Sources
<![ %not-sparc [ <p>First you need to install the latest version of
<package/apt/ and <package/dpkg/ packages, as described above.
@@ -646,18 +625,18 @@
CD-ROM drive, <file>/etc/fstab</file> should contain a line like:
<example>
-/dev/hdc /cdrom auto defaults,noauto,ro 0 0
+/dev/hdc /cdrom auto defaults,noauto,ro 0 0
</example>
- <p>Note that there may be <em/no spaces/ between the words
+ <p>Note that there must be <em/no spaces/ between the words
<tt>defaults,noauto,ro</tt> in the fourth field.
<p>To verify it works, insert a CD and try running
<example>
-mount /cdrom (this will mount the CD to the mount point)
+mount /cdrom (this will mount the CD to the mount point)
ls -alF /cdrom (this should show the CD's root directory)
-umount /cdrom (this will unmount the CD)
+umount /cdrom (this will unmount the CD)
</example>
<p>Next, run:
@@ -669,10 +648,17 @@
for each Debian Binary CD-ROM you have, to add the data about each
CD to APT's database.
- <sect1 id="actualupgrade">Upgrading
+ <sect id="actualupgrade">Upgrading
- <p>Once you have configured <package/apt/'s <file/sources.list/, run
- (as root):
+ <p>Don't forget to mount all needed partitions (notably the root and
+ <file>/usr</file> partitions) read-write, with a command like:
+
+<example>
+mount -o remount,rw /<var>mountpoint</var>
+</example>
+
+ <p>Assuming you have already configured <package/apt/'s
+ <file/sources.list/ as explained above, run (as root):
<example>
apt-get update
@@ -681,6 +667,21 @@
<p>This will resynchronize the package overview files from their
sources, updating information about new and updated packages.
+ <p>It is strongly recommended that you use the
+ <prgn>/usr/bin/script</prgn> program to record a transcript of
+ the upgrade session. Then if any problems develop, you will
+ have a log of what happened, and if needed, can provide exact
+ information in a bug report. To start the recording, type:
+
+<example>
+script -a ~/upgrade-to-woody.typescript
+</example>
+
+ or similar. Do not put the typescript file in a temporary
+ directory such as <file>/tmp</file> or <file>/var/tmp</file>
+ (files in those directories may be deleted during the upgrade
+ or during any restart).
+
<![ %sparc [
<p>If you are upgrading using CD-ROMs, now run:
@@ -694,18 +695,18 @@
<!-- i.e. libc6 and libstdc++ that dpkg and apt depend on - JAB -->
]]>
- <p>Some people prefer to run
+ <p>Some people prefer to first rehearse the upgrade using
<example>
apt-get --fix-broken --show-upgraded --simulate dist-upgrade | pager
</example>
- in order to see what will happen. While this may be somewhat time
- consuming, it may avoid some surprises. This will tell you either
- what's wrong with your system (and how to solve it), or, most
- likely, what exactly will be done during the upgrade. Pay special
- attention to the packages that will be "REMOVEd"; no essential
- packages should be listed there.
+ While this may be somewhat time consuming, it may avoid some
+ surprises. This will tell you either what's wrong with your
+ system (and how to solve it), or, most likely, what exactly
+ will be done during the upgrade. Pay special attention to the
+ packages that will be "REMOVEd"; no essential packages should
+ be listed there.
<p>After you have verified that <prgn/apt-get/ should work fine,
run:
@@ -740,7 +741,7 @@
dependencies in place. <package/apt/ does not allow broken package
dependencies to exist on a system.
- <sect1 id="trouble">Possible issues during or after upgrade
+ <sect1 id="trouble">Possible Issues During or After Upgrade
<p>Sometimes it's necessary to enable APT::Force-LoopBreak option in
APT to be able to temporarily remove an essential package due to a
@@ -770,11 +771,12 @@
dpkg --install /path/to/packagename.deb
</example>
- After these things, you should be able to resume the upgrade using
- the previously described <tt/dist-upgrade/ commands.
+ After fixing things up, you should be able to resume the upgrade
+ by repeating the previously described <tt/dist-upgrade/
+ commands.
<p>During the upgrade, you will be asked questions to configure or
- re-configure several packages. When/if you are asked if any file in
+ re-configure several packages. When you are asked if any file in
the <file>/etc/init.d</file> or <file>/etc/terminfo</file>
directories, or the <file>/etc/manpath.config</file> file should be
replaced by the package maintainer's version, it's usually necessary
@@ -782,14 +784,16 @@
to the old versions, since they will be saved with a <tt/.dpkg-old/
extension.
- <p>If you're not sure what to do, write down the name of the package
- or file, and sort things out on a later time. You can search in the
- typescript to re-view the information that was on the screen during
- the upgrade.
-
- <p>When <tt>apt-get dist-upgrade</tt> is done, the "formal" upgrade
- is finished, but there are some other things that should be taken
- care of <em/before/ the next reboot.
+ <p>If you're not sure what to do, write down the name of the
+ package or file, and sort things out at a later time. You can
+ search in the typescript file to review the information that
+ was on the screen during the upgrade.
+
+ <sect1 id="trouble">ToDo Before the Next Reboot
+
+ <p>When <tt>apt-get dist-upgrade</tt> has finished, the
+ "formal" upgrade is complete, but there are some other things
+ that should be taken care of <em/before/ the next reboot.
<p>Most importantly, packages <package/locales/ and
<package/util-linux/ may need to be installed. This can be done
@@ -822,7 +826,7 @@
example, the old <package/gimp-smotif/ and <package/gimp-dmotif/
packages were replaced by <package/gimp/ in &debian; 2.1.
<!-- Some potato examples would be better; maybe I can provide
- some at a later time - JAB --> You can either install the
+ some at a later time - JAB --> You can either install the
new package via <prgn/dselect/ (which will then show a "dependency
conflict resolution" screen indicating that the old packages should
be removed), or by using:
@@ -846,14 +850,15 @@
<p>The same applies to <package/manpages-dev/, which was split off
from <package/manpages/.
- <p>Please refer to the Release Notes document for &debian; 2.1 for
- more information about those packages that were split in that
- release; go back and read <ref id="renames"> and <ref id="splits">
- to see the list of packages split in this release.
+ <p>Please refer to the Release Notes document for previous
+ releases of &debian; for more information about packages that
+ were split in that release; go back and read <ref
+ id="renames"> and <ref id="splits"> to see the list of
+ packages split in this release.
<![ %not-sparc [
<![ %not-alpha [
- <p>If you were upgrading from Debian version 2.0 or earlier, AND
+ <p>If you were upgrading from Debian version 2.0 or earlier, <em/and/
have the X Window System installed, give the following commands:
<example>
@@ -881,9 +886,9 @@
]]>
]]>
-<![ %i386 [ <p>Then, if you were upgrading from a &debian; version 1.x (i.e.
+<![ %i386 [ <p>If you were upgrading from a &debian; version 1.x (i.e.
lower than 2.0), the old system was using the `libc5' library, while
- the upgraded system uses the `libc6' version. The new library has a
+ the upgraded system uses the `libc6' version. The new library has
changed the format for the <file/utmp/ and <file/wtmp/ files; you
can check this by trying the <prgn/last/ command. To solve this, a
reboot is necessary, but first copy the old file and empty the
@@ -915,64 +920,59 @@
<chapt id="moreinfo">
<heading>More information on Debian GNU/Linux</heading>
<sect id="morereading">
- <heading>Further reading</heading>
- <p>
- Beyond these release notes and the installation
- guide further documentation on Debian GNU/Linux is
- available from the Debian Documentation Project,
- whose goal is to create high quality documentation
- for Debian users and developers. They have
- documenation ranging from the Debian Guide to the
- Debian New Maintainers Guide to the Debian FAQ. For
- full details of the resources available see their
- website at <url id="http://www.debian.org/doc/ddp";>.
- </p>
- <p>
- Documentation for individual packages is installed
- into <file>/usr/share/doc/<var>package</var></file>,
- this may include copyright information, Debian
- specific details and any upstream documentation.
- </p>
+ <heading>Further Reading</heading>
+ <p>
+ Beyond these release notes and the installation guide further
+ documentation on Debian GNU/Linux is available from the
+ Debian Documentation Project, whose goal is to create high
+ quality documentation for Debian users and developers.
+ Documentation including the Debian Guide, Debian New
+ Maintainers Guide, and Debian FAQ are available, and many
+ more. For full details of the resources available see the DDP
+ website at <url id="http://www.debian.org/doc/ddp";>.
+ </p>
+ <p>
+ Documentation for individual packages is installed
+ into <file>/usr/share/doc/<var>package</var></file>,
+ this may include copyright information, Debian
+ specific details and any upstream documentation.
+ </p>
</sect>
<sect id="gethelp">
- <heading>Getting help</heading>
- <p>
- There are many sources of help, advice and support
- for Debian users, these should only be considered if
- research into documentation of the issue has
- exhausted all sources. This section provides a short
- introduction into these which may be helpful for new
- Debian users.
- </p>
- <sect1 id="lists">
- <heading>Mailing lists</heading>
- <p>
- The mailing list mostly to be of interest to Debian users is debian-user, for information on th
-is list
- and for details of how to subscribe see <url id="http://lists.debian.org";>. Please check the ar
-chives
- available, for answers to your question
- prior to posting and also adhere to standard list
- etiquette.
- </p>
- </sect1>
- <sect1 id="irc">
- <heading>Internet Relay Chat</heading>
- <p>
- Debian has an IRC channel dedicated to the
- support and aid of Debian users located on
- the Open Projects IRC network which is
- dedicated to providing collaborative
- information sharing resources for the Open
- Source community. To access the channel
- point your favourite IRC client at
- irc.openprojects.net and join #debian.
- </p>
- <p>
- Please follow the channel guidelines, respecting other users fully. For more information on
- Open Projects please visit the <url id="http://www.openprojects.net"; name="website">.
- </p>
- </sect1>
+ <heading>Getting Help</heading>
+ <p>
+ There are many sources of help, advice and support for Debian
+ users, but these should only be considered if research into
+ documentation of the issue has exhausted all sources. This
+ section provides a short introduction into these which may be
+ helpful for new Debian users.
+ </p>
+ <sect1 id="lists">
+ <heading>Mailing lists</heading>
+ <p>
+ The mailing lists of most interest to Debian users are the
+ debian-user (English) and other debian-user-<var/language/ lists
+ (for other languages). For information on these lists and details of
+ how to subscribe see <url id="http://lists.debian.org";>. Please
+ check the archives for answers to your question prior to posting and
+ also adhere to standard list etiquette.
+ </p>
+ </sect1>
+ <sect1 id="irc">
+ <heading>Internet Relay Chat</heading>
+ <p>
+ Debian has an IRC channel dedicated to the support and aid of Debian
+ users located on the Open Projects IRC network which is dedicated to
+ providing collaborative information sharing resources for the Open
+ Source community. To access the channel point your favourite IRC
+ client at irc.openprojects.net and join #debian.
+ </p>
+ <p>
+ Please follow the channel guidelines, respecting other users
+ fully. For more information on Open Projects please visit the <url
+ id="http://www.openprojects.net"; name="website">.
+ </p>
+ </sect1>
</sect>
</chapt>
</book>
Reply to: