New kernel on --Current.

If you run the Nvidia driver, download the latest driver. There is a new ABI this time and the older driver is not compatible.

4 members found this post helpful.

The nvidia problem is with the new xorg 1.19, not the kernel.

You are right - my reply has no business in this thread. That said, I got caught with my pants down on this upgrade. Forgot to add the new libXfont2 so things didn't start off real well after the upgrade. My inattention took me an extra 30 minutes to fix things up.

Thanks for the heads-up. Awesome!

solved my own problem lol

4.4.32 working good here..

After the latest update on -current I noted today that when I ran slackpkg clean-system there were a number of obsolete x libraries that I removed.

I never run slackpkg clean-system. Is it a recommended regular maintenance item when running -current?

I'll run it occasionally, such as after upgrading 14.2----> -current. It isn't a regular maintenance item for me. I'll run it once in a while to check for obsolete packages.

1 members found this post helpful.

I run it in my update script at the end, of course it could be potentially destructive if you both fail to read and do not maintain your slackpkg blacklist file correctly.

1 members found this post helpful.

It is suggested because it will remove any packages that Pat removes from -current. If you keep them, depending on the program, it could cause instability or prevent booting.

As long as you pay attention to the changelog and remove things when he removes them, clean-system isn't really needed.

And you can always blacklist your SBo packages (and any other common packages you install) to ensure they aren't removed when you run it. The below would prevent SBo and alien packages from being removed with clean-system.

1 members found this post helpful.

slackpkg clean-system is part of my update script (which I got from one of my LUG members).

If you have installed any SlackBuilds or any programs from sources, you should update /etc/slackpkg/blacklist accordingly and read the "to be removed" list displayed by clean-system carefully, or those programs will be removed. The blacklist file is well-annotated as to how to edit it.

I recall having only two significant update-related issues since running --Current for the past six years or so. Several years ago, on a different computer, gtkam broke (I just put the SD card from my camera into the card slot and copied pictures directly from it), more recently, Libreoffice broke, but AlienBob had a fix out in less than a week.\

(Whoops, I see BassMadrigal beat me to it. I'm off to work on my reading comprehension . . . .)

1 members found this post helpful.

Thanks for the responses. One more question.

I honestly can't remember everything I have installed from sbo, alien, slackbuilds etc. Is there a script that could export them to a list so that I could easily copy them into the blacklist.

I have added these for now Thanks.

You'll need to make sure they're each on their own line for it to work properly.

As far as finding packages, I'm not aware of any script. For my machine, I just ran slackpkg clean-system and looked through presented list (you have to ok the removal of the programs after it shows you the list). If I found any common programs (like stuff from SBo), then I would add an entry into the blacklist.

However, in case you aren't aware, you may still need to remove and/or rebuild those 3rd-party programs if they rely on something in Slackware that was updated.

1 members found this post helpful.

Umm - perhaps this thread?

1 members found this post helpful.