LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

View Poll Results: How are people keeping Slackware up to date
Slackpkg 92 74.80%
Slackroll 2 1.63%
Slapt-get 2 1.63%
Swaret 0 0%
Local mirror 11 8.94%
Your own update script 11 8.94%
Other 5 4.07%
Voters: 123. You may not vote on this poll

Reply
 
Search this Thread
Old 03-31-2013, 03:13 PM   #1
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,812

Rep: Reputation: 817Reputation: 817Reputation: 817Reputation: 817Reputation: 817Reputation: 817Reputation: 817
How are people keeping Slackware up to date


I suspect most people use slackpkg but I am curious if any of the regulars here do anything else. I know from this thread that Lufbery and H_TeXMeX_H do (or did) use their own scripts and of course there are plenty of other options, e.g. a local mirror (+upgradepkg), slackroll, slapt-get, swaret, etc.

I was using slackpkg but since I tend to stick with stable (only switching to -current around the first RC stage) I realised that I didn't really need its full range of features so I also wrote my own update script. Not because it was needed but just to see what it would involve.

P.S. My script basically mirrors the patches directory but only for packages I have installed and not blacklisted, checking the md5sums and signatures. Nothing else but then that is all I need.
 
Old 03-31-2013, 03:22 PM   #2
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,428

Rep: Reputation: 867Reputation: 867Reputation: 867Reputation: 867Reputation: 867Reputation: 867Reputation: 867
I use slackpkg with a local mirror mounted via nfs (with a line cdrom://slackware/slackware64-current/ in /etc/slackpkg/mirrors).
 
Old 03-31-2013, 03:28 PM   #3
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Main: Gentoo Others: What fits the task
Posts: 15,530
Blog Entries: 2

Rep: Reputation: 4024Reputation: 4024Reputation: 4024Reputation: 4024Reputation: 4024Reputation: 4024Reputation: 4024Reputation: 4024Reputation: 4024Reputation: 4024Reputation: 4024
slackpkg with a local mirror (serving the files using apache) for both, my stable and my -current systems.
 
Old 03-31-2013, 03:34 PM   #4
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,812

Original Poster
Rep: Reputation: 817Reputation: 817Reputation: 817Reputation: 817Reputation: 817Reputation: 817Reputation: 817
Hmm ... ponce and TobiSGD, It seems I should have also provided a combined slackpkg+local mirror option. Ah well, these polls are never perfect.
 
Old 03-31-2013, 04:22 PM   #5
mina86
Member
 
Registered: Aug 2008
Distribution: Slackware
Posts: 357

Rep: Reputation: 148Reputation: 148
I have the following run daily from crontab:
Code:
#!/bin/sh

OPTIONS="-arvzmh --stats --progress --delete-after"

__ARG=$1
shift

for ARG in $__ARG; do
	# [slack[ware]]64 -> 64, slackware -> slack
	case "$ARG" in
	slack64*|slackware64*) ARG=64${ARG#*64};;
	slackware*)            ARG=slack${ARG#slackware}
	esac

	case "$ARG" in
	slack)           DIST=  ; VER=current  ;;
	slack-[1-9]*.?*) DIST=  ; VER=${ARG#*-};;
	64)              DIST=64; VER=current  ;;
	64-[1-9]*.?*)    DIST=64; VER=${ARG#*-};;
	[1-9]*.?*)
		case `uname -m` in
		i?86|x86)   DIST=  ;;
		x86_64|x64) DIST=64;;
		*)
			cat <<EOF >&2
${0##/*}: unable to guess architecture
${0##/*}: 'uname -m' returned: `uname -m`
EOF
			exit 2
		esac
		VER=$ARG     ;;
	*)
		cat <<EOF >&2
usage: $0 ( [<dist>-]<ver> | <dist> ) [<switches>]
   eg: $0 slack-13.37
<dist> is  slack[ware][64] or 64  (default depends on 'uname -m')
<ver>  is  current or ##.#        (default is current)
<switches> are passed to rsync directly
EOF
		exit 1
	esac

	MIRROR=rsync.slackware.at
	SOURCE=rsync://$MIRROR/slackware/slackware$DIST-$VER/
	DEST=/data/slack/${DIST:-32}-$VER

	echo rsync $OPTIONS -f._- "$@" "$SOURCE" "$DEST" '<<EOF'
	rsync $OPTIONS -f._- "$@" "$SOURCE" "$DEST" <<EOF
- *.asc
- /slackware$DIST/kde
- /slackware$DIST/kdei
- /slackware$DIST/xfce
- /slackware$DIST/f
- /slackware$DIST/k
- /slackware$DIST/e
- /slackware$DIST/t
- /slackware$DIST/y
- /testing/
- /usb-and-pxe-installers/
- /source/
- /pasture/
- /isolinux/
- /usb-and-pxe-installers/
+ /extra/aspell-word-lists
+ /extra/aspell-word-lists/aspell-pl-*
- /extra/aspell-word-lists/aspell-*
- /extra/*
- /kernels/
EOF
done
And than, every now and than, upgradepkg /data/slack/64-current/slackware64/*/*.t?z. Occasionally I also look at upgrading instructions to figure out removed packages.
 
Old 03-31-2013, 04:40 PM   #6
fskmh
Member
 
Registered: Jun 2002
Location: South Africa
Distribution: Slackware64-current multilib
Posts: 235

Rep: Reputation: 55
rsync + own script
 
Old 03-31-2013, 04:48 PM   #7
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,970

Rep: Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848
slackpkg with a local repository which is updated with my own rsync-script.

Markus
 
Old 03-31-2013, 04:52 PM   #8
wroom
Member
 
Registered: Dec 2009
Location: Sweden
Posts: 91

Rep: Reputation: 24
Personally i tend to use slackware where i need a linuxbox to work in a known state without errors not bothering me for year after another.

It is easy to get a full slackware install with 95% of what i need installed once. And merely having to add some few custom packages, and then do my configuration.

And seldom i have to do updates because of vulnerabilities or need of new functionality. Slackware has been a workhorse that once installed and tested, it just runs and runs...

If something really need updating i will do it manually from a local verified package repository.
 
Old 03-31-2013, 04:58 PM   #9
GazL
Senior Member
 
Registered: May 2008
Posts: 3,367

Rep: Reputation: 904Reputation: 904Reputation: 904Reputation: 904Reputation: 904Reputation: 904Reputation: 904Reputation: 904
I keep a full mirror of current using rsync and then have a script that will identify differences between what is installed and what is available from the mirror plus any other local package sources I specify. The output of that script can then be used with upgradepkg, installpkg, removepkg as needed. The slacklist script only lists differences to stdout, it takes no actions itself.

I normally have 3 package trees stored locally:
  1. 'patches' - packages that replace stock packages
  2. slackware64-current - which s my local mirror
  3. 'extras' packages that are additions - from slackbuilds or elsewhere (these are my extras not "slackware64-current/extra", though I could add that one to the list if I wanted)
Should I need to I can simply add additional package sources, e.g. if i were testing a new version of xfce, I might add a new /local/slackware/xfce directory to the beginning rather than dump it all in with the rest of my stuff in 'patches'.


Here's an example with my usual PKGPATH
Code:
gazl@ws1:~$ PKGPATH="/local/slackware/patches/packages/:/local/slackware/slackware64-current/slackware64:/local/slackware/extras/packages"
gazl@ws1:~$ export PKGPATH
gazl@ws1:~$ /usr/local/sbin/slacklist install
/local/slackware/slackware64-current/slackware64/a/kernel-generic-3.8.4-x86_64-1.txz
/local/slackware/slackware64-current/slackware64/a/kernel-huge-3.8.4-x86_64-1.txz
/local/slackware/slackware64-current/slackware64/a/kernel-modules-3.8.4-x86_64-1.txz
/local/slackware/slackware64-current/slackware64/k/kernel-source-3.8.4-noarch-1.txz
gazl@ws1:~$ /usr/local/sbin/slacklist upgrade
gazl@ws1:~$ /usr/local/sbin/slacklist remove 
gazl@ws1:~$
I haven't installed the stock kernel packages which is why they are showing up in the results of the install option.


By changing the PKGPATH I can get different results. i.e. by removing extras or patches from the PKGPATH I can easily see what I've changed or switch back
to a stock install

Here's an example with just current and extras.
Code:
gazl@ws1:~$ PKGPATH="/local/slackware/slackware64-current/slackware64:/local/slackware/extras/packages"
gazl@ws1:~$ /usr/local/sbin/slacklist install
/local/slackware/slackware64-current/slackware64/a/kernel-generic-3.8.4-x86_64-1.txz
/local/slackware/slackware64-current/slackware64/a/kernel-huge-3.8.4-x86_64-1.txz
/local/slackware/slackware64-current/slackware64/a/kernel-modules-3.8.4-x86_64-1.txz
/local/slackware/slackware64-current/slackware64/k/kernel-source-3.8.4-noarch-1.txz
gazl@ws1:~$ /usr/local/sbin/slacklist upgrade
/local/slackware/slackware64-current/slackware64/xap/MPlayer-1.1_20120701-x86_64-2.txz
/local/slackware/slackware64-current/slackware64/a/sed-4.2.1-x86_64-1.txz
/local/slackware/slackware64-current/slackware64/a/shadow-4.1.4.3-x86_64-9.txz
gazl@ws1:~$ /usr/local/sbin/slacklist remove 
gazl@ws1:~$
In this case slacklist can still see that the kernel packages aren't installed, but for 'upgrade' it can see that the installed packages for MPlayer, sed and shadow are different versions to the ones found in the package sources in PKGPATH and so it lists them as possible updates. Just like upgradepkg it doesn't care what is older or newer, only what is installed and what is available.


And if I also drop the 'extras' directory I can effectively do a 'clean' of my system.
Code:
gazl@ws1:~$ PKGPATH="/local/slackware/slackware64-current/slackware64"
gazl@ws1:~$ /usr/local/sbin/slacklist install
/local/slackware/slackware64-current/slackware64/a/kernel-generic-3.8.4-x86_64-1.txz
/local/slackware/slackware64-current/slackware64/a/kernel-huge-3.8.4-x86_64-1.txz
/local/slackware/slackware64-current/slackware64/a/kernel-modules-3.8.4-x86_64-1.txz
/local/slackware/slackware64-current/slackware64/k/kernel-source-3.8.4-noarch-1.txz
gazl@ws1:~$ /usr/local/sbin/slacklist upgrade
/local/slackware/slackware64-current/slackware64/xap/MPlayer-1.1_20120701-x86_64-2.txz
/local/slackware/slackware64-current/slackware64/a/sed-4.2.1-x86_64-1.txz
/local/slackware/slackware64-current/slackware64/a/shadow-4.1.4.3-x86_64-9.txz
gazl@ws1:~$ /usr/local/sbin/slacklist remove 
dmenu-4.5.gazl1-x86_64-1_local
dvdauthor-0.7.1-x86_64-1_local
dwm-6.0.gazl5-x86_64-1_local
easytag-2.1.7-x86_64-1_local
faac-1.28-x86_64-3_local
faad2-2.7-x86_64-3_local
ffmpeg-git_20130330-x86_64-1_local
gtk-engines-2.20.2-x86_64-1_local
id3lib-3.8.3-x86_64-1_local
kernel-3.8.5-custom-none-x86_64-1_local
lame-3.99.5-x86_64-1_local
libdvdcss-1.2.12-x86_64-1_local
libmp4v2-1.9.1-x86_64-1_local
libvpx-1.1.0-x86_64-1_local
mame-0.146-x86_64-4_local
mame-data-0.146-noarch-2_local
opera-12.14.1738-x86_64-1_local
unrar-4.0.7-x86_64-1_SBo
vobcopy-1.2.0-x86_64-1_local
x264-0.130.2274-x86_64-1_local
xvidcore-1.3.2-x86_64-1_local
This time 'remove' returns some results as it has found packages that are installed, but which have no .t?z available in the configured package sources.


The PKGPATH approach is quite flexible. Instead of pointing it at the whole of slackware64-current/slackware64, you can point it to one or more individual package-sets if you wanted to only include certain sets:
e.g.
Code:
gazl@ws1:~$ PKGPATH="/local/slackware/slackware64-current/slackware64/xap"
gazl@ws1:~$ /usr/local/sbin/slacklist upgrade
/local/slackware/slackware64-current/slackware64/xap/MPlayer-1.1_20120701-x86_64-2.txz
In the case above remove wouldn't really make sense as it would decimate your system, but 'install' could be used to install any missing packages from xap, and 'upgrade' could be used to do an upgrade operation limited to only a single package-set.

There is also a 'reinstall' option which works exactly the same as upgrade but lists the available package file regardless of whether the installed version is different or not.


Anyway, I think that gives you a flavour of how it all works.

Last edited by GazL; 03-31-2013 at 05:27 PM.
 
Old 03-31-2013, 05:18 PM   #10
tux_dude
Member
 
Registered: Dec 2008
Distribution: Slackware64 Current
Posts: 226

Rep: Reputation: 33
What do you choose if using slackpkg with local mirror? I'm using Alien's mirror script.
 
Old 03-31-2013, 05:24 PM   #11
afreitascs
Member
 
Registered: Aug 2004
Location: Brasil
Distribution: Slackware_Cur-64_mult
Posts: 432

Rep: Reputation: 30
I voted for slackpkg, simple as slackware

I use the script for the Alien "mirror-slackware-current.sh" . So I download all of the updated files current. After slackpkg I use to update my system ...

So when a new version of slackware is released, I can burn to a DVD media as well.

Last edited by afreitascs; 03-31-2013 at 10:06 PM.
 
Old 03-31-2013, 05:38 PM   #12
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,169

Rep: Reputation: 1013Reputation: 1013Reputation: 1013Reputation: 1013Reputation: 1013Reputation: 1013Reputation: 1013Reputation: 1013
I voted other, but: a local mirror rsync'ed on my laptop's hard disk, then slackpkg update && slackpkg upgrade-all.

This is for Slackware-14.0.

EDIT after reading mails from root@slackware

Last edited by Didier Spaier; 04-01-2013 at 01:10 AM.
 
Old 03-31-2013, 05:49 PM   #13
Jeebizz
Senior Member
 
Registered: May 2004
Distribution: Slackware 14.1 64-bit with multilib
Posts: 2,074

Rep: Reputation: 199Reputation: 199
Other - I just keep up with security updates via emails from slackware.com.
 
Old 03-31-2013, 05:53 PM   #14
jtsn
Member
 
Registered: Sep 2011
Location: Europe
Distribution: Slackware
Posts: 803

Rep: Reputation: 354Reputation: 354Reputation: 354Reputation: 354
I use slackpkg with a rsync'ed local mirror exported via NFS.
 
Old 03-31-2013, 07:05 PM   #15
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,407

Rep: Reputation: 830Reputation: 830Reputation: 830Reputation: 830Reputation: 830Reputation: 830Reputation: 830
I use Slackpkg with 'DELALL=off' in /etc/slackpkg/slackpkg.conf. After an upgrade I then do 'mv /var/cache/packages /var/cache/packages<date>'. This maintains an archive of older packages so that I can easily revert if required.
 
  


Reply


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
A great method for keeping Slackware up-to-date...without slackpkg. Lufbery Slackware 80 06-23-2010 08:27 PM
Keeping Slackware Up-to-date Bash Rules Slackware 22 09-08-2009 10:20 PM
Keeping Slackware 12.1 up to date. glore2002 Slackware 10 06-18-2008 09:58 AM
keeping slackware 11 up-to date ronty Slackware 6 01-20-2007 08:14 AM
Keeping Slackware Up-To-Date introuble Slackware 4 03-21-2006 08:08 AM


All times are GMT -5. The time now is 06:42 AM.

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