-->
Previous | Table of Contents | Next |
If youre using an older version of Slackware and you want to upgrade to the version on the accompanying CD-ROMs, you can do so without going through the agony of a full installation.
The new versions of pkgtool (a package maintenance tool developed for the Slackware distribution) should provide a clean upgrade path from earlier versions of Slackware. Because pkgtool can now remove packages from your hard drive while running on a self-contained Linux filesystem loaded into a ramdisk, it can remove any files from your system, including ones, such as the shell, shared libraries, init, and other crucial system files, that were difficult or impossible to remove while running on the hard drive.
NOTE: Upgrading through this method is probably more trouble than its worth. For example, several commonly reported bugs are caused by improper upgradingmixing disks from different versions of the distribution and/or failing to remove old packages first. We need to face the fact that things havent quite settled down yet, and until they do its not always possible to foresee differences in filesystem structure, daemons, utilities, and so on that can lead to problems with the system.The correct and best way to upgrade to a new distribution version is to back up everything you want saved and then reinstall from scratch. This is especially true for the A and N series disks. If you do upgrade packages from one of those disksets, you should seriously consider which packages from the other one might be related somehow and install those too. Again, it can be tricky to know just which packages are related, given the overall complexity of the Linux system. Thats why, unless you really know what youre doing, there is a substantial risk of screwing up a system while attempting to upgrade it.
Heres how youd upgrade to a newer version of Slackware from any previous version that supports package information files in /var/adm/packages. (If your system puts these files elsewhere, you might still be able to do this by creating a symbolic link from the package information directory to /var/adm/packages.) The steps are as follows:
mount /dev/hda1 /mnt -t ext2
mount /dev/hda1 /mnt -t umsdos
mount /dev/hda2 /mnt/usr -t ext2
Disk /dev/hda: 15 heads, 17 sectors, 1001 cylinders Units = cylinders of 255 * 512 bytes Device Boot Begin Start End Blocks Id System /dev/hda1 10 10 90 10327+ 1 DOS 12-bit FAT /dev/hda2 91 91 1000 116025 5 Extended /dev/hda3 * 1 1 9 1139 a OPUS /dev/hda5 * 91 91 1000 116016+ 6 DOS 16-bit >=32M Disk /dev/hdb: 16 heads, 31 sectors, 967 cylinders Units = cylinders of 496 * 512 bytes Device Boot Begin Start End Blocks Id System /dev/hdb1 * 1 1 921 228392+ 6 DOS 16-bit >=32M /dev/hdb2 922 922 966 11160 82 Linux swap
mkswap /dev/hdb2 11160
swapon /dev/hdb2
Thats it! Now youve cleaned up the old packages and youre ready to install the new ones. Type setup at a command line and install the new packages as normal.
Although it never hurts to play it safe and remove all packages from the bootdisk, almost all of them can be removed using pkgtool from your hard drive. The A series is the important exception here.
Previous | Table of Contents | Next |