Skip to main content

Upgrading Slackware 14.1 to Current and MATE 1.12 to 1.14

Since Slackware 14.2 is getting closer to release, i decided to try migrating my wife's desktop machine from Slackware 14.1 to Slackware 14.2 (current). It still uses MATE 1.12 since i don't build MATE 1.14 for Slackware 14.1 (mostly because some deps require higher version of library that what's included in 14.1), so it's a good opportunity to try the upgrade process from MATE 1.12 to MATE 1.14 as well.

Since my wife's usage on this machine is limited to simple activities, i didn't install many third party packages besides LibreOffice and some other packages (less than 10 i counted). This gives me an easy start because i can simply wipe all of them during the upgrade process and reinstall it later if deemed necessary.

Here's what i did :
  • rsync a backup copy of slackware-current repository from my desktop
  • change the mirror in slackpkg to local file instead of remote repository
  • slackpkg install-new (install new packages introduced in 14.2)
  • slackpkg upgrade-all (upgrade all packages)
  • slackpkg clean-system (remove deprecated Slackware + third party packages)
  • reboot
For MATE, it was wiped clean during slackpkg clean-system procedure. I haven't built MATE 1.14 for x86 architecture, so i had to clone the repository and built it manually using the build scripts and in short time, i have MATE 1.14 ready and i can enter the MATE desktop again. She will never notice that the underlying OS and Desktop Environment have been upgraded.

In short, the upgrade procedure from Slackware 14.1 to 14.2 and MATE 1.12 to 1.14 is straightforward and smooth. When MATE 1.14 packages is ready for Slackware 14.2, if you use slackpkg+ and configured msb repository in the configuration, the above procedure will also upgrade MATE 1.12 to MATE 1.14 so no need to built it manually.

Popular posts from this blog

Running Rsync Via Proxy

One way to get the latest Slackware updates is by running rsync to syncronize your local repository and the main repository that hold the Slackware packages. Eric Hameleers has provided a great script called rsync_current.sh and how i modified this tool has been discussed on my previous post. In general, it works, except for one problem, when your computer is connecting to the Internet through a proxy.

My workstation at my office is connected to the Internet through a proxy, so i can't use normal rsync to work normally. I browsed the web and i found this site which tells us about how we should modify our squid configuration to allow rsync connection from any computer from our local networks. I asked my sysadmin to try this script. He agreed and he updated the squid configuration on the proxy.

Next, i need to update my environment variable RSYNC_PROXY to the host of the proxy and also the port. Let's say you are running a proxy on 192.168.1.1 and port 8080, then you need to run …

NVidia Legacy Unix Driver Update

NVidia has released an updated legacy drivers to support X.Org 1.19 with ABI 23. It has been mentioned in the UNIX drivers, but you can directly find the drivers from the links below:
NVidia 304.134 (x86x86_64)NVidia 340.101 (x86, x86_64) I have tested the 304.134 driver and it's working great here. I can finally remove x from my /etc/slackpkg/blacklist file since it's a showstopper for me.
Aside from legacy driver, NVidia has also released their latest driver 375.26 (x86, x86_64), which brings support for newer cards and also many new features (including X.Org 1.19 with ABI 23 support). 

Security Update: firefox, irssi, pidgin

Three security updates were released for today:
firefox: Upgraded to 45.4.0esr for 14.1 and 14.2 and 49.0 for currentirssi: Upgraded to 0.8.20pidgin: Upgraded to 2.10.11, 2.10.12, and 2.11.0 for all stable Slackware releases depending on their support Some minor update in current:
mkinitrd: Add dmsetup supportemacs: Upgraded to 25.1qt: Fix multilib issue network-scripts: Fix minor issue