This is currently in testing so it is not recommended to use these instruction in production.
deb lenny main contrib non-free deb-src lenny main contrib non-free deb lenny/updates main contrib non-free The above example is for a system using the main UK mirrors; your file might use a different local one WARNING: if for some reason your apt sources doesn’t use etch, but “stable” then your apt commands will start to use lenny the moment it is released.
I am inside archive.debian.org, but I am a little confused as to how to follow it's instructions/modify the sources list.
Here's the contents of the current list: deb etch ndn deb etch ksplice deb main non-free contrib deb etch-backports main deb etch/volatile main contrib non-free deb etch/updates main deb etch main I had to actually follow the steps above to clear the errors.
To upgrade to Debian Lenny : Edit /etc/apt/d/etch.list, replacing the word etch with lenny.
I also changed the mirror url to a North American mirror rather than the German one by removing the de. You may also rename the filename from to if you feel so inclined. When Debian comes back up, it will be running Lenny.
What steps should I follow to end up with the server running lenny/xen3.2 and the virtual machines running lenny?
After making sure the grub config is correct and will be booting 3.2 all of my paravirtual machines booted up.
Perform upgrade After changing apt sources we need to update source list using the following command Note:-dist-upgrade was renamed to full-upgrade in lenny’s aptitude; or you can use:apt-get dist-upgrade This will take a while depending on what packages you have installed (that will need to be upgraded) and on your internet connection speed.
After this is done you will have to reboot your system in order to activate the kernel upgrade to the lenny 2.6.26 kernel.
That chapter covers potential issues not directly related to the upgrade process but which could still be important to know about before you begin.
Before upgrading your system, it is strongly recommended that you make a full backup, or at least back up any data or configuration information you can't afford to lose.