On Fri 24 Jan 2014 at 11:54:12 +0200, Andrei POPESCU wrote: > The recommended way is specific to each release and thoroughly > documented in the Release Notes.
Which is where I got what I wrote from: If the system being upgraded provides critical services for your users or the network[2], you can reduce the downtime if you do a minimal system upgrade, as described in Section 4.4.5, “Minimal system upgrade”, followed by a kernel upgrade and reboot, and then upgrade the packages associated with your critical services. Upgrade these packages prior to doing the full upgrade described in Section 4.4.6, “Upgrading the system”. This way you can ensure that these critical services are running and available through the full upgrade process, and their downtime is reduced. Alternatively: In some cases, doing the full upgrade (as described below) directly might remove large numbers of packages that you will want to keep. We therefore recommend a two-part upgrade process: first a minimal upgrade to overcome these conflicts, then a full upgrade as described in Section 4.4.6, “Upgrading the system” Sections 4.1.3. and 4.4.5. of http://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.html -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/24012014101334.9799707e5...@desktop.copernicus.demon.co.uk
