Hi --

I decided to upgrade to --current. Did so without difficulties, ran lilo as suggested at the end of the process. Rebooted.

Alas, I'm getting the same "Read-only file system" errors reported in this SOLVED thread:

http://www.linuxquestions.org/questi...ed-4175611523/

There are also lots of complaints in the boot messages about "/lib64/libc.so.6: version 'GLIBC_2.25' not found (required by /lib64/libblkid.so.1)"
<-- that's one example - the same message pops up for many libraries. Perhaps slackpkg didn't update glibc correctly? I'm stabbing in the dark here.

Unfortunately, because I'm too boneheaded to have backed things up, I can't restore as the OP in that previous post did.

I don't know whether the fact that I am experiencing the same problem indicates anything whatsoever. Am looking through the output of dmesg, but not seeing anything suspect yet.

I've downloaded Slacko as one poster to that prior thread suggested, but am not sure what to look for (one person suggested deleting everything in /tmp ... I suppose that is a good first thing to try).

Suggestions are welcome. I'm looking through the SOLVED post and trying the suggestions there. Some are moot due to the filesystem being read-only

Thanks,

Glenn

Using Slacko, I emptied out /tmp and cleared some lock files from /var/log. No happiness booting. I am downloading the Slackware DVD image and will use that to attempt a repair.

There was no actual solution. I simply reinstalled stable. Unsure whether I want to try another upgrade to --current.

I offer this as a shot in the dark.

I once made this mistake in upgrading a Slackware install:

I ran slackpkg upgrade-all before slackpkg install-new. A crucial new package was not in place when I ran upgrade-all and I bricked my system.

That's when I learned how to boot to a live CD and rescue my install.

1 members found this post helpful.

Indeed. There are a lot of new packages that have been introduced in -current since 14.2's release.
I also run slackpkg clean-system after upgrade-all as there will be obsolete packages to remove.

In case it helps anyone, here is my Slackware update script, for which I do not claim authorship, as I learned it from a member of my LUG. It should be run as root.

It should not be run unattended, as it requires interaction from root.

Because I have configured my blacklist file, when it asks what I want to do with new configuration files, I always answer "P" for "prompt," so I can decline overwrites of files I have configured to differ from default.

1 members found this post helpful.

The very first time I run slackpkg I run slackpkg update gpg, then the four commands that you mentioned. That command adds Slackware's GPG key.

If you are running a mulitlib system you can get that error if you don't make sure to upgrade the mulitlib packages before you reboot. You need the multilib compatible version of GLIB to match the current version. Not sure if that was your problem.