LinuxQuestions.org
Share your knowledge at the LQ Wiki.
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 10-31-2016, 06:36 PM   #1
TroN-0074
Senior Member
 
Registered: Dec 2011
Location: Michigan USA
Distribution: OpenSUSE 13.2 64bit-Gnome on ASUS U52F
Posts: 1,444

Rep: Reputation: 340Reputation: 340Reputation: 340Reputation: 340
upgrading to Slackware 14.2


I remember being able to upgrade over the air by switching repo from an old stable to current then jumping to the new stable. I can't find the instruction for some reason. Can somebody kindly point out were these have been placed. I will hightly appreciate it. Thank you.
 
Old 10-31-2016, 07:53 PM   #2
hitest
Guru
 
Registered: Mar 2004
Location: Canada
Distribution: Void, Slackware
Posts: 7,341

Rep: Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744
Quote:
Originally Posted by TroN-0074 View Post
I remember being able to upgrade over the air by switching repo from an old stable to current then jumping to the new stable. I can't find the instruction for some reason. Can somebody kindly point out were these have been placed. I will hightly appreciate it. Thank you.
How to upgrade to 14.2.

http://slackware.osuosl.org/slackwar...nt/UPGRADE.TXT
 
Old 10-31-2016, 08:33 PM   #3
frankbell
LQ Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 19,272
Blog Entries: 28

Rep: Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124
I tried to do an upgrade once, following the instructions in the file in the install *.iso. I botched it and ended up running Debian on that machine and did so until that machine wore out. (I do quite like Debian; it's also stable. I prefer stable.)

That's one reason I started using --Current. I can put up with the occasional glitches on --Current if it means I don't get the opportunity to botch another upgrade.

Last edited by frankbell; 10-31-2016 at 08:35 PM.
 
Old 11-01-2016, 07:39 AM   #4
TroN-0074
Senior Member
 
Registered: Dec 2011
Location: Michigan USA
Distribution: OpenSUSE 13.2 64bit-Gnome on ASUS U52F
Posts: 1,444

Original Poster
Rep: Reputation: 340Reputation: 340Reputation: 340Reputation: 340
Thank you for pointing that out, I thought there was a set of instructions from AlienBob and I had used them before. There was not require to download the ISO file and mounting the disk in the computer.

I followed the instructions on the slackdoc and I think there is something missing in there too.

I appreciate your input.

Quote:
Originally Posted by hitest View Post
 
1 members found this post helpful.
Old 11-01-2016, 09:04 AM   #5
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,792

Rep: Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656
You're probably looking for this on the SlackWiki.
 
Old 11-01-2016, 09:23 AM   #6
RadicalDreamer
Senior Member
 
Registered: Jul 2016
Location: USA
Distribution: Slackware64-Current
Posts: 1,816

Rep: Reputation: 981Reputation: 981Reputation: 981Reputation: 981Reputation: 981Reputation: 981Reputation: 981Reputation: 981
I used slackpkg to update from 14.1 to current.

I used these instructions:
https://slackalaxy.wordpress.com/201...kware-current/
http://www.linuxquestions.org/questi...5/#post4676576

Last edited by RadicalDreamer; 11-01-2016 at 09:24 AM.
 
1 members found this post helpful.
Old 11-01-2016, 09:55 AM   #7
xj25vm
Member
 
Registered: Jun 2008
Posts: 393

Rep: Reputation: 68
Quote:
Originally Posted by bassmadrigal View Post
You're probably looking for this on the SlackWiki.
I normally use the instructions from the SlackWiki as well for over-the-air upgrades. Probably best to jump only one version though - so, for example, from 14.1 I would go to 14.2, and then to -current - although you might be able to do it directly. I think the wiki doesn't mention it directly - but I go to /etc/slackpkg/mirrors - uncomment one mirror, and change the link to point to the next version of Slackware (or -current, if that's what I'm after). Then run "slackpkg update" and "slackpkg upgrade slackpkg" as per the wiki instructions.
 
Old 11-01-2016, 10:23 AM   #8
hitest
Guru
 
Registered: Mar 2004
Location: Canada
Distribution: Void, Slackware
Posts: 7,341

Rep: Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744
Quote:
Originally Posted by RadicalDreamer View Post
I used slackpkg to update from 14.1 to current.
That's the way I do it as well even though it isn't the official, recommended method to upgrade from one version to the next. I've been lucky and have not experienced any glitches using this method. That's why I recommend the official document. I've also found slackpkg to be reliable.
 
1 members found this post helpful.
Old 11-01-2016, 12:25 PM   #9
andrew.46
Senior Member
 
Registered: Oct 2007
Distribution: Slackware
Posts: 1,364

Rep: Reputation: 493Reputation: 493Reputation: 493Reputation: 493Reputation: 493
I confess that I am a big fan of a clean installation which avoids more than a few issues with upgrading. I run -current but even there I still wipe and reinstall from time to time...
 
2 members found this post helpful.
Old 11-01-2016, 02:56 PM   #10
hitest
Guru
 
Registered: Mar 2004
Location: Canada
Distribution: Void, Slackware
Posts: 7,341

Rep: Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744Reputation: 3744
Quote:
Originally Posted by andrew.46 View Post
I confess that I am a big fan of a clean installation which avoids more than a few issues with upgrading. I run -current but even there I still wipe and reinstall from time to time...
Agreed. I do that on regular basis as well. Also, if you have a separately mounted /home partition you can do a clean install on / without wiping saved stuff (documents, pictures, etc) on /home.
 
Old 11-02-2016, 07:47 AM   #11
TroN-0074
Senior Member
 
Registered: Dec 2011
Location: Michigan USA
Distribution: OpenSUSE 13.2 64bit-Gnome on ASUS U52F
Posts: 1,444

Original Poster
Rep: Reputation: 340Reputation: 340Reputation: 340Reputation: 340
I think the wiki doesn't emphasizes this step quoted here. I will try again once I get home tonight and see how that works.
Thank you.

Quote:
You will need to add a 14.2 mirror to /etc/slackpkg/mirrors
I would edit /etc/slackpkg/slackpkg.conf and set DOWNLOAD_ALL=off to on.
When you have a 14.2 mirror in place
 
Old 11-03-2016, 04:44 AM   #12
SCerovec
Senior Member
 
Registered: Oct 2006
Location: Cp6uja
Distribution: Slackware on x86 and arm
Posts: 2,470
Blog Entries: 2

Rep: Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979
Lightbulb

I have an habit developed over a lifetime long dealing with computers:
multiboot.
And the consequence is I rarely upgrade, but merely switch OS instead:
50G gaming OS
20G linux1
20G linux2
1G swap
100G home
So most of time I do a fresh install

also proper (wise?) use of slackpkg+ relives the burden of managing multilib a bit?
This implies using it for mulitlib only and not "spamming" it any further
 
Old 11-03-2016, 04:57 AM   #13
xj25vm
Member
 
Registered: Jun 2008
Posts: 393

Rep: Reputation: 68
Different people have different needs and preferences. Also, different setups have different requirements. For years I preferred the clean re-install method - but sooner or later I had to upgrade servers - and the ability to upgrade with slackpkg in the background and just do a reboot at the end - crossing fingers that everything will be fine - with minimum of downtime - is a major advantage. The beauty of open source: many ways to achieve the same goal :-)
 
3 members found this post helpful.
Old 11-04-2016, 04:47 AM   #14
SCerovec
Senior Member
 
Registered: Oct 2006
Location: Cp6uja
Distribution: Slackware on x86 and arm
Posts: 2,470
Blog Entries: 2

Rep: Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979
I concur, updating "on the fly" is a major advantage.
The way it works (and it really works) on Slackware is something I appreciate the most.
Few (most important and fragile) steps to do manually (micro management), and after that the heavy lifting is handled by the automatron (=slackpkg).
I also recommend slackpkg+ (again) for automating an multilib:
My son had an upgrade-all and lost 32bit -compat32 packages to it , had he installed the "plus" he would just never learned it "hard way"
 
  


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
[SOLVED] Upgrading Slackware 12.2 kernel - Slackware can no longer "see" ethernet card. madsovenielsen Linux - Newbie 21 07-23-2011 07:08 PM
Upgrading? : Slackware 9 to 9.1 Jalalabee Linux - Newbie 3 12-17-2003 08:32 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 02:22 PM.

Main Menu
Advertisement
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
Open Source Consulting | Domain Registration