LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
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 06-11-2009, 02:19 PM   #1
Yalla-One
Member
 
Registered: Oct 2004
Location: Norway
Distribution: Slackware, CentOS
Posts: 635

Rep: Reputation: 35
Upgrade from 12.0 to -current


Finally time to upgrade some of the lesser used machines, but which has services upon which we're highly dependent.

I'm intimately familiar with -current, and run it on identical hardware to the machine in question.

However, just as a last resolve - any possible pitfalls going from something as old as 12.0 to -current without stepping into 12.1 and 12.2 in between as long as I do it in singleuser and do the libraries and pkgtools first as suggested by upgrade.txt, and then remove all packages that have been removed since then?

thanks in advance,

-y1
 
Old 06-12-2009, 03:04 PM   #2
business_kid
Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 6,187

Rep: Reputation: 530Reputation: 530Reputation: 530Reputation: 530Reputation: 530Reputation: 530
If you do it blind, YMMV. Mine did attempting similar things. I grew to distrust the upgrade option.

After a linuxfromscratch, I had a much better understanding. The real issue is that your toolchain consiste so: gcc; Kernel headers; & libc, usually glibc. Every binary is linked against libc.so.6 on the original system, and everything you compiled is likewise. In my slack 12 box (this) libc.so.6 is a symlink to libc-2.5.so. If the new system is linked against libc-2.6.so there might be big issues with anything you didn't upgrade. Likewise, compile errors have been traced to a mismatch of tools (wrong version of gcc or kernel headers).

So try it. The dodgy parts would be things like gnome, SDL, or k3b which utilise an awful lot of external libs. Straight GNU console stuff should be fine, unless your present versions are all compiled on the box.
 
Old 06-13-2009, 06:30 AM   #3
Yalla-One
Member
 
Registered: Oct 2004
Location: Norway
Distribution: Slackware, CentOS
Posts: 635

Original Poster
Rep: Reputation: 35
Thanks for answering.

I trusted the pkgtools and did a slow conversion with upgradepkg of the glibc and pkgtools first, then added xz and then did a crude slackware/*/*.t?z at the end, not rebooting inbetween. Got the new kernel installed, removed all packages removed since then and an upgradepkg --reinstall of those that were changed (probably not necessary), and it works like a charm.

-y1
 
  


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
DISCUSSION: Upgrade to Slackware -current without a -current CD truthfatal LinuxAnswers Discussion 0 09-19-2006 01:42 PM
How to upgrade from Slackware 10.1 to current? Basel Slackware 21 07-18-2005 07:00 AM
What first upgrade kernel or upgrade slack 10.0 to current Kelean Slackware 7 01-16-2005 06:54 PM
I need to upgrade my current Kernel xmdms Linux - Software 2 05-06-2004 04:58 PM
Is there a way to upgrade to current? trey85stang Debian 9 04-10-2004 10:43 PM


All times are GMT -5. The time now is 12:13 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