LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 08-27-2012, 06:21 AM   #16
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,842

Rep: Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850

Quote:
Originally Posted by honeybadger View Post
I was hoping to wait some time longer with 13.37 (hear me out before you stone me) because I am at home with 13.37 (honestly wished 14 came out a bit more later).
You could just hold off on upgrading until a time that suites you better. You are not forced to upgrade to 14 the moment it comes out. 13.37 will likely be supported for quite some time if the history of support for other old Slackware releases is a reliable indicator. Slackware 12.1 is still supported and it was released in the first half of 2008.
 
Old 08-27-2012, 09:11 AM   #17
Mark Pettit
Member
 
Registered: Dec 2008
Location: Cape Town, South Africa
Distribution: Slackware 14.1 64 Multi-Lib
Posts: 429

Rep: Reputation: 124Reputation: 124
My laptop is where I do most of my work - and downtime there costs me. Every new release of Slackware I go out and buy a brand new 2.5" drive (usually higher capacity if I can) and then re-install from scratch. I takes me a few days, and I end up swapping around the 2 disks until I'm satisfied the new matches and exceeds the old. Then the old becomes a multimedia drive :-) The point of replacing the drive of course is to never have a disk crash. Sure, that's not a guarantee, but I've never had one on a laptop, whereas I've had quite a few on servers - especially when the disks start hitting 3 or 4 years old.

This time around, due to some stupid things I did on my server (involving a crashed disk, use of 'root' when I ought not to have) I went out and bought a small (60GB) SSD drive, which I'll use just for the O/S (excluding /var, /tmp). So I'll be doing a brand new install there. My home server (multimedia, internet gateway, backups of laptops) generally goes a few years on 1 release. It will be nice to have both my laptop and home server on the same release (for a year anyway).
 
1 members found this post helpful.
Old 08-27-2012, 11:10 AM   #18
Lufbery
Senior Member
 
Registered: Aug 2006
Location: Harrisburg, PA
Distribution: Slackware 64 14.0
Posts: 1,142
Blog Entries: 29

Rep: Reputation: 119Reputation: 119
Quote:
Originally Posted by tronayne View Post

I noticed a long time ago that during Slackware installation, when you're adding drive partitions, you have a choice of formatting or not formatting individual partitions. Hmm. So, /root gets formatted but none of the rest of them do -- so, they're just sitting there with all their data intact when the system boots when setup is finished.
Exactly! That's what I meant in my post above where I wrote about having /home and /root on separate partitions. I also now have /boot on a separate partition because I dual boot LFS and Slackware.

On a clean installation, I typically only format the / partition, which (of course) does not have /home, /root, or /boot.

Regards,
 
Old 08-28-2012, 12:15 AM   #19
D1ver
Member
 
Registered: Jan 2010
Distribution: Slackware 13.37
Posts: 527
Blog Entries: 3

Rep: Reputation: 126Reputation: 126
Regarding packages installed from sbopkg or Slackbuilds.org, is it best to just use 'slackpkg clean-system' to remove everything and then install everything again once a slackbuilds 14.0 repo goes up? Or is there a way to automatically rebuild everything from SBO?
 
Old 08-28-2012, 02:52 AM   #20
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,842

Rep: Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850
Quote:
Originally Posted by D1ver View Post
Or is there a way to automatically rebuild everything from SBO?
If you kept a list of everything you installed from SBo, in the order you installed it, you could use this as a queue file to rebuild everything.

If you didn't do this it might still be possible to recreate such a list, with a little effort.

If you installed all of your SBo packages once and have never upgraded them then "/var/log/packages" alone can provide you with a nice sorted list based on when they were installed, which you could use as a queue file, e.g. try something like this:

Code:
$ ls -tr /var/log/packages | sed -nr 's#^([[:graph:]]+)(-[[:alnum:]\.\+_]+){3}SBo#\1#p'
If however you have been upgrading SBo packages from time to time (most likely), it gets a little more complex. The above might still work but because the upgraded packages will be out of sync in the list, there is a fair chance they will appear after one of more of their build dependencies causing a build failure. To get an idea of how big a problem this could be for you, try creating a list of the SBo packages that have been upgraded at some point in time, like so:

Code:
$ ls --full-time -tr /var/log/removed_packages | sed -nr 's#.* ([0-9]{4}-[0-9]{2}-[0-9]{2}) ([0-9]{2}:[0-9]{2}:[0-9]{2})\..* ([[:graph:]]+)(-[[:alnum:]\.\+_]+){3}SBo-upgraded-(.*)#Installed: \1,\2\tUpgraded: \5\t\3#p'
If this list is fairly small, you might get away with using your original list or perhaps you could use the new one to give you some clues about what to shift around in the build order of the original list. If it is fairly long however you will probably need some help to fix the build order. In which case the following steps should give you a rough list:

Code:
$ ls --full-time -tr /var/log/packages | sed -nr 's#.* ([0-9]{4}-[0-9]{2}-[0-9]{2}) ([0-9]{2}:[0-9]{2}:[0-9]{2})\..* ([[:graph:]]+)(-[[:alnum:]\.\+_]+){3}SBo#\1,\2\t\3#p' > /tmp/SBo-install-times
$ ls --full-time -tr /var/log/removed_packages | sed -nr 's#.* ([0-9]{4}-[0-9]{2}-[0-9]{2}) ([0-9]{2}:[0-9]{2}:[0-9]{2})\..* ([[:graph:]]+)(-[[:alnum:]\.\+_]+){3}SBo-upgraded.*#\1,\2\t\3#p' >> /tmp/SBo-install-times
$ sort /tmp/SBo-install-times | sed "s,.*\t,," > /tmp/SBo-install-order-with-dupes
The final output file (/tmp/SBo-install-order-with-dupes) shows the actual install order but packages that have been upgraded will be listed multiple times (once for each install/upgrade). You will need to edit this list and remove all but the first reference to each package before you can use it as a queue file, otherwise you will end up building some of your packages more than once.

