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

Release Notes - Proposed last minute changes



I propose to make the following last changes to the release notes.

The first change (in [a]) is in reaction to [1].
The second change (in [b]) is in reaction to upgrade reports #309548 [2]
and #310490 [3].
The third change (in [c]) improves the description of udev somewhat.

Comments on the proposed texts ASAP please as I intend to commit these
changes withing the next 5 hours.

Cheers,
FJP

[a] http://www.debian.org/releases/testing/i386/release-notes/ch-upgrading.en.html#s-backup
[b] http://www.debian.org/releases/testing/i386/release-notes/ch-upgrading.en.html#s-upgrading_aptitude
[c] http://www.debian.org/releases/testing/i386/release-notes/ch-information.en.html#s-2.6-udev
[1] http://lists.debian.org/debian-devel/2005/05/msg01380.html
[2] http://lists.debian.org/debian-testing/2005/05/msg00104.html
[3] http://lists.debian.org/debian-testing/2005/05/msg00281.html


@@ -330,6 +330,13 @@
           <file>/etc</file>, <file>/var/lib/dpkg</file> and the output of
           <tt>dpkg --get-selections "*"</tt> (the quotes are important).</p>

+          <p>You may also want to make a backup of your <file>/home</file>
+          directory. Some applications (e.g. mozilla, some KDE applications)
+          are known to overwrite existing user settings with new defaults
+          when a new version of the application is first started by a user.
+          Having a backup of the hidden files and directories in user's home
+          directories may help you to restore or recreate the old settings.</p>
+
           <p>It's wise to inform all users in advance of any upgrades you're
           planning, although users accessing your system via SSH (at least)
           shouldn't notice much during the upgrade, and may want to continue
@@ -816,6 +823,14 @@
           the proposed changes, especially packages that will be removed by the
           upgrade, before you confirm.</p>

+          <p>In some cases if a large number of packages is listed for removal,
+          you may be able to reduce this list by "pre-upgrading" selected other
+          packages alongside <package/aptitude/. An example may clarify this.
+          During upgrade tests for systems having KDE installed, we have seen
+          that this step would cause removal of a large number of KDE packages
+          and/or perl. The solution proved to be to <tt>install aptitude perl</tt>
+          instead of <tt>install aptitude</tt>.</p>
+
         </sect1>

         <sect1 id="upgrading_doc-base"><heading>Upgrading doc-base</heading>
@@ -1277,10 +1292,11 @@
         <heading>Switching to 2.6 may activate udev</heading>

         <p><package/udev/ is a userspace implementation of devfs. It is mounted
-        over the <file>/dev/</file> directory and will dynamically populate that
-        directory with devices as kernel modules are loaded. It works together
-        with <package/hotplug/ to detect new devices. <package/udev/ works
-        only with 2.6 kernels.</p>
+        over the <file>/dev/</file> directory and will populate that directory
+        with devices supported by the kernel. It will also dynamically add and
+        remove devices as kernel modules are loaded or unloaded respectively,
+        working together with <package/hotplug/ to detect new devices.
+        <package/udev/ works only with 2.6 kernels.</p>

         <p>As <package/udev/ is automatically installed as a dependency of
         e.g. <package/gnome/, there is a chance that upgrading to a 2.6 kernel

Attachment: pgpEBVV1jLUKf.pgp
Description: PGP signature


Reply to: