/[ddp]/manuals/branches/release-notes/lenny/en/release-notes.dbk
ViewVC logotype

Diff of /manuals/branches/release-notes/lenny/en/release-notes.dbk

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

revision 3046 by robster, Fri May 6 19:05:46 2005 UTC revision 3047 by robster, Fri May 6 19:25:15 2005 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.22 2005-05-06 19:05:46 robster Exp $">    <!entity docid "$Id: release-notes.en.sgml,v 1.23 2005-05-06 19:25:15 robster 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 230  release: architectures: Line 230  release: architectures:
230            because each of those services may well be terminated during the            because each of those services may well be terminated during the
231            upgrade, which can result in an <em/inaccessible/ system that is only            upgrade, which can result in an <em/inaccessible/ system that is only
232            half-upgraded.</p>            half-upgraded.</p>
233    
234              <p>The recommended method of upgrading is to use <prgn/aptitude/, as
235              described here. The built-in dependency analysis enables smooth
236              upgrades and easy installations.</p>
237    
238              <p>Any package installation operation must be run with superuser
239              privileges, so either login as root or use <prgn/su/ or
240              <prgn/sudo/ to gain the necessary access rights.</p>
241    
242              <p>First the <package>aptitude</package> package needs to be installed.
243              This is done with:</p>
244    
245              <p><example>
246    apt-get install aptitude
247              </example></p>
248    
249              <p>Provided that you have a working APT configuration this will
250              install the &oldreleasename; version of
251    
252              <prgn>aptitude</prgn>.</p>
253    
254          <sect1><heading>Disabling APT pinning</heading>          <sect1><heading>Disabling APT pinning</heading>
255    
# Line 300  aptitude hold | unhold &lt;package&gt; Line 320  aptitude hold | unhold &lt;package&gt;
320    
321          <sect id="upgrade-process"><heading>Preparing sources for APT</heading>          <sect id="upgrade-process"><heading>Preparing sources for APT</heading>
322    
           <p>The recommended method of upgrading is to use <prgn/aptitude/, as  
           described here. The built-in dependency analysis enables smooth  
           upgrades and easy installations.</p>  
   
           <p>Any package installation operation must be run with superuser  
           privileges, so either login as root or use <prgn/su/ or  
           <prgn/sudo/ to gain the necessary access rights.</p>  
323    
324            <p>Before starting the upgrade you must set up <package/apt/'s            <p>Before starting the upgrade you must set up <package/apt/'s
325            configuration file for package lists,            configuration file for package lists,
# Line 481  script -a ~/upgrade-to-&releasename;.typ Line 494  script -a ~/upgrade-to-&releasename;.typ
494            in those directories may be deleted during the upgrade or during any            in those directories may be deleted during the upgrade or during any
495            restart).</p>            restart).</p>
496    
           <p>Next the <package>aptitude</package> package needs to be installed.  
           This is done with:</p>  
   
 <!-- JFS: Shouldn't apt-get update be run first, otherwise they might get an outdated aptitude version (i.e. woody's)... -->  
   
           <p><example>  
 apt-get install aptitude  
           </example></p>  
   
           <p>Provided that you have a working APT configuration as described  
           above this will install the &releasename; version of  
           <prgn>aptitude</prgn>.</p>  
 <!-- FJP: Will it really? Haven't we have just instructed users to point  
           everything to the new release? -->  
   
497            <p>First <prgn>aptitude</prgn> needs to fetch a list of new and            <p>First <prgn>aptitude</prgn> needs to fetch a list of new and
498            updated packages for the new release. This is done by executing:</p>            updated packages for the new release. This is done by executing:</p>
499    
# Line 675  that are included in the non-free sectio Line 673  that are included in the non-free sectio
673          <sect id="kernel_update">          <sect id="kernel_update">
674          <heading>Keyboard issues on upgrades to a 2.6 kernel</heading>          <heading>Keyboard issues on upgrades to a 2.6 kernel</heading>
675    
676            <p>After the upgrade to &releasname;, you may have 2.6 kernel images            <p>After the upgrade to &releasename;, you may have 2.6 kernel images
677            available for installation. There is an important change in the            available for installation. There is an important change in the
678            input layer for 2.6 kernels that you should be aware of before you            input layer for 2.6 kernels that you should be aware of before you
679            attempt to switch from using a 2.4 to a 2.6 kernel.</p>            attempt to switch from using a 2.4 to a 2.6 kernel.</p>
Legend:
Removed from v.3046  
changed lines
  Added in v.3047
  ViewVC Help
Powered by ViewVC 1.1.5