| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision |
| howtos:systemupgrade [2012/09/21 12:27 (UTC)] – Incorporate the feedback from the discussion page. alienbob | howtos:systemupgrade [2012/09/21 21:36 (UTC)] – The Proprietary Graphics Drivers page has moved. alienbob |
|---|
| |
| <note tip>Bottom-line: you can trust slackpkg to perform a system upgrade safely, but it will need your brains and care.</note> | <note tip>Bottom-line: you can trust slackpkg to perform a system upgrade safely, but it will need your brains and care.</note> |
| | |
| | |
| | |
| | ===== Multilib considerations ===== |
| | |
| | If you are upgrading a multilib 64-bit Slackware computer, there are additional considerations to make. |
| | |
| | A multilib installation means that you have replaced Slackware's 64-bit ''gcc'' and ''glibc'' packages with multilib versions (ie.e. supporting both 32-bit and 64-bit binaries). Also, you have installed a set of "converted" 32-bit Slackware packages on your 64-bit multilib Slackware. These modifications are all needed to allow you to run and compile 32-bit software. |
| | |
| | When upgrading such a system, you must of course upgrade the standard Slackware packages, but separately you must upgrade the multilib-specific packages with new versions which you can obtain from http://slackware.com/~alien/multilib/ |
| | |
| | * First (if you use slackpkg), you must blacklist all these multilib packages so that they will not be accidentally replaced or removed during a system upgrade. If you don't blacklist them, you will face a lot of manual de-selections in "''slackpkg clean-system''". \\ Starting with the release of ''[[http://slackware.com/~alien/multilib/14.0/|compat32-tools]]'' for Slackware 14.0 you can simply add two lines to the ''/etc/slackpkg/blacklist'' file: <code> |
| | [0-9]+alien |
| | [0-9]+compat32 |
| | </code> Then you will manually have to download and upgrade the multilib packages. In the below example I will use Slackware 14.0 as the release to which you will be upgrading. |
| | * Download the multilib packages suitable for your new Slackware release from a mirror, like this: <code> |
| | # rsync -av rsync://taper.alienbase.nl/mirrors/people/alien/multilib/14.0/ multilib-14.0/ |
| | </code> This command will create a new subdirectory "''multilib-14.0''" in your current directory with all packages inside |
| | * install/upgrade the existing ''gcc'' and ''glibc'' packages, and ''compat32-tools'': <code> |
| | # cd multilib-14.0 |
| | # upgradepkg --install-new *.t?z |
| | </code> |
| | * Upgrade the set of converted 32-bit Slackware packages (often referredto as the "//compat32//" packages): <code> |
| | # upgradepkg --install-new slackware64-compat32/*-compat32/*.t?z |
| | </code> Alternatively you can run the "''massconvert32.sh''" script which will have been installed as part of the ''compat32-tools'' package. Pass it a 32-bit Slackware package directory (or a 32-bit Slackware mirror URL) as parameter and that will create a set of converted "''compat32''" packages which you can then install. You would only have to do this if you suspect that the content of the "''slackware64-compat32''" directory is not up to date. |
| | |
| | ===== Video driver considerations ===== |
| | |
| | If your computer is equipped with a video card powered by an [[http://www.nvidia.com/object/unix.html|Nvidia]] or [[http://www2.ati.com/drivers/linux/installernotes.html|Ati]] graphics processor and you have installed these companies' accelerated graphics drivers (closed-source and binary-only), you should not attempt start an X session after upgrading to the next Slackware release. \\ These drivers depend on kernel version, Mesa version and the X.Org server. You must re-install the binary driver before starting graphical mode. Also, the mesa and xorg-server packages of Slackware overwrite essential files of these closed-source accelerated graphics drivers anyway. |
| | |
| | If you want to know how to deal with these binary drivers, we have more detailed instructions in the "[[howtos:proprietary_graphics_drivers|Proprietary Graphics Drivers]]" article on this Wiki. |
| |
| |
