I see. Seems like older versions of lilo have trouble handling xz compressed kernel images...

The problem was more accurately the maximum number of sectors for kernel setup code being too short in lilo versions < 23.2. As stated by lilo-23-2's CHANGELOG:

1 members found this post helpful.

I see, thanks for the answer. I wonder why that happened though? The first time I ran slackpkg upgrade-all and chose to get everything, I ran into that error. After that I ran it again but only grabbing the kernal and lilo this time and didn't get the error. Maybe I somehow unselcted lilo when I scrolled through the upgrade list the first time. Not sure how but hey, things happen.

Well, I think I'm about ready to install Slackware then (as soon as I get a new dvd drive). When I actually install it though I'm planning on just sticking with the stable versions. When a new stable version comes out will a slackpkg update be available so that one can get the updated mirrors?

You can easily install from a USB memory stick, if you have one that's big enough.

Unfortunately, I don't, I really need to upgrade.

OT:

Addressable memory has everything to do with 32- vs 64-bit kernels since an earlier post seemed to confuse "addressable RAM" (how much memory kernel supports) with modules (what hardware can I run).

What I pointed to was our beloved BDFL's explanantion of the difference in generic and huge (and he should know!) and not kernel arch. Isn't it better to point to the information than to just say one kernel is "bigger" than the other. Yes, you are right that the huge kernel has all the modules build in and so takes up more more space both on disk and in memory (feel better?). The generic kernel expects to find the modules elsewhere on hardware detection. Yes, O Great and Wise Slackware Guru, that is the difference. I am humbled that you took the time to respond to this unworthy one.

@kingbeowulf: no need to be sarcastic. I now see, looking at it again, that I read wrong (actually, very wrong) your previous post, misunderstanding it all.
My humble excuses.

@414N: No worries. I still have a bit of sarcasm left over from decades of Usenet that spills out from time to time. We all need to slow down to comprehend what we think we are reading...

Why reinstall the slack? The upgrade process is really simply with Slack. I've personally upgraded multiple times from 12.0 to 13.37 without an issue. Just follow the UGRADE.txt and CHANGES_AND_HINTS.txt files and you are good to go.

Linux version is just a set of packages. In newer slack, there are newer versions and some packages are either added or removed. All that information is in the UPGRADE.txt file

So really there is no need to reinstall slack ever.

Alright, I'm having trouble with sudo.

I made sure that my normal user account was in the wheel group and used visudo uncomment this line:

I can use sudo for some things now, but not anything related to package management. I found an old thread on this that said I probably need to put PATH="$PATH:/usr/sbin" in either ~/.profile or ~/.bash_login. Well I did that (both were blank files by the way, not sure if that affects anything) however I am still unable to use package managers with sudo. What am I missing/doing wrong?

There is no reason to use sudo in Slackware for maintenance of the system. Do everything package management related as root: just type "su" or "su -" in a terminal or xterm to become root.

The administrative files are not part of the user's path in Slackware. You can either use /sbin/upgradepkg and such or edit /etc/profile and add /sbin and /usr/sbin to the user's path. Or just use sudo -i if you insist on using sudo.

Ah thanks. I don't really have a problem using su most of the time, it's just that I'd prefer to be able to just sudo installpkg instead of logging in as super user just to install a single package.

You can also use the -c option for su:
The double quotes are needed if the command needs additional space-separated arguments.

This is easily accomplished - you'll need to adjust sudoers (using visudo). Have a look here and scroll down to Example Entries.

https://wiki.archlinux.org/index.php/Sudo

If you don't want to use vi use this command to use nano; use su if you need to.