Upgrade 11.0 to 12.0 nightmare

krazykatt wrote:

> At some point while attempting to upgrade I kept getting
> 'GLIBC_2.4 not found' errors and a number of packages failed to
> install.
>
> Has anyone seen this and how do I correct the install?
>

This usually implies you've incorrectly upgraded your glibc packages. The
best basic advice for upgrading glibc packages is boot to single user mode
first, then upgrade the glibc packages in ....../slackware/a
and ...../slackware/l. Then do the rest of the upgrading. A word of
advice, you'll get lots of errors if you try to reboot and do this now, and
you may be unable to boot into your system easily. I used to keep a umsdos
setup for situations like this. I could boot into it, then mount the
partition and upgrade with that partition as the root partition without
worrying about this problem. It's not easily possible anymore, umsdos
isn't supported by 2.6.X as far as I can tell.

Art Clemons wrote:
> krazykatt wrote:
>
> > At some point while attempting to upgrade I kept getting
> > 'GLIBC_2.4 not found' errors and a number of packages failed to
> > install.
> >
> > Has anyone seen this and how do I correct the install?
> >
>
> This usually implies you've incorrectly upgraded your glibc packages. The
> best basic advice for upgrading glibc packages is boot to single user mode
> first, then upgrade the glibc packages in ....../slackware/a
> and ...../slackware/l. Then do the rest of the upgrading.

I'm not the O.P. but I have the same problem.

I have followed the UPGRADE.TXT religiously, I have upgraded the
hernel and the kernel modules,
downloaded all the new packages into a temporary directory, rebooted
the system into the new kernel,
then upgraded one by one the packages in single mode, in the order
suggested by the upgrade file.

After going Init 3, that's where I couldn't run anything. I couldn't
even run pkgtool.

I also tried to boot from an emergency usb image and chroot to the
hard disk, but I had the same
problems. It couldn't find the ternimal 'linux'.

Ottavio
http://www.pledgebank.com/boycottvista

In article <i_ednWOcerd_mC3bnZ2dnUVZ_judnZ2d RemoveThis @comcast.com>,
Art Clemons <ArtClemons RemoveThis @aolSPAM.com> wrote:

> I used to keep a umsdos
> setup for situations like this. I could boot into it, then mount the
> partition and upgrade with that partition as the root partition without
> worrying about this problem. It's not easily possible anymore, umsdos
> isn't supported by 2.6.X as far as I can tell.

But on a modern computer its easy to boot from the CD and do the same
thing you describe from there.

- Martijn

In article <1185918685.653541.120000.RemoveThis@b79g2000hse.googlegroups.com>,
krazykatt <dbredy.RemoveThis@gmail.com> wrote:

> I've been trying to upgrade from 11.0 to 12.0 using the UPGRADE.TXT
> instructions and having all kinds of problems.
>
> I successfully upgraded the kernel on my system to 2.6.21.5 from
> 2.6.17.3. I then upgraded the packages as advised
> and somehow my /bin/sh link was deleted. I promptly recreated the link
> and continued upgrading packages following the instructions to the
> letter. At some point while attempting to upgrade I kept getting
> 'GLIBC_2.4 not found' errors and a number of packages failed to
> install.
>
> Has anyone seen this and how do I correct the install?

At this point it sounds like you're better off deleting everything but
/home and perhaps /etc, then just installing your system afresh with the
setup program. That would probably be less work than trying to salvage
this situation, in fact some use this as their primary upgrade method.
If you keep /etc, don't forget to move over and/or merge those .new
files as necessary. Good luck.

- Martijn