Re: Slink to Potato
>>>>> "markzimm" == markzimm <firstname.lastname@example.org> writes:
>> That was supposed to be the point of my message -- In my
>> experience, upgrading from glibc 2.0 to 2.1 is *trivial*, and needs
>> no special consideration, migration guides, hand-holding sessions,
>> or support groups.
>> Stop whining and just do it.
>> p.s. The `stop whining' bit was for dramatic effect only.
markzimm> I've got to agree with Miles here. Once I stopped shaking in
markzimm> fear of a possible instability, I started doing it one step
markzimm> at a time and I haven't had any serious problems. The few
markzimm> problems I did have generally had solutions in the mailing
markzimm> list archives and were easily dealt with.
markzimm> The important thing is: take small steps and test them out
markzimm> before going on.
markzimm> -- Mark
I'll add my $0.02 (CDN) to what has developed into a really interesting
thread on this list.
I upgraded to glibc-2.1 I think 2 or 3 days after installing Slink mainly
because I couldn't do without the unstable versions of a few packages :
XFree-188.8.131.52 (which support my Matrox G200 card very well), WDM and
After upgrading to the unstable versions of those 2 packages (and glibc-2.1
and a bunch of other stuff that was mandatory), I took things one package
from unstable at a time. And for the most part, things have worked out well
for me. Of course, I am talking about my home system here not a production
system where reliability and stability are much more important.
I then decided to jump up to the the 2.2.12 kernel in one shot without
bothering to recompile the stock 2.0.36 kernel even once. Despite the
information posted on the Debian website about known problems running the
2.2.x kernels, I think I only upgraded the netstd, netbase and lsof and
have had in general no problem running the 2.2.12 kernel alongwith
I was quite nervous about adding so many packages from unstable but my
system has been very solid and stable.
And of course, this list has been a tremendous resource whenever I have had
If sth breaks, edit /etc/apt/sources.list (and possibly dpkg
--remove/--purge <package) and get the version from stable, if possible.
Like Mark said above, take small steps and test them out before going
PS : If anyone is interested, I have made a logfile detailing all of the
changes (configuration, package upgrades/installations) that I have made to
my system since installing slink about a month ago.
ssahmed AT interlog DOT com