Slackware 13.37 to 14.0 Upgrade HOWTO This document explains how to upgrade from Slackware 13.37 to Slackware 14.0. Updated step 7 for Slackware ARM ---------------------------------------------------------------------------- For details of important changes from Slackware 13.37 to 14.0, see the file 'CHANGES_AND_HINTS.TXT'. Thanks to Robby Workman for help with this. 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 after 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 14.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" or "slackware64" directory from the install disc) 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 Note that this is _not_ strictly required, and there have been reports of success remotely upgrading machines that are still in multiuser mode. However, more things can go wrong in multiuser, so especially if you're considering a remote upgrade in multiuser mode, you might want to clone the machine locally so that you can do a test run to uncover any problem areas and come up with workarounds for them. 1. Upgrade your glibc shared libraries. This is important, or things might go haywire during the next part of the upgrade: upgradepkg /root/slackware/a/glibc-solibs-*.t?z 2. Upgrade your package utilities and related tools: upgradepkg /root/slackware/a/pkgtools-*.tgz upgradepkg /root/slackware/a/tar-*.tgz upgradepkg /root/slackware/a/xz-*.tgz upgradepkg /root/slackware/a/findutils-*.txz 3. Upgrade everything else (and install new packages): upgradepkg --install-new /root/slackware/*/*.t?z If you wish to upgrade everything except for the KDEI language packs for KDE (these take a lot of space and can be dealt with after the main upgrade more quickly and easily), running this script in the "slackware" directory will do the trick: #!/bin/sh for dir in a ap d e f k kde l n t tcl x xap xfce y ; do ( cd $dir ; upgradepkg --install-new *.t?z ) done 4. Remove obsolete packages. The CHANGES_AND_HINTS.TXT file should have a list of these. You may also wish to 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'. This command will get rid of the packages which became obsolete since Slackware 13.37: removepkg gdisk hal hal-info iwlwifi-100-ucode iwlwifi-1000-ucode \ iwlwifi-3945-ucode iwlwifi-4965-ucode iwlwifi-5000-ucode \ iwlwifi-5150-ucode iwlwifi-6000-ucode iwlwifi-6xxx-ucode \ jre kdeaccessibility kdebase kdebase-runtime kdebase-workspace \ kdebindings kdeedu kdegraphics kdeutils koffice konq-plugins \ kopete-cryptography module-init-tools ntfsprogs polkit-kde-1 \ radeon_ucode raptor rt2860-firmware rt2870-firmware rt61-firmware \ rt71w-firmware scripts wv2 xaw3d xf86-video-radeonhd \ xf86-video-sisusb xf86-video-tseng xf86-video-xgi xfce 5. 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 most 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" = "./rc.d/rc.local.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 might also wish to move these config files over: /usr/lib*/man.conf.new /usr/share/vim/vimrc.new 6. If you use a non-en_US language pack for KDE and you already have it installed, then you may upgrade it by moving into the slackware/kdei directory and using this command: upgradepkg --install-new *--*t?z The KOffice suite has been renamed to Calligra, so you'll need to remove any old koffice-l10n package that remains: removepkg /var/log/packages/koffice-l10n* If your language has been added to KDE since Slackware 13.37, you'll need to install it using installpkg, or upgradepkg --install-new. Typically you'll need to make sure that you have installed the slackware/kdei packages for kde, calligra, and k3b (if you use those). 7. IMPORTANT! *Before* attempting to reboot your system, you will need to make sure that the bootloader has been updated for the new kernel! For the supported systems such as the SheevaPlug, OpenRD client et al-- which have been installed on to a USB/eSATA type drive-- upgrading the kernel packages alone should suffice. However, if you have placed your kernel onto a NAND device or some other method, or your kernel exists outside of the ARM Linux Operating System, (as is the case with a QEMU installation), then you need to copy the new kernel images manually. The kernel images can be found inside the "kernels" directory inside root of the Slackware tree (slackwarearm-14.0/kernels). 8. Return to multi-user mode: telinit 3 9. Restart the 'init' process: telinit u 10. Reboot to start using the new kernel. At this point you should be running Slackware 14.0. :-) I wish everyone good luck with this! --- Patrick Volkerding volkerdi@slackware.com