SEO

Ok, didn't there used to be an upgrade howto on the
slackware.org site???

I am using slack 9 still, (haven't had a need to upgrade till now)
and am finding that more and more apps need the GLIBC 2.3.2 libs
to even build, FIrefox for one.

But after searching the slackware.org I couldn't find the
instructions for upgrading to slack 10. I don't want to do a
complete install.

Did I just miss this somehow?

Anyone know where a howto is?

Thanks

---
[Thou] rump-fed ronyon!
-William Shakespeare, Macbeth

Widgeteye (Widgeteye@widgets.com) writes:
> Ok, didn't there used to be an upgrade howto on the
> slackware.org site???
>
> I am using slack 9 still, (haven't had a need to upgrade till now)
> and am finding that more and more apps need the GLIBC 2.3.2 libs
> to even build, FIrefox for one.
>
> But after searching the slackware.org I couldn't find the
> instructions for upgrading to slack 10. I don't want to do a
> complete install.
>
> Did I just miss this somehow?
>
> Anyone know where a howto is?
>
> Thanks
>
Yes, you missed something. I only got on board with Slack 7, but
there and since there's been a bit about upgrade. The old comment
suggested the best way was to just do a new install, but there were
instructions. The latest just goes into the instructions.

It's on the "root" directory of the CDROM, ie the first layer where
you mount it. It's one of the all upper-case files, titled UPGRADE.TXT
You can go to it online here:

ftp://sunsite.ualberta.ca/pub/Mirror/Linux/slackware
/slackware-current/UPGRADE.TXT

among an awful lot of other places. You'll have to cut and paste
that long URL.

Michael

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Widgeteye wrote:
> Ok, didn't there used to be an upgrade howto on the
> slackware.org site???
>
> I am using slack 9 still, (haven't had a need to upgrade till now)

I assume that's Slack 9.0 rather than Slack 9.1, right?

> and am finding that more and more apps need the GLIBC 2.3.2 libs
> to even build, FIrefox for one.
>
> But after searching the slackware.org I couldn't find the
> instructions for upgrading to slack 10. I don't want to do a
> complete install.

Hmmm. I didn't even check for them because PV doesn't usually write
instructions for more than one release back. However, the CD should have
a document on how to upgrade from Slack 9.1.

> Did I just miss this somehow?
>
> Anyone know where a howto is?

The good news is that a few months ago, I found (and cribbed) a document
describing the process of upgrading from Slackware 9.0 to Slackware
10.0. I'll post it this evening, when I get home from work.

The bad news is that, although I followed the instructions, things
didn't work out for me. Enough has moved around since 9.0 to make some
of the upgrading less than trivial, and several packages have been split
apart and/or renamed. After following the upgrade doc and messing my
system up completely, I wiped out the upgrade and reinstalled Slack 10.0
from scratch. Fortunately for me, I had partitioned my HD, and my
/usr/local and /home directories were safe. But, that was one of the
four Slackware systems that I run; the other three are still running
Slackware 9.0, and won't be upgraded until I get all my notes together
and make complete backups.




- --

Lew Pitcher, IT Consultant, Enterprise Data Systems
Enterprise Technology Solutions, TD Bank Financial Group

(Opinions expressed here are my own, not my employer's)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)

iD8DBQFBWby2agVFX4UWr64RAhprAJ91AHEnztMU2LoSMrazBP HgrM9BiQCbBLpn
EsJUpaLtXMK0zG5wNBQDrmw=
=L7YE
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Lew Pitcher wrote:
> Widgeteye wrote:
>
>>>Ok, didn't there used to be an upgrade howto on the
>>>slackware.org site???
>>>
>>>I am using slack 9 still, (haven't had a need to upgrade till now)
[snip]
>>>Anyone know where a howto is?
>
> The good news is that a few months ago, I found (and cribbed) a document
> describing the process of upgrading from Slackware 9.0 to Slackware
> 10.0. I'll post it this evening, when I get home from work.
[snip]

OK, I found the notes. I believe I got them from Slackware.com, but I have no
proof. In any case, I've snipped them from my home wiki, and here they are...

- -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-

Moving from Slackware 9.0 with customization to Slackware 10.0, using Slackware
UPGRADE.TXT instructions, with alterations.

Before you begin, I would strongly recommend making a backup of your system,
or, if not the entire system, at least the /etc directory. You might find that
you need to refer to a few things about the upgrade process is complete. Back
it up, or take your chances.

OK, now that everything is safely backed up, let's proceed. :-)

To do this, you'll need the Slackware 10.0 packages. If these are on a CD,
create a new directory to mount the CD on so that it doesn't get in the way
during the upgrade:

mkdir /packages
mount /dev/cdrom /packages

The packages don't have to be on a CD-ROM, as an alternative you could copy the
slackware directory (the one with the various package subdirectories in it,
basically the "slackware" directory from the install CD) to someplace like
/root/slackware/. The important thing is that you know where the slackware
packages directory is. We'll use /root/slackware in the following examples.

* 0. Put your machine in single-user mode:

telinit 1

* 1. 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

* 2. Upgrade your package utilities:

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

* 3. Install sed. You should already have this, but since it's used by the
package utilities it is best to be sure:

upgradepkg --install-new /root/slackware/a/sed-*.tgz

* 4. Upgrade everything else (and install new packages):

upgradepkg --install-new /root/slackware/*/*.tgz

* 5. Make sure your system will boot. If you use LILO, make sure the paths
in /etc/lilo.conf point to a valid kernel and then type 'lilo' to reinstall
LILO. If you use a bootdisk, you'll need to use makebootdisk to make a new
bootdisk using the kernel in /boot.

* 6. Fix your config files. Some of the config files in /etc are going to
need your attention. You'll find the new incoming config files on your system
with the ".new" extension. You may need to fill these in with information from
your old config files and then move them over.

Feel brave? You can use this little script to install all of the .new config
files in /etc. If you've made any local changes you'll need to add them to the
newly installed files. Your old config files will be copied to *.bak. Anyway,
it might be an easier starting point. Here it is:

#!/bin/sh
cd /etc
find . -name "*.new" | while read configfile ; do
if [ ! "$configfile" = "./rc.d/rc.inet1.conf.new" \
-a ! "$configfile" = "./group.new" \
-a ! "$configfile" = "./passwd.new" \
-a ! "$configfile" = "./shadow.new" ]; then
cp -a $(echo $configfile | rev | cut -f 2- -d . | rev) \
$(echo $configfile | rev | cut -f 2- -d . | rev).bak 2> /dev/null
mv $configfile $(echo $configfile | rev | cut -f 2- -d . | rev)
fi
done

You'll probably also want to either remove your old /etc/X11/XF86Config or move
it to /etc/X11/xorg.conf. It's probably best to start with one of the new
examples or xorgconfig, though, as there are a few minor config file changes
(easily spotted by diffing the supplied sample config files, if you're interested).

* 7. Return to multi-user mode:

telinit 3

* 8. Remove obsolete packages.

If you go into /var/log/packages and take a look at the package list:

ls -lt | less

You may spot some old, obsolete, or discontinued packages. If so,
you can remove these using 'removepkg'. Here's a command line to
remove all the packages from Slackware 9.1 that are now obsolete:

removepkg devfsd elflibs oggutils acme gal2 gnome-extra-themes \
linc kde-i18n-af kde-i18n-eo kde-i18n-mk kde-i18n-mt \
kde-i18n-nso kde-i18n-se kde-i18n-ss kde-i18n-th kde-i18n-ven \
kde-i18n-vi kde-i18n-xh kde-i18n-zu koffice-i18n-ar \
koffice-i18n-bs koffice-i18n-lt koffice-i18n-lv \
koffice-i18n-uk db1 db2 libgr ttf-bitstream-vera xfree86 \
xfree86-devel xfree86-docs xfree86-docs-html \
xfree86-fonts-100dpi xfree86-fonts-cyrillic \
xfree86-fonts-misc xfree86-fonts-scale xfree86-xnest \
xfree86-xprt xfree86-xvfb

9. Remove KDE language bloat. By upgrading all packages using

--install-new you've probably installed all of the KDE language
translations from the KDEI series, which will use up about
500MB. If you need only US English, you may remove the KDE
language packs like this:

cd /var/log/packages
removepkg kde-i18n* koffice-i18n*

Even if you need one of these, it might be best to start by
removing them all, and then go back and install the ones you
need with installpkg.

At this point you should be running Slackware 10.0. :-)

I wish everyone good luck with this!

- --- Patrick Volkerding volkerdi@slackware.com

- -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-

- --
Lew Pitcher

Master Codewright and JOAT-in-training
Registered Linux User #112576 (http://counter.li.org/)
Slackware - Because I know what I'm doing.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBWekZagVFX4UWr64RAledAKCGDjwXUZMGkXp1zVDNte 4Gm7q/AgCgnMkK
V4m1FjvR/QaLcRVZhgzeFKQ=
=8nI7
-----END PGP SIGNATURE-----

Lew Pitcher (lpitcher@sympatico.ca) writes:
> OK, I found the notes. I believe I got them from Slackware.com, but I have no
> proof. In any case, I've snipped them from my home wiki, and here they are...
>
That's straight off the distribution. I pointed it out in an earlier message.

I suspect the original poster simply didn't look closely.

Michael

Widgeteye wrote:
> Ok, didn't there used to be an upgrade howto on the
> slackware.org site???

How many people perform upgrades rather than fresh installs?

I keep a spare partition for installing newer versions or other distros:

1) I don't tell the new distro about my live /home partition.

2) If it beds in well with a test /home/user I'll copy real /home into
the new partition as a simple /home directory tree, add real
users/groups and run with real users.

3) If it passes muster after a week I'll copy /home out to its own
partition, at this point the old "/" becomes free for the next distro. I
don't keep a large /home, instead I use other partitions which are
rarely written to such as /mnt/backup, /mnt/multimedia, /mnt/store.

Some advantages are:

* If I/it cocks up, I have the previous working system immediately
available.

* Upgrade instructions vary, installing a fresh partition I then go
through the same procedure of installing the addons I like for instance
I have to check out my scanner, camera, mailfilter, getmail, smtpsend,
ATI gfx drivers, lm_sensors, firefox, thunderbird.

* It gets you to think about the junk that has built up on your system
and to keep a simple list of extras.

* It's the same procedure for upgrading or a different distro.

Paul Harris wrote:

> How many people perform upgrades rather than fresh installs?

Lots of people do. I assume that many people even do what I do, which is to
run Slackware-current and *never* do a fresh install on an old system. I
find upgrading easy enough these days that I don't even bother with extra
partitions for /home or /usr/local on workstations or laptops (I use a good
handful of partitions on servers though, for security purposes.)

Jeffrey

Paul Harris wrote:
> Widgeteye wrote:
>
>> Ok, didn't there used to be an upgrade howto on the
>> slackware.org site???
>
>
> How many people perform upgrades rather than fresh installs?
>
> I keep a spare partition for installing newer versions or other distros:
>
> 1) I don't tell the new distro about my live /home partition.
>
> 2) If it beds in well with a test /home/user I'll copy real /home into
> the new partition as a simple /home directory tree, add real
> users/groups and run with real users.
>
> 3) If it passes muster after a week I'll copy /home out to its own
> partition, at this point the old "/" becomes free for the next distro. I
> don't keep a large /home, instead I use other partitions which are
> rarely written to such as /mnt/backup, /mnt/multimedia, /mnt/store.
>
> Some advantages are:
>
> * If I/it cocks up, I have the previous working system immediately
> available.
>
> * Upgrade instructions vary, installing a fresh partition I then go
> through the same procedure of installing the addons I like for instance
> I have to check out my scanner, camera, mailfilter, getmail, smtpsend,
> ATI gfx drivers, lm_sensors, firefox, thunderbird.
>
> * It gets you to think about the junk that has built up on your system
> and to keep a simple list of extras.
>
> * It's the same procedure for upgrading or a different distro.

An excellent strategy, I can confirm you will be very happy if you
follow this route.

Widgeteye wrote:

>
> Ok, didn't there used to be an upgrade howto on the
> slackware.org site???

I log in the fail safe mode then uninstall all packages (pgktool) then just
reinstall the packages off the 10.0 cd. Then it's just a matter of
reconfiguring a few things but all my settings from 9.0 were saved and all
my data.

On Tuesday 28 September 2004 11:55 am, Widgeteye did deign to grace us with
the following:

>
> Ok, didn't there used to be an upgrade howto on the
> slackware.org site???
>
> I am using slack 9 still, (haven't had a need to upgrade till now)
> and am finding that more and more apps need the GLIBC 2.3.2 libs
> to even build, FIrefox for one.
>
> But after searching the slackware.org I couldn't find the
> instructions for upgrading to slack 10. I don't want to do a
> complete install.
>
> Did I just miss this somehow?
>
> Anyone know where a howto is?
>
> Thanks
>
FWIW, I've always done a clean install, saving all of my settings and
data, of course.

It has always worked, and if I needed to do any tweaking, it was so
minor that I haven't bothered to remember it. Maybe one thing in xorg.conf,
or maybe just renaming XF86Config. The pertinent stuff in /etc just
copied right over.

Now, I'm about to embark on learning how to do a kernel. ;-) (since I've
started studying C++, of course, I now can program anything. ;-) )

Have Fun!
Rich