Web lists-archives.com

Re: Upgrading from very-old Debian (and xtoolwait)

On Fri 01 Dec 2017 at 21:52:33 (+0100), deloptes wrote:
> Jonathan Dowland wrote:
> > Non-the-less, it's not something that many people will have attempted,
> > and there are quite likely to be things that might slip through the net.
> > Not just things within the Debian ecosystem: a machine running Lenny was
> > presumably installed in or around 2009, so there's nearly 9 years worth
> > of local sysadmin changes that might have been made.
> > 
> >> I had few problems from wheezy to lenny,
> > 
> > That would be downgrading by two releases. That's bound to be
> > troublesome.
> > 
> >>but almost no problem from lenny to stretch.
> > 
> > That's the path that OP's friend would be attempting (as lenny is
> > currently oldoldoldoldstable). I'm glad it worked for you, but I would
> > still not recommend it to anyone else.
> Aah sorry, I moved from lenny to squeeze then I moved partially to wheezy
> last year before squeeze got obsolated and this year I moved to stretch in
> one day, doing wheezy -> jessie and jessie -> stretch.
> So the problem was squeeze -> wheezy

My only negative recollections there are:

a) I played safe on this very old laptop and upgraded to a 486 kernel
(3.2.0-4-486 IIRC) because of the necessity for pae in 686 versions.

b) I've still found no replacement for xtoolwait which was last
available in squeeze (version 1.3-6.2). It's the only thing that
ensures all the xterms appear in their correct places when starting
X. But I have to have a workaround for a bug where it sometimes
sticks around and consumes most of the CPU cycles, typically while
starting xclock. I just put the following line early on in .xsession

( sleep 60; pgrep xtoolwait; pkill xtoolwait ) &