-   Slackware (
-   -   Upgrade from 12.0 to -current (

Yalla-One 06-11-2009 03:19 PM

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,


business_kid 06-12-2009 04:04 PM

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 on the original system, and everything you compiled is likewise. In my slack 12 box (this) is a symlink to If the new system is linked against 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.

Yalla-One 06-13-2009 07:30 AM

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.


All times are GMT -5. The time now is 05:02 AM.