Upgrading from Slackware 10.2 to 12

dave`2005 · 11-04-2007, 07:32 AM

Hi all,

I'm want to move from slackware 10.2 to 12 and i've been told that using slapt-get to do it is a pretty bad idea, so im thinking maybe its best if i just do a fresh install.

I'm running apache, mysql, php and an IRCD (hybrid7, which was set up by someone else). Also I'd like to keep the files that took a bit of fiddling around with like xorg.conf so i dont have to go through that again.

What dirs/files should i back up so that the web/irc servers dont need to be re-installed and then configured again?

What other dirs/files should i burn so i dont have as much stress as last time getting stuff working? (i use KDE btw)

Is using slapt-get to upgrade a bad idea?

I know this is all a bit vague but its been so long since i installed 10.2 i cant remember much about it :/

Any help very much appreciated.

TSquaredF · 11-04-2007, 08:32 AM

Quote:

Is using slapt-get to upgrade a bad idea?

Everything I have heard says that upgrading versions is a bad idea, whether or not you are using a package manager. I copy my configuration files to a separate partition, so that once I have upgraded, I can copy them back. I do the same with data, never keeping it in the same partition as the OS. That way I can wipe the entire OS partition, if I want, & not have to worry about my data.

wmhrae · 11-04-2007, 08:46 AM

Upgrading from 10.2 - 12.0

boot with dvdrom and mount your hardisk partition with slackware 10.2 under /mnt and do the upgrade it will work fine : Download the dvd.iso and use that to upgrade !!!
ftp://ftp.heanet.ie/mirrors/ftp.slac...nstall-dvd.iso

Ok slapt-get mode ....

Ok first you have to do this :
download glibc-solibs-*.tgz
ftp://ftp.heanet.ie/mirrors/ftp.slac...2.5-i486-4.tgz
then download pkgtools-*.tgz
ftp://ftp.heanet.ie/mirrors/ftp.slac...0-noarch-4.tgz

A. Put your machine in single-user mode:
telinit 1

B. Upgrade your glibc shared libraries. This is important, or things
might go haywire during the first part of the upgrade:

upgradepkg /root/slackware/a/glibc-solibs-*.tgz

C. Upgrade your package utilities:

upgradepkg /root/slackware/a/pkgtools-*.tgz

now you can use slapt-get to do the rest ... WARNING if you use gslapt then ask me what to do ...

If you are worried then contact me even if you stuff up the system DO NOT FORMAT I can tell you what to do ... or if you want to be ready then I can tell you beforehand !!!

XGizzmo · 11-05-2007, 04:51 PM

The very first thing you should do is read http://ftp://carroll.cac.psu.edu/pub/linux/distributions/slackware/slackware-12.0/CHANGES_AND_HINTS.TXT and follow it step by step word for word, also look over the same file for slackware 11 for anything you may need to add or remove. When done you will have a working slackware 12 install.

onebuck · 11-05-2007, 07:37 PM

Hi,

I think you should read all Slackware 12.0 txt files that PV provides;

CHANGES_AND_HINTS.TXT, UPGRADE.TXT and RELEASE_NOTES!

If you were just moving from 11 to 12 then I would say it shouldn't be a problem. But you are wanting to move from 10.2 (major) to Slackware 12.0(major). The problem will be everything relative to 11 and the installs you made.

You could just backup the configuration files and make the move. Or use your system maintenance log to guide you through. Oh! You didn't document your installs did you. No system documentation or entry too assist. I'd start one now if I were you. That way you won't get into situations of this type in the future.

hitest · 11-05-2007, 10:58 PM

I would back up your data and start fresh and do a clean install. I agree with onebuck, keep a log of your installation, jot down notes. It is best if you install and set-up slackware yourself as you will learn more unassisted.

ludist · 11-06-2007, 03:57 AM

Linux is not Windows.

Slackware is awfull (lol) simple.

Upgraded from 10.1 > 10.2 > 12 > 12.1 (current) no problemos.

Read UPGRADE.TXT and the other files.

dunric · 11-06-2007, 09:45 AM

Quote:

Originally Posted by dave`2005

Is using slapt-get to upgrade a bad idea?

No, it is not, if you'll keep instructions described in slapt-get's FAQ

onebuck · 11-07-2007, 06:10 AM

Quote:

Originally Posted by dunric

No, it is not, if you'll keep instructions described in slapt-get's FAQ

Hi,

Quote:

exerpt from slapt-get FAQ;

You can specify --remove-obsolete to remove all depreciated packages.
CAUTION: this can only take into consideration packages that are available
from your current sources. Thus self made packages will be considered
obsolete as well (they can be excluded within slapt-getrc, however). Only
use this if you have been using Slackware packages exclusively. You can
also use this option for information purposes, observing the obsolete
packages, then passing all the ones you are sure of to --remove (which can
accept multiple packages at once).
### dist upgrade and remove all depreciated/obsolete packages
$ slapt-get --dist-upgrade --remove-obsolete

Then follow the rest of the directions in UPGRADE.TXT.

You should make sure any new packages within the disk sets you are using are
also installed, as they will not be detected during --dist-upgrade, as only
packages already installed will be upgraded. To accomplish this, you can
specify slapt-get to install a disk set like so:

### install all X and X application packages
$ slapt-get --install-set x xap

Do the same for all your installed disk sets, such as gnome, x, xap, l, n, etc.

If you re-read the OP, then the criteria can be a problem. The above caution should be noted! I'm not saying that slapt-get can't be used but you will have to know your system. With system maintenance logs/system logs maintained during the operation or generation of the system then things become a lot easier.