Share your knowledge at the LQ Wiki.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 06-25-2019, 03:24 AM   #16
LQ Guru
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 6,046

Rep: Reputation: Disabled

I already linked this above but I just link it again here
Old 06-25-2019, 10:17 AM   #17
Senior Member
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 1,785

Rep: Reputation: 743Reputation: 743Reputation: 743Reputation: 743Reputation: 743Reputation: 743Reputation: 743
How to keep a fresh slackware-current installation up to date?

This is how I do it. I use slackpkg with slackpkg+. From this point on any reference to slackpkg implies with slackpkg+

My setup.

I have local mirrors of Slackware64-current, ktown and multilib and a local repository (nonslack) for my packages.

The Slackware64-current mirror is kept up to date using Alien Bob's via a daily cron job. The ktown and multilib mirrors are updated manually via a bash script that rsync's the parts I want. I have a few of Alien Bob's packages installed. I have slackpkg+ configured to use Alien Bob's and slackpkg+'s online repository, and to use my local nonslack, ktown and multilib mirrors.

Running 'slackpkg update' will update the database. Since slackware64-current is a daily cron job and I have no control over updates to Alien Bob or slackpkg+ packages any updates will be included when running 'slackpkg upgrade-all'.

With my own repository. I use a script by Alien Bob called which generates the files needed for slackpkg. If I have added, rebuilt, upgraded or removed any of my nonslack packages then I need to run this script before running slackpkg for the changes to be picked up.

With multilib and ktown I have to manually run my scripts to update those mirrors before changes will be picked up by slackpkg from the last run. Why manually and not a cron job? I want more control over when to upgrade. It's not much to run my update.multilib script just before running 'slackpkg upadate'. As for ktown, unless there are some small maintenance updates I prefer to upgrade as outlined in the ktown README. I have a script that take care of that. If this was a cron job I would get a boat load of ktown packages wanting to be upgraded after running 'slackpkg update' 'slackpkg upgrade-all' when I'm not really ready yet.

My basic steps (almost daily based on slackware64-current updates and I am a few days behind right now) are:

bash (if needed)
bash (if needed)
bash (only if minor updates)
slackpkg update
slackpkg install-new (if needed)
slackpkg install ktown (if needed)
slackpkg install mulilib (if needed)
slackpkg install nonslack (if needed)
slackpkg upgrade-all (this includes slackware64-current, ktown, multilib, nonslack, alienbob and slackpkg+)
slackpkg clean-system (if needed)

If Eric has updated ktown to a next release. I do this after doing above. I do not use slackpkg.
bash (syncs)
bash (does the upgrade per the README)

If there has been a kernel update.
Usage note: I keep two kernels installed, LastWorking (4.19.50) and Slackware64 (4.19.51)
lilo.conf snippet
# Slackware64
image = /boot/vmlinuz
  initrd = /boot/initrd.gz
  label = Slackware64
# Working kernel
image = /boot/vmlinuz-working
  initrd = /boot/initrd-working.gz
  label = LastWorking
cd /boot
run 'removepkg /var/lib/pkgtools/packages/kernel*-4.19.50-*'
set the LastWorking symlinks to 4.19.51
edit /etc/slackpkg/blacklist to comment out kernel-generic, kernel-modules, kernel-source
run 'slackpkg download kernel-generic, kernel-modules, kernel-source'
edit /etc/slackpkg/blacklist to delete the "#" and blacklist them again.
run 'installpkg /var/cache/packages/slackware64/*/*.txz'
run 'rm /var/cache/packages/slackware64/*/*'
mkinitrd -F -k 4.19.55
mkinitrd -F -k 4.19.51 -s initrd-working-tree -o initrd-working.gz

If needed I will reinstall my NVIDIA graphics driver.
bash -k 4.19.55

Then reboot.

I don't do all of this every day. Right now the last slackware64-current update applied on my main system is Mon Jun 17 03:26:28 UTC 2019 latest in my local mirror is Mon Jun 24 18:47:52 UTC 2019. I am in the process of upgrading several packages in my repository as time permits. Perhaps tomorrow I will do an update.

Last edited by chrisretusn; 06-25-2019 at 10:28 AM.
2 members found this post helpful.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Unable to subtract current date and future date in YYYY-MM-DD format archie7 Linux - Newbie 11 05-11-2018 03:29 AM
[SOLVED] [Slackware 64-current] Fresh installation with KDE5 stucks when open the "Leave" tab Francexi Slackware 1 09-14-2015 09:09 AM
Best way to keep Slackware 14.1 current upto date with the latest packages Quicken2k Slackware 10 11-10-2014 09:22 AM
[SOLVED] BASH: Keep original mod date of a file and 'date' it back to same file? SilversleevesX Programming 4 07-16-2010 11:12 AM
current date - yesterday's date newbie_adm Linux - Newbie 4 09-04-2006 03:56 PM > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 01:26 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration