Andrew Sackville-West on 20/06/08 14:38, wrote:
On Fri, Jun 20, 2008 at 04:51:25AM -0700, Adam Hardy (debian) wrote:
[snipped tales of woe regarding mixed systems]
I have a 5 year-old system hosted on Xen by a hosting company, which I only
use for Java and mysql - currently it's running Woody and being slap-dash, I
tried to install a piece of software using apt-get, which promptly failed.
Seeing the conversation above, it sounds bad - but I'm going to try
something otherwise I have to ask the hosting co to wipe my Xen slice for
me.
If I put 'sarge' in all the sources.list urls, I should be able to upgrade
to sarge OK? Or is it too late?
you should read the release notes for sarge first:
http://www.debian.org/releases/sarge/i386/release-notes/ch-upgrading.en.html
and you might need to use "oldstable" as the identifier in
sources.list. But yes, you should be able to upgrade to sarge. Once
you're in the think of it, you might want to take the next step and
move up to etch since it may go to old stable in the next few
months. Then when that happens, you can move up to lenny when it's
fairly fresh. At that point, you can let it go for another 5 years or
so... ;-)
OK!
Those upgrade instructions warn:
"Important! You should not upgrade using telnet, rlogin, rsh, or from an X
session managed by xdm, gdm or kdm etc on the machine you are upgrading. That is
because each of those services may well be terminated during the upgrade, which
can result in an inaccessible system that is only half-upgraded."
Do you think ssh is deliberately excluded from that list of remote shells?
I can only get onto my server via ssh since the machine is at the hosting co's
site (and indeed it's only a Xen slice, not a whole OS).
Adam
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
