After Installed Slackware 14.2

This is my note after I installed Slackware 14.2, but I think it can be used also in Slackware 14.1 or even Slackware Current. I believe many experience Slackware user already make this to do list too, but I still want to made this in purpose as reminder for myself and I hope it can also be useful for you who want use Slackware as daily Operating System.

Setup Graphical Environment

I believe graphical environment is just a preference matters among people, some experience Linux user will be more comfort just using text without Desktop Environment (DE) which why Slackware just provide console login at the first time. Since our purpose is to make Slackware as our workstation we need to configure this.

Choosing Desktop Environment / Window Manager

Slackware is provide many option regarding Desktop Environment (DE) or Window Manager (WM) such as KDE, XFCE, LXDE, etc. The best thing about DE / WE in Slackware is we can changed this freely, or add new DE / WE in our machine.

Said I bored with my KDE and want to changed with lightweight WM, I just need run command below as super user (root) and will shown an interactive window to choose what DE or WM options.


Boot in Graphical User Interface

The default Slackware User Interface was Command Line Interface (CLI), so the first time we booting into Slackware we also need to do login using CLI. Some people more preferred to have Graphical User Interface (GUI) at the first time, we can do this with some change in /etc/inittab file.

Slackware using run level 3 as default, so if we want to make Slackware booting using GUI change this

id:3:initdefault: into id:4:initdefault:

Warning, never change Slackware run level into 6 & 0 or Slackware won’t booting.

Optimizing LiLo (Linux Loader)

Linux Loader (LiLo) is one of the most popular boot loader in Linux, and Slackware was using this. To be honest, we can improve boot time in Slackware with just configure LiLo. We just need tweak lilo configuration which located in /etc/lilo.conf


This will tell Slackware to read our hard drive more faster. Warning, some old systems will give error or freeze screen and if this happen don’t add this.


This tell how long to wait at the prompt before booting the default operating system, measured in tenths of a second. This configuration tell to waits for 5 seconds.


The last, when everything is done, don’t forget to update our LiLo configuration with command above in command line (cli) as root (super user). More details about what or how to configure LiLo can be found here.

Enable Unicode

Sometimes you forgotten to enable unicode on your machine, don’t worry you still can enable unicode, you need switch into root user to do this. Open and edit file /etc/profile.d/ remove # (uncomment) line of export LANG=en_US.UTF-8 .

Configure Slackpkg

Slackpkg is the most useful Slackware tools for packaging manager on top of Slackware’s own pkgtools, not only for installing new package, we also can updated our Slackware using slackpkg.

Slackware Mirror’s

Before we can used slackpkg we need to choose our Slackware mirror’s. Slackware already listed all Slackware mirror’s both 32 & 64 bit from all the world, it can be seen in /etc/slackpkg/mirrors.

The coolest thing about slackpkg is, not only it can fetch data from internet but it can also fetch data from CD-Rom and also our local machine which is we just need to download Slackware Repository, put it in our machine or burn into CD-Rom, then configure slackpkg mirrors. This can be happen because slackpkg is just need to find Changelog.txt files.

Blacklist Sbo and Alien Package

Slackbuilds was the biggest Slackware Repository, and I believe most of our application was build from there. Unfortunately, slackpkg can’t identify Slackbuilds package and the rest. To avoided slackpkg harm our package we can add this package into slackpkg blacklist in /etc/slackpkg/blacklist


Create New Non Super User

As we know Linux always have this super user (root), and we MUST avoided using this user in daily use. We don’t want to make a stupid mistake that can harmed our machine, right? Because as Uncle Ben in Spiderman Movie said

With Great Power Comes Great Responsibility

We need to create a new user with less privileges than super user (root), and this is a best practice in every Linux Distro. We can created new user with CLI and the most preferred command was Slackware’s own interactive adduser script, thus execute this command as super user (root):


Adding Users to Sudoers File

Having restricted users is good, but sometimes is bothersome to switch between your regular user with root / super user. To make it more simple, add your regulars users into sudoers file and every time you want executed something that need root / super user privileges you can do with sudo.

The most safe and recommended way to add user into sudoers was using visudo command. Execute visudo as root / super user, you will given file that opened with vim editor. Find something like root ALL=(ALL) ALL copy that line, paste on the new line and change it with your regular user name.

root ALL=(ALL) ALL
swhp ALL=(ALL) ALL

However, if you want to something more mainstream like other distribution which is rather than define the user privilege you can add your user into wheel group. Execute visudo as root / super user find line below.

# Uncomment to allow people in group wheel to run all commands  
# %wheel ALL=(ALL) ALL

Uncomment that %wheel ALL=(ALL) ALL with remove # , then add your regular user name into that group also as root / super user.

gpasswd -a swhp wheel

Setup Network Manager

The most important thing about having a workstation is we should be able connect to the internet, so we also need configure our network manager. Slackware already provide network manager daemon, we just need to make this daemon can be execute and started when the OS start thus execute this command as super user (root)

chmod 765 /etc/rc.d/rc.networkmanager
/etc/rc.d/rc.networkmanager start

To started network manager daemon we need to give execute permissions, with this kind of permissions will also make the network manager daemon started when the OS start. So, we just need to start network manager daemon once and it will always ready to used.

If you enjoyed reading this article, please recommend with click the 👏 below and share it to help others find it!

Like what you read? Give Sukma Wardana a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.