Thanks Pat!

Tue Oct 23 05:11:47 UTC 2018 a/kernel-generic-4.19.0-x86_64-1.txz: Upgraded. a/kernel-huge-4.19.0-x86_64-1.txz: Upgraded. a/kernel-modules-4.19.0-x86_64-1.txz: Upgraded. d/kernel-headers-4.19.0-x86-1.txz: Upgraded.

Now my Ryzen 3 will run with no problems. Awesome.

Very happy to see this!

My CPU is 9 years old, but I still approve of this. Great stuff.

Fantastic. Something is getting closer!
https://www.youtube.com/watch?v=kLBWkM0jzK0

Hey guys, I am missing something. I just run 'slackpkg' and I got downgrade to 4.4.157. I had installed 4.19. Do you upgrade version to 4.19 the one I actually removed today (Wednesday) (due to slackpkg)?

Originally Posted by igadoter Hey guys, I am missing something. I just run 'slackpkg' and I got downgrade to 4.4.157. I had installed 4.19 -so now I am scratching my head - do you upgrade version to 4.19 the one I actually removed today (due to slackpkg) ?

4.4.157 is the newest official revision for the stable branch. Seeing as slackpkg updates only the official packages, unless you have blacklisted kernel upgrades, it will update whatever kernel you have to 4.4.157. 14.2 runs 4.4.xxx, so it will never update to 4.19.

If you wanted to go back to 4.19, you would have to blacklist the kernel packages in /etc/slackpkg/blacklist and then reinstall. However, I don't know if stepping out of the 4.4 series is recommended in stable, I would imagine not.

EDIT: this is somewhat off topic, isn't it. Better to put this in the kernel thread.

Originally Posted by igadoter Hey guys, I am missing something. I just run 'slackpkg' and I got downgrade to 4.4.157. I had installed 4.19 -so now I am scratching my head - do you upgrade version to 4.19 the one I actually removed today (due to slackpkg) ?

slackpkg will always try to 'upgrade' packages to the latest ones available for your Slackware version, even if it's really a downgrade. 4.4.157 is the latest kernel for 14.2, so that's why slackpkg is trying to upgrade to that. You need to put 'kernel' in /etc/slackpkg/blacklist to avoid that.

Edit: too slow.

Thanks @Lysander666 I feel little stupid. Then what should I use to upgrade Slackware-current? Rsynced with @AlienBob script and use upgradepkg?

Edit: I am master of obvious. So I answered the question myself. I think it is just safe and more convenient to rsync Slackware-current (local mirror) than to play with slackpkg blacklist. It seems for me now that 'slackpkg' is good system tool for stable version.

Originally Posted by igadoter Thanks @Lysander666 I feel little stupid. Then what should I use to upgrade Slackware-current? Rsynced with @AlienBob script and use upgradepkg?

No need to feel stupid, it's all a learning process and, I feel, one cannot be stupid if one is running Slackware.

In response to your question, someone else would have to help with that since I don't run -current.

My mistake. In mirrors file I pick one pointing to stable release.

Originally Posted by igadoter My mistake. In mirrors file I pick one pointing to stable release.

No worries, just point to a -current mirror, then

# slackpkg update gpg
# slackpkg update
# slackpkg upgrade-all
# slackpkg install-new
# slackpkg clean-system

If something you installed from SlackBuilds doesnt work anymore, recompile and it should be fine

Thanks @giomat. I did as you suggested. Now kernel is regraded(?). I decided however that default way slackpkg is working is not safe. At least for me. Because already I have local mirror of current then I decided to put this mirror as default. Via ftp://localhost. More convenient would be something like that file://'repository' pointing to directory.

Originally Posted by igadoter Hey guys, I am missing something. I just run 'slackpkg' and I got downgrade to 4.4.157. I had installed 4.19. Do you upgrade version to 4.19 the one I actually removed today (Wednesday) (due to slackpkg)?

One can always use one of these images to install from:
https://slackware.nl/slackware-live/latest/


I am of the nuke and pave camp between stable releases. It does not matter so much these days, you can switch to -current pretty flawless as -current is generally more stable than Debian Stable presently. More up to date too.


When Alien Bob regenerates the next Plasma5 ISO switching back as the 4.19 kernel will be included to help test on the Ryzen.

Ok guys I did it. Now 'slackpkg' is running on localhost - on my local mirror of -current. With some excludes - say sources etc. It is my private mirror. So I setup ftp server - local mirror is on another partition than root. So essentially in mirrors file for 'slackpkg' is

ftp://localhost/pub/Linux/Slackware/slackware64-current

at the end of file. Now no way slackpkg would go wild cause there is no other versions being mirrored! I put @AlienBob script in crontab. For 'slackpkg' I will make script to send mail to myself (not root) about new updates - if there are new updates. Few hours of work - mostly troubles configuring proftpd.

Originally Posted by igadoter Ok guys I did it. Now 'slackpkg' is running on localhost - on my local mirror of -current. With some excludes - say sources etc. It is my private mirror. So I setup ftp server - local mirror is on another partition than root. So essentially in mirrors file for 'slackpkg' is ftp://localhost/pub/Linux/Slackware/slackware64-current at the end of file. Now no way slackpkg would go wild cause there is no other versions being mirrored! I put @AlienBob script in crontab. For 'slackpkg' I will make script to send mail to myself (not root) about new updates - if there are new updates. Few hours of work - mostly troubles configuring proftpd.

You can use a local folder without setting up a ftp/http server by using the file:// designator. You would start with the root directory, so in my root directory, I have a share folder with additional folders under there. Mine is set up as:

file://share/slackware-mirrors/slackware64-14.2/