Last edited by ruario; 08-28-2012 at 03:42 AM. Reason: Simplified the commands and explanation slightly
 
Old 08-28-2012, 03:04 AM   #21
D1ver
Member
 
Registered: Jan 2010
Distribution: Slackware 13.37
Posts: 527
Blog Entries: 3

Rep: Reputation: 126Reputation: 126
Thanks, that pretty much answers my question

One of these days I'm going to have to learn the black magic involved with grep, sed and awk..
 
Old 08-28-2012, 03:28 AM   #22
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,842

Rep: Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850
@D1ver: I have found the FSF/GNU online manuals for grep, awk and sed to be pretty good. For example the sed overview of regular expression syntax is pretty through without being overly long.

As an off-topic side note, the fact that you can do stuff like (re)create an SBo queue file using standard UNIX utils demonstrates the beauty and simplicity of the Slackware packaging system. It doesn't try to do too much itself and instead leverages the power of everything already present in a UNIX-like system. It shows that well organised text logs are enough. This also demonstrates to those who are ignorant of how Slackware works that it has a complete package management solution. I don't remember how many times I have read "Slackware lacks a package manager" but it continues to piss me off.
 
Old 08-28-2012, 04:04 AM   #23
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,842

Rep: Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850
Quote:
Originally Posted by ruario View Post
The final output file (/tmp/SBo-install-order-with-dupes) shows the actual install order but packages that have been upgraded will be listed multiple times (once for each install/upgrade). You will need to edit this list and remove all but the first reference to each package before you can use it as a queue file, otherwise you will end up building some of your packages more than once.
This will help you find the packages that are listed more than once:

Code:
$ sort /tmp/SBo-install-order-with-dupes
(Just look out for duplicate lines!)

EDIT: I have realised however that this isn't perfect because the method listed in my earlier post could have included stuff that was upgraded and later uninstalled. The best way to deal with those problems would be to recreate the list of currently installed SBo packages:

Code:
$ ls -tr /var/log/packages | sed -nr 's#^([[:graph:]]+)(-[[:alnum:]\.\+_]+){3}SBo#\1#p' > /tmp/SBo-list
Then use this list to find the dupes within /tmp/SBo-install-order-with-dupes, e.g.:

Code:
$ while read p; do printf "$p:" ;grep -xcF "$p" /tmp/SBo-install-order-with-dupes; done < /tmp/SBo-list | grep -v ':1$'
Afterwards, you can also use /tmp/SBo-list again to check for packages that shouldn't be listed in /tmp/SBo-install-order-with-dupes at all (because you removed them at some later stage):

Code:
$ grep -vxFf /tmp/SBo-list /tmp/SBo-install-order-with-dupes
Once you have finished manually editing /tmp/SBo-install-order-with-dupes to remove duplicate entries or packages you don't want, you could do the following to rebuild and reinstall your current selection of SBo packages:

Code:
# mv /tmp/SBo-install-order-with-dupes /var/lib/sbopkg/queues/mypackages.sqf 
# sbopkg -i mypackages

Last edited by ruario; 08-28-2012 at 10:05 AM. Reason: rewrote examples and explanation again
 
Old 08-28-2012, 10:22 PM   #24
shadowsnipes
Senior Member
 
Registered: Sep 2005
Distribution: Slackware
Posts: 1,441

Rep: Reputation: 70
Quote:
Originally Posted by D1ver View Post
Regarding packages installed from sbopkg or Slackbuilds.org, is it best to just use 'slackpkg clean-system' to remove everything and then install everything again once a slackbuilds 14.0 repo goes up? Or is there a way to automatically rebuild everything from SBO?
Unless I want to remove all of the SBo packages in order to have a "clean system" for testing software against the vanilla Slackware package set, I usually don't remove them...unless I don't use them anymore.

Part of the reason I like Slackware is that I can setup a super-stable custom linux install quickly and not worry about updating software all the time. I just do security updates mostly.

So this is what I usually follow:
  • If it's broken, rebuild, upgrade, or remove
  • If it's not broken, then don't fix (rebuild) it
  • That being said, I typically take the major Slackware upgrades as an opportunity to upgrade any SBo packages that have an updated version (particularly if the newer version has wanted features and/or better stability).

Oh, and for an easy way to add your currently installed SBo packages to a queuefile, use sbopkg to create it. Go to the queue menu -> Add installed sbo packages to queue. It will ignore any SBo packages that aren't in the repo you are using when creating the queue.
 
  


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
Upgrade and dist-upgrade problem reinstall aMule end packare libupnp6 anunix Debian 2 05-12-2012 01:36 PM
Upgrade and dist-upgrade problem reinstall aMule end packare libupnp6 anunix Debian 1 05-12-2012 09:06 AM
How to upgrade kernel in rhel6/centos6 with internet. manually download and upgrade. Gil@LQ Linux - Kernel 3 03-12-2012 05:07 PM
Partial Upgrade of BIG NEW KDE UPGRADE (debsig-verify related?) linuxStudent11 Debian 1 04-27-2011 12:29 PM
Will 'aptitude upgrade or dist-upgrade' downgrade manually installed deb package? Akhran Debian 3 03-14-2006 02:40 PM


All times are GMT -5. The time now is 07:33 PM.

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