Correct.

Make sure you have a look at the line about -EEXIST errors in CHANGES_AND_HINTS.TXT though - you'll get that with the huge* kernels.
There may very well be other issues along those lines with huge* kernels, but none of which I'm aware at this time.

The huge* kernels are really intended for installation, with the generic* ones for actually running the system. The "safe" option (the way it falls back after an installation) though is to link /boot/vmlinuz with the huge kernel, as that way (as long as /sbin/lilo is run and the correct boot and root devices are specified), the system will definitely boot after the upgrade (in case you forget to make an initrd).

That is nonsense. I run slackware 11.0 and SlackBuild scripts just plain work. In fact all Slackbuild scripts currently hosted at SlackBuilds.org work on standard 11.0 installs. Thats the way they are written *and* tested.

More Likely you have missed out something of the d/ selection. Unless you post better errros, it's hard to say what "does not work" constitute off. Just upgrading to -current because you think something is not right, is probably not the best way to go about troubleshooting.

As BlackPanther advised, this is not a good approach. I don't know for sure if you're referring to using things from SlackBuilds.org, but nothing there is guaranteed to work on -current at all. Everything is tested and supported on 11.0.

It sounds like you missed some things in the D/ package series.

What my post was about, you should have 2.6 kernel headers installed if you plan to compile glibc with 2.6 kernel (not 2.4). The headers which are in use, should be those against which you will compile your glibc.

I still have some questions before I go through with upgrading glibc. Is this the only command I need to enter for Step #1 in Pat V's Hints and Changes text file?

And what does Pat V mean when he says: In what directory can I find kernel-modules-2.4.* packages?

You're attempting to use instructions written for Slackware but on Slamd64. If memory serves correctly, Slamd64 11.0 didn't have a 2.4 kernel. If it did, though, the records would be in /var/log/packages.

Should a disclaimer be added to UPGRADE.TXT / CHANGES_AND_HINTS.TXT ?? Something along the lines of:
"If the instructions in this file do not make sense, do not attempt the upgrade - continue running your present version."

Run pkgtool and search for package. In /lib/modules directory.

Slamd64 is the origional 64 bit clone of Slackware, which is a 32 bit distribution. You do not want to install a Slamd64 kernel with Slackware -current, only grief and heartache lie along that path. If you are trying to install Slamd64 -current, then please say so.

I am installing Slamd64-current. DUH.

I installed several of the generic kernels before I noticed that warning about needing an initrd. Worked anyway.

If you're talking about 11.0, then then the generic kernels had support for ext2 built in; as such, an ext3 root filesystem could be mounted just fine with the generic kernel and no initrd.

On -current right now (20070523), the generic kernels do not include any filesystem support, so you *will* need an initrd. If you do a full installation, then the the huge kernels will take precedence (as they are installed after the generic kernels during installation) over the generic kernels (with respect to symlinks created in /boot), even though the generic kernel is installed.

Yes, two of them were from 11.0, and I noticed a booting message that ext3 was being mounted as ext2. Apparently, I was just lucky.

I did upgrade to glibc 2.3.6, after "telinit 1", with no apparent problem.

hmmm,I just installed the 2.6.21.3 smp kernel and it isn't showing up in lilo. What should I put for the image variable in my lilo.conf?