upgrading glibc in current

Upgrading to current since about a month ago from Slack 11 requires special instructions Pat V clearly outlines in CHANGES_AND_HINTS.TXT. His instructions I find confusing because I am relatively new. For starters, what does Pat mean by

Note that the generic* kernels will require an initrd, so you should probably choose one of the huge* kernels for now.

This is confusing too:

At this point, use "installpkg" to install the kernel rather than "upgradepkg"

Doesn't that mean I have to alter the vmlinuz entry in my boot loader? I ask because I tried doing this on my other Slackware box and I got a kernel panic.

The answer to my first question, according to rworkman on FreeNode, is I need to read /boot/README.initrd.

What he means by the huge installation is when you installed slackware you need the 2.6 kernel to install the new glibc. being that current is slackware 12 in the works, you can't upgrade to it, you have to install it.

Originally Posted by Hern_28 What he means by the huge installation is when you installed slackware you need the 2.6 kernel to install the new glibc. being that current is slackware 12 in the works, you can't upgrade to it, you have to install it.

But do I have to edit my lilo.conf at all?

I didn't upgrade to slackware current from slackware, upgraded from zenwalk. i didn't have to change mine but not sure doing it the other way. could type /etc/lilo when finished just in case before rebooting.

If your lilo points to vmlinuz, everything should be allright. But I don't understand why do you want to upgrade the kernel. It's the most easiest way to make the system unusable.

Do you not need the 2.6 kernel to upgrade to install glibc? Will have to double check that but your right it will mess with the system coming from 2.4 but should be fixed after aptget current install.

There are two great threads:

http://www.linuxquestions.org/questi...d.php?t=430773

http://www.linuxquestions.org/questi...d.php?t=484109

Originally Posted by Alien_Hominid There are two great threads: http://www.linuxquestions.org/questi...d.php?t=430773 http://www.linuxquestions.org/questi...d.php?t=484109

I don't see how installing kernel headers is relavent to installing glibc, the task at hand.

After I install my new generic kernel, must I add anything to my lilo.conf?

Originally Posted by Drone4four After I install my new generic kernel, must I add anything to my lilo.conf?

According to the slackers on FreeNode I do. In my case, I am actually not using lilo. I will be editing /home/ubuntu/boot/grub/menu.lst.

Originally Posted by Hern_28 Do you not need the 2.6 kernel to upgrade to install glibc? Will have to double check that but your right it will mess with the system coming from 2.4 but should be fixed after aptget current install.

As the CHANGES_AND_HINTS.TXT indicates, yes, you *must* be running a 2.6 kernel *before* you upgrade glibc.

As for "aptget current install" -- what are you talking about? There is no such tool on Slackware, and even if the user has installed something of that sort, it's *not* an officially sanctioned or supported upgrade.

Originally Posted by Drone4four Upgrading to current since about a month ago from Slack 11 requires special instructions Pat V clearly outlines in CHANGES_AND_HINTS.TXT. His instructions I find confusing because I am relatively new.

I'm going to sound harsh here, but...

Quite frankly, if those instructions are confusing to you, you should probably continue running the stable (11.0) release of Slackware until 12.0 releases, and then do a completely fresh installation (not an upgrade) to it. I don't know how to make those instructions any clearer.

So lemme get this straight. If I use this kernel, I will need to install a new initrd.gz:

http://mirror.vbfx.com/slamd64/slamd64-current/slackware/a/kernel-generic-2.6.18.8_smp-x86_64_slamd64-1.tgz

But if I use this one,

http://mirror.vbfx.com/slamd64/slamd64-current/slackware/a/kernel-huge-2.6.18.8_smp-x86_64_slamd64-1.tgz

then I will NOT need to install a new initrd.gz?

Originally Posted by rworkman I'm going to sound harsh here, but... Quite frankly, if those instructions are confusing to you, you should probably continue running the stable (11.0) release of Slackware until 12.0 releases, and then do a completely fresh installation (not an upgrade) to it. I don't know how to make those instructions any clearer.

lol

I can't wait until 12.0 because I need to use slackbuilds to install things. Slackbuilds at the momment stop half way to complain about GCC and C++. -current is my only option. I am willing to learn.