Parent Directory
| 
Revision Log
| 
Patch
| revision 2853 by jseidel, Fri Feb 4 21:15:28 2005 UTC | revision 4627 by joy, Thu May 3 07:58:24 2007 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.15 2005-02-04 21:15:28 jseidel Exp $"> | <!entity docid "$Id: release-notes.en.sgml,v 1.289 2007-05-03 07:58:24 joy Exp $"> |
| 5 | ]> | ]> |
| 6 | ||
| 7 | <!-- Be careful with automatic reformatting. Please note that the indentation | <!-- Be careful with automatic reformatting. Please note that the indentation |
| # | Line 10 | Line 10 |
| 10 | <debiandoc> | <debiandoc> |
| 11 | <book> | <book> |
| 12 | <titlepag> | <titlepag> |
| 13 | <title>Release Notes for &debian; &release; (`&releasename'), &arch-title;</title> | <title>Release Notes for &debian; &release; ("&releasename;"), &arch-title;</title> |
| 14 | <author> | <author> |
| 15 | <name>Josip Rodin, Bob Hilliard, Adam Di Carlo, Anne Bezemer, Rob | <name>Josip Rodin, Bob Hilliard, Adam Di Carlo, Anne Bezemer, Rob |
| 16 | Bradford (current)</name><email></email> | Bradford, Frans Pop (current), Andreas Barth (current), Javier |
| 17 | Fernández-Sanguino Peña (current), Steve Langasek | |
| 18 | (current)</name><email></email> | |
| 19 | </author> | </author> |
| 20 | <author> | <author> |
| 21 | <name></name><email>debian-doc@lists.debian.org</email> | <name></name><email>debian-doc@lists.debian.org</email> |
| # | Line 21 | Line 23 |
| 23 | <version>&docid;</version> | <version>&docid;</version> |
| 24 | </titlepag> | </titlepag> |
| 25 | <toc detail="sect1"> | <toc detail="sect1"> |
| 26 | <chapt id="about"><heading>What's New in the Release Notes</heading> | <chapt id="about"><heading>Introduction</heading> |
| 27 | ||
| 28 | <p>[The most recent version of this document is always available at | <p>The primary goals of these Release Notes are to inform users |
| 29 | <url id="&url-release-notes;">. If your version is more than a month | of major changes in this release of the &debian; distribution, to |
| 30 | old, you might wish to download the latest version.]</p> | provide information on how to upgrade safely from the previous |
| 31 | release to the current release and finally to inform users of known potential | |
| 32 | <p>Please note that previous editions of the release notes contained | issues they could encounter when upgrading to or using the |
| 33 | information about upgrading from releases older than than the previous | &releasename; release.</p> |
| 34 | release. However such content often complicated the documentation so we | |
| 35 | have decided to only discuss upgrades from &debian; 3.0 ('woody'). If | <p>Note that it is impossible to list every known issue and that |
| 36 | you need to upgrade from older releases please read previous editions of | therefore a selection has been made based on a combination of the |
| 37 | the release notes.</p> | expected prevalence and impact of issues.</p> |
| 38 | ||
| 39 | <p>The most recent version of this document is always available at <url | |
| 40 | id="&url-release-notes;">. If the version you are reading is more than a | |
| 41 | month old<footnote>As listed on the front page of the PDF version and in | |
| 42 | the footer of the HTML version.</footnote>, you might wish to obtain | |
| 43 | the latest version.</p> | |
| 44 | ||
| 45 | <p>Please note that we only support and document upgrading from the | |
| 46 | previous release of Debian (in this case, the upgrade from | |
| 47 | &oldreleasename;). If you need to upgrade from older releases, we suggest | |
| 48 | you read previous editions of the release notes and upgrade to | |
| 49 | &oldreleasename; first.</p> | |
| 50 | ||
| 51 | <sect id="bug_reports"><heading>Reporting bugs on this document</heading> | |
| 52 | ||
| 53 | <p>We have attempted to test all the different upgrade steps | |
| 54 | described in this document and we have also tried to anticipate all | |
| 55 | the possible issues our users might encounter.</p> | |
| 56 | ||
| 57 | <p>Nevertheless, if you think you have found any bug in this | |
| 58 | documentation (incorrect information or information that is missing), | |
| 59 | please file a bug in the <url id="&url-bts;" name="bug tracking | |
| 60 | system"> against the <package>release-notes</package> package.</p> | |
| 61 | ||
| 62 | </sect> | |
| 63 | ||
| 64 | <sect id="upgrade_reports"><heading>Contributing upgrade reports</heading> | |
| 65 | <p>We welcome any information from users related to upgrades from | |
| 66 | &oldreleasename; to &releasename;. If you are willing to share information | |
| 67 | please file a bug in the <url id="&url-bts;" name="bug tracking system"> | |
| 68 | against the <package>upgrade-reports</package> package with your results. | |
| 69 | We request that you compress any attachments that are included (using | |
| 70 | <prgn/gzip/).</p> | |
| 71 | ||
| 72 | <p>Please include the following information when submitting your upgrade report: | |
| 73 | ||
| 74 | <list> | |
| 75 | ||
| 76 | <!-- TODO: any more things to add here? --> | |
| 77 | <item><p>The status of your package database before and after the | |
| 78 | upgrade: <prgn/dpkg/'s status database available at | |
| 79 | <file>/var/lib/dpkg/status</file> and <prgn/aptitude/'s package | |
| 80 | state information, available at | |
| 81 | <file>/var/lib/aptitude/pkgstates</file>. You should have made a | |
| 82 | backup before the upgrade as described at <ref id="data-backup">, | |
| 83 | but you can also find backups of this information in | |
| 84 | <file>/var/backups</file>.</p></item> | |
| 85 | ||
| 86 | <item><p>Session logs using <prgn/script/, as described in | |
| 87 | <ref id="record_session">.</p></item> | |
| 88 | ||
| 89 | <item><p>Your <prgn/aptitude/ logs, available at <file>/var/log/aptitude</file>.</p></item> | |
| 90 | ||
| 91 | </list></p> | |
| 92 | ||
| 93 | <p>Note: you should take some time to review and remove any sensitive and/or confidential | |
| 94 | information from the logs before including them in a bug report as the information | |
| 95 | will be published in a public database.</p> | |
| 96 | ||
| 97 | </sect> | |
| 98 | ||
| 99 | <sect id="sources"><heading>Sources for this document</heading> | |
| 100 | <p>This document is generated using <package>debiandoc-sgml</package>. | |
| 101 | Sources for the Release Notes | |
| 102 | are available in the CVS repository of the <em>Debian Documentation Project</em>. | |
| 103 | You can use the <url id="&url-cvs-release-notes;" name="web | |
| 104 | interface"> to access its files individually through the web and see | |
| 105 | their changes. For more information on how to access the CVS please | |
| 106 | consult the <url id="&url-ddp-cvs-info;" name="Debian Documentation Project CVS pages">. | |
| 107 | </p> | |
| 108 | ||
| 109 | </sect> | |
| 110 | <!-- | |
| 111 | <sect id="changes"><heading>Changes in the Release Notes</heading> | |
| 112 | ||
| 113 | <p>This section lists changes in the Release Notes since the original | |
| 114 | version that was published with &debian; &release;r0. Minor textual | |
| 115 | corrections are omitted.</p> | |
| 116 | ||
| 117 | <p><list> | |
| 118 | ||
| 119 | <item><p>Description of change.</p></item> | |
| 120 | ||
| 121 | </list></p> | |
| 122 | ||
| 123 | </sect> | |
| 124 | --> | |
| 125 | ||
| 126 | </chapt> | </chapt> |
| <chapt id="whats-new"><heading>What's New in &debian; &release;</heading> | ||
| 127 | ||
| 128 | <p>The list of supported architectures has not changed since the | <chapt id="whats-new"><heading>What's new in &debian; &release;</heading> |
| 129 | previous release, &debian; 3.0 ('woody'). Here is the full list of | |
| 130 | architectures for this release.</p> | <p>This release adds official support for the AMD64 architecture which |
| 131 | supports 64-bit processors from both Intel (EM64T) and AMD (AMD64). | |
| 132 | During the previous release, &debian; 3.1 ('sarge'), an unofficial | |
| 133 | version of this port was available. | |
| 134 | <![ %amd64 [ | |
| 135 | Upgrading from this unofficial version should be possible using these | |
| 136 | Release Notes, but is not officially supported by Debian. | |
| 137 | ]]> | |
| 138 | </p> | |
| 139 | ||
| 140 | <p>Official support for the Motorola 680x0 ('m68k') architecture has been | |
| 141 | dropped because it did not meet the criteria set by the Debian Release | |
| 142 | Managers. The most important underlying reasons are performance and limited | |
| 143 | upstream support for essential toolchain components. However, the m68k port | |
| 144 | is expected to remain active and available for installation even if not a | |
| 145 | part of this official stable release.</p> | |
| 146 | ||
| 147 | <p>The following are the officially supported architectures for | |
| 148 | &debian; &releasename;:</p> | |
| 149 | ||
| 150 | <p> | <p> |
| 151 | <list> | <list> |
| 152 | <item><p>Intel x86 ('i386')</p></item> | <item><p>Intel x86 ('i386')</p></item> |
| <item><p>Motorola 680x0 ('m68k')</p></item> | ||
| 153 | <item><p>Alpha ('alpha')</p></item> | <item><p>Alpha ('alpha')</p></item> |
| 154 | <item><p>SPARC ('sparc')</p></item> | <item><p>SPARC ('sparc')</p></item> |
| 155 | <item><p>PowerPC ('powerpc')</p></item> | <item><p>PowerPC ('powerpc')</p></item> |
| 156 | <item><p>ARM ('arm')</p></item> | <item><p>ARM ('arm')</p></item> |
| 157 | <item><p>MIPS ('mips' (Big endian) and 'mipsel' (Little endian))</p></item> | <item><p>MIPS ('mips' (big-endian) and 'mipsel' (little-endian))</p></item> |
| 158 | <item><p>Intel Itanium ('ia64')</p></item> | <item><p>Intel Itanium ('ia64')</p></item> |
| 159 | <item><p>HP PA-RISC ('hppa')</p></item> | <item><p>HP PA-RISC ('hppa')</p></item> |
| 160 | <item><p>S/390 ('s390')</p></item> | <item><p>S/390 ('s390')</p></item> |
| 161 | <item><p>AMD64 ('amd64')</p></item> | |
| 162 | </list> | </list> |
| 163 | </p> | </p> |
| 164 | ||
| # | Line 61 | Line 167 |
| 167 | name="Debian port web pages">.</p> | name="Debian port web pages">.</p> |
| 168 | ||
| 169 | <![ %secondrelease [ | <![ %secondrelease [ |
| 170 | <p>This is only the second official release of &debian; for the | <p>This is only the second official release of &debian; for the |
| 171 | &arch-title; architecture. We feel that it has proven itself | &arch-title; architecture. We feel that it has proven itself |
| 172 | sufficiently to be released. However, because it has not had the | sufficiently to be released. However, because it has not had the |
| 173 | exposure (and hence testing by users) that our other releases on | exposure (and hence testing by users) that our releases on |
| 174 | other architectures have had, you may encounter a few bugs. Please | other architectures have had, you may encounter a few bugs. Please |
| 175 | use our <url id="&url-bts;" name="bug tracking system"> to report | use our <url id="&url-bts;" name="bug tracking system"> to report |
| 176 | any problems; make sure to mention the fact that the bug is on the | any problems; make sure to mention the fact that the bug is on the |
| 177 | &architecture; platform.</p> | &architecture; platform.</p> |
| 178 | ]]> | |
| 179 | ||
| 180 | <![ %arm [ | |
| 181 | <sect id="new-arch"><heading>What's new for &arch-title;?</heading> | |
| 182 | <p>RiscPC (RPC) support is incomplete and will be removed after etch. | |
| 183 | While a kernel for RiscPC is still provided in etch, the installer | |
| 184 | doesn't support this system.</p> | |
| 185 | ||
| 186 | <p>Support for Intel's IXP4xx platform has been added. The installer | |
| 187 | includes support for the Linksys NSLU2, a small and inexpensive device | |
| 188 | which allows the usage of attached storage through USB. More | |
| 189 | information about Debian on the NSLU2 can be found at | |
| 190 | <url id="http://www.cyrius.com/debian/nslu2/">.</p> | |
| 191 | ||
| 192 | <p>Support has also been added for Intel's I/O Processor (IOP) platform. | |
| 193 | Specifically, &debian; &release; supports IOP 32x based devices. Two Network | |
| 194 | Attached Storage (NAS) devices based on an IOP chip are supported in | |
| 195 | the installer: the GLAN Tank from IO-Data and the Thecus N2100. See | |
| 196 | <url id="http://www.cyrius.com/debian/iop/">.</p> | |
| 197 | </sect> | |
| 198 | ]]> | |
| 199 | ||
| 200 | <![ %mips-mipsel [ | |
| 201 | <sect id="new-arch"><heading>What's new for &arch-title;?</heading> | |
| 202 | <![ %mipsel [ | |
| 203 | <p>DECstation support is incomplete and untested in etch and will be | |
| 204 | removed completely after this release. This includes both DECstation | |
| 205 | variants previously supported in Debian, r3k-kn02 and r4k-kn04.</p> | |
| 206 | ||
| 207 | <p>Installations on MIPS based Cobalt machines (Qube 2700, RaQ1, Qube2, | |
| 208 | RaQ2) are now possible without the use of a serial console. By | |
| 209 | default, installations on Cobalt are now done via SSH. See | |
| 210 | <url id="http://www.cyrius.com/debian/cobalt/"> for more information.</p> | |
| 211 | ]]> | |
| 212 | <![ %mips [ | |
| 213 | <p>Support for SGI's IP32 platform has been added. The IP32 platform | |
| 214 | consists of SGI O2 machines with R5000, R5200 or RM7000 processors. | |
| 215 | Installation is possible via frame buffer or the serial console.</p> | |
| 216 | ]]> | |
| 217 | <p>Support for Broadcom's SB1A evaluation board BCM91480B ("BigSur"), | |
| 218 | which is based on the BCM1480 quad-core chip, has been added, both to | |
| 219 | the kernel and the installer. This board is supported both in little | |
| 220 | and big endian mode.</p> | |
| 221 | ||
| 222 | <p>Support for a Qemu machine has been added. The Qemu/MIPS machine | |
| 223 | emulates a classic ISA PC style machine with a MIPS 4Kc CPU.</p> | |
| 224 | </sect> | |
| 225 | ]]> | |
| 226 | ||
| 227 | <![ %powerpc [ | |
| 228 | <sect id="new-arch"><heading>What's new for &arch-title;?</heading> | |
| 229 | <p>This release adds support for 64bit PowerPC architectures (IBM | |
| 230 | pSeries, Apple G5 powermacs). Support for the Apple Apus subarchitecture | |
| 231 | has been dropped; the Apple Nubus subarchitecture is also not supported.</p> | |
| 232 | </sect> | |
| 233 | ]]> | ]]> |
| 234 | ||
| 235 | <!-- | |
| 236 | <p>&debian; &release; for the &arch-title; architecture ships with | <p>&debian; &release; for the &arch-title; architecture ships with |
| 237 | kernel version &kernelversion;.</p> | kernel version &kernelversion;.</p> |
| 238 | <![ %available-2.6 [ | --> |
| <p>On the &arch-title; architecture a 2.6 kernel is also available, | ||
| this has kernel version &kernelversion-2.6;. Note that Debian's 2.6.8 | ||
| kernel packages include the 2.6.8.1 kernel release and selected other | ||
| patches.</p> | ||
| ]]> | ||
| <sect id="newinst"><heading>What's New in the Installation System?</heading> | ||
| <p>The old &debian; installation system has been replaced by a | ||
| completely new installation system called | ||
| <prgn>debian-installer</prgn>. The new installation system is | ||
| modular in design and so has been developed with extensibility in | ||
| mind.</p> | ||
| <p>Some of the new features in the installation system include | ||
| support for booting off USB flash devices, choosing | ||
| <prgn>aptitude</prgn> to install packages in the first-boot stage | ||
| and support for the <prgn>XFS</prgn> file system and | ||
| <prgn>LVM</prgn> (a volume management tool).</p> | ||
| <p>For full details of the new Debian installation system, users | ||
| are advised to read the Debian Installation Guide included on the | ||
| first CD or at <url id="&url-install-manual;">.</p> | ||
| <![ %i386 [ | ||
| <p>Kernel images are available in various "flavours". These | ||
| flavours each support a different set of hardware. The flavours | ||
| available in &debian; &release; for &arch-title; are:</p> | ||
| 239 | ||
| 240 | <p> | <sect id="newdistro"><heading>What's new in the distribution?</heading> |
| <taglist> | ||
| <tag>vanilla</tag> | ||
| <item><p>The standard kernel package available in Debian. This | ||
| includes almost all drivers supported by Linux built as | ||
| modules. Including drivers for network devices, SCSI devices, | ||
| sound cards, Video4Linux devices, etc. The | ||
| `vanilla' flavour includes one boot, one root and two | ||
| driver disks.</p></item> | ||
| <tag>speakup</tag> | ||
| <item><p>This is almost the same as the vanilla kernel above | ||
| but with support for braille displays. A complete list of | ||
| supported models may be found in the brltty documentation. | ||
| This flavour includes one boot, one root and one driver floppy | ||
| disk image.<p></item> | ||
| </taglist> | ||
| <!-- FJP: I feel the info about floppies should be removed from this table as | ||
| floppies are no longer the most used installation method. --> | ||
| <p>The kernel config files for these flavours can be found in their | ||
| respective directories in a file named 'kernel-config'.</p> | ||
| 241 | ||
| 242 | <!-- TODO (jfs): numbers could be entities so that updating them was easier, like | |
| 243 | in the FAQ --> | |
| 244 | <!-- TODO: Numbers need to be reviewed, these values have been obtained | |
| 245 | using the changes-release script --> | |
| 246 | <p>This new release of Debian again comes with a lot more software | |
| 247 | than its predecessor &oldreleasename;; the distribution includes | |
| 248 | over &packages-new; new packages, for a total of over &packages-total; packages. Most | |
| 249 | of the software in the distribution has been updated: over &packages-updated; | |
| 250 | software packages (this is &packages-update-percent;% of all packages in &oldreleasename;). | |
| 251 | Also, a significant number of packages (over &packages-removed;, &packages-removed-percent;% of the | |
| 252 | packages in &oldreleasename;) have for various reasons been removed | |
| 253 | from the distribution. You will not see any updates for these | |
| 254 | packages and they will be marked as 'obsolete' in package management | |
| 255 | front-ends.</p> | |
| 256 | ||
| 257 | <p>With this release, &debian; switches from XFree86 to the 7.1 | |
| 258 | release of X.Org, which includes support for a greater range of | |
| 259 | hardware and better autodetection. This allows the use of Compiz, | |
| 260 | which is one of the first compositing window managers for the X | |
| 261 | Window System, taking full advantage of hardware | |
| 262 | OpenGL acceleration for supported devices.</p> | |
| 263 | ||
| 264 | <p>&debian; again ships with several desktop applications and environments. | |
| 265 | Among others it now includes the desktop environments GNOME | |
| 266 | 2.14<footnote>With some modules from GNOME 2.16.</footnote>, KDE 3.5.5a, | |
| 267 | and Xfce 4.4. Productivity applications have also been upgraded, | |
| 268 | including the office suites OpenOffice.org 2.0.4a and KOffice 1.6 as | |
| 269 | well as GNUcash 2.0.5, GNUmeric 1.6.3 and Abiword 2.4.6.</p> | |
| 270 | ||
| 271 | <p>Updates of other desktop applications include the upgrade to | |
| 272 | Evolution 2.6.3 and Gaim 2.0. The Mozilla suite has also been updated, | |
| 273 | with a rename of the main programs: <prgn>iceweasel</prgn> | |
| 274 | (version 2.0.0.2) is the unbranded <prgn>Firefox</prgn> web browser | |
| 275 | and <prgn/icedove/ (version 1.5) is the unbranded <prgn/Thunderbird/ | |
| 276 | mail client.</p> | |
| 277 | ||
| 278 | <p>Among many others, this release also includes the following software | |
| 279 | updates:</p> | |
| 280 | ||
| 281 | <p><list> | |
| 282 | ||
| 283 | <item>the GNU C library, version 2.3.6</item> | |
| 284 | ||
| 285 | <item>the GNU Compiler Collection 4.1 as default compiler</item> | |
| 286 | ||
| 287 | <item>language interpreters: Python 2.4, PHP 5.2</item> | |
| 288 | ||
| 289 | <item>server software: | |
| 290 | ||
| 291 | <p><list> | |
| 292 | <item>e-mail servers: Exim 4.63 (default email server | |
| 293 | for new installations), Postfix 2.3, Courier 0.53, Cyrus 2.2</item> | |
| 294 | ||
| 295 | <!-- TODO: Cherokee, lighttpd, and Tomcat 5 are NEW --> | |
| 296 | <!-- Note: No significant changes for Roxen4, Boa, and thttpd --> | |
| 297 | <item>web servers: Apache 2.2, fnord 1.10</item> | |
| 298 | ||
| 299 | <item>database servers: MySQL 5.0.32, PostgreSQL 8.1</item> | |
| 300 | ||
| 301 | <item>the OpenSSH server, version 4.3</item> | |
| 302 | ||
| 303 | <item>name servers: Bind 9.3, maradns 1.2</item> | |
| 304 | ||
| 305 | <item>directory server: OpenLDAP 2.3</item> | |
| 306 | ||
| 307 | <!-- FIXME (JFS): List other server software? RADIUS? Streaming ? --> | |
| 308 | </list></p> | |
| 309 | ||
| 310 | </list></p> | |
| 311 | ||
| 312 | ||
| 313 | <p>The official &debian; distribution now ships on 19 to 23 | |
| 314 | binary CDs (depending on the architecture) and a similar number of | |
| 315 | source CDs. A DVD version of the distribution is also available.</p> | |
| 316 | ||
| 317 | <!-- FIXME: Note on LSB support? (3.1?) --> | |
| 318 | ||
| 319 | <sect1 id="pkgmgmt"><heading>Package management</heading> | |
| 320 | ||
| 321 | <!-- FIXME (vorlon): is aptitude news for etch, does it belong here? --> | |
| 322 | <p><prgn/aptitude/ is the preferred program for package management | |
| 323 | from console. | |
| 324 | <prgn/aptitude/ supports most command line operations of <prgn/apt-get/ | |
| 325 | and has proven to be better at dependency resolution than <prgn/apt-get/. | |
| 326 | If you are still using <prgn/dselect/, you should switch to | |
| 327 | <package/aptitude/ as the official frontend for package management.</p> | |
| 328 | <p>For &releasename; an advanced conflict resolving mechanism has been | |
| 329 | implemented in <prgn/aptitude/ that will try to find the best solution | |
| 330 | if conflicts are detected because of changes in dependencies between | |
| 331 | packages.</p> | |
| 332 | ||
| 333 | <!-- FIXME: More content needed here? --> | |
| 334 | <p><em/Secure APT/ is now available in &releasename;. This feature adds | |
| 335 | extra security to &debian; systems by easily supporting strong | |
| 336 | cryptography and digital signatures to validate downloaded packages. | |
| 337 | This release includes the <prgn/apt-key/ tool for adding new keys to | |
| 338 | apt's keyring, which by default includes only the current Debian archive | |
| 339 | signing key, provided in the <package>debian-archive-keyring</package> | |
| 340 | package.</p> | |
| 341 | ||
| 342 | <p>In its default configuration, <prgn/apt/ will now warn if packages | |
| 343 | are downloaded from sources that are not authenticated. Future releases | |
| 344 | might force all packages to be verified before downloading them. | |
| 345 | Administrators of unofficial apt repositories are encouraged to | |
| 346 | generate a cryptographic key and sign their Release files, as well | |
| 347 | as providing a secure way to distribute their public keys.</p> | |
| 348 | ||
| 349 | <p>For more information please read <manref name="apt" section="8">, the | |
| 350 | <url | |
| 351 | id="http://www.debian.org/doc/manuals/securing-debian-howto/ch7#s-deb-pack-sign" | |
| 352 | name="Package signing in Debian"> chapter of the <em/Securing Debian | |
| 353 | Manual/ and the <url id="http://wiki.debian.org/SecureApt" | |
| 354 | name="Debian Wiki">.</p> | |
| 355 | ||
| 356 | <p>Another feature that was added in <prgn/apt/ is the ability to | |
| 357 | download only the changes in <file/Packages/ files since your last | |
| 358 | update. More about this feature in <ref id="apt-pdiff">.</p> | |
| 359 | ||
| 360 | </sect1> | |
| 361 | <sect1 id="volatile"><heading>debian-volatile now an official service</heading> | |
| 362 | ||
| 363 | <p>The <em/debian-volatile/ service that was introduced as an | |
| 364 | unofficial service with the release of &oldreleasename; has now | |
| 365 | become an official &debian; service.</p> | |
| 366 | ||
| 367 | <p>This means that it now uses a <tt/.debian.org/ address<footnote> | |
| 368 | The old <tt/volatile.debian.net/ address will also remain valid for | |
| 369 | the time being. </footnote>. Please make sure to update | |
| 370 | your <file>/etc/apt/sources.list</file> accordingly if you were | |
| 371 | already using this service.</p> | |
| 372 | ||
| 373 | <p><em/debian-volatile/ allows users to easily | |
| 374 | update stable packages that contain information that quickly goes out | |
| 375 | of date. Examples are a virus scanner's signatures list or a spam | |
| 376 | filter's pattern set. For more information and a list of mirrors, | |
| 377 | please see the archive's <url id="&url-debian-volatile;" | |
| 378 | name="web page">.</p> | |
| 379 | ||
| 380 | </sect1> | |
| 381 | </sect> | |
| 382 | ||
| 383 | <sect id="system-changes"><heading>System improvements</heading> | |
| 384 | ||
| 385 | <p>There have been a number of changes in the distribution that will | |
| 386 | benefit new installations of &releasename;, but may not be automatically | |
| 387 | applied on upgrades from &oldreleasename;. This section gives an | |
| 388 | overview of the most relevant changes. | |
| 389 | </p> | |
| 390 | ||
| 391 | <p><taglist> | |
| 392 | ||
| 393 | <!-- Bug #301138, fixed in etch --> | |
| 394 | <tag>Priority for basic development packages lowered</tag> | |
| 395 | <item><p>A number of development packages that used to be priority | |
| 396 | <em/standard/ are now priority <em/optional/, which means they will | |
| 397 | no longer be installed by default. | |
| 398 | This includes the standard C/C++-compiler, <package>gcc</package>, | |
| 399 | as well as some other software (<package>dpkg-dev</package>, | |
| 400 | <package>flex</package>, <package>make</package>) and development | |
| 401 | headers (<package>libc6-dev</package>, | |
| 402 | <package>linux-kernel-headers</package>).</p> | |
| 403 | <!-- TODO: Point to the bug report for the full list of packages in case | |
| 404 | users want to remove them ? --> | |
| 405 | <p>If you do wish to have these packages on your system, the easiest way | |
| 406 | to install them is by installing <package/build-essential/, which will | |
| 407 | pull in most of them.</p> | |
| 408 | </item> | |
| 409 | ||
| 410 | <tag>SELinux priority standard, but not enabled by default</tag> | |
| 411 | <item><p>The packages needed for SELinux support have been | |
| 412 | promoted to priority <em/standard/. This means that they will be | |
| 413 | installed by default during new installations. For existing systems | |
| 414 | you can install SELinux using: | |
| 415 | <example> | |
| 416 | # aptitude install selinux-basics | |
| 417 | </example></p> | |
| 418 | ||
| 419 | <p>Note that SELinux support is <em/not/ enabled by default. Information | |
| 420 | on setting up and enabling SELinux can be found on the | |
| 421 | <url id="&url-wiki-selinux;" name="Debian Wiki">. | |
| 422 | </p></item> | |
| 423 | ||
| 424 | <tag>New default inet superdaemon</tag> | |
| 425 | <item><p>The default inet superdaemon for &releasename; is | |
| 426 | <package>openbsd-inetd</package> instead of <package>netkit-inetd</package>. | |
| 427 | It will not be started if no services are configured, which is true by | |
| 428 | default. The new default daemon will be installed automatically on | |
| 429 | upgrade. | |
| 430 | </p></item> | |
| 431 | ||
| 432 | <tag>Default <prgn/vi/ clone changed</tag> | |
| 433 | <item><p>The <prgn/vi/ clone installed by default is now a compact version | |
| 434 | of <prgn/vim/ (<package/vim-tiny/) instead of <package/nvi/.</p></item> | |
| 435 | ||
| 436 | <tag>Changes in default features for <tt>ext2</tt>/<tt>ext3</tt></tag> | |
| 437 | <item><p>New ext2 and ext3 file systems will be created with features | |
| 438 | <em/dir_index/ and <em/resize_inode/ enabled by default. The first | |
| 439 | feature speeds up operations on directories with many files; the | |
| 440 | second makes it possible to resize a file system on-line (i.e. while it | |
| 441 | is mounted).</p> | |
| 442 | <p>Users upgrading from &oldreleasename; could consider adding the | |
| 443 | <em/dir_index/ flag manually using <prgn/tune2fs/<footnote> | |
| 444 | The flag <em/filetype/ should already be set on most file systems, except | |
| 445 | possibly on systems installed before &oldreleasename;. | |
| 446 | </footnote>; the <em/resize_inode/ flag cannot be added to an existing | |
| 447 | file system. It is possible to check which flags are set for a file | |
| 448 | system using <tt/dumpe2fs -h/.</p></item> | |
| 449 | ||
| 450 | <!-- TODO: Add for lenny, link to utf8-migration-tool, which is right now not | |
| 451 | available for etch --> | |
| 452 | <tag>Default encoding for &releasename; is UTF-8</tag> | |
| 453 | <item><p>The default encoding for new &debian; installations is UTF-8. A | |
| 454 | number of applications will also be set up to use UTF-8 by default.</p> | |
| 455 | <p>Users upgrading to &releasename; that wish to switch to UTF-8 will | |
| 456 | need to reconfigure their environment and locale definitions. The | |
| 457 | system-wide default can be changed using <tt/dpkg-reconfigure locales/; | |
| 458 | first select a UTF-8 locale for your language and country and then | |
| 459 | set that as default. Note that switching to UTF-8 means that you will | |
| 460 | probably also need to convert existing files from your previous | |
| 461 | (legacy) encoding to UTF-8.</p> | |
| 462 | <p>The package <package/utf8-migration-tool/ contains a tool that may | |
| 463 | help the migration, however that package is only available in unstable | |
| 464 | as it was not ready in time for &releasename;. Making a backup of | |
| 465 | your data and configuration before using the tool is strongly | |
| 466 | recommended.</p> | |
| 467 | <p>Note that some applications may not yet work correctly in a UTF-8 | |
| 468 | environment, mostly due to display issues.</p></item> | |
| 469 | ||
| 470 | </taglist></p> | |
| 471 | ||
| 472 | <p>The <url id="http://wiki.debian.org/Sarge2EtchUpgrade" | |
| 473 | name="Debian Wiki"> has some additional information about changes between | |
| 474 | &oldreleasename; and &releasename;.</p> | |
| 475 | ||
| 476 | </sect> | |
| 477 | ||
| 478 | <sect id="kernel-changes"><heading>Major kernel-related changes</heading> | |
| 479 | ||
| 480 | <p>&debian; &release; ships with kernel version &kernelversion; for all | |
| 481 | architectures; the release is still mostly | |
| 482 | <!-- JFS: Needed because of the cross ref, build errors will appear in some | |
| 483 | architectures otherwise --> | |
| 484 | <![ %defaulted-2.4 [ | |
| 485 | <footnote>Some individual | |
| 486 | packages may no longer work correctly with a 2.4 kernel; see | |
| 487 | <ref id="incompatible-2.4">.</footnote> | |
| 488 | ]]> | |
| 489 | compatible with 2.4 kernels, but | |
| 490 | Debian no longer provides or supports 2.4 kernel packages.</p> | |
| 491 | ||
| 492 | <p>There have been major changes both in the kernel itself and in the | |
| 493 | packaging of the kernel for Debian. Some of these changes complicate | |
| 494 | the upgrade procedure and can potentially result in problems while | |
| 495 | rebooting the system after the upgrade to &releasename;. This section | |
| 496 | gives an overview of the most important changes; potential issues and | |
| 497 | information on how to work around them is included in later chapters.</p> | |
| 498 | ||
| 499 | <![ %defaulted-2.4 [ | |
| 500 | <p>If you are currently using a 2.4 kernel, you should read | |
| 501 | <ref id="upgrade-to-2.6"> carefully.</p> | |
| 502 | ]]> | |
| 503 | ||
| 504 | <sect1 id="kernel-packaging"><heading>Changes in kernel packaging</heading> | |
| 505 | ||
| 506 | <p><taglist> | |
| 507 | <tag>Kernel packages renamed</tag> | |
| 508 | <item><p>All Linux kernel packages have been renamed from <tt/kernel-*/ | |
| 509 | to <tt/linux-*/ to clean up the namespace. This will make it easier to | |
| 510 | include non-Linux kernels in Debian in the future.</p></item> | |
| 511 | ||
| 512 | <![ %i386 [ | |
| 513 | <tag>Flavor "386" replaced with "486"</tag> | |
| 514 | <item><p>As support for 80386 processors was dropped with &oldreleasename;, | |
| 515 | the 386 kernel flavor has now been dropped as well and replaced by a | |
| 516 | new 486 flavor.</p></item> | |
| 517 | ]]> | |
| 518 | <![ %amd64 [ | |
| 519 | <tag>Single generic kernel for &arch-title;</tag> | |
| 520 | <item><p>In &oldreleasename; there were separate kernel flavors for | |
| 521 | different processor families of this architecture. Because of changes | |
| 522 | in the kernel which will | |
| 523 | automatically optimize the kernel for the processor(s) in the system, | |
| 524 | there is no longer any real need for seperate kernel flavors.</p></item> | |
| 525 | ]]> | |
| 526 | ||
| 527 | <![ %i386-amd64-ia64 [ | |
| 528 | <tag>Standard kernels have SMP abilities</tag> | |
| 529 | <item><p>Multiprocessor systems no longer require an <tt/*-smp/ flavor of the | |
| 530 | Linux kernel. For &arch-title;, <tt/linux-image/ packages without the <tt/-smp/ | |
| 531 | suffix support both uniprocessor and multiprocessor systems. | |
| 532 | <![ %i386 [ | |
| 533 | (The one exception is the 486 flavor, which only supports a single | |
| 534 | processor.) | |
| 535 | ]]> | |
| 536 | </p></item> | |
| 537 | ]]> | |
| 538 | ||
| 539 | <![ %mips [ | |
| 540 | <tag>r5k-ip22 kernel flavor dropped</tag> | |
| 541 | <item><p>The kernel image for IP22 machines with an R5000 CPU has been | |
| 542 | dropped because the r4k-ip22 image now supports IP22 machines with either | |
| 543 | an R4x000 or an R5000 CPU.</p></item> | |
| 544 | ]]> | |
| 545 | </taglist></p> | |
| 546 | ||
| 547 | <p>Where possible, dummy transition packages that depend on the new packages | |
| 548 | have been provided for the dropped packages.</p> | |
| 549 | ||
| 550 | </sect1> | |
| 551 | ||
| 552 | <sect1 id="kernel-initrd"><heading>New utilities to generate initrds</heading> | |
| 553 | ||
| 554 | <![ %no-initrd [ | |
| 555 | <p>The Debian kernel image packages for &arch-title; do not require an | |
| 556 | initrd for booting the system. This means that the information in this | |
| 557 | section may not be relevant for you, but is still included for | |
| 558 | reference.</p> | |
| 559 | ]]> | |
| 560 | <p> | |
| 561 | <![ %uses-initrd [ | |
| 562 | The Debian kernel image packages for &arch-title; require an initrd | |
| 563 | for booting the system. | |
| 564 | ]]> | ]]> |
| 565 | Because of changes in the kernel, the utility used to generate initrds in | |
| 566 | &oldreleasename;, <package/initrd-tools/ can no longer be used and has been | |
| 567 | deprecated. Two new utilities have been developed that replace it: | |
| 568 | <package/initramfs-tools/ and <package/yaird/. The concepts behind the new | |
| 569 | utilities are very different; an overview is available on the | |
| 570 | <url id="http://wiki.debian.org/InitrdReplacementOptions" name="Debian Wiki">. | |
| 571 | Both will generate an initrd using the <em/initramfs/ file system, which is | |
| 572 | a compressed <prgn/cpio/ archive. | |
| 573 | The default and recommended utility is <package/initramfs-tools/. | |
| 574 | </p> | |
| 575 | ||
| 576 | <![ %uses-initrd [ | |
| 577 | <p>Upgrading to an &releasename; kernel will cause | |
| 578 | <package/initramfs-tools/ to be installed by default. | |
| 579 | <![ %defaulted-2.4 [ | |
| 580 | If you are upgrading from a 2.4 kernel to a 2.6 Debian kernel, | |
| 581 | you must use <package/initramfs-tools/. Using | |
| 582 | <package/yaird/ will cause linux-image-2.6 installations to | |
| 583 | fail if you are running a 2.2 or 2.4 kernel. | |
| 584 | ]]> | |
| 585 | </p> | |
| 586 | ||
| 587 | <!-- FJP: Maybe a short description of available installation methods could be | <p>The package <package/initrd-tools/ is still included in &releasename; |
| 588 | added here: floppy, CD (netinst/business-card/full set), netboot, | because it is needed for upgrades from &oldreleasename;. It will |
| 589 | hd-media, USB-stick. --> | be dropped for the next release.</p> |
| 590 | ]]> | |
| <![ %available-2.6 [ | ||
| <p>An installer using a 2.6 based kernel is available for | ||
| &arch-title;. For more details on how to use it please consult the | ||
| installation guide.</p> | ||
| ]]> | ||
| </sect> | ||
| <sect id="newdistro"><heading>What's New in the Distribution?</heading> | ||
| <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. Interested users | ||
| should investigate the <package>aptitude</package> and | ||
| <package>synaptic</package> packages.</p> | ||
| <p>This release of &debian; contains the much improved XFree86 | ||
| 4.3 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>&debian; is more desktop orientated than ever in this new release, | ||
| it now includes GNOME 2.8 and KDE 3.3. Also included for the | ||
| first time is a complete office suite in the form of OpenOffice.org | ||
| 1.1, other productivity tools included in the release are the | ||
| Evolution groupware software and GAIM instant messaging client. | ||
| <p>The official &debian; distribution now ships on thirteen | ||
| binary CDs with a similar number of source CDs, and a DVD version | ||
| of the distribution is now also available.</p></sect> | ||
| 591 | ||
| 592 | </sect1> | |
| 593 | ||
| 594 | <sect1 id="kernel-udev"> | |
| 595 | <heading>Dynamic <file>/dev</file> management and hardware discovery</heading> | |
| 596 | ||
| 597 | <p>&releasename; kernels no longer provide support for <tt>devfs</tt>.</p> | |
| 598 | ||
| 599 | <p>The replacement for <tt>devfs</tt> is <package/udev/, a userspace | |
| 600 | implementation of devfs.</p> | |
| 601 | <p><package/udev/ is mounted | |
| 602 | over the <file>/dev</file> directory and will populate that directory | |
| 603 | with devices supported by the kernel. It will also dynamically add and | |
| 604 | remove devices as kernel modules are loaded or unloaded respectively, | |
| 605 | based on events generated by the kernel. <prgn/udev/ is a lot more | |
| 606 | versatile than <tt/devfs/ and offers services that are used by other | |
| 607 | packages like <package/hal/ (hardware abstraction layer).</p> | |
| 608 | ||
| 609 | <p>In combination with the kernel, <package/udev/ also takes care of | |
| 610 | hardware discovery and module loading for detected devices. Because of | |
| 611 | this it conflicts with <package/hotplug/. | |
| 612 | In &oldreleasename;, <package/discover/ could also be used for loading | |
| 613 | modules during the boot process, but its new version in &releasename; no | |
| 614 | longer provides that function. | |
| 615 | <![ %not-s390 [ | |
| 616 | <package/discover/ is still used by X.Org to detect what graphics | |
| 617 | controller is present in the system. | |
| 618 | ]]> | |
| 619 | </p> | |
| 620 | ||
| 621 | <![ %uses-initrd [ | |
| 622 | <p>If you install a Debian kernel image, <package/udev/ will be installed | |
| 623 | by default as <package/initramfs-tools/ depends on it.</p> | |
| 624 | <p>You can avoid installing <package/udev/ by compiling a custom non-modular | |
| 625 | kernel or by using an alternative initrd generator, such as <package/yaird/. | |
| 626 | However, <package/initramfs-tools/ is the recommended initrd generator.</p> | |
| 627 | ]]> | |
| 628 | ||
| 629 | </sect1> | |
| 630 | </sect> | |
| 631 | </chapt> | </chapt> |
| 632 | ||
| 633 | <chapt id="installing"><heading>New Installations</heading> | <chapt id="installing"><heading>Installation System</heading> |
| 634 | ||
| 635 | <p>If you are making a new installation of Debian, you should read | <p>The Debian Installer is the official installation system for Debian. |
| 636 | the Installation Guide, which is available on the Official CD at: | It offers a variety of installation methods. Which methods |
| 637 | are available to install your system depends on your architecture.</p> | |
| 638 | ||
| 639 | <p>Images of the installer for &releasename; can be found together with the | |
| 640 | Installation Guide on the <url id="&url-installer;" | |
| 641 | name="Debian website">.</p> | |
| 642 | ||
| 643 | <p>The Installation Guide is also included on the first CD/DVD of the | |
| 644 | official Debian CD/DVD sets, at: | |
| 645 | ||
| 646 | <example> | <example> |
| 647 | /doc/install/manual/<var>language</var>/index.html | /doc/install/manual/<var>language</var>/index.html |
| 648 | </example> | </example></p> |
| 649 | ||
| 650 | <p>You may also want to check the <url id="&url-installer;index#errata" | |
| 651 | name="errata"> for debian-installer for a list of known issues.</p> | |
| 652 | ||
| 653 | <![ %alpha [ | |
| 654 | <p>The installer can only be used to install on alpha systems which | |
| 655 | support the SRM console. Be sure to switch your system to SRM before | |
| 656 | starting the installation. If your machine supports only the AlphaBIOS/ARC | |
| 657 | console, the recommended way to install &releasename; is to first install | |
| 658 | a (minimal) woody system, then upgrade to &oldreleasename; and finally to | |
| 659 | &releasename;. For more information about the different consoles please | |
| 660 | read the references on the <url id="http://www.debian.org/ports/alpha" | |
| 661 | name="Debian alpha port web pages">. | |
| 662 | </p> | |
| 663 | ]]> | |
| 664 | ||
| 665 | or on the Internet at: <url id="&url-install-manual;">.</p> | <![ %sparc [ |
| 666 | <sect id="sparc_fb"><heading>Issues with framebuffer on &arch-title;</heading> | |
| 667 | ||
| 668 | <p>Because of display problems on some systems, framebuffer support is | |
| 669 | disabled by default for &arch-title; for most graphics cards. This can | |
| 670 | result in ugly display on systems that do properly support the framebuffer. | |
| 671 | If you see display problems in the installer, you can try booting the installer | |
| 672 | with the parameter <tt>framebuffer=true</tt>. | |
| 673 | Please let us know if the framebuffer is not used by default, but works for | |
| 674 | your hardware.</p> | |
| 675 | ||
| 676 | </sect> | |
| 677 | ||
| 678 | <sect id="sparc_illegal_instruction"><heading>Issues with booting on &arch-title;</heading> | |
| 679 | ||
| 680 | <p>It has been reported by several users that the installation CD | |
| 681 | fails to boot successfully upon the '<tt>boot cdrom</tt>' PROM | |
| 682 | command, displaying the error '<tt>Illegal Instruction</tt>'.</p> | |
| 683 | ||
| 684 | <p>The apparent explanation for this problem is that it doesn't work | |
| 685 | because the machine had previously been rebooted from Solaris. | |
| 686 | The workaround is to power the machine off fully, and then boot it | |
| 687 | directly into the installation CD.</p> | |
| 688 | ||
| 689 | <p>The problem was reported by users of various systems (namely, | |
| 690 | Enterprise 450, Blade 2000, Fire V240, Enterprise 250 and Blade 100 | |
| 691 | at the time of writing), so it is believed to be generic. Please | |
| 692 | let us know if you observe similar issues with your hardware.</p> | |
| 693 | ||
| 694 | </sect> | |
| 695 | ||
| 696 | <sect id="sparc_qlogic_firmware"><heading>Issues with booting from qla2xxx on &arch-title;</heading> | |
| 697 | ||
| 698 | <p>It has been reported by several users that the installation | |
| 699 | system fails to recognize hard disks on machines which have the | |
| 700 | hard disks connected to a QLogic fibre-channel SCSI controller. | |
| 701 | The qla2xxx driver loads, but it cannot load firmware, which makes | |
| 702 | it useless.</p> | |
| 703 | ||
| 704 | <p>The explanation for this problem is that the QLogic controller | |
| 705 | firmware is not free, and it had to be moved to a separate non-free | |
| 706 | package (<url id="http://packages.debian.org/firmware-qlogic" | |
| 707 | name="firmware-qlogic">) which is not used by the installation system. | |
| 708 | ||
| 709 | <p>There is no straightforward solution, unfortunately; one has to | |
| 710 | provide the firmware image to the installation system. This is | |
| 711 | possible if Internet connectivity is available while the machine is | |
| 712 | being installed - download the firmware-qlogic package with wget, | |
| 713 | install it with udpkg, and then reload the qla2xxx module. | |
| 714 | Alternatively, install from an older installation CD (where non-free | |
| 715 | firmware was still integrated) and then upgrade.</p> | |
| 716 | ||
| 717 | </sect> | |
| 718 | ]]> | |
| 719 | ||
| 720 | <sect id="inst-new"><heading>What's new in the installation system?</heading> | |
| 721 | ||
| 722 | <p>There has been a lot of development on the Debian Installer | |
| 723 | since its first official release with &oldreleasename; resulting | |
| 724 | in both improved hardware support and some exciting new features.</p> | |
| 725 | ||
| 726 | <p>In these Release Notes we'll only list the major changes in the | |
| 727 | installer. If you are interested in an overview of the detailed | |
| 728 | changes since &oldreleasename;, please check the release announcements | |
| 729 | for the &releasename; beta and RC releases available from the | |
| 730 | Debian Installer's <url id="&url-installer-news;" name="news history">.</p> | |
| 731 | ||
| 732 | <sect1 id="inst-changes"><heading>Major changes</heading> | |
| 733 | ||
| 734 | <p><taglist> | |
| 735 | <tag>No reboot during the installation</tag> | |
| 736 | <item><p>Previously, the installation was split into two parts: | |
| 737 | setting up the base system and making it bootable, followed | |
| 738 | by a reboot and after that the execution of <prgn/base-config/ | |
| 739 | which would take care of things like user setup, setup of the | |
| 740 | package management system and installation of additional | |
| 741 | packages (using tasksel).</p> | |
| 742 | <p>For &releasename; the second stage has been integrated into | |
| 743 | Debian Installer itself. This has a number of advantages, | |
| 744 | including increased security and the fact that after the reboot | |
| 745 | at the end of the installation the new system should already have | |
| 746 | the correct timezone and, if you installed the Desktop environment, | |
| 747 | will at once start the graphical user interface.</p></item> | |
| 748 | ||
| 749 | <!-- FIXME (vorlon): is this true for /all/ languages? --> | |
| 750 | <tag>UTF-8 encoding default for new systems</tag> | |
| 751 | <item><p>The installer will set up systems to use UTF-8 encoding | |
| 752 | rather than the old language-specific encodings (like ISO-8859-1, | |
| 753 | EUC-JP or KOI-8).</p></item> | |
| 754 | ||
| 755 | <tag>More flexible partitioning</tag> | |
| 756 | <item><p>It is now possible to set up file systems on an LVM volume | |
| 757 | using guided partitioning.</p> | |
| 758 | <p>The installer is also able to set up encrypted file systems. | |
| 759 | Using manual partitioning you have the choice between <tt/dm-crypt/ | |
| 760 | and <tt/loop-aes/, using a passphrase or a random key, and you can | |
| 761 | tune various other options. Using guided partitioning, the installer | |
| 762 | will create an encrypted LVM partition that contains any other | |
| 763 | file systems (except <file>/boot</file>) as logical volumes.</p></item> | |
| 764 | ||
| 765 | <![ %g-i [ | |
| 766 | <tag>Graphical user interface</tag> | |
| 767 | <item> | |
| 768 | <![ %i386-amd64 [ | |
| 769 | <p>If you prefer a graphical user interface, try booting | |
| 770 | the installer with <tt/installgui/.</p> | |
| 771 | ]]> | |
| 772 | ||
| 773 | <![ %powerpc [ | |
| 774 | <p>For &arch-title; a separate installation image using a | |
| 775 | graphical user interface is available on an experimental basis. | |
| 776 | It is known to work on most CHRP systems that have an ATI graphics | |
| 777 | card, but has been insufficiently tested on &arch-title; to include | |
| 778 | it on the normal installation CDs.</p> | |
| 779 | <p>If you'd like to try the graphical installer, look for the | |
| 780 | "gtk-miniiso" image.</p> | |
| 781 | ]]> | |
| 782 | ||
| 783 | <p>The functionality of the graphical installer is almost identical | |
| 784 | to the regular installer, only the presentation differs. There is one | |
| 785 | exception: the graphical frontend does not support setting up | |
| 786 | encrypted partitions using random keys.</p> | |
| 787 | <p>The major advantage of the graphical user interface is that it | |
| 788 | supports more languages than the regular user interface (newt). | |
| 789 | Information about the graphical installer and the most important | |
| 790 | differences between the graphical and regular installer are documented | |
| 791 | in an appendix in the installation guide.</p> | |
| 792 | <p>Note: the graphical user interface is not available for all | |
| 793 | architectures.</p> | |
| 794 | </item> | |
| 795 | ]]> | |
| 796 | ||
| 797 | <tag>Rescue mode</tag> | |
| 798 | <item><p>You can use the installer to solve problems with your | |
| 799 | system, for example when it refuses to boot. The first steps will | |
| 800 | be just like a regular installation, but the installer will not | |
| 801 | start the partitioner. Instead it will offer you a menu of rescue | |
| 802 | options.</p> | |
| 803 | <p>Activate the rescue mode by booting the installer with | |
| 804 | <tt/rescue/, or by adding a boot parameter | |
| 805 | <tt>rescue/enable=true</tt>.</p></item> | |
| 806 | ||
| 807 | <tag>Using sudo instead of root account</tag> | |
| 808 | <item><p>During expert installations you can choose to not | |
| 809 | set up the root account (it will be locked), but instead set | |
| 810 | up <prgn/sudo/ so that the first user can use that for | |
| 811 | system administration.</p></item> | |
| 812 | ||
| 813 | <tag>Cryptographic verification of downloaded packages</tag> | |
| 814 | <item><p>Packages downloaded with the installer are | |
| 815 | now cryptographically checked using <prgn/apt/, | |
| 816 | making it more difficult to compromise a system being | |
| 817 | installed over the network.</p></item> | |
| 818 | ||
| 819 | <tag>Simplified mail configuration</tag> | |
| 820 | <item><p>If the "standard system" is installed, the installer sets up | |
| 821 | a basic configuration for the system's mail server which will only | |
| 822 | provide for local e-mail delivery. The mail server will be unavailable | |
| 823 | to other systems connected to the same network. If you want to | |
| 824 | configure your system to handle e-mail not local to the system (either | |
| 825 | to send e-mail or to receive it), you will have to reconfigure the mail | |
| 826 | system after installation.</p></item> | |
| 827 | ||
| 828 | <tag>Desktop selection</tag> | |
| 829 | <item><p>The installation system will install | |
| 830 | a GNOME desktop as the default desktop if the user asks for one.</p> | |
| 831 | <p>However, users wishing to install alternate desktop environments | |
| 832 | can easily do so by adding boot parameters: | |
| 833 | <tt>tasks="standard, kde-desktop"</tt> for KDE and | |
| 834 | <tt>tasks="standard, xfce-desktop"</tt> for Xfce. Note that this | |
| 835 | will not work when installing from a full CD image without using | |
| 836 | a network mirror as an additional package source; it will work | |
| 837 | when using a DVD image or any other installation method.</p> | |
| 838 | <p>There are also separate CD images available that install the | |
| 839 | KDE or Xfce desktop environment by default.</p></item> | |
| 840 | ||
| 841 | <![ %not-s390 [ | |
| 842 | <tag>New languages</tag> | |
| 843 | <item><p>Thanks to the huge efforts of translators, Debian can | |
| 844 | now be installed in 47 languages using the text-based | |
| 845 | installation user interface. This is six languages more | |
| 846 | than in &oldreleasename;. Languages added in this release include | |
| 847 | Belarusian, Esperanto, Estonian, Kurdish, Macedonian, | |
| 848 | Tagalog, Vietnamese and Wolof. | |
| 849 | Due to lack of translation updates, two languages have been dropped | |
| 850 | in this release: Persian and Welsh.</p> | |
| 851 | <![ %g-i [ | |
| 852 | <p>If the graphical user interface is used, an additional eleven | |
| 853 | languages are supported. These languages can only be selected | |
| 854 | using this installer as their character sets cannot be presented | |
| 855 | in a non-graphical environment. The new languages are: | |
| 856 | Bengali, Dzongkha, Gujarati, Hindi, Georgian, Khmer, Malayalam, | |
| 857 | Nepali, Punjabi, Tamil and Thai.</p> | |
| 858 | ]]> | |
| 859 | <p>Users that do not wish to use any locale can now select | |
| 860 | <em/C/ as their preferred locale in the installer's language | |
| 861 | selection. | |
| 862 | More information on language coverage is available at the | |
| 863 | <url id="&url-d-i-i18n;" name="d-i languages list">. | |
| 864 | </p></item> | |
| 865 | ||
| 866 | <tag>Simplified localization and timezone selection</tag> | |
| 867 | <item><p>Configuration of language, countries and timezones | |
| 868 | has been simplified to reduce the amount of information | |
| 869 | needed from the user. The installer will now guess | |
| 870 | what the system's country and timezone is based on the | |
| 871 | language selected, or will provide a limited selection | |
| 872 | if it cannot. Users can still introduce obscure | |
| 873 | combinations if need be.</p></item> | |
| 874 | ||
| 875 | <tag>Improved system-wide localization</tag> | |
| 876 | <item><p>Most of the internationalization and localization tasks that | |
| 877 | were previously handled by the <package>localization-config</package> tool are now | |
| 878 | included in the stock Debian installer or in packages themselves. This | |
| 879 | means that selection of a language will automatically install packages | |
| 880 | necessary for that language (dictionaries, documentation, fonts...) in both | |
| 881 | standard and desktop environments. Configuration that is no longer | |
| 882 | handled automatically includes the papersize configuration and some | |
| 883 | advanced X Windows keyboard settings for some languages.</p> | |
| 884 | <p>Note that language-specific packages will only be installed | |
| 885 | automatically if they are available during the installation.</p></item> | |
| 886 | ||
| 887 | ]]> <!-- not-s390 --> | |
| 888 | ||
| 889 | </taglist></p> | |
| 890 | </sect1> | |
| 891 | ||
| 892 | <sect1 id="inst-auto"><heading>Automated installation</heading> | |
| 893 | ||
| 894 | <p>A lot of the changes mentioned in the previous section also | |
| 895 | imply changes in the support in the installer for automated | |
| 896 | installation using preconfiguration files. This means that if | |
| 897 | you have existing preconfiguration files that worked with the | |
| 898 | &oldreleasename; installer, you cannot expect these to work | |
| 899 | with the new installer without modification.</p> | |
| 900 | ||
| 901 | <p>The good news is that the <url id="&url-install-manual;" | |
| 902 | name="Installation Guide"> now has a separate appendix with | |
| 903 | extensive documentation on using preconfiguration.</p> | |
| 904 | ||
| 905 | <p>The &releasename; installer introduces some exciting new | |
| 906 | features that allow further and easier automation of installs. | |
| 907 | It also adds support for advanced partitioning using RAID, LVM | |
| 908 | and encrypted LVM. See the documentation for details.</p> | |
| 909 | ||
| 910 | </sect1> | |
| 911 | </sect> | |
| 912 | ||
| 913 | <sect id="popcon"><heading>Popularity contest</heading> | |
| 914 | ||
| 915 | <p>The installation system will again offer | |
| 916 | to install the <package/popularity-contest/ package. This package was not | |
| 917 | installed by default in &oldreleasename; but it was installed in older releases.</p> | |
| 918 | ||
| 919 | <p><package/popularity-contest/ provides the Debian project with valuable information | |
| 920 | on which packages in the distribution are actually used. This information | |
| 921 | is used mainly to decide the order in which packages are included on | |
| 922 | installation CD-ROMs, but is also often consulted by Debian developers | |
| 923 | in deciding whether or not to adopt a package that no longer has a | |
| 924 | maintainer.</p> | |
| 925 | ||
| 926 | <p>Information from <package/popularity-contest/ is processed anonymously. | |
| 927 | We would appreciate it if you would participate in this official survey, | |
| 928 | helping to improve Debian.</p> | |
| 929 | ||
| 930 | </sect> | |
| 931 | ||
| <p>The old &debian; installation system called | ||
| <prgn>boot-floppies</prgn> has been replaced by a new componentized and | ||
| more powerful installation system called <prgn>debian-installer</prgn>.</p> | ||
| 932 | </chapt> | </chapt> |
| 933 | ||
| 934 | ||
| 935 | <chapt id="upgrading"><heading>Upgrades from Previous Releases</heading> | <chapt id="upgrading"><heading>Upgrades from previous releases</heading> |
| 936 | ||
| 937 | <!-- For doc-writers' convenience: | <!-- For doc-writers' convenience: |
| 938 | Debian Supported | Debian Supported |
| # | Line 197 release: architectures: | Line 942 release: architectures: |
| 942 | 2.0 i386,m68k | 2.0 i386,m68k |
| 943 | 2.1 i386,m68k,alpha,sparc | 2.1 i386,m68k,alpha,sparc |
| 944 | 2.2 i386,m68k,alpha,sparc,powerpc,arm | 2.2 i386,m68k,alpha,sparc,powerpc,arm |
| 945 | 3.0 + hppa s390 mips mipsel ia64 | 3.0 + hppa,s390,mips,mipsel,ia64 |
| 946 | 3.1 i386,m68k,alpha,sparc,powerpc,arm,hppa,s390,mips,mipsel,ia64 (no changes) | |
| 947 | 4.0 i386,alpha,sparc,powerpc,arm,hppa,s390,mips,mipsel,ia64,amd64 | |
| 948 | (+ amd64; - m68k) | |
| 949 | --> | --> |
| 950 | ||
| 951 | <sect id="information"><heading>Detailed Changes to the System</heading> | <sect id="backup"><heading>Preparing for the upgrade</heading> |
| 952 | ||
| 953 | <!-- Controversial, disabled for now, please translate though | <p>We suggest that before upgrading you also read the information in |
| 954 | <sect1 id="german-quotes"><heading>Problems with German Quotes</heading> | <ref id="information">. That chapter covers potential issues not |
| 955 | directly related to the upgrade process but which could still be | |
| 956 | <p>The locales for German style languages (e.g. de_DE@euro) | important to know about before you begin.</p> |
| unfortunately use an aesthetically unpleasing way of representing | ||
| open quotation marks. We have retained it this way in order to | ||
| preserve compatibility with other Linux distributions, and we hope | ||
| that in the future it will be fixed. We suggest that you switch to a | ||
| UTF-8 locale (e.g. de_DE@euro.UTF-8), which fully supports German with | ||
| the correct quotation marks, and, using Unicode encoding, has better | ||
| support for other languages as well.</p> | ||
| <p>To change the system wide locale choice, use: | ||
| <example>dpkg-reconfigure locales</example></p> | ||
| --> | ||
| <sect1 id="syntax"><heading>Important program syntax changes</heading> | ||
| <p>Debian attempts to avoid changing upstream packages, therefore | ||
| any changes in the upstream package will be present in the version in | ||
| &debian;. This can mean that program behaviour may change between | ||
| releases of &debian;. </p> | ||
| <p><em>No changes yet reported.</em></p> | ||
| </sect1> | ||
| </sect> | ||
| <sect id="backup"><heading>Preparing for the Upgrade</heading> | ||
| 957 | ||
| 958 | <sect1 id="data-backup"><heading>Back up any data or configuration information</heading> | |
| 959 | ||
| 960 | <p>Before upgrading your system, it is strongly recommended that | <p>Before upgrading your system, it is strongly recommended that |
| 961 | you make a full backup, or at least backup any data or | you make a full backup, or at least back up any data or |
| 962 | configuration information you can't afford to lose. The upgrade | configuration information you can't afford to lose. The upgrade |
| 963 | tools and process are quite reliable, but a hardware failure in | tools and process are quite reliable, but a hardware failure in |
| 964 | the middle of an upgrade could result in a severely damaged | the middle of an upgrade could result in a severely damaged |
| # | Line 239 release: architectures: | Line 966 release: architectures: |
| 966 | ||
| 967 | <p>The main things you'll want to back up are the contents of | <p>The main things you'll want to back up are the contents of |
| 968 | <file>/etc</file>, <file>/var/lib/dpkg</file> and the output of | <file>/etc</file>, <file>/var/lib/dpkg</file> and the output of |
| 969 | <tt>dpkg --get-selections \*</tt>.</p> | <tt>dpkg --get-selections "*"</tt> (the quotes are important).</p> |
| 970 | ||
| 971 | <p>The upgrade process itself does not modify anything in the | |
| 972 | <file>/home</file> directory. However, some applications (e.g. | |
| 973 | parts of the Mozilla suite, and the GNOME and KDE desktop | |
| 974 | environments) are known to overwrite existing user settings with new | |
| 975 | defaults when a new version of the application is first started by a | |
| 976 | user. As a precaution, you may want to make a backup of the hidden | |
| 977 | files and directories ("dotfiles") in users' home directories. This | |
| 978 | backup may help to restore or recreate the old settings. You may | |
| 979 | also want to inform users about this.</p> | |
| 980 | ||
| 981 | <p>Any package installation operation must be run with superuser | |
| 982 | privileges, so either login as root or use <prgn/su/ or | |
| 983 | <prgn/sudo/ to gain the necessary access rights.</p> | |
| 984 | ||
| 985 | <p>The upgrade has a few preconditions; you should check them | |
| 986 | before actually executing the upgrade.</p> | |
| 987 | ||
| 988 | </sect1> | |
| 989 | ||
| 990 | <sect1><heading>Inform users in advance</heading> | |
| 991 | ||
| 992 | <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 |
| 993 | planning, although users accessing your system via SSH (at least) | planning, although users accessing your system via an <prgn/ssh/ |
| 994 | shouldn't notice much during the upgrade, and may want to continue | connection should notice little during the upgrade, and should be |
| 995 | working. If you wish to take extra precautions, back up or unmount | able to continue working. </p> |
| 996 | user's partitions (<file>/home</file>) before upgrading. A reboot | |
| 997 | will not normally be necessary.</p> | <p>If you wish to take extra precautions, back up or |
| 998 | unmount users' partitions (<file>/home</file>) before upgrading.</p> | |
| 999 | ||
| 1000 | <!-- JFS: Not true in etch, maybe for lenny? | |
| 1001 | <p>A reboot will not normally be necessary, unless you also plan to | |
| 1002 | upgrade your kernel.</p> | |
| 1003 | --> | |
| 1004 | <p>You will probably have to do a kernel upgrade when upgrading to | |
| 1005 | &releasename;, so a reboot will normally be necessary. Typically, | |
| 1006 | this will be done after the upgrade is finished.</p> | |
| 1007 | ||
| 1008 | </sect1> | |
| 1009 | ||
| 1010 | <sect1 id="recovery"><heading>Prepare for recovery</heading> | |
| 1011 | ||
| 1012 | <p>Because of the many changes in the kernel between &oldreleasename; | |
| 1013 | and &releasename; regarding drivers, hardware discovery and the | |
| 1014 | naming and ordering of device files, there is a real risk that you | |
| 1015 | may experience problems rebooting your system after the upgrade. | |
| 1016 | A lot of known potential issues are documented in this and the next | |
| 1017 | chapters of these Release Notes.</p> | |
| 1018 | ||
| 1019 | <p>For that reason it makes sense to ensure that you will be able to | |
| 1020 | recover if your system should fail to reboot or, for remotely managed | |
| 1021 | systems, fail to bring up networking.</p> | |
| 1022 | ||
| 1023 | <!-- JFS: probably can be removed for lenny --> | |
| 1024 | <p>If you are upgrading remotely via an <prgn/ssh/ link it is highly | |
| 1025 | recommended that you take the necessary precautions to be able to | |
| 1026 | access the server through a remote serial terminal. There is a chance | |
| 1027 | that, after upgrading the kernel and rebooting, some devices will | |
| 1028 | be renamed (as described in <ref id="device-reorder">) and you will | |
| 1029 | have to fix the system configuration through a local console. Also, | |
| 1030 | if the system is rebooted accidentally in the middle of an upgrade | |
| 1031 | there is a chance you will need to recover using a local console.</p> | |
| 1032 | <!-- END - remove for lenny --> | |
| 1033 | ||
| 1034 | <p>The most obvious thing to try first is to reboot with your | |
| 1035 | old kernel. However, for various reasons documented elsewhere in this | |
| 1036 | document, this is not guaranteed to work.</p> | |
| 1037 | ||
| 1038 | <p>If that fails, you will need an alternative way to boot your | |
| 1039 | system so you can access and repair it. One option is to use a | |
| 1040 | special rescue image or a Linux live CD. After booting from that, | |
| 1041 | you should be able to mount your root file system and <tt/chroot/ | |
| 1042 | into it to investigate and fix the problem.</p> | |
| 1043 | ||
| 1044 | <p>Another option we'd like to recommend is to use the | |
| 1045 | <em/rescue mode/ of the &releasename; Debian Installer. The advantage | |
| 1046 | of using the installer is that you can choose between its many | |
| 1047 | installation methods for one that best suits your situation. | |
| 1048 | For more information, please consult the section | |
| 1049 | "Recovering a Broken System" in chapter 8 of the | |
| 1050 | <url id="&url-install-manual;" name="Installation Guide"> and the | |
| 1051 | <url id="http://wiki.debian.org/DebianInstaller/FAQ" | |
| 1052 | name="Debian Installer FAQ">.</p> | |
| 1053 | ||
| 1054 | <![ %uses-initrd [ | |
| 1055 | <sect2 id="recovery-initrd"><heading>Debug shell during boot using initrd</heading> | |
| 1056 | <p>The <package/initramfs-tools/ includes a debug shell<footnote> | |
| 1057 | This feature can be disabled by adding the parameter <tt/panic=0/ | |
| 1058 | to your boot parameters.</footnote> in the initrds it generates. | |
| 1059 | If for example the initrd is unable to mount your root file system, | |
| 1060 | you will be dropped into this debug shell which has basic commands | |
| 1061 | available to help trace the problem and possibly fix it.</p> | |
| 1062 | ||
| 1063 | <p>Basic things to check are: | |
| 1064 | presence of correct device files in <file>/dev</file>; | |
| 1065 | what modules are loaded (<tt>cat /proc/modules</tt>); | |
| 1066 | output of <prgn/dmesg/ for errors loading drivers. | |
| 1067 | The output of <prgn/dmesg/ will also show what device files have | |
| 1068 | been assigned to which disks; you should check that against the | |
| 1069 | output of <tt/echo $ROOT/ to make sure that the root file system | |
| 1070 | is on the expected device.</p> | |
| 1071 | ||
| 1072 | <p>If you do manage to fix the problem, typing <tt/exit/ will | |
| 1073 | quit the debug shell and continue the boot process at the point | |
| 1074 | it failed. Of course you will also need to fix the underlying | |
| 1075 | problem and regenerate the initrd so the next boot won't fail | |
| 1076 | again.</p> | |
| 1077 | </sect2> | |
| 1078 | ]]> | |
| 1079 | ||
| 1080 | </sect1> | |
| 1081 | ||
| 1082 | <p>Distribution upgrade should be done either locally from a | <sect1 id="upgrade_preparations"><heading>Prepare a safe environment for the upgrade</heading> |
| 1083 | ||
| 1084 | <p>The distribution upgrade should be done either locally from a | |
| 1085 | textmode virtual console (or a directly connected serial | textmode virtual console (or a directly connected serial |
| 1086 | terminal), or remotely via an <prgn/ssh/ link.</p> | terminal), or remotely via an <prgn/ssh/ link.</p> |
| 1087 | ||
| 1088 | <p><em/Important/: You should <em/not/ upgrade using <prgn/telnet/, | <p>In order to gain extra safety margin when upgrading remotely, we |
| 1089 | suggest that you run upgrade processes in the virtual console provided by | |
| 1090 | the <prgn/screen/ program, which enables safe reconnection and ensures | |
| 1091 | the upgrade process is not interrupted even if the remote connection | |
| 1092 | process fails.</p> | |
| 1093 | ||
| 1094 | <p><strong/Important!/ You should <em/not/ upgrade using <prgn/telnet/, | |
| 1095 | <prgn/rlogin/, <prgn/rsh/, or from an X session managed by <prgn/xdm/, | <prgn/rlogin/, <prgn/rsh/, or from an X session managed by <prgn/xdm/, |
| 1096 | <prgn/gdm/ or <prgn/kdm/ etc on the machine you are upgrading. That is | <prgn/gdm/ or <prgn/kdm/ etc on the machine you are upgrading. That is |
| 1097 | because each of those services may well be terminated during the | because each of those services may well be terminated during the |
| 1098 | upgrade, which can result in an <em/inaccessible/ system that is only | upgrade, which can result in an <em/inaccessible/ system that is only |
| 1099 | half-upgraded.</p> | half-upgraded.</p> |
| 1100 | ||
| 1101 | <sect1><heading>Disabling APT Pinning</heading> | <!-- TODO: surely gdm/kdm are sane? --> |
| 1102 | <!-- (vorlon) haha, no, gdm is not; I had that thought, and tested a gdm | |
| 1103 | restart on my live session ;) --> | |
| 1104 | </sect1> | |
| 1105 | ||
| 1106 | <sect1 id="glibc-kernel"><heading>Support for 2.2-kernels has been dropped</heading> | |
| 1107 | <p>In case you run a kernel prior to 2.4.1, | |
| 1108 | you need to upgrade to (at least) the | |
| 1109 | 2.4-series before upgrading <package/glibc/. | |
| 1110 | This should be done before starting the upgrade. | |
| 1111 | It is recommended that you directly upgrade to the 2.6.8 kernel available | |
| 1112 | in &oldreleasename;, instead of upgrading to a 2.4 kernel. | |
| 1113 | </p> | |
| 1114 | </sect1> | |
| 1115 | ||
| 1116 | </sect> | |
| 1117 | ||
| 1118 | <sect id="system-status"> | |
| 1119 | <heading>Checking system status</heading> | |
| 1120 | ||
| 1121 | <p>The upgrade process described in this chapter has been designed for | |
| 1122 | upgrades from "pure" &oldreleasename; systems without third-party | |
| 1123 | packages. | |
| 1124 | <!-- vorlon: remove for lenny --> | |
| 1125 | In particular, there are known problems with third-party packages | |
| 1126 | which install programs under <file>/usr/X11R6/bin/</file> causing problems | |
| 1127 | with upgrades due to the X.org transition (<ref id="xorg">). | |
| 1128 | <!-- --> | |
| 1129 | For greatest reliability of the upgrade process, you may wish to remove | |
| 1130 | third-party packages from your system before you begin upgrading.</p> | |
| 1131 | ||
| 1132 | <p>This procedure also assumes your system has been updated to the | |
| 1133 | latest point release of &oldreleasename;. If you have not done this | |
| 1134 | or are unsure, follow the instructions in <ref id="old-upgrade">.</p> | |
| 1135 | ||
| 1136 | <sect1><heading>Review actions pending in package manager</heading> | |
| 1137 | ||
| 1138 | <p>In some cases, the use of <prgn/apt-get/ for installing packages instead | |
| 1139 | of <prgn/aptitude/ might make <prgn/aptitude/ consider a package as | |
| 1140 | "unused" and schedule it for removal. In general, you should make sure | |
| 1141 | the system is fully up-to-date and "clean" before proceeding with | |
| 1142 | the upgrade.</p> | |
| 1143 | ||
| 1144 | <p>Because of this you should review if there are any pending actions | |
| 1145 | in the package manager <prgn/aptitude/. If a package is scheduled | |
| 1146 | for removal or update in the package manager, it might negatively impact | |
| 1147 | the upgrade procedure. Note that correcting this is only possible if your | |
| 1148 | <file/sources.list/ still points to <em/&oldreleasename/; and not to | |
| 1149 | <em/stable/ or <em/&releasename;/; see <ref id="old-sources">.</p> | |
| 1150 | ||
| 1151 | <p>To do this, you have to run <prgn/aptitude/'s user interface and | |
| 1152 | press 'g' ("Go"). If it shows any actions, you should review them and | |
| 1153 | either fix them or implement the suggested actions. If no actions are | |
| 1154 | suggested you will be presented with a message saying "No packages are | |
| 1155 | scheduled to be installed, removed, or upgraded".</p> | |
| 1156 | ||
| 1157 | </sect1> | |
| 1158 | ||
| 1159 | <sect1><heading>Disabling APT pinning</heading> | |
| 1160 | ||
| 1161 | <p>If you have configured APT to install certain packages from a | <p>If you have configured APT to install certain packages from a |
| 1162 | distribution other than stable (e.g from testing), you may have to | distribution other than stable (e.g. from testing), you may have to |
| 1163 | change your APT pinning configuration (stored in | change your APT pinning configuration (stored in |
| 1164 | <file>/etc/apt/preferences</file>) to allow the upgrade of packages to | <file>/etc/apt/preferences</file>) to allow the upgrade of packages to |
| 1165 | the versions in the new stable release. Further information on APT | the versions in the new stable release. Further information on APT |
| 1166 | pinning can be found in <manref name="apt_preferences" section="5">.</p> | pinning can be found in <manref name="apt_preferences" section="5">.</p> |
| <!-- FJP: Couldn't the advise to hold such packages prevent the upgrade of e.g. | ||
| libc6 if the package depends on the old version! --> | ||
| 1167 | ||
| 1168 | </sect1> | </sect1> |
| 1169 | ||
| 1170 | <sect1><heading>Checking Packages Status</heading> | <sect1 id="package_status"><heading>Checking packages status</heading> |
| 1171 | ||
| 1172 | <p>Regardless of the method used for upgrading, it is recommended | <p>Regardless of the method used for upgrading, it is recommended |
| 1173 | that you check the status of all packages first, and verify that | that you check the status of all packages first, and verify that |
| # | Line 294 release: architectures: | Line 1189 release: architectures: |
| 1189 | or | or |
| 1190 | ||
| 1191 | <example> | <example> |
| 1192 | # dpkg --get-selections > ~/curr-pkgs.txt | # dpkg --get-selections "*" > ~/curr-pkgs.txt |
| 1193 | </example></p> | </example></p> |
| 1194 | ||
| 1195 | <p>It is desirable to remove any holds before upgrading. If any | <p>It is desirable to remove any holds before upgrading. If any |
| 1196 | package that is essential for the upgrade is on hold, the upgrade | package that is essential for the upgrade is on hold, the upgrade |
| 1197 | will fail. You can identify packages on hold with | will fail.</p> |
| 1198 | ||
| 1199 | <p>Note that <prgn/aptitude/ uses a different method for registering | |
| 1200 | packages that are on hold than <prgn/apt-get/ and <prgn/dselect/. | |
| 1201 | You can identify packages on hold for <prgn/aptitude/ with | |
| 1202 | ||
| 1203 | <example> | <example> |
| 1204 | # dpkg --audit | # aptitude search "~ahold" | grep "^.h" |
| 1205 | </example></p> | |
| 1206 | ||
| 1207 | <p>If you want to check which packages you had on hold for | |
| 1208 | <prgn/apt-get/, you should use | |
| 1209 | <example> | |
| 1210 | # dpkg --get-selections | grep hold | |
| 1211 | </example></p> | </example></p> |
| 1212 | ||
| 1213 | <p>If you changed and recompiled a package locally, and didn't rename | <p>If you changed and recompiled a package locally, and didn't rename |
| 1214 | it or put an epoch in the version, you must put it on hold to prevent | it or put an epoch in the version, you must put it on hold to prevent |
| 1215 | it from being upgraded. The `hold' package state can be changed by | it from being upgraded.</p> |
| 1216 | using <prgn/aptitude/. With | |
| 1217 | <p>The "hold" package state for <prgn/aptitude/ can be changed using: | |
| 1218 | <example> | <example> |
| 1219 | aptitude hold | unhold <package> | # aptitude hold <var>package_name</var> |
| 1220 | </example> | </example> |
| 1221 | </p> | Replace <tt/hold/ with <tt/unhold/ to unset the "hold" state. |
| 1222 | </sect1> | </p> |
| 1223 | <sect1><heading>Special Considerations for SSH Users</heading> | |
| 1224 | <p>If there is anything you need to fix, it is best to make sure your | |
| 1225 | <p>The commercial SSH located in the <package/ssh/ package before | <file/sources.list/ still refers to &oldreleasename; as explained in |
| 1226 | release 2.2 or in the <package/ssh-nonfree/ package in release 2.2 has | <ref id="old-sources">.</p> |
| 1227 | been replaced by the DFSG free <package/ssh/ package (OpenSSH) in | </sect1> |
| 1228 | this release. The commercial SSH collection is no longer present. | |
| 1229 | The <package/ssh/ package includes a Debconf question which will | <sect1 id="backports"><heading>Unofficial sources and backports</heading> |
| 1230 | regenerate a configuration which is OpenSSH compatible.</p> | |
| 1231 | <p>If you have any non-Debian packages on your system, you should be | |
| 1232 | <sect1><heading>Directories Possibly Needing Attention</heading> | aware that these may be removed during the upgrade because of |
| 1233 | conflicting dependencies. If these packages were installed by adding | |
| 1234 | <p>It is important that the <file>/etc/rcS.d</file> directory | an extra package archive in your <file>/etc/apt/sources.list</file>, |
| 1235 | exists prior to the upgrade; the installation of the | you should check if that archive also offers packages compiled for |
| 1236 | <package/libc6/ package will fail otherwise.</p> | &releasename; and change the source line accordingly at the same time |
| 1237 | as your source lines for Debian packages.</p> | |
| 1238 | <p>The <file>/usr/share/doc</file> directory (if it exists | |
| 1239 | already) should not be a symlink (e.g. to <file>/usr/doc</file>), | <p>Some users may have unofficial backported "newer" versions of |
| 1240 | since that will cause some packages to break. However, symlinking | packages that <em/are/ in Debian installed on their &oldreleasename; |
| 1241 | <file>/usr/doc</file> to <file>/usr/share/doc</file> is allowed. | system. Such packages are most likely to cause problems during an |
| 1242 | Please note that if you use such a symlink there will be numerous | upgrade as they may result in file conflicts<footnote>Debian's |
| 1243 | messages about <file>/usr/doc</file> directories that can't be | package management system normally does not allow a package to remove |
| 1244 | removed. Those are normal, and you can safely ignore them.</p></sect1></sect> | or replace a file owned by another package unless it has been |
| 1245 | defined to replace that package.</footnote>. Section <ref id="trouble"> | |
| 1246 | has some information on how to deal with file conflicts if they should | |
| 1247 | <sect id="upgrade-process"><heading>Preparing Sources for APT</heading> | occur.</p> |
| 1248 | ||
| 1249 | <p>The recommended method of upgrading is to use <prgn/aptitude/, as | </sect1> |
| 1250 | described here. The built-in dependency analysis enables smooth | </sect> |
| 1251 | upgrades and easy installations.</p> | |
| 1252 | <!-- JFS: This section should be probably removed for lenny --> | |
| 1253 | <p>Any package installation operation must be run with superuser | <sect id="handle-conflict"><heading>Manually unmarking packages</heading> |
| 1254 | privileges, so either login as root or use <prgn/su/ or | |
| 1255 | <prgn/sudo/ to gain the necessary access rights.</p> | <p>To prevent <prgn/aptitude/ from removing some packages that were pulled |
| 1256 | in through dependencies, you need to manually unmark them as <em/auto/ | |
| 1257 | packages. This includes OpenOffice and Vim for desktop installs: | |
| 1258 | <!-- This is a no-op if none of them are installed --> | |
| 1259 | <example> | |
| 1260 | # aptitude unmarkauto openoffice.org vim | |
| 1261 | </example></p> | |
| 1262 | ||
| 1263 | <!-- JFS: This cannot be in the same line as above since it produces an ugly output if | |
| 1264 | you just have 2.4 kernels installed --> | |
| 1265 | <p>And 2.6 kernel images if you have installed them using a kernel metapackage: | |
| 1266 | ||
| 1267 | <example> | |
| 1268 | # aptitude unmarkauto $(dpkg-query -W 'kernel-image-2.6.*' | cut -f1) | |
| 1269 | </example></p> | |
| 1270 | ||
| 1271 | <p>Note: You can review which packages are marked as <em/auto/ in aptitude by running: | |
| 1272 | ||
| 1273 | <example> | |
| 1274 | # aptitude search 'i~M <package name>' | |
| 1275 | </example></p> | |
| 1276 | </sect> | |
| 1277 | ||
| 1278 | <sect id="upgrade-process"><heading>Preparing sources for APT</heading> | |
| 1279 | ||
| 1280 | <p>Before starting the upgrade you must set up <package/apt/'s | <p>Before starting the upgrade you must set up <package/apt/'s |
| 1281 | configuration file for package lists, | configuration file for package lists, |
| 1282 | <file>/etc/apt/sources.list</file>.</p> | <file>/etc/apt/sources.list</file>.</p> |
| 1283 | ||
| 1284 | <p><package/apt/ will consider all packages that can be found via | <p><package/apt/ will consider all packages that can be found via |
| 1285 | any "<tt>deb</tt>" line, and install the package with the highest | any "<tt>deb</tt>" line, and install the package with the highest |
| 1286 | version number, giving priority to the first mentioned lines (that | version number, giving priority to the first mentioned lines (that |
| # | Line 360 aptitude hold | unhold <package> | Line 1288 aptitude hold | unhold <package> |
| 1288 | name a local harddisk, then CD-ROMs, and then HTTP/FTP | name a local harddisk, then CD-ROMs, and then HTTP/FTP |
| 1289 | mirrors).</p> | mirrors).</p> |
| 1290 | ||
| 1291 | <sect1 id="network"><heading>Adding APT Internet Sources</heading> | <p>A release can often be referred to by both its codename (e.g. |
| 1292 | &oldreleasename;, &releasename;) and by its status name (i.e. | |
| 1293 | oldstable, stable, testing, unstable). Referring to a release by its | |
| 1294 | codename has the advantage that you will never be surprised by a | |
| 1295 | new release and for this reason is the approach taken here. It | |
| 1296 | does of course mean that you will have to watch out for release | |
| 1297 | announcements yourself. If you use the status name instead, you | |
| 1298 | will just see loads of updates for packages available as soon as a | |
| 1299 | release has happened.</p> | |
| 1300 | ||
| 1301 | <sect1 id="network"><heading>Adding APT Internet sources</heading> | |
| 1302 | ||
| 1303 | <p>The default configuration is set up for installation from main | <p>The default configuration is set up for installation from main |
| 1304 | Debian Internet servers, but you may wish to modify | Debian Internet servers, but you may wish to modify |
| # | Line 377 aptitude hold | unhold <package> | Line 1315 aptitude hold | unhold <package> |
| 1315 | <url id="&url-debian-mirrors;"> (look at the "Full list of | <url id="&url-debian-mirrors;"> (look at the "Full list of |
| 1316 | mirrors" section). HTTP mirrors are generally speedier than FTP | mirrors" section). HTTP mirrors are generally speedier than FTP |
| 1317 | mirrors.</p> | mirrors.</p> |
| <!-- FJP: 'Otherwise' does not refer back to anything here, so I deleted it | ||
| (unless the intention was to refer to local intr_a_net HTTP | ||
| servers in the previous para). --> | ||
| 1318 | ||
| 1319 | <p>For example, suppose your closest Debian mirror is | <p>For example, suppose your closest Debian mirror is |
| 1320 | <tt>&url-debian-mirror-eg;/</tt>. When inspecting that mirror | <tt>&url-debian-mirror-eg;/</tt>. When inspecting that mirror |
| # | Line 387 aptitude hold | unhold <package> | Line 1322 aptitude hold | unhold <package> |
| 1322 | directories are organized like this: | directories are organized like this: |
| 1323 | ||
| 1324 | <example> | <example> |
| 1325 | &url-debian-mirror-eg;/dists/stable/main/binary-&architecture;/... | &url-debian-mirror-eg;/dists/&releasename;/main/binary-&architecture;/... |
| 1326 | &url-debian-mirror-eg;/dists/stable/contrib/binary-&architecture;/... | &url-debian-mirror-eg;/dists/&releasename;/contrib/binary-&architecture;/... |
| 1327 | </example></p> | </example></p> |
| 1328 | ||
| 1329 | <p>To use this mirror with <prgn/apt/, you add this line to your | <p>To use this mirror with <prgn/apt/, you add this line to your |
| # | Line 403 deb &url-debian-mirror-eg; &releasename; | Line 1338 deb &url-debian-mirror-eg; &releasename; |
| 1338 | multiple directories.</p> | multiple directories.</p> |
| 1339 | ||
| 1340 | <p>After adding your new sources, disable the previously existing | <p>After adding your new sources, disable the previously existing |
| 1341 | "<tt/deb/" lines in <file/sources.list/, by placing a hash sign | "<tt/deb/" lines in <file/sources.list/ by placing a hash sign |
| 1342 | (<tt/#/) in front of them.</p> | (<tt/#/) in front of them.</p> |
| 1343 | ||
| <p>Any package needed for installation that is fetched from the | ||
| network is stored in <file>/var/cache/apt/archives</file> | ||
| (and the <file>partial/</file> subdirectory, during download), so | ||
| you must make sure you have enough space before attempting to | ||
| start the installation. With a reasonably extended Debian | ||
| installation, you can expect at least 300 MB of downloaded | ||
| data.</p> | ||
| 1344 | </sect1> | </sect1> |
| 1345 | ||
| 1346 | <sect1 id="localmirror"><heading>Adding APT Local Mirror Sources</heading> | <sect1 id="localmirror"><heading>Adding APT sources for a local mirror</heading> |
| 1347 | ||
| 1348 | <p>Instead of using HTTP or FTP packages mirrors, you may wish to | <p>Instead of using HTTP or FTP packages mirrors, you may wish to |
| 1349 | modify <file>/etc/apt/sources.list</file> to use a mirror on a | modify <file>/etc/apt/sources.list</file> to use a mirror on a |
| 1350 | local disk (possibly NFS-mounted).</p> | local disk (possibly mounted over NFS).</p> |
| 1351 | ||
| 1352 | <p>For example, your packages mirror may be under | <p>For example, your packages mirror may be under |
| 1353 | <file>/var/ftp/debian/</file>, and have main directories like | <file>/var/ftp/debian/</file>, and have main directories like |
| 1354 | this: | this: |
| 1355 | ||
| 1356 | <example> | <example> |
| 1357 | /var/ftp/debian/dists/stable/main/binary-&architecture;/... | /var/ftp/debian/dists/&releasename;/main/binary-&architecture;/... |
| 1358 | /var/ftp/debian/dists/stable/contrib/binary-&architecture;/... | /var/ftp/debian/dists/&releasename;/contrib/binary-&architecture;/... |
| 1359 | </example></p> | </example></p> |
| 1360 | ||
| 1361 | <p>To use this with <prgn/apt/, add this line to your | <p>To use this with <prgn/apt/, add this line to your |
| # | Line 443 deb file:/var/ftp/debian &releasename; m | Line 1370 deb file:/var/ftp/debian &releasename; m |
| 1370 | multiple directories.</p> | multiple directories.</p> |
| 1371 | ||
| 1372 | <p>After adding your new sources, disable the previously | <p>After adding your new sources, disable the previously |
| 1373 | existing "<tt/deb/" lines in <file/sources.list/, by placing a | existing "<tt/deb/" lines in <file/sources.list/ by placing a |
| 1374 | hash sign (<tt/#/) in front of them.</p></sect1> | hash sign (<tt/#/) in front of them.</p></sect1> |
| 1375 | ||
| 1376 | <sect1 id="cdroms"><heading>Adding APT CD-ROM Sources</heading> | <sect1 id="cdroms"><heading>Adding APT source from CD-ROM or DVD</heading> |
| <!-- FJP: Are these instructions also valid for adding DVD's? --> | ||
| <p>See above if you need to first install the latest version of | ||
| <package/apt/ and <package/dpkg/ packages, as described above.</p> | ||
| <!-- FJP: See above [...], as described above is a bit double. | ||
| Also, I don't think the need to update the package tools and how | ||
| to do that has been described 'above' yet. --> | ||
| 1377 | ||
| 1378 | <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 |
| 1379 | "<tt/deb/" lines in <file>/etc/apt/sources.list</file> by placing | "<tt/deb/" lines in <file>/etc/apt/sources.list</file> by placing |
| 1380 | a hash sign (<tt/#/) in front of them.</p> | a hash sign (<tt/#/) in front of them.</p> |
| 1381 | ||
| 1382 | <!-- Default cdrom mount point is /cdrom, not /media/cdrom and fixed!, see #282344 | |
| 1383 | (but the -d option of apt-cdrom allows scanning from somewhere else) --> | |
| 1384 | <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 |
| 1385 | enables mounting your CD-ROM drive at the <file>/cdrom</file> | enables mounting your CD-ROM drive at the <file>/cdrom</file> |
| 1386 | mount point (the exact <file>/cdrom</file> mount point is required | mount point (the exact <file>/cdrom</file> mount point is required |
| # | Line 477 deb file:/var/ftp/debian &releasename; m | Line 1398 deb file:/var/ftp/debian &releasename; m |
| 1398 | <p>To verify it works, insert a CD and try running | <p>To verify it works, insert a CD and try running |
| 1399 | ||
| 1400 | <example> | <example> |
| 1401 | mount /cdrom # this will mount the CD to the mount point | # mount /cdrom # this will mount the CD to the mount point |
| 1402 | ls -alF /cdrom # this should show the CD's root directory | # ls -alF /cdrom # this should show the CD's root directory |
| 1403 | umount /cdrom # this will unmount the CD | # umount /cdrom # this will unmount the CD |
| 1404 | </example></p> | </example></p> |
| 1405 | ||
| 1406 | <p>Next, run: | <p>Next, run: |
| 1407 | ||
| 1408 | <example> | <example> |
| 1409 | apt-cdrom add | # apt-cdrom add |
| 1410 | </example> | </example> |
| 1411 | ||
| 1412 | for each Debian Binary CD-ROM you have, to add the data about | for each Debian Binary CD-ROM you have, to add the data about |
| # | Line 494 apt-cdrom add | Line 1415 apt-cdrom add |
| 1415 | </sect> | </sect> |
| 1416 | ||
| 1417 | <sect id="upgradingpackages"><heading>Upgrading packages</heading> | <sect id="upgradingpackages"><heading>Upgrading packages</heading> |
| 1418 | ||
| 1419 | <p>The recommended tool for upgrading between &debian; releases is | <p>The recommended way to upgrade from previous &debian; releases is |
| 1420 | to use the package management tool <prgn>aptitude</prgn>. This tool | to use the package management tool <prgn>aptitude</prgn>. This program |
| 1421 | makes safer decisions about package installations than running | makes safer decisions about package installations than running |
| 1422 | <prgn>apt-get</prgn> directly.</p> | <prgn>apt-get</prgn> directly.</p> |
| 1423 | ||
| 1424 | <p>Don't forget to mount all needed partitions (notably the root | <p>Don't forget to mount all needed partitions (notably the root |
| 1425 | and <file>/usr</file> partitions) read-write, with a command | and <file>/usr</file> partitions) read-write, with a command |
| 1426 | like: | like: |
| 1427 | ||
| 1428 | <example> | <example> |
| 1429 | mount -o remount,rw /<var>mountpoint</var> | # mount -o remount,rw /<var>mountpoint</var> |
| 1430 | </example></p> | </example></p> |
| 1431 | ||
| 1432 | <p>Next ensure that the APT source entries (in | <p>Next you should double-check that the APT source entries (in |
| 1433 | <file>/etc/apt/sources.list</file>) refer to the <tt>'stable'</tt> | <file>/etc/apt/sources.list</file>) refer either to |
| 1434 | distribution and do not refer to it by its codename (e.g. | "<tt/&releasename;/" or to "<tt>stable</tt>". There should not be |
| 1435 | <tt>&oldreleasename;</tt>). | any sources entries pointing to &oldreleasename;. |
| 1436 | Note: source lines for a CD-ROM will often refer to "<tt/unstable/"; | |
| 1437 | although this may be confusing, you should <em/not/ change it.</p> | |
| 1438 | ||
| 1439 | <sect1 id="record_session"><heading>Recording the session</heading> | |
| 1440 | ||
| 1441 | <p>It is strongly recommended that you use the | <p>It is strongly recommended that you use the |
| 1442 | <prgn>/usr/bin/script</prgn> program to record a transcript of the | <prgn>/usr/bin/script</prgn> program to record a transcript of the |
| 1443 | upgrade session. Then if any problems develop, you will have a log of | upgrade session. Then if a problem occurs, you will have a log of |
| 1444 | what happened, and if needed, can provide exact information in a bug | what happened, and if needed, can provide exact information in a bug |
| 1445 | report. To start the recording, type: | report. To start the recording, type: |
| 1446 | ||
| 1447 | <example> | <example> |
| 1448 | script -a ~/upgrade-to-sarge.typescript | # script -t 2>~/upgrade-&releasename;.time -a ~/upgrade-&releasename;.script |
| 1449 | </example> | </example> |
| 1450 | ||
| 1451 | or similar. Do not put the typescript file in a temporary | or similar. Do not put the typescript file in a temporary |
| 1452 | directory such as <file>/tmp</file> or <file>/var/tmp</file> (files | directory such as <file>/tmp</file> or <file>/var/tmp</file> (files |
| 1453 | in those directories may be deleted during the upgrade or during any | in those directories may be deleted during the upgrade or during any |
| 1454 | restart).</p> | restart).</p> |
| 1455 | ||
| 1456 | <p>Next the <package>aptitude</package> package needs to be installed. | <p>The typescript will also allow you to review information that has |
| 1457 | This is done with:</p> | scrolled off-screen. Just switch to VT2 (using <tt/Alt-F2/) and, after |
| 1458 | logging in, use <tt>less -R ~root/upgrade-&releasename;.script</tt> | |
| 1459 | to view the file.</p> | |
| 1460 | ||
| 1461 | <p>After you have completed the upgrade, you can stop <prgn/script/ | |
| 1462 | by typing <tt/exit/ at the prompt.</p> | |
| 1463 | ||
| 1464 | <!-- TODO: Could mention the script I provided in 400725 which is useful if you | |
| 1465 | have not dumped the timing file --> | |
| 1466 | <p>If you have used the <em>-t</em> switch for <prgn/script/ | |
| 1467 | you can use the <prgn/scriptreplay/ program to replay the whole session: | |
| 1468 | ||
| 1469 | <example> | |
| 1470 | # scriptreplay ~/upgrade-&releasename;.time ~/upgrade-&releasename;.script | |
| 1471 | </example> | |
| 1472 | ||
| 1473 | </p> | |
| 1474 | </sect1> | |
| 1475 | ||
| 1476 | <sect1 id="updating_lists"><heading>Updating the package list</heading> | |
| 1477 | ||
| 1478 | <p>First the list of available packages for the new release needs to | |
| 1479 | be fetched. This is done by executing:</p> | |
| 1480 | ||
| 1481 | <p><example> | <p><example> |
| 1482 | apt-get install aptitude | # aptitude update |
| 1483 | </example></p> | </example></p> |
| 1484 | ||
| 1485 | <p>Provided that you have a working APT configuration as described | <!-- JFS: Hopefully this will be fixed in lenny --> |
| 1486 | above this will install the &releasename; version of | <p>Running this the first time new sources are updated will print out |
| 1487 | <prgn>aptitude</prgn>.</p> | some warnings related to the availability of the sources. These |
| 1488 | <!-- FJP: Will it really? Haven't we have just instructed users to point | warnings are harmless and will not appear if you rerun the command again. |
| 1489 | everything to the new release? --> | </p> |
| 1490 | ||
| 1491 | <p>First <prgn>aptitude</prgn> needs to fetch a list of new and | </sect1> |
| 1492 | updated packages for the new release. This is done by executing:</p> | |
| 1493 | <sect1><heading>Make sure you have sufficient space for the upgrade</heading> | |
| 1494 | <p><example> | |
| 1495 | aptitude update | <p>You have to make sure before upgrading your system that you have |
| 1496 | sufficient hard disk space when you start the full system upgrade | |
| 1497 | described in <ref id="upgrading_other">. First, any package needed for | |
| 1498 | installation that is fetched from the network is stored in | |
| 1499 | <file>/var/cache/apt/archives</file> (and the <file>partial/</file> | |
| 1500 | subdirectory, during download), so you must make sure you have enough space | |
| 1501 | on the file system partition that holds <file>/var/</file> | |
| 1502 | to temporarily download the packages that will be installed in your system. | |
| 1503 | After the download, you will probably need more space in other | |
| 1504 | file system partitions in order to both install upgraded packages (which | |
| 1505 | might contain bigger binaries or more data) and new packages that will be pulled | |
| 1506 | in for the upgrade. If your system does not have sufficient space you | |
| 1507 | might end up with an incomplete upgrade that might be difficult to | |
| 1508 | recover from.</p> | |
| 1509 | ||
| 1510 | <!-- JFS: Apt will not always abort if you do not have enough disk space. | |
| 1511 | For reference see: #247331, #214119, #192146, #185201, #40438 and #32919 --> | |
| 1512 | ||
| 1513 | <p>Both <prgn/aptitude/ and <prgn/apt/ will show you detailed information | |
| 1514 | of the disk space needed for the installation. Before executing the | |
| 1515 | upgrade, you can see this estimate by running: | |
| 1516 | </p> | |
| 1517 | ||
| 1518 | <p><example> | |
| 1519 | # aptitude -y -s -f --with-recommends dist-upgrade | |
| 1520 | [ ... ] | |
| 1521 | XXX upgraded, XXX newly installed, XXX to remove and XXX not upgraded. | |
| 1522 | Need to get xx.xMB/yyyMB of archives. After unpacking AAAMB will be used. | |
| 1523 | Would download/install/remove packages. | |
| 1524 | </example></p> | |
| 1525 | ||
| 1526 | ||
| 1527 | <p>If you do not have enough space for the upgrade, make sure you free up | |
| 1528 | space beforehand. You can: | |
| 1529 | </p> | |
| 1530 | ||
| 1531 | <!-- JFS There are more tips at | |
| 1532 | http://lists.debian.org/debian-user/2005/11/msg02078.html or | |
| 1533 | http://www.debian-administration.org/articles/143 | |
| 1534 | but maybe that should be in the Debian Reference best and pointed from here --> | |
| 1535 | <p> | |
| 1536 | <list> | |
| 1537 | <!-- JFS: Does aptitude to 'apt-get autoclean' by itself? --> | |
| 1538 | <item>Remove packages that have been previously downloaded for | |
| 1539 | installation (at <file>/var/cache/apt/archive</file>). Cleaning up the | |
| 1540 | package cache by running <prgn>apt-get clean</prgn> or <prgn>aptitude | |
| 1541 | clean</prgn> will remove all previously downloaded package files. | |
| 1542 | ||
| 1543 | <!-- JFS Point to http://www.enricozini.org/blog/eng/pkgsizestat.html ? | |
| 1544 | Enrico's script shows files that occupy space in a given partition | |
| 1545 | which might be good for systems that are heavily partitioned --> | |
| 1546 | ||
| 1547 | <item>Remove old packages you no longer use. If you have | |
| 1548 | <prgn/popularity-contest/ installed, you can use | |
| 1549 | <prgn/popcon-largest-unused/ to list the packages you do not use in the | |
| 1550 | system that occupy the most space. You can also use <prgn/deborphan/ | |
| 1551 | or <prgn/debfoster/ to find obsolete packages (see | |
| 1552 | <ref id="obsolete">). | |
| 1553 | Alternatively you can start <prgn/aptitude/ in "visual mode" and find | |
| 1554 | obsolete packages under "Obsolete and Locally Created Packages". | |
| 1555 | ||
| 1556 | <item>Remove packages taking up too much space, which are not currently | |
| 1557 | needed (you can always reinstall them after the | |
| 1558 | upgrade). You can list the packages that take up most of the disk space | |
| 1559 | with <prgn/dpigs/ (available in the <package/debian-goodies/ package) | |
| 1560 | or with <prgn/wajig/ (running <tt>wajig size</tt>). | |
| 1561 | ||
| 1562 | <!-- TODO: consider this for lenny | |
| 1563 | You can list packages that take up most of the disk space with | |
| 1564 | <prgn/aptitude/ . Start <prgn/aptitude/ into "visual mode", select | |
| 1565 | "Views" and "New Flat Package List" (this menu entry is available only | |
| 1566 | after etch version), press "l" and enter "~i", press "S" and enter | |
| 1567 | "~installsize", then it will give you nice list to work with. Doing | |
| 1568 | this after partial upgrade described in <ref id="upgrading_aptitude"> | |
| 1569 | should give you access to this new feature. | |
| 1570 | --> | |
| 1571 | ||
| 1572 | <item>Temporarily move to another system, or permanently remove, system | |
| 1573 | logs residing under <file>/var/log/</file>. | |
| 1574 | ||
| 1575 | </list></p> | |
| 1576 | ||
| 1577 | <p>Note that in order to safely remove packages, it is advisable to | |
| 1578 | switch your <file>sources.list</file> back to &oldreleasename; as | |
| 1579 | described in <ref id="old-sources">.</p> | |
| 1580 | ||
| 1581 | </sect1> | |
| 1582 | ||
| 1583 | <sect1 id="minimal_upgrade"><heading>Minimal system upgrade</heading> | |
| 1584 | ||
| 1585 | <p>Because of certain necessary package conflicts between &oldreleasename; | |
| 1586 | and &releasename;, running <tt>aptitude dist-upgrade</tt> directly will | |
| 1587 | often remove large numbers of packages that you will want to keep. We | |
| 1588 | therefore recommend a two-part upgrade process, first a minimal upgrade to | |
| 1589 | overcome these conflicts, then a full <tt>dist-upgrade</tt>. | |
| 1590 | </p> | |
| 1591 | ||
| 1592 | <p>First, run: | |
| 1593 | <example> | |
| 1594 | # aptitude upgrade | |
| 1595 | </example> | |
| 1596 | </p> | |
| 1597 | ||
| 1598 | <p>This has the effect of upgrading those packages which can be upgraded | |
| 1599 | without requiring any other packages to be removed or installed.</p> | |
| 1600 | ||
| 1601 | <p>Follow the minimal upgrade with: | |
| 1602 | <example> | |
| 1603 | # aptitude install initrd-tools | |
| 1604 | </example></p> | |
| 1605 | ||
| 1606 | <p>This step will automatically upgrade <package/libc6/ and | |
| 1607 | <package/locales/ and will pull in SELinux support libraries | |
| 1608 | (<package/libselinux1/). At this point, some running services will be | |
| 1609 | restarted, including <prgn/xdm/, <prgn/gdm/ and <prgn/kdm/. As a | |
| 1610 | consequence, local X11 sessions will be disconnected.</p> | |
| 1611 | ||
| 1612 | <p>The next step will vary depending on the set of packages that you have | |
| 1613 | installed. These release notes give general advice about which method | |
| 1614 | should be used, but if in doubt, it is recommended that you examine the | |
| 1615 | package removals proposed by each method before proceeding.</p> | |
| 1616 | <p>Some common packages that are expected to be removed include | |
| 1617 | <package/base-config/, <package/hotplug/, <package/xlibs/, | |
| 1618 | <package/netkit-inetd/, <package/python2.3/, <package/xfree86-common/, | |
| 1619 | and <package/xserver-common/. For a more complete list of packages | |
| 1620 | obsoleted in &releasename;, see <ref id="obsolete">. | |
| 1621 | </p> | |
| 1622 | ||
| 1623 | <sect2 id="minimal_upgrade_desktop"><heading>Upgrading a desktop system</heading> | |
| 1624 | <p>This upgrade path has been verified to work on systems with the sarge | |
| 1625 | <tt>desktop</tt> task installed. It is probably the method that will give | |
| 1626 | the best results on systems with the <tt>desktop</tt> task installed, or | |
| 1627 | with the <tt>gnome</tt> or <tt>kde</tt> packages installed. | |
| 1628 | ||
| 1629 | <p>It is probably <em>not</em> the correct method to use if you do not | |
| 1630 | already have the <package/libfam0c102/ and <package/xlibmesa-glu/ packages | |
| 1631 | installed: | |
| 1632 | <example> | |
| 1633 | # dpkg -l libfam0c102 | grep ^ii | |
| 1634 | # dpkg -l xlibmesa-glu | grep ^ii | |
| 1635 | </example> | |
| 1636 | </p> | |
| 1637 | ||
| 1638 | <p>If you do have a full desktop system installed, run: | |
| 1639 | <example> | |
| 1640 | # aptitude install libfam0 xlibmesa-glu | |
| 1641 | </example></p> | </example></p> |
| 1642 | ||
| 1643 | <p>Once <prgn>aptitude</prgn> has information on all the available | </sect2> |
| 1644 | packages, the system is almost ready to be fully upgraded.</p> | |
| 1645 | <!-- FJP: Why 'almost'? The next command will perform the upgrade. | <sect2 id="minimal_upgrade_x_server"><heading>Upgrading a system with some X packages installed</heading> |
| 1646 | 'Almost' implies the user needs to do something else first... --> | <p>Systems with some X packages installed, but not the full |
| 1647 | <tt>desktop</tt> task, require a different method. This method applies in | |
| 1648 | general to systems with <package/xfree86-common/ installed, including some | |
| 1649 | server systems which have <package/tasksel/ server tasks installed as some | |
| 1650 | of these tasks include graphical management tools. It is likely the | |
| 1651 | correct method to use on systems which run X, but do not have the full | |
| 1652 | <tt>desktop</tt> task installed. | |
| 1653 | <example> | |
| 1654 | # dpkg -l xfree86-common | grep ^ii | |
| 1655 | </example> | |
| 1656 | </p> | |
| 1657 | ||
| 1658 | <p>First, check whether you have the <package/libfam0c102/ and | |
| 1659 | <package/xlibmesa-glu/ packages installed. | |
| 1660 | <example> | |
| 1661 | # dpkg -l libfam0c102 | grep ^ii | |
| 1662 | # dpkg -l xlibmesa-glu | grep ^ii | |
| 1663 | </example> | |
| 1664 | </p> | |
| 1665 | ||
| 1666 | <p>If you do not have <package/libfam0c102/ installed, do not include | |
| 1667 | <package/libfam0/ in the following commandline. If you do not have | |
| 1668 | <package/xlibmesa-glu/ installed, do not include it in the following | |
| 1669 | commandline. | |
| 1670 | <footnote>This command will determine whether you need libfam0 and | |
| 1671 | xlibmesa-glu installed, and auto-select them for you: | |
| 1672 | <example> | |
| 1673 | # aptitude install x11-common \ | |
| 1674 | $(dpkg-query --showformat '${Package} ${Status}\n' -W libfam0c102 xlibmesa-glu \ | |
| 1675 | | grep 'ok installed$' | sed -e's/ .*//; s/c102//') | |
| 1676 | </example> | |
| 1677 | </footnote> | |
| 1678 | ||
| 1679 | <example> | |
| 1680 | # aptitude install x11-common <var>libfam0</var> <var>xlibmesa-glu</var> | |
| 1681 | </example> | |
| 1682 | </p> | |
| 1683 | ||
| 1684 | <p>Note that installing <package/libfam0/ will also install the File Alteration Monitor | |
| 1685 | (<package/fam/) as well as the RPC portmapper (<package/portmap/) if | |
| 1686 | not already available in your system. Both packages will enable a new | |
| 1687 | network service in the system although they can both be configured to | |
| 1688 | be bound to the (internal) loopback network device.</p> | |
| 1689 | </sect2> | |
| 1690 | ||
| 1691 | <sect2 id="minimal_upgrade_server"><heading>Upgrading a system with no X support installed</heading> | |
| 1692 | <p>On a system with no X, no additional aptitude install command should be | |
| 1693 | required, and you can move on to the next step. | |
| 1694 | </p> | |
| 1695 | ||
| 1696 | </sect2> | |
| 1697 | ||
| 1698 | </sect1> | |
| 1699 | ||
| 1700 | <sect1 id="upgrading_kernel"><heading>Upgrading the kernel</heading> | |
| 1701 | ||
| 1702 | <p>The <package/udev/ version in &releasename; does not support kernel | |
| 1703 | versions earlier than 2.6.15 (which includes &oldreleasename; 2.6.8 | |
| 1704 | kernels), and the <package/udev/ version in &oldreleasename; will not work | |
| 1705 | properly with the latest kernels. In addition, installing the | |
| 1706 | &releasename; version of <package/udev/ will force the removal of | |
| 1707 | <package/hotplug/, used by Linux 2.4 kernels.</p> | |
| 1708 | ||
| 1709 | <p>As a consequence, the previous kernel package will probably not boot | |
| 1710 | properly after this upgrade. Similarly, there is a time window during | |
| 1711 | the upgrade in which <package/udev/ has been upgraded but the latest kernel | |
| 1712 | has not been installed. If the system were to be rebooted at this point, | |
| 1713 | in the middle of the upgrade, it might not be bootable because of | |
| 1714 | drivers not being properly detected and loaded. (See <ref | |
| 1715 | id="upgrade_preparations"> for recommendations on preparing for this | |
| 1716 | possibility if you are upgrading remotely.)</p> | |
| 1717 | ||
| 1718 | <p>Unless your system has the <tt>desktop</tt> task installed, or | |
| 1719 | other packages that would cause an unacceptable number of package | |
| 1720 | removals, it is therefore recommended that you upgrade the kernel on its | |
| 1721 | own at this point.</p> | |
| 1722 | ||
| 1723 | <p>To proceed with this kernel upgrade, run: | |
| 1724 | <example> | |
| 1725 | # aptitude install linux-image-2.6-<var>flavor</var> | |
| 1726 | </example> | |
| 1727 | ||
| 1728 | See <ref id="kernel-metapackage"> for help in determining which flavor of | |
| 1729 | kernel package you should install.</p> | |
| 1730 | ||
| 1731 | <p>In the desktop case, it is unfortunately not possible to ensure the | |
| 1732 | new kernel package is installed immediately after the new <package/udev/ | |
| 1733 | is installed, so there is a window of unknown length when your system | |
| 1734 | will have no kernel installed with full hotplug support. See <ref | |
| 1735 | id="newkernel"> for information on configuring your system to not depend | |
| 1736 | on hotplug for booting.</p> | |
| 1737 | ||
| 1738 | </sect1> | |
| 1739 | ||
| 1740 | <!-- TODO: For lenny, consider restoring the section 'Upgrade aptitude' --> | |
| 1741 | ||
| 1742 | <sect1 id="upgrading_other"><heading>Upgrading the rest of the system</heading> | |
| 1743 | ||
| 1744 | <p>You are now ready to continue with the main part of the | |
| 1745 | upgrade. Execute:</p> | |
| 1746 | <!-- NOTE (jfs): we have not tested with the -f and with-recommends option --> | |
| 1747 | <p><example> | <p><example> |
| 1748 | aptitude -f --with-suggests --with-recommends dist-upgrade | # aptitude dist-upgrade |
| 1749 | </example></p> | </example></p> |
| 1750 | ||
| 1751 | <p>This will perform a complete upgrade of the system, i.e. install | <p>This will perform a complete upgrade of the system, i.e. install |
| 1752 | the newest available versions of all packages, and resolve all | the newest available versions of all packages, and resolve all |
| 1753 | possible dependency changes between packages in different releases. | possible dependency changes between packages in different releases. |
| 1754 | If necessary, it will install some new packages (usually new library | If necessary, it will install some new packages (usually new library |
| 1755 | versions, or renamed packages), and remove any conflicting obsoleted | versions, or renamed packages), and remove any conflicting obsoleted |
| 1756 | packages (such as <package>console-tools-libs</package>).</p> | packages.</p> |
| 1757 | ||
| 1758 | <p>When upgrading from a set of CD-ROMs, you will be asked to | <p>When upgrading from a set of CD-ROMs, you will be asked to |
| 1759 | insert specific CDs at several points during the upgrade. You | insert specific CDs at several points during the upgrade. You |
| 1760 | might have to insert the same CD multiple times; this is due to | might have to insert the same CD multiple times; this is due to |
| 1761 | inter-related packages that have been spread out over the CDs.</p> | inter-related packages that have been spread out over the CDs.</p> |
| 1762 | ||
| 1763 | <p>New versions of currently installed packages that cannot be | <p>New versions of currently installed packages that cannot be |
| 1764 | upgraded without changing the install status of another package will | upgraded without changing the install status of another package will |
| 1765 | be left at their current version (displayed as "held back"). This can | be left at their current version (displayed as "held back"). This can |
| 1766 | be resolved by either using <prgn>aptitude</prgn> to choose these | be resolved by either using <prgn>aptitude</prgn> to choose these |
| 1767 | packages for installation or by trying <tt>aptitude -f install | packages for installation or by trying <tt>aptitude -f install |
| 1768 | <package></tt>.</p> | <var>package</var></tt>.</p> |
| 1769 | ||
| 1770 | <p>The <tt/--fix-broken/ (or just <tt/-f/) option causes | </sect1> |
| 1771 | <package/apt/ to attempt to correct a system with broken | |
| 1772 | dependencies in place. <package/apt/ does not allow broken package | <!-- JFS: Bug #403496 --> |
| 1773 | dependencies to exist on a system.</p> | <sect1 id="get_signatures"><heading>Getting package signatures</heading> |
| 1774 | ||
| 1775 | <p>After the upgrade, with the new version of <prgn/apt/ you can now | |
| 1776 | update your package information, which will include the new package | |
| 1777 | signature checking mechanism:</p> | |
| 1778 | <p><example> | |
| 1779 | # aptitude update | |
| 1780 | </example></p> | |
| 1781 | ||
| 1782 | <p>The upgrade will have already retrieved and enabled the signing | |
| 1783 | keys for Debian's package archives. If you add other (unofficial) | |
| 1784 | package sources, <prgn/apt/ will print warnings related to its | |
| 1785 | inability to confirm that packages downloaded from them are | |
| 1786 | legitimate and have not been tampered with. For more information | |
| 1787 | please see <ref id="pkgmgmt">. | |
| 1788 | </p> | |
| 1789 | ||
| 1790 | <!-- JFS: Bug #376158 --> | |
| 1791 | <p>You will notice that, since you are using the new version of | |
| 1792 | <prgn/apt/, it will download package differences files (<tt/pdiff/) | |
| 1793 | instead of the full package index list. For more information on this | |
| 1794 | feature please read <ref id="apt-pdiff">.</p> | |
| 1795 | ||
| 1796 | </sect1> | |
| 1797 | ||
| 1798 | <sect1 id="trouble"><heading>Possible Issues During or After Upgrade</heading> | <sect1 id="trouble"><heading>Possible issues during upgrade</heading> |
| 1799 | ||
| 1800 | <p>Sometimes it's necessary to enable APT::Force-LoopBreak option | <p>If an operation using <prgn/aptitude/, <prgn/apt-get/, or |
| 1801 | <prgn/dpkg/ fails with the error | |
| 1802 | <example> | |
| 1803 | E: Dynamic MMap ran out of room | |
| 1804 | </example> | |
| 1805 | the default cache space is insufficient. You can solve this by either | |
| 1806 | removing or commenting lines you don't need in | |
| 1807 | <file>/etc/apt/sources.list</file> or by increasing the cache size. | |
| 1808 | The cache size can be increased by setting <tt/APT::Cache-Limit/ in | |
| 1809 | <file>/etc/apt/apt.conf</file>. The following command will set it | |
| 1810 | to a value that should be sufficient for the upgrade: | |
| 1811 | <example> | |
| 1812 | # echo 'APT::Cache-Limit "12500000";' >> /etc/apt/apt.conf | |
| 1813 | </example> | |
| 1814 | This assumes that you do not yet have this variable set in that file.</p> | |
| 1815 | ||
| 1816 | <!-- (vorlon) FIXME: I recommend dropping this paragraph, it doesn't seem relevant | |
| 1817 | for sarge->etch? | |
| 1818 | --> | |
| 1819 | <p>Sometimes it's necessary to enable the <tt/APT::Force-LoopBreak/ option | |
| 1820 | in APT to be able to temporarily remove an essential package due | in APT to be able to temporarily remove an essential package due |
| 1821 | to a Conflicts/Pre-Depends loop. <prgn/aptitude/ will alert you of | to a Conflicts/Pre-Depends loop. <prgn/aptitude/ will alert you of |
| 1822 | this and abort the upgrade. You can work around that by specifying | this and abort the upgrade. You can work around that by specifying |
| 1823 | <tt>-o APT::Force-LoopBreak=1</tt> option on <prgn/aptitude/ | <tt>-o APT::Force-LoopBreak=1</tt> option on <prgn/aptitude/ |
| 1824 | command line.</p> | command line.</p> |
| 1825 | <!-- JFS: Shouldn't this mention also Apt's configuration file? --> | |
| 1826 | ||
| 1827 | <p>It is possible that a system's dependency structure can be so | <p>It is possible that a system's dependency structure can be so |
| 1828 | corrupt as to require manual intervention. Usually this means | corrupt as to require manual intervention. Usually this means |
| 1829 | using <prgn/aptitude/ or | using <prgn/aptitude/ or |
| 1830 | ||
| 1831 | <example> | <example> |
| 1832 | dpkg --remove <var>packagename</var> | # dpkg --remove <var>package_name</var> |
| 1833 | </example> | </example> |
| 1834 | ||
| 1835 | to eliminate some of the offending packages, or | to eliminate some of the offending packages, or |
| 1836 | ||
| 1837 | <example> | <example> |
| 1838 | aptitude --fix-broken install | # aptitude --fix-broken install |
| 1839 | dpkg --configure --pending | # dpkg --configure --pending |
| 1840 | </example></p> | </example></p> |
| 1841 | ||
| 1842 | <p>In extreme cases you might have to force re-installation with a | <p>In extreme cases you might have to force re-installation with a |
| 1843 | command like | command like |
| 1844 | ||
| 1845 | <example> | <example> |
| 1846 | dpkg --install /path/to/packagename.deb | # dpkg --install <var>/path/to/package_name.deb</var> |
| 1847 | </example></p> | |
| 1848 | ||
| 1849 | <p>File conflicts should not occur if you upgrade from a "pure" | |
| 1850 | &oldreleasename; system, but can occur if you have unofficial | |
| 1851 | backports installed. A file conflict will result in an error like: | |
| 1852 | ||
| 1853 | <example> | |
| 1854 | Unpacking <var><package-foo></var> (from <var><package-foo-file></var>) ... | |
| 1855 | dpkg: error processing <var><package-foo></var> (--install): | |
| 1856 | trying to overwrite `<var><some-file-name></var>', | |
| 1857 | which is also in package <var><package-bar></var> | |
| 1858 | dpkg-deb: subprocess paste killed by signal (Broken pipe) | |
| 1859 | Errors were encountered while processing: | |
| 1860 | <var><package-foo></var> | |
| 1861 | </example></p> | |
| 1862 | ||
| 1863 | <p>You can try to solve a file conflict by forcibly removing the | |
| 1864 | package mentioned on the <em/last/ line of the error message: | |
| 1865 | ||
| 1866 | <example> | |
| 1867 | # dpkg -r --force-depends <var>package_name</var> | |
| 1868 | </example></p> | </example></p> |
| 1869 | ||
| 1870 | <p>After fixing things up, you should be able to resume the | <p>After fixing things up, you should be able to resume the |
| 1871 | upgrade by repeating the previously described <tt/dist-upgrade/ | upgrade by repeating the previously described <tt/aptitude/ |
| 1872 | commands.</p> | commands.</p> |
| 1873 | ||
| 1874 | <p>During the upgrade, you will be asked questions to configure or | <p>During the upgrade, you will be asked questions regarding the |
| 1875 | re-configure several packages. When you are asked if any file in | configuration or re-configuration of several packages. When you are |
| 1876 | the <file>/etc/init.d</file> or <file>/etc/terminfo</file> | asked if any file in the <file>/etc/init.d</file> or |
| 1877 | directories, or the <file>/etc/manpath.config</file> file should | <file>/etc/terminfo</file> directories, or the |
| 1878 | be replaced by the package maintainer's version, it's usually | <file>/etc/manpath.config</file> file should be replaced by the |
| 1879 | necessary to answer `yes' to ensure system consistency. You can | package maintainer's version, it's usually necessary to answer `yes' |
| 1880 | always revert to the old versions, since they will be saved with a | to ensure system consistency. You can always revert to the old |
| 1881 | <tt/.dpkg-old/ extension.</p> | versions, since they will be saved with a <tt/.dpkg-old/ |
| 1882 | extension.</p> | |
| 1883 | ||
| 1884 | <p>If you're not sure what to do, write down the name of the | <p>If you're not sure what to do, write down the name of the |
| 1885 | package or file, and sort things out at a later time. You can | package or file and sort things out at a later time. You can |
| 1886 | search in the typescript file to review the information that | search in the typescript file to review the information that |
| 1887 | was on the screen during the upgrade.</p></sect1> | was on the screen during the upgrade.</p> |
| 1888 | ||
| 1889 | <sect1 id="nownownow"><heading>ToDo Before the Next Reboot</heading> | </sect1> |
| 1890 | </sect> | |
| 1891 | ||
| 1892 | <sect id="newkernel"><heading>Upgrading your kernel and related | |
| 1893 | packages</heading> | |
| 1894 | ||
| 1895 | <p>This section explains how to upgrade your kernel and identifies | |
| 1896 | potential issues related to this upgrade. You can either install one of | |
| 1897 | the <package/linux-image-*/ packages provided by Debian, or compile a | |
| 1898 | customized kernel from source.</p> | |
| 1899 | ||
| 1900 | <![ %uses-initrd [ | |
| 1901 | <p>Note that a lot of information in this section is based on the | |
| 1902 | assumption that you will be using one of the modular Debian kernels, | |
| 1903 | together with <package/initramfs-tools/ and <package/udev/. If you | |
| 1904 | choose to use a custom kernel that does not require an initrd or | |
| 1905 | if you use a different initrd generator, some of the information may not be | |
| 1906 | relevant for you.</p> | |
| 1907 | ]]> | |
| 1908 | <![ %no-initrd [ | |
| 1909 | <p>Note that this section contains a lot of information related to | |
| 1910 | the use of <package/initramfs-tools/ and <package/udev/. However, | |
| 1911 | as the Debian kernels for &architecture; do not use an initrd to | |
| 1912 | boot the system, some of this information may not be relevant for | |
| 1913 | you. The information is still included as you may have | |
| 1914 | <package/udev/ installed for other reasons.</p> | |
| 1915 | ]]> | |
| 1916 | <p>Note also that if <package/udev/ is <em/not/ installed on your | |
| 1917 | system, it is still possible to use <package/hotplug/ for | |
| 1918 | hardware discovery.</p> | |
| 1919 | ||
| 1920 | <![ %defaulted-2.4 [ | |
| 1921 | <p>If you are currently using a 2.4 kernel, you should also read | |
| 1922 | <ref id="upgrade-to-2.6"> carefully.</p> | |
| 1923 | ]]> | |
| 1924 | ||
| 1925 | <sect1 id="kernel-metapackage"><heading>Installing the kernel metapackage</heading> | |
| 1926 | <p>When you dist-upgrade from &oldreleasename; to &releasename;, | |
| 1927 | it is strongly recommended that you install a new | |
| 1928 | linux-image-2.6-* metapackage. | |
| 1929 | This package may be installed automatically by the dist-upgrade | |
| 1930 | process. You can verify this by running: | |
| 1931 | <!-- NOTE (jfs): Users using apt/aptitude might not have their available file | |
| 1932 | updated so '^ii' is really unnecessary, maybe dpkg -l 'linux-image*' would be | |
| 1933 | better here? --> | |
| 1934 | <example> | |
| 1935 | # dpkg -l "linux-image*" | grep ^ii | |
| 1936 | </example></p> | |
| 1937 | ||
| 1938 | <p>If you do not see any output, then you will need to install a | |
| 1939 | new linux-image package by hand. To see a list of available | |
| 1940 | linux-image-2.6 metapackages, run: | |
| 1941 | <example> | |
| 1942 | # apt-cache search linux-image-2.6- | grep -v transition | |
| 1943 | </example></p> | |
| 1944 | ||
| 1945 | <p>If you are unsure about which package to select, run | |
| 1946 | <tt>uname -r</tt> and look for a package with a similar name. | |
| 1947 | For example, if you see '2.4.27-3-686', it is recommended that you | |
| 1948 | install <package/linux-image-2.6-686/. | |
| 1949 | <![ %i386 [ | |
| 1950 | (Note that the 386 flavor no longer exists; if you are currently using | |
| 1951 | the 386 kernel flavor, you should install the 486 flavor instead.) | |
| 1952 | ]]> | |
| 1953 | You may also use <prgn>apt-cache</prgn> to see a long description of each | |
| 1954 | package in order to help choose the best one available. | |
| 1955 | For example: | |
| 1956 | <example> | |
| 1957 | # apt-cache show linux-image-2.6-686 | |
| 1958 | </example></p> | |
| 1959 | ||
| <p>When <tt>aptitude 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> | ||
| <p>Read | ||
| <file>/usr/share/doc/xfree86-common/README.Debian-upgrade</file> for | ||
| more info on the upgrade of the X window system packages. This is | ||
| relevant for users of all previous Debian releases. In short, you | ||
| need to read it.</p> | ||
| <sect2 id="newkernel"><heading>Upgrading your kernel</heading> | ||
| <p>Note that the Linux kernel was <em/not/ upgraded by these | ||
| procedures. You may wish to do so yourself, either by installing one | ||
| of the <package/kernel-image-*/ packages or by compiling a customized | ||
| kernel from sources.</p> | ||
| <![ %available-2.6 [ | ||
| <p>&debian; comes with a &kernelversion; kernel which is in the 2.4 | ||
| series, the older stable Linux kernel series. You may wish to use a 2.6 | ||
| series kernel for better hardware support or improved performance.</p> | ||
| ]]> | ||
| <p>To upgrade your kernel you must first choose the kernel most | ||
| appropriate for your subarchitecture. A list of kernels available for | ||
| you to install can be found with: | ||
| <!-- FJP: s/subarchitecture/subarchitecture and processor/ ??? --> | ||
| <example> | ||
| apt-cache search ^kernel-image | ||
| </example></p> | ||
| 1960 | <p>You should then use <tt/aptitude install/ to install it. Once | <p>You should then use <tt/aptitude install/ to install it. Once |
| 1961 | this new kernel is installed you should reboot at the next available | this new kernel is installed you should reboot at the next available |
| 1962 | opportunity to get the benefit.</p> | opportunity to get the benefits provided by the new kernel version.</p> |
| 1963 | ||
| 1964 | <p>For the more adventurous there is an easy way to compile your | <p>For the more adventurous there is an easy way to compile your |
| 1965 | own custom kernel on &debian;. Install the | own custom kernel on &debian;. Install the |
| 1966 | <package>kernel-package</package> tool and read the documentation | <package>kernel-package</package> tool and read the documentation |
| 1967 | in <file>/usr/share/doc/kernel-package</file>.</p> | in <file>/usr/share/doc/kernel-package</file>.</p> |
| </sect2></sect1></sect> | ||
| 1968 | ||
| 1969 | </sect1> | |
| 1970 | ||
| 1971 | <sect1 id="upgrade-from-2.6"><heading>Upgrading from a 2.6 kernel</heading> | |
| 1972 | ||
| 1973 | <p>If you are currently running a 2.6 series kernel from | |
| 1974 | &oldreleasename; this upgrade will take place automatically after you do a full upgrade | |
| 1975 | of the system packages (as described in <ref id="upgradingpackages">). | |
| 1976 | </p> | |
| 1977 | ||
| 1978 | <p>If possible, it is to your advantage to upgrade the kernel package | |
| 1979 | separately from the main <tt/dist-upgrade/ to reduce the chances of a | |
| 1980 | temporarily non-bootable system. See <ref id="upgrading_kernel"> for a | |
| 1981 | description of this process. Note that this should only be done after the | |
| 1982 | minimal upgrade process described in <ref id="minimal_upgrade">. | |
| 1983 | </p> | |
| 1984 | ||
| 1985 | <p>You can also take this step if you are using your own custom | |
| 1986 | kernel and want to use the kernel available in &releasename;. | |
| 1987 | If your kernel version is not supported by <package/udev/ then | |
| 1988 | it is recommended that you upgrade after the minimal upgrade. | |
| 1989 | If your version is supported by <package/udev/ you can safely wait | |
| 1990 | until after the full system upgrade.</p> | |
| 1991 | ||
| 1992 | <!-- | |
| 1993 | <p><em>TRY</em>: In aptitude, upgrade only 'required' 'important' | |
| 1994 | 'standard' packages limit by pressing 'l' and input | |
| 1995 | !~v(~pextra|~poptional) keep with : for hold this time upgrade by | |
| 1996 | pressing 'U' and 'g' (untested but ...) (You can do this in much | |
| 1997 | finer steps.) | |
| 1998 | --> | |
| 1999 | </sect1> | |
| 2000 | ||
| 2001 | <![ %defaulted-2.4 [ | |
| 2002 | <sect1 id="upgrade-from-2.4"><heading>Upgrading from a 2.4 kernel</heading> | |
| 2003 | ||
| 2004 | <p>If you have a 2.4 kernel installed, and your system relies on | |
| 2005 | <package/hotplug/ for its hardware detection you should first upgrade | |
| 2006 | to a 2.6 series kernel from &oldreleasename; before attempting the upgrade. Make | |
| 2007 | sure that the 2.6 series kernel boots your system and all your hardware is | |
| 2008 | properly detected before you perform the upgrade. The <package/hotplug/ package | |
| 2009 | is removed from the system (in favor of <package/udev/) when you do a full system | |
| 2010 | upgrade. If you do not do the kernel upgrade before this your system might | |
| 2011 | not boot up properly from this point on. Once you have done an upgrade | |
| 2012 | to a 2.6 series kernel in &oldreleasename; you can do a kernel upgrade | |
| 2013 | as described in <ref id="upgrade-from-2.6">.</p> | |
| 2014 | ||
| 2015 | <p>If your system does not rely on <package/hotplug/<footnote>You can | |
| 2016 | have the kernel modules needed by your system loaded statically through proper configuration | |
| 2017 | of <file>/etc/modules</file></footnote> you can delay the kernel upgrade | |
| 2018 | to after you have done a full system upgrade, as described in <ref | |
| 2019 | id="upgrading_other">. Once your system has been upgraded | |
| 2020 | you can then do the following (changing the kernel package name to the one most | |
| 2021 | suited to your system by substituting <em><flavor></em>): | |
| 2022 | <example> | |
| 2023 | # aptitude install linux-image-2.6-<flavor> | |
| 2024 | </example> | |
| 2025 | </p> | |
| 2026 | ||
| 2027 | </sect1> | |
| 2028 | ]]> | |
| 2029 | ||
| 2030 | <sect1 id="device-reorder"><heading>Device enumeration reordering</heading> | |
| 2031 | <p>&releasename; features a more robust mechanism for hardware discovery | |
| 2032 | than previous releases. However, this may cause changes in the | |
| 2033 | order devices are discovered on your system, affecting the order | |
| 2034 | in which device names are assigned. | |
| 2035 | For example, if you have two network adapters that are associated | |
| 2036 | with two different drivers, the devices eth0 and eth1 refer to | |
| 2037 | may be swapped. | |
| 2038 | Please note that the new mechanism means that if you e.g. exchange | |
| 2039 | ethernet adapters in a running &releasename; system, the new adapter | |
| 2040 | will also get a new interface name.</p> | |
| 2041 | ||
| 2042 | <p>For network devices, you can avoid this reordering by using | |
| 2043 | <package>udev</package> rules, more specifically, through the definitions at | |
| 2044 | <file>/etc/udev/rules.d/z25_persistent-net.rules</file><footnote> | |
| 2045 | The rules there are automatically generated by the script | |
| 2046 | <file>/etc/udev/rules.d/z45_persistent-net-generator.rules</file> to | |
| 2047 | have persistent names for network interfaces. Delete this symlink to | |
| 2048 | disable persistent device naming for NICs by <package/udev/.</footnote>. | |
| 2049 | Alternatively you can use the <prgn>ifrename</prgn> utility to bind | |
| 2050 | physical devices to specific names at boot time. | |
| 2051 | <!-- TODO: add ifupdown-scripts-zg2 as well here? --> | |
| 2052 | See <manref name="ifrename" section="8"> and <manref name="iftab" | |
| 2053 | section="5"> for more information. | |
| 2054 | The two alternatives (<package>udev</package> and <prgn>ifrename</prgn>) | |
| 2055 | should not be used at the same time. | |
| 2056 | </p> | |
| 2057 | ||
| 2058 | <!-- TODO: | |
| 2059 | *** maks: please review the initramfs stuff for accuracy - I'm going | |
| 2060 | *** by what I remember, and haven't tested this recently | |
| 2061 | --> | |
| 2062 | <p>For storage devices, you can avoid this reordering by using | |
| 2063 | <package/initramfs-tools/ and configuring it to load storage device | |
| 2064 | driver modules in the same order they are currently loaded. | |
| 2065 | To do this, identify the order the storage modules on your system | |
| 2066 | were loaded by looking at the output of <prgn/lsmod/. | |
| 2067 | <prgn/lsmod/ lists modules in the reverse order that they were loaded | |
| 2068 | in, i.e., the first module in the list was the last one | |
| 2069 | loaded. Note that this will only work for devices which the kernel | |
| 2070 | enumerates in a stable order (like PCI devices).</p> | |
| 2071 | ||
| 2072 | <p>However, removing and reloading modules after initial boot | |
| 2073 | will affect this order. Also, your kernel may have some drivers | |
| 2074 | linked statically, and these names will not appear in the output | |
| 2075 | of <prgn>lsmod</prgn>. You may be able to decipher these driver | |
| 2076 | names and load order from looking at | |
| 2077 | <file>/var/log/kern.log</file>, or the output of | |
| 2078 | <prgn>dmesg</prgn>.</p> | |
| 2079 | ||
| 2080 | <p>Add these module names to <file>/etc/initramfs-tools/modules</file> | |
| 2081 | in the order they should be loaded at boot time. Some module names may | |
| 2082 | have changed between &oldreleasename; and &releasename;. For | |
| 2083 | example, sym53c8xx_2 has become sym53c8xx.</p> | |
| 2084 | ||
| 2085 | <p>You will then need to regenerate your initramfs image(s) by | |
| 2086 | executing <tt>update-initramfs -u -k all</tt>.</p> | |
| 2087 | ||
| 2088 | <p>Once you are running a &releasename; kernel and <package/udev/, you may | |
| 2089 | reconfigure your system to access disks by an alias that is not | |
| 2090 | dependent upon driver load order. These aliases reside in the | |
| 2091 | <file>/dev/disk/</file> hierarchy.</p> | |
| 2092 | </sect1> | |
| 2093 | ||
| 2094 | <![ %ia64 [ | |
| 2095 | <sect1><heading>Serial device reordering</heading> | |
| 2096 | <p>If you have an HP machine and you're using the MP serial | |
| 2097 | console port (the connector labelled "console" on the 3-headed | |
| 2098 | cable), this kernel upgrade will break your console!</p> | |
| 2099 | ||
| 2100 | <p>Upon reboot, the system will show up the message "Loading | |
| 2101 | initrd...." but it will stop there. Notice that systems with | |
| 2102 | outdated firmware will show similar symptoms, although the issue is | |
| 2103 | related to kernel incompatibilities (see <ref | |
| 2104 | id="upgrade-to-2.6">).</p> | |
| 2105 | ||
| 2106 | <p>Please read the following information before upgrading.</p> | |
| 2107 | ||
| 2108 | <p><list> | |
| 2109 | <item><p>The console device will change from <file>ttyS0</file> to | |
| 2110 | <file>ttyS1</file>, <file>ttyS2</file>, or <file>ttyS3</file> so | |
| 2111 | <list> | |
| 2112 | <item><p>Edit <file>/etc/inittab</file> to add a getty entry for | |
| 2113 | <file>/dev/ttyS1</file> (rx4640, rx5670, rx7620, rx8620, Superdome), | |
| 2114 | <file>/dev/ttyS2</file> (rx1600), or | |
| 2115 | <file>/dev/ttyS3</file> (rx2600).</p></item> | |
| 2116 | <item><p>Edit <file>/etc/securetty</file> to add | |
| 2117 | <file>ttyS1</file>, <file>ttyS2</file>, or | |
| 2118 | <file>ttyS3</file>.</p></item> | |
| 2119 | <item><p>Leave the existing <file>ttyS0</file> entries in | |
| 2120 | <file>/etc/inittab</file> and <file>/etc/securetty</file> so | |
| 2121 | you can still boot old kernels.</p></item> | |
| 2122 | </list> | |
| 2123 | </p></item> | |
| 2124 | ||
| 2125 | <item><p>Edit <file>/etc/elilo.conf</file> to remove any "console=" | |
| 2126 | arguments.</p></item> | |
| 2127 | ||
| 2128 | <item><p>Run <prgn/elilo/ to install the bootloader with new | |
| 2129 | configuration.</p></item> | |
| 2130 | ||
| 2131 | <item><p>Reboot and use the EFI boot option maintenance menu to | |
| 2132 | select exactly one device for console output, input, and standard | |
| 2133 | error. Then do a cold reset so the changes take | |
| 2134 | effect.</p> | |
| 2135 | ||
| 2136 | <p>For the MP console, be careful to select the device with | |
| 2137 | "Acpi(HWP0002,700)/Pci(...)/Uart" in the path.</p></item> | |
| 2138 | </list></p> | |
| 2139 | ||
| 2140 | <p>More details about these changes and troubleshooting hints are | |
| 2141 | available at | |
| 2142 | <url id="http://lists.debian.org/debian-ia64/2005/01/msg00008.html">.</p> | |
| 2143 | ||
| 2144 | </sect1> | |
| 2145 | ]]> | |
| 2146 | <![ %uses-initrd [ | |
| 2147 | <!-- #417643 --> | |
| 2148 | <sect1 id="boot-timing"><heading>Boot timing issues</heading> | |
| 2149 | ||
| 2150 | <p>If an initrd created with <package/initramfs-tools/ is used to | |
| 2151 | boot the system, in some cases the creation of device files by | |
| 2152 | <package/udev/ can happen too late for the boot scripts to act on.</p> | |
| 2153 | <p>The usual symptoms are that the boot will fail because the root | |
| 2154 | file system cannot be mounted and you are dropped into a debug shell, | |
| 2155 | but that when you check afterwards, all devices that are needed are | |
| 2156 | present in <file>/dev</file>. This has been observed in cases where | |
| 2157 | the root file system is on a USB disk or on RAID.</p> | |
| 2158 | <p>A workaround for this issue is to use the boot parameter | |
| 2159 | <tt>rootdelay=<var/9/</tt>. The value for the timeout (in seconds) may | |
| 2160 | need to be adjusted.</p> | |
| 2161 | ||
| 2162 | </sect1> | |
| 2163 | ]]> | |
| 2164 | </sect> | |
| 2165 | ||
| 2166 | <sect id="nownownow"><heading>Things to do before rebooting</heading> | |
| 2167 | ||
| 2168 | <p>When <tt>aptitude dist-upgrade</tt> has finished, the | |
| 2169 | "formal" upgrade is complete, but there are some other things | |
| 2170 | that should be taken care of <em/before/ the next reboot.</p> | |
| 2171 | ||
| 2172 | <sect1 id="convert-devfs"><heading>Converting from devfs</heading> | |
| 2173 | <p>Debian kernels no longer include support for <tt>devfs</tt>, | |
| 2174 | so <tt>devfs</tt> users will need to convert their systems | |
| 2175 | manually before booting an &releasename; kernel.</p> | |
| 2176 | ||
| 2177 | <p>If you see the string 'devfs' in <file>/proc/mounts</file>, | |
| 2178 | you are most likely using <tt>devfs</tt>. | |
| 2179 | Any configuration files that reference <tt>devfs</tt>-style names will need to be | |
| 2180 | adjusted to use <package>udev</package>-style names. Files that are likely to | |
| 2181 | refer to <tt>devfs</tt>-style device names include <file>/etc/fstab</file>, | |
| 2182 | <file>/etc/lilo.conf</file>, <file>/boot/grub/menu.lst</file>, and <file>/etc/inittab</file>.</p> | |
| 2183 | ||
| 2184 | <p>More information about potential issues is available in bug report | |
| 2185 | <url id="http://bugs.debian.org/341152" name="#341152">.</p> | |
| 2186 | </sect1> | |
| 2187 | ||
| 2188 | <![ %sparc [ | |
| 2189 | <sect1 id="missingdrivers"><heading>Possible missing drivers in initrd</heading> | |
| 2190 | <p>The &releasename; kernels do not yet have full sysfs support for | |
| 2191 | the native sparc sbus. <package/initramfs-tools/ relies on this to | |
| 2192 | include drivers for disk controllers in the initrd. If a driver is | |
| 2193 | not included in the initrd, your system may fail to boot. | |
| 2194 | <p>If your system uses the <tt/esp/ or <tt/qlogicpti/ module to | |
| 2195 | access your hard disks, you will need to include that module in | |
| 2196 | <file>/etc/initramfs-tools/modules</file> and regenerate the initrd | |
| 2197 | before you reboot your system. The initrd can be regenerated using: | |
| 2198 | <example> | |
| 2199 | # update-initramfs -u -k all | |
| 2200 | </example></p> | |
| 2201 | </sect1> | |
| 2202 | ]]> | |
| 2203 | ||
| 2204 | <![ %hppa [ | |
| 2205 | <sect1 id="missingdrivers"><heading>Possible missing drivers in initrd</heading> | |
| 2206 | <p>The &releasename; kernels do not yet have full sysfs support for | |
| 2207 | the native HP bus. <package/initramfs-tools/ relies on this to | |
| 2208 | include drivers for disk controllers in the initrd. If a driver is | |
| 2209 | not included in the initrd, your system may fail to boot. | |
| 2210 | <p>If your system uses the <tt/lasi700/ or <tt/zalon7xx/ module to | |
| 2211 | access your hard disks, you will need to include that module in | |
| 2212 | <file>/etc/initramfs-tools/modules</file> and regenerate the initrd | |
| 2213 | before you reboot your system. The initrd can be regenerated using: | |
| 2214 | <example> | |
| 2215 | # update-initramfs -u -k all | |
| 2216 | </example></p> | |
| 2217 | </sect1> | |
| 2218 | ]]> | |
| 2219 | ||
| 2220 | <![ %i386-amd64 [ | |
| 2221 | <sect1 id="rerunlilo"><heading>Rerun lilo</heading> | |
| 2222 | ||
| 2223 | <p>If you are using <package/lilo/ as your bootloader (it is the | |
| 2224 | default bootloader for some installations of &oldreleasename;) it is strongly recommended | |
| 2225 | that you rerun <prgn>lilo</prgn> after the upgrade: | |
| 2226 | <example> | |
| 2227 | # /sbin/lilo | |
| 2228 | </example></p> | |
| 2229 | ||
| 2230 | <p>Notice this is needed even if you did not upgrade your system's kernel, as | |
| 2231 | <prgn>lilo</prgn>'s second stage will change due to the package upgrade.</p> | |
| 2232 | ||
| 2233 | <p>Also, review the contents of your <file>/etc/kernel-img.conf</file> and | |
| 2234 | make sure that you have <em>do_bootloader = Yes</em> in it. That way the | |
| 2235 | bootloader will always be rerun after a kernel upgrade. | |
| 2236 | </p> | |
| 2237 | ||
| 2238 | <p>If you encounter any issues when running <prgn/lilo/, review the | |
| 2239 | symbolic links in <file>/</file> to <file>vmlinuz</file> and | |
| 2240 | <file>initrd</file> and the contents of your | |
| 2241 | <file>/etc/lilo.conf</file> for discrepancies.</p> | |
| 2242 | ||
| 2243 | <p>If you forgot to rerun <prgn/lilo/ before the reboot or the system | |
| 2244 | is accidentally rebooted before you could do this manually, your | |
| 2245 | system might fail to boot. Instead of the lilo prompt, you will only | |
| 2246 | see <em/LI/ when booting the system<footnote>For more information on | |
| 2247 | <prgn/lilo/'s boot error codes please see <url | |
| 2248 | id="http://tldp.org/HOWTO/Bootdisk-HOWTO/a1483.html" name="The Linux | |
| 2249 | Bootdisk HOWTO">.</footnote>. See <ref id="recovery"> for information | |
| 2250 | on how to recover from this.</p> | |
| 2251 | ||
| 2252 | </sect1> | |
| 2253 | ]]> | |
| 2254 | ||
| 2255 | <![ %s390 [ | |
| 2256 | <sect1 id="s390-config"><heading>S/390 hardware configuration</heading> | |
| 2257 | ||
| 2258 | <p>Not all S/390 hardware can be configured automatically. For the | |
| 2259 | &releasename; kernels a new utility <package/sysconfig-hardware/ is | |
| 2260 | used to correctly set up devices. Unfortunately documentation for | |
| 2261 | this utility and its configuration files is not yet available. The | |
| 2262 | configuration files for <package/sysconfig-hardware/ can be found | |
| 2263 | under <file>/etc/sysconfig/</file>.</p> | |
| 2264 | ||
| 2265 | <p>Especially if your system is currently running a 2.4 kernel, | |
| 2266 | getting the configuration right can be a challenge. If you need any | |
| 2267 | help, feel free to contact the | |
| 2268 | <url id="http://lists.debian.org/debian-s390" | |
| 2269 | name="Debian S/390 mailing list">.</p> | |
| 2270 | ||
| 2271 | <p>First install the utility and regenerate the initramfs initrd as | |
| 2272 | the utility provides some scripts that need to be included in the | |
| 2273 | initrd: | |
| 2274 | <example> | |
| 2275 | # aptitude install sysconfig-hardware | |
| 2276 | # update-initramfs -u -k all | |
| 2277 | </example></p> | |
| 2278 | ||
| 2279 | <sect2 id="s390-dasd"><heading>Configuration for disks</heading> | |
| 2280 | ||
| 2281 | <p>This is done by modifying <file>/etc/zipl.conf</file>. The | |
| 2282 | sysconfig utility can use the device path to the root device to | |
| 2283 | enable it, which means that this path needs to be passed in the kernel | |
| 2284 | boot parameters. For a regular dasd, the path is composed as follows: | |
| 2285 | <example> | |
| 2286 | <bus>-<device> | |
| 2287 | </example> | |
| 2288 | ||
| 2289 | For the <tt/root/ parameter the partition needs to be appended to | |
| 2290 | the path. So if your dasda is <tt/0.0.0122/, instead of | |
| 2291 | <file>root=/dev/dasda1</file> you would include the following in | |
| 2292 | the <tt/parameters/ line in <tt>/etc/zipl.conf</tt>: | |
| 2293 | <example> | |
| 2294 | root=/dev/disks/by-path/ccw-0.0.0122-part1 | |
| 2295 | </example> | |
| 2296 | ||
| 2297 | Or, alternatively you can use the <tt/enable/ parameter to specify | |
| 2298 | the device to be enabled; in that case the partition: | |
| 2299 | <example> | |
| 2300 | root=/dev/dasda1 enable=ccw-0.0.0122 | |
| 2301 | </example> | |
| 2302 | ||
| 2303 | The paths to be used can vary for different devices. For example, for | |
| 2304 | disks on a zFCP fiberchannel host adapter, the path consists of bus, | |
| 2305 | device, driver, wwpn and lun. The parameters for a RAID1 would look | |
| 2306 | like (on a single line): | |
| 2307 | <example> | |
| 2308 | root=/dev/md0 enable=ccw-0.0.2900-zfcp-0x21000020371c93a5:0 | |
| 2309 | enable=ccw-0.0.2900-zfcp-0x21000020371d8f94:0 | |
| 2310 | </example></p> | |
| 2311 | ||
| 2312 | <p>Other dasd devices (dasds not needed to bring up the root file | |
| 2313 | system) are enabled through configuration files in | |
| 2314 | <file>/etc/sysconfig/hardware/</file>. For a regular dasd, you just | |
| 2315 | need to touch a file with the device path in its name: | |
| 2316 | <example> | |
| 2317 | # cd /etc/sysconfig/hardware | |
| 2318 | # touch config-ccw-0.0.0122 | |
| 2319 | </example> | |
| 2320 | ||
| 2321 | For disks on a zFCP fiberchannel host adapter the individual devices | |
| 2322 | are listed inside the file. Using the same example as above, | |
| 2323 | create a file <file/config-ccw-0.0.2900/ containing (second device | |
| 2324 | truncated for readability): | |
| 2325 | <example> | |
| 2326 | ZFCP_DEVICES=(0x21000020371c93a5:0x0000000000000000 0x2100...:0x...) | |
| 2327 | </example></p> | |
| 2328 | ||
| 2329 | </sect2> | |
| 2330 | <sect2 id="s390-other"><heading>Configuration for network devices</heading> | |
| 2331 | ||
| 2332 | <p>Network devices are enabled through configuration files in | |
| 2333 | <file>/etc/sysconfig/hardware/</file>. For a ctc network device with | |
| 2334 | read channel <tt/0.0.0a00/ and write channel <tt/0.0.0a01/ and using | |
| 2335 | the S/390 protocol, you would create a file <file/config-ccw-0.0.0a00/ | |
| 2336 | containing: | |
| 2337 | <example> | |
| 2338 | CCWGROUP_CHANS=(0.0.0a00 0.0.0a01) | |
| 2339 | CTC_PROTOCOL=0 | |
| 2340 | </example> | |
| 2341 | ||
| 2342 | For a qeth network device with layer2 mode enabled, this could be a | |
| 2343 | file <file/config-ccw-0.0.0600/: | |
| 2344 | <example> | |
| 2345 | CCWGROUP_CHANS=(0.0.0600 0.0.0601 0.0.0602) | |
| 2346 | QETH_OPTIONS=(layer2) | |
| 2347 | </example></p> | |
| 2348 | ||
| 2349 | <p>Supported options for ctc are: <tt/CTC_PROTOCOL/ and <tt/CTC_BUFFER/; | |
| 2350 | and for qeth: <tt/QETH_PORTNAME/, <tt/QETH_PORTNO/ and <tt/QETH_OPTIONS/. | |
| 2351 | </p> | |
| 2352 | <p>As network devices on S/390 do not have a stable MAC address, it is | |
| 2353 | not possible to use <package/udev/ persistent device naming. Instead you | |
| 2354 | can add an option <tt/INTERFACE_NAME/ in the configuration file to | |
| 2355 | rename an interface.</p> | |
| 2356 | ||
| 2357 | </sect2> | |
| 2358 | </sect1> | |
| 2359 | ]]> | |
| 2360 | ||
| 2361 | <sect1 id="mdadm"><heading>Upgrading mdadm</heading> | |
| 2362 | ||
| 2363 | <p>mdadm now needs a configuration file to assemble MD arrays (RAID) | |
| 2364 | from the initial ramdisk and during the system initialisation | |
| 2365 | sequence. Please make sure to read and act upon the instructions in | |
| 2366 | <file>/usr/share/doc/mdadm/README.upgrading-2.5.3.gz</file> after | |
| 2367 | the package has been upgraded <strong>and before you reboot</strong>. | |
| 2368 | The latest version of this file is available at | |
| 2369 | <url id="http://svn.debian.org/wsvn/pkg-mdadm/mdadm/trunk/debian/README.upgrading-2.5.3?op=file">; | |
| 2370 | please consult it in case of problems.</p> | |
| 2371 | ||
| 2372 | </sect1> | |
| 2373 | </sect> | |
| 2374 | ||
| 2375 | <sect id="for_next"><heading>Preparing for the next release</heading> | |
| 2376 | ||
| 2377 | <p>After the upgrade there are several things you can do | |
| 2378 | to prepare for the next release.</p> | |
| 2379 | ||
| 2380 | <p><list> | |
| 2381 | ||
| 2382 | <item><p>If using <prgn/grub/, edit <file>/etc/kernel-img.conf</file> | |
| 2383 | and adjust the location of the <prgn/update-grub/ program changing | |
| 2384 | <file>/sbin/update-grub</file> to <file>/usr/sbin/update-grub</file>.</p> | |
| 2385 | ||
| 2386 | <item><p>If the new kernel image metapackage was pulled in as a | |
| 2387 | dependency of the old one, it will be marked as automatically installed, | |
| 2388 | which should be corrected: | |
| 2389 | <example> | |
| 2390 | # aptitude unmarkauto $(dpkg-query -W 'linux-image-2.6-*' | cut -f1) | |
| 2391 | </example> | |
| 2392 | </p> | |
| 2393 | <item><p>Remove &oldreleasename;'s kernel metapackages by running: | |
| 2394 | <example> | |
| 2395 | # aptitude purge kernel-image-2.6-<flavor> | |
| 2396 | </example> | |
| 2397 | </p> | |
| 2398 | ||
| 2399 | <item><p>Move any kernel configuration values at | |
| 2400 | <file>/etc/network/options</file> to <file>/etc/sysctl.conf</file>.</p> | |
| 2401 | ||
| 2402 | <item><p>Remove obsolete and unused packages as described in <ref | |
| 2403 | id="obsolete">. You should review which configuration files they use | |
| 2404 | and consider purging the packages to remove their configuration files</p> | |
| 2405 | ||
| 2406 | </list></p> | |
| 2407 | ||
| 2408 | </sect> | |
| 2409 | ||
| 2410 | <sect id="obsolete"><heading>Obsolete packages</heading> | |
| 2411 | ||
| 2412 | <!-- JFS: Providing a full listing might be useful, especially if we can | |
| 2413 | point to the Bug that was opened when the bug was removed. This list should | |
| 2414 | be moved to an appendix, instead of adding it inline as we did in the | |
| 2415 | potato to woody RN --> | |
| 2416 | ||
| 2417 | <p>Introducing several thousand new packages, &releasename; also | |
| 2418 | retires and omits more than two thousand old packages that were in | |
| 2419 | &oldreleasename;. It provides no upgrade path for these obsolete | |
| 2420 | packages. While nothing prevents you from continuing to use an | |
| 2421 | obsolete package where desired, the Debian project will usually | |
| 2422 | discontinue security support for it a year after &releasename;'s | |
| 2423 | release<footnote>Or for as long as there is not another release in | |
| 2424 | that time frame. Typically only two stable releases are supported | |
| 2425 | at any given time.</footnote>, and will not normally provide other | |
| 2426 | support in the meantime. Replacing them with available | |
| 2427 | alternatives, if any, is recommended.</p> | |
| 2428 | ||
| 2429 | <p>There are many reasons why packages might have been removed from | |
| 2430 | the distribution: they are no longer maintained upstream; there is | |
| 2431 | no longer a Debian Developer interested in maintaining the packages; | |
| 2432 | the functionality they provide has been superseded by different | |
| 2433 | software (or a new version); or they are no longer considered | |
| 2434 | suitable for &releasename; due to bugs in them. In the latter case, | |
| 2435 | packages might still be present in the "unstable" distribution.</p> | |
| 2436 | ||
| 2437 | <!-- (vorlon) FIXME: not true in etch because 'Obsolete and Locally Created | |
| 2438 | Packages' is not the default view AFAICS? | |
| 2439 | --> | |
| 2440 | <p>Detecting which packages in an updated system are "obsolete" is | |
| 2441 | easy since the package management front-ends will mark them as | |
| 2442 | such. If you are using <prgn>aptitude</prgn>, you will see a | |
| 2443 | listing of these packages in the "Obsolete and Locally Created | |
| 2444 | Packages" entry. <prgn>dselect</prgn> provides a similar section | |
| 2445 | but the listing it presents might differ. Also, if you have used | |
| 2446 | <prgn>aptitude</prgn> to manually install packages in | |
| 2447 | &oldreleasename; it will have kept track of those packages you | |
| 2448 | manually installed and will be able to mark as obsolete those | |
| 2449 | packages pulled in by dependencies alone which are no longer | |
| 2450 | needed if a package has been removed. Also, <prgn>aptitude</prgn>, | |
| 2451 | unlike <prgn>deborphan</prgn> will not mark as obsolete packages | |
| 2452 | that you manually installed, as opposed to those that were | |
| 2453 | automatically installed through dependencies.</p> | |
| 2454 | ||
| 2455 | <!-- (vorlon) FIXME: AIUI, cruft is not useful for this? --> | |
| 2456 | <p>There are additional tools you can use to find obsolete packages | |
| 2457 | such as <prgn>deborphan</prgn>, <prgn>debfoster</prgn> or | |
| 2458 | <prgn>cruft</prgn>. <prgn>deborphan</prgn> is highly recommended, | |
| 2459 | although it will (in default mode) only report obsolete libraries: | |
| 2460 | packages in the "libs" or "oldlibs" sections that are not used by | |
| 2461 | any other packages. Do not blindly remove the packages these tools | |
| 2462 | present, especially if you are using aggressive non-default | |
| 2463 | options that are prone to produce false positives. It is highly | |
| 2464 | recommended that you manually review the packages suggested for | |
| 2465 | removal (i.e. their contents, size and description) before you | |
| 2466 | remove them.</p> | |
| 2467 | ||
| 2468 | <!-- JFS: Should we recommend purging old packages? This might be | |
| 2469 | dangerous since the maintainer scripts might try to remove stuff that | |
| 2470 | didn't belong to them... --> | |
| 2471 | ||
| 2472 | <p>The <url id="&url-bts;" name="Debian Bug Tracking System"> | |
| 2473 | often provides additional information on why the package was | |
| 2474 | removed. You should review both the archived bug reports for the | |
| 2475 | package itself and the archived bug reports for the <url | |
| 2476 | id="&url-bts;cgi-bin/pkgreport.cgi?pkg=ftp.debian.org&archive=yes" | |
| 2477 | name="ftp.debian.org pseudo-package">.</p> | |
| 2478 | ||
| 2479 | <sect1 id="dummy"><heading>Dummy packages</heading> | |
| 2480 | ||
| 2481 | <!-- JFS: If the appendix is kept this section should point there and the packages described here should be moved to that section --> | |
| 2482 | ||
| 2483 | <p>Some packages from &oldreleasename; have been split into several | |
| 2484 | packages in &releasename;, often to improve system maintainability. To | |
| 2485 | ease the upgrade path in such cases, &releasename; often provides | |
| 2486 | "dummy" packages: empty packages that have the same name as the old | |
| 2487 | package in &oldreleasename; with dependencies that cause the new | |
| 2488 | packages to be installed. These "dummy" packages are considered | |
| 2489 | obsolete packages after the upgrade and can be safely removed. | |
| 2490 | ||
| 2491 | <p>Most (but not all) dummy packages' descriptions indicate their | |
| 2492 | purpose. Package descriptions for dummy packages are not uniform, | |
| 2493 | however, so you might also find <prgn>deborphan</prgn> with the | |
| 2494 | <tt>--guess</tt> options useful to detect them in your system. | |
| 2495 | Note that some dummy packages are not intended to be removed after | |
| 2496 | an upgrade but are, instead, used to keep track of the current | |
| 2497 | available version of a program over time.</p> | |
| 2498 | ||
| 2499 | </sect1> | |
| 2500 | </sect> | |
| 2501 | </chapt> | </chapt> |
| 2502 | ||
| 2503 | <!-- FJP: Add more info here on dealing with obsolete packages? | |
| 2504 | Also how to purge packages that were deleted but still have conffiles | |
| 2505 | (use "limit" command in aptitude and search for ~c) --> | |
| 2506 | ||
| 2507 | <chapt id="information"> | |
| 2508 | <heading>Issues to be aware of for &releasename;</heading> | |
| 2509 | ||
| 2510 | <sect id="problems"><heading>Potential problems</heading> | |
| 2511 | <p>Sometimes, changes have side-effects we cannot reasonably avoid, | |
| 2512 | or we expose bugs somewhere else. | |
| 2513 | We document here the issues we are aware of. | |
| 2514 | Please also read the errata, the relevant packages' documentation, | |
| 2515 | bug reports and other information mentioned in <ref id="morereading">. | |
| 2516 | </p> | |
| 2517 | ||
| 2518 | <sect1 id="udev"> <heading>Problems with devices related to udev</heading> | |
| 2519 | <p>Although <package/udev/ has been tested extensively, you may experience | |
| 2520 | minor problems with some devices that will need to be fixed. The most | |
| 2521 | common problems are changed permission and/or ownership of a device. | |
| 2522 | In some cases a device may not be created by default (e.g. | |
| 2523 | <file>/dev/video</file> and <file>/dev/radio</file>).</p> | |
| 2524 | ||
| 2525 | <p><package/udev/ provides configuration mechanisms to deal with these | |
| 2526 | issues. See <manref name="udev" section="8"> and <file>/etc/udev</file> | |
| 2527 | for further information.</p> | |
| 2528 | </sect1> | |
| 2529 | ||
| 2530 | <![ %defaulted-2.4 [ | |
| 2531 | <sect1 id="incompatible-2.4"> | |
| 2532 | <heading>Some applications may no longer work with a 2.4 kernel</heading> | |
| 2533 | <p>Some applications in &releasename; may no longer work with a 2.4 | |
| 2534 | kernel, for example because they require <tt/epoll()/ support, which | |
| 2535 | is not available in 2.4 kernels. Such applications may either not | |
| 2536 | work at all or not work correctly until the system has been rebooted | |
| 2537 | with a 2.6 kernel.</p> | |
| 2538 | <p>One example is the HTTP proxy <package/squid/.</p> | |
| 2539 | </sect1> | |
| 2540 | ]]> | |
| 2541 | ||
| 2542 | <sect1 id="window-scaling"><heading>Certain network sites cannot be reached by TCP</heading> | |
| 2543 | <p> | |
| 2544 | Since 2.6.17, Linux aggressively uses TCP window scaling which is specified in RFC 1323. | |
| 2545 | Some servers have a broken behavior, and announce wrong | |
| 2546 | window sizes for themselves. | |
| 2547 | For more details, please see the bug reports | |
| 2548 | <url id="http://bugs.debian.org/381262" name="#381262">, | |
| 2549 | <url id="http://bugs.debian.org/395066" name="#395066">, | |
| 2550 | <url id="http://bugs.debian.org/401435" name="#401435">. | |
| 2551 | </p> | |
| 2552 | ||
| 2553 | <p> | |
| 2554 | There are usually two workarounds to these problems: either revert | |
| 2555 | the maximum allowed TCP window sizes to a smaller value (preferable) | |
| 2556 | or turn off TCP window scaling altogether (deprecated). | |
| 2557 | See the example commands in the | |
| 2558 | <url id="http://www.debian.org/devel/debian-installer/errata" | |
| 2559 | name="debian-installer errata page">. | |
| 2560 | </p> | |
| 2561 | </sect1> | |
| 2562 | ||
| 2563 | <![ %i386 [ | |
| 2564 | <sect1 id="poweroff"><heading>Automatic poweroff stops working</heading> | |
| 2565 | <p> | |
| 2566 | On some older systems, <tt>shutdown -h</tt> may not power off the system | |
| 2567 | anymore (but just stop it). This happens because apm needs to be used there. | |
| 2568 | Adding <tt>acpi=off apm=power_off</tt> to the kernel's command line, e.g. | |
| 2569 | in <package/grub/ or <package/lilo/ configuration files should fix this issue. | |
| 2570 | Please see bug | |
| 2571 | <url id="http://bugs.debian.org/390547" name="#390547"> | |
| 2572 | for additional information. | |
| 2573 | </p> | |
| 2574 | </sect1> | |
| 2575 | ]]> | |
| 2576 | ||
| 2577 | <!-- JFS: Bug #376158 --> | |
| 2578 | <sect1 id="apt-pdiff"><heading>Slower updates of APT package index files</heading> | |
| 2579 | <p>By default, the &releasename; version of <prgn>apt</prgn> uses a | |
| 2580 | new way to update APT package | |
| 2581 | index files (when you run <tt/aptitude update/) which downloads differences | |
| 2582 | files (instead of the full package index file) called <tt/pdiff/. This new | |
| 2583 | feature should use less bandwidth and be faster for most systems. | |
| 2584 | Unfortunately, it can also have the opposite effect of making the updates | |
| 2585 | slower on systems with fast network connections (or a very nearby | |
| 2586 | mirror) which are infrequently updated, as it might take more time | |
| 2587 | for the system to merge the differences files than to download a | |
| 2588 | full package index. It is possible to disable this feature by adding | |
| 2589 | <tt>Acquire::Pdiffs "false";</tt> to the | |
| 2590 | <file>/etc/apt/apt.conf</file> configuration file.</p> | |
| 2591 | <!-- For more info, see thread "These new diffs are great, but...", d-devel, july 2006 --> | |
| 2592 | ||
| 2593 | <p>This change mostly affects users of the <em/unstable/ and | |
| 2594 | <em/testing/ branch of &debian;, due to the changing nature of these | |
| 2595 | archives. Users of &releasename; will notice this | |
| 2596 | feature mainly when updating their package status for the security | |
| 2597 | archive.</p> | |
| 2598 | </sect1> | |
| 2599 | ||
| 2600 | <![ %i386 [ | |
| 2601 | <sect1 id="hp-acpi"><heading>ACPI support disabled for some HP laptop models in &releasename; kernel</heading> | |
| 2602 | <p> | |
| 2603 | Certain models of HP laptops have an ACPI BIOS that is incompatible with the | |
| 2604 | Linux 2.6.18 kernel shipped in &releasename;, which would prevent the fans from | |
| 2605 | spinning up leading to unnecessary heat stress. Also, fans might not work after | |
| 2606 | the system is suspended. The kernel therefore disables ACPI support | |
| 2607 | internally when it detects certain ACPI BIOS versions. Models known | |
| 2608 | to be affected by this change include the HP nx6125, nx6120, nx6325, | |
| 2609 | nc6120 and nc6000 models. | |
| 2610 | </p> | |
| 2611 | <p> | |
| 2612 | Users who require ACPI support on these systems may install a Linux 2.6.19 or | |
| 2613 | later kernel. Please see Debian bug | |
| 2614 | <url id="http://bugs.debian.org/404143" name="#404143"> and | |
| 2615 | <url id="http://bugs.debian.org/400488" name="#400488">, | |
| 2616 | and Linux Kernel's bugs | |
| 2617 | <url id="http://bugzilla.kernel.org/show_bug.cgi?id=5534" name="#5534"> | |
| 2618 | and | |
| 2619 | <url id="http://bugzilla.kernel.org/show_bug.cgi?id=7122" name="#7122"> | |
| 2620 | for additional information. | |
| 2621 | </p> | |
| 2622 | </sect1> | |
| 2623 | ]]> | |
| 2624 | ||
| 2625 | <sect1 id="asynchronous-network-start"><heading>Asynchronous network initialization may cause unpredictable behavior</heading> | |
| 2626 | <p>On systems which use <package/udev/ to load drivers for network | |
| 2627 | interfaces, it is possible due to the asynchronous nature of | |
| 2628 | <package/udev/ that the network driver will not be loaded before | |
| 2629 | <prgn>/etc/init.d/networking</prgn> runs on system boot. Although | |
| 2630 | including <tt/allow-hotplug/ to <file>/etc/network/interfaces</file> (in | |
| 2631 | addition to <tt/auto/) will ensure that the network interface is enabled | |
| 2632 | once it becomes available, there is no guarantee that this will finish | |
| 2633 | before the boot sequence begins to start network services, some of which | |
| 2634 | may not behave correctly in the absence of the network interface.</p> | |
| 2635 | ||
| 2636 | </sect1> | |
| 2637 | ||
| 2638 | <![ %not-s390 [ | |
| 2639 | <sect1 id="wpa"><heading>Trouble when using WPA secured wireless networks</heading> | |
| 2640 | <p>In &oldreleasename;, the <package/wpasupplicant/ package was | |
| 2641 | set up as a system service, configured via | |
| 2642 | <file>/etc/default/wpasupplicant</file> and a user-provided | |
| 2643 | <file>/etc/wpasupplicant.conf</file>.</p> | |
| 2644 | ||
| 2645 | <p>In &releasename;, <file>/etc/init.d/wpasupplicant</file> has been | |
| 2646 | dropped and the Debian package now integrates with | |
| 2647 | <file>/etc/network/interfaces</file>, similar to other packages such as | |
| 2648 | <package/wireless-tools/. This means <package/wpasupplicant/ no longer | |
| 2649 | provides a system service directly.</p> | |
| 2650 | ||
| 2651 | <p>For information on configuring wpasupplicant please refer to | |
| 2652 | <file>/usr/share/doc/wpasupplicant/README.modes.gz</file>, which gives | |
| 2653 | examples for <file>/etc/network/interfaces</file> files. Updated | |
| 2654 | information about the usage of the <package/wpasupplicant/ package | |
| 2655 | in Debian can be found in the <url id="http://wiki.debian.org/WPA" | |
| 2656 | name="Debian Wiki">.</p> | |
| 2657 | </sect1> | |
| 2658 | ]]> | |
| 2659 | ||
| 2660 | <sect1 id="partitionenc"><heading>Problems with non-ASCII characters in filenames</heading> | |
| 2661 | <p> | |
| 2662 | Mounting vfat, ntfs or iso9660 file systems with files that include | |
| 2663 | non-ASCII characters in their filenames will give failures when one | |
| 2664 | tries to use the filenames unless mounting is done with the utf8 | |
| 2665 | option. An indication might be the following failure: 'Invalid or | |
| 2666 | incomplete multibyte or wide character'. A possible solution is to | |
| 2667 | use <tt>defaults,utf8</tt> as mount options for vfat, ntfs and iso9660 | |
| 2668 | file systems when they contain filenames with non-ASCII characters. | |
| 2669 | </p> | |
| 2670 | <p>Note that the Linux kernel does not support case-insensitive | |
| 2671 | filename handling for vfat when the <tt>utf8</tt> option is used.</p> | |
| 2672 | </sect1> | |
| 2673 | ||
| 2674 | <![ %amd64 [ | |
| 2675 | <sect1 id="nvidia-iommu"><heading>Data corruption with Hardware IOMMU on Nvidia chipsets</heading> | |
| 2676 | <p>A problem has been identified on &arch-title; systems with Nvidia | |
| 2677 | chipsets and more than 3GB of RAM that causes sporadic data corruption | |
| 2678 | when the hardware IOMMU is used. This problem is still under | |
| 2679 | investigation by the Linux kernel developers and the hardware | |
| 2680 | manufacturers, and no official upstream fix has been released. To | |
| 2681 | protect the integrity of their data, users of these systems are advised | |
| 2682 | to manually disable the use of hardware IOMMU at boot time by adding | |
| 2683 | <tt>iommu=soft</tt> to their kernel boot options until a correct solution | |
| 2684 | can be found.</p> | |
| 2685 | <p>More information about this issue is available in Debian bug | |
| 2686 | <url id="http://bugs.debian.org/404148" name="#404148"> | |
| 2687 | and Linux Kernel bug | |
| 2688 | <url id="http://bugzilla.kernel.org/show_bug.cgi?id=7768" name="#7768">.</p> | |
| 2689 | </sect1> | |
| 2690 | ]]> | |
| 2691 | </sect> | |
| 2692 | ||
| 2693 | <!-- Controversial, disabled for now, please translate though | |
| 2694 | <sect id="german-quotes"><heading>Problems with German Quotes</heading> | |
| 2695 | ||
| 2696 | <p>The locales for German style languages (e.g. de_DE@euro) | |
| 2697 | unfortunately use an aesthetically unpleasing way of representing | |
| 2698 | open quotation marks. We have retained it this way in order to | |
| 2699 | preserve compatibility with other Linux distributions, and we hope | |
| 2700 | that in the future it will be fixed. We suggest that you switch to a | |
| 2701 | UTF-8 locale (e.g. de_DE@euro.UTF-8), which fully supports German with | |
| 2702 | the correct quotation marks, and, using Unicode encoding, has better | |
| 2703 | support for other languages as well.</p> | |
| 2704 | ||
| 2705 | <p>To change the system wide locale choice, use: | |
| 2706 | <example>dpkg-reconfigure locales</example></p> | |
| 2707 | </sect> | |
| 2708 | --> | |
| 2709 | <!-- Will be added if relevant information is written here | |
| 2710 | <sect id="syntax"><heading>Important program syntax changes</heading> | |
| 2711 | ||
| 2712 | <p>Debian attempts to avoid changing upstream packages, therefore | |
| 2713 | any changes in the upstream package will be present in the version in | |
| 2714 | &debian;. This can mean that program behavior may change between | |
| 2715 | releases of &debian;. </p> | |
| 2716 | ||
| 2717 | <p><em>No changes yet reported.</em></p> | |
| 2718 | ||
| 2719 | </sect> | |
| 2720 | --> | |
| 2721 | ||
| 2722 | <![ %defaulted-2.4 [ | |
| 2723 | <sect id="upgrade-to-2.6"> | |
| 2724 | <heading>Upgrading to a 2.6 kernel</heading> | |
| 2725 | ||
| 2726 | <p>The 2.6 kernel series contains major changes from the 2.4 series. | |
| 2727 | Modules have been renamed and a lot of drivers have been partially | |
| 2728 | or sometimes almost completely rewritten. Upgrading to a 2.6 kernel | |
| 2729 | from an earlier version is therefore not a process to be undertaken | |
| 2730 | lightly. This section aims to make you aware of some of the issues | |
| 2731 | you may face.</p> | |
| 2732 | ||
| 2733 | <p>If you compile your own kernel from source, make sure you install | |
| 2734 | <package/module-init-tools/ before you reboot with the 2.6 kernel. | |
| 2735 | This package replaces <package/modutils/ for 2.6 kernels. If you | |
| 2736 | install one of the Debian <package/linux-image/ packages, this | |
| 2737 | package will be installed automatically because of dependencies.</p> | |
| 2738 | ||
| 2739 | <p>If you use <em/LVM/, you should also install <package/lvm2/ | |
| 2740 | before you reboot as the 2.6 kernel does not directly support LVM1. | |
| 2741 | To access LVM1 volumes, the compatibility layer of <package/lvm2/ | |
| 2742 | (the dm-mod module) is used. You can leave <package/lvm10/ installed; | |
| 2743 | the init scripts will detect which kernel is used and execute the | |
| 2744 | appropriate version.</p> | |
| 2745 | ||
| 2746 | <p>If you have entries in the <file>/etc/modules</file> file (the | |
| 2747 | list of modules to be loaded during system boot), be aware that some | |
| 2748 | module names may have changed. If this happens you will have to update | |
| 2749 | this file with the new module names.</p> | |
| 2750 | ||
| 2751 | <!-- JFS: Can't this device name change even for some other disk controllers? I've found | |
| 2752 | references in debian-user posts talking about some strange chipsets and BIOS | |
| 2753 | which are seen in sarge' 2.4 as hda and in etch's 2.6 as hdf... --> | |
| 2754 | <![ %i386 [ | |
| 2755 | <p>For some SATA disk controllers, the device assigned to a drive and | |
| 2756 | its partitions may change from <file>/dev/hdX</file> to | |
| 2757 | <file>/dev/sdX</file>. If this happens, you will have to modify your | |
| 2758 | <file>/etc/fstab</file> and bootloader configuration accordingly. | |
| 2759 | Unless these changes are made correctly, your system may not boot | |
| 2760 | correctly<footnote>It will boot the kernel but will fail when trying | |
| 2761 | to mount the root file system and will abort with an error <em>waiting for root file system</em> | |
| 2762 | followed by <em>unable to mount /dev/hdX ..not found</em>. | |
| 2763 | You can use the <prgn/initramfs/ shell to fix this issue, after you | |
| 2764 | identify the newly assigned device names in the kernel boot messages or by reviewing | |
| 2765 | the contents of <file>/dev/disk/</file>.</footnote>.</p> | |
| 2766 | ]]> | |
| 2767 | ||
| 2768 | <!-- Bug: #416720 --> | |
| 2769 | <![ %ia64 [ | |
| 2770 | <p>HP Itanium systems running older firmware are incompatible with the | |
| 2771 | 2.6 kernel in &releasename;. That means you should upgrade your | |
| 2772 | system to the latest firmware before upgrading your kernel. It is | |
| 2773 | recommended you do this before the system upgrade, as if you are | |
| 2774 | already running a 2.6 kernel you will automatically retrieve the | |
| 2775 | latest kernel when upgrading the rest of the system (see <ref | |
| 2776 | id="upgrading_other">). Failing to do this will result in an system | |
| 2777 | that does not boot. | |
| 2778 | </p> | |
| 2779 | ]]> | |
| 2780 | ||
| 2781 | <p>Once you have installed your 2.6 kernel, but before you reboot, | |
| 2782 | make sure you have a recovery method. First, make sure that the | |
| 2783 | bootloader configuration has entries for both the new kernel and | |
| 2784 | the old, working 2.4 kernel. You should also ensure you have a "rescue" | |
| 2785 | floppy or CD-ROM to hand, in case misconfiguration of the bootloader | |
| 2786 | prevents you from booting the old kernel.</p> | |
| 2787 | ||
| 2788 | <![ %not-s390 [ | |
| 2789 | <sect1 id="2.6-keyboard"> | |
| 2790 | <heading>Keyboard configuration</heading> | |
| 2791 | ||
| 2792 | <p>The most invasive change in the 2.6 kernels is a fundamental | |
| 2793 | change of the input layer. This change makes all keyboards look | |
| 2794 | like "normal" PC keyboards. This means that if you currently have | |
| 2795 | a different type of keyboard selected (e.g. a USB-MAC or Sun | |
| 2796 | keyboard), you will very likely end up with a non-working keyboard | |
| 2797 | after rebooting with the new 2.6 kernel.</p> | |
| 2798 | ||
| 2799 | <p>If you can SSH into the box from another system, you can resolve | |
| 2800 | this issue by running <tt>dpkg-reconfigure console-data</tt>, choosing | |
| 2801 | the option "Select keymap from full list" and selecting a "pc" | |
| 2802 | keyboard.</p> | |
| 2803 | ||
| 2804 | <p>If your console keyboard is affected, you will probably also need to | |
| 2805 | reconfigure your keyboard for the X Window System. You can do this | |
| 2806 | either by running <tt>dpkg-reconfigure xserver-xorg</tt> or by | |
| 2807 | editing <file>/etc/X11/xorg.conf</file> directly. Don't forget | |
| 2808 | to read the documentation referred to in <ref id="nownownow">.</p> | |
| 2809 | ||
| 2810 | <![ %i386 [ | |
| 2811 | <p>This issue is unlikely to affect the &arch-title; architecture | |
| 2812 | as all PS/2 and most USB keyboards will already be configured as | |
| 2813 | a "normal" PC keyboard.</p> | |
| 2814 | ]]> | |
| 2815 | <![ %not-i386 [ | |
| 2816 | <p>Note that if you are using a USB keyboard, this may be configured | |
| 2817 | as either a "normal" PC keyboard or as a USB-MAC keyboard. In the | |
| 2818 | first case you will not be affected by this issue.</p> | |
| 2819 | ]]> | |
| 2820 | </sect1> | |
| 2821 | ||
| 2822 | <sect1 id="2.6-mouse"> | |
| 2823 | <heading>Mouse configuration</heading> | |
| 2824 | ||
| 2825 | <p>Again because of the changes in the input layer, you may have to | |
| 2826 | reconfigure the X Window System and <package/gpm/ if your mouse is | |
| 2827 | not working after upgrading to a 2.6 kernel. The most likely cause is | |
| 2828 | that the device which gets the data from the mouse has changed. | |
| 2829 | You may also need to load different modules.</p> | |
| 2830 | ||
| 2831 | <![ %sparc [ | |
| 2832 | <p>If you currently have X configured for <file>/dev/sunmouse</file>, | |
| 2833 | you probably need to change this to <file>/dev/psaux</file>.</p> | |
| 2834 | ]]> | |
| 2835 | ||
| 2836 | </sect1> | |
| 2837 | ||
| 2838 | <!-- FIXME: should be udev now? (vorlon) --> | |
| 2839 | <sect1 id="2.6-sound"> | |
| 2840 | & |