What to do after installing Slackware? Quick and easy guide

Hello friends from FromLinux, after a long time without posting anything, here they have me again. Today I am going to show you how to get our Slackware ready after having installed it.

Why use Slackware?

Well everyone knows that it will be more than five months ago I made the change of Debian a openSUSE on all my machines including my servers. Now I did the same as I told myself .. If openSUSE has exited SUSE and this came from Slackware .. What will Slackware be like? And I decided to try it :).

Such was my pleasure that I could not contain the emotion and although one has to play a little with the roll of slackpkg, installpkg, sbopkg and the Slackbuilds website, it is clear that it is worth it since we achieve a performance that we will not see even in Debian, Fedora, RHEL, SUSE, ArchEtc. ...

The only distro that shows its performance is Gentoo and this lacks compilation times and a very long installation, while Slackware is installed in 20 minutes (depending on the software we choose): D.

My story ... the story of a Debian, the father of Linux, whom I adored for years and from whom I passed through the RHEL brothers and their descendants, and later by a daughter of a completely independent branch openSUSE of the mother SUSE which opened to me road to an unprecedented world. The mother of Linux distributions .. Slackware: D.

A long road led me to a world called real Linux. A world that looks a lot like Unix. A world in which packages are compiled. A world in which junk packages are not installed when wanting to install an application since we only need only their dependencies. A world of stability. A world without versiontitis and dystrotitis.

Even so, this distro is current, it is updated periodically .. To give an example: Slackware 14.1 It came out on 7.11.2013. We all know what happened recently with OpenSSL and we all know that the major distros have patched their OpenSSL versions. In the case of Debian or RHEL, they patched their versions 1.0.1e. Slackware 14.1 It also came out with this version, but when it detected this bug, it chose to put version 1.0.1g directly into the stable branch. This distro chooses to put the official version instead of making patches that can cause more bugs apart.

Which is why I kept Slackware on all my machines and servers and I plan to stay here. During these months I have been testing this distro very, very deeply to know if this step is correct. And the answer is yes .. Mother yes . This distro conquered me, completely captivated me and without a doubt it is the best thing I tried. I have no other words.

Without further ado, some images of my system:






Where I download it?

32 bit

64 bit

I am not going to go into how to do the installation itself since it is simple. It is a text mode installer, but it guides us step by step.

What to do after installing Slackware?

Add a new user:


During the dialog that appears when this appears:

Additional UNIX groups:

press the up key on your keyboards and at the end of the group line that is auto-completed with said key add: wheel and press enter.

Enable sudo to our user:

nano /etc/sudoers

Uncomment (#):

%wheel ALL=(ALL) ALL

We save the document with CTRL + O and close with CTRL + X.

Translate the system to Spanish:

List all available languages: locale -a

nano /etc/profile.d/lang.sh

Substitute export LANG = en_US:

export LANG=es_ES.utf8

We save the document with CTRL + O and close with CTRL + X.

nano /etc/profile.d/lang.csh

Replace setenv LANG en_US:

setenv LANG es_ES.utf8

We save the document with CTRL + O and close with CTRL + X.

Configure the repositories:

nano /etc/slackpkg/mirrors

Uncomment the links of Portugal since Spain does not have repos:

ftp://darkstar.ist.utl.pt/pub/slackware/slackware-14.1/ http://darkstar.ist.utl.pt/pub/slackware/slackware-14.1/

We save the document with CTRL + O and close with CTRL + X.

Update system:

slackpkg update slackpkg update gpg slackpkg upgrade-all

Start the system directly in graphic mode:

nano /etc/inittab

Change id: 3: initdefault: to:


We save the document with CTRL + O and close with CTRL + X.

Change the lilo wait from two minutes to five seconds:

nano /etc/lilo.conf

Replace timeout = 2000 with:


We save the document with CTRL + O and close with CTRL + X.


Now we install a very useful tool, which will compile and install the programs for us:

wget http://sbopkg.googlecode.com/files/sbopkg-0.37.0-noarch-1_cng.tgz installpkg sbopkg-0.37.0-noarch-1_cng.tgz

We update the database of programs available on Slackbuilds.org:

sbopkg -r

How to install packages through sbopkg…?

We verify that the package is available at http://slackbuilds.org/ and note all the dependencies.
Then just run: sbopkg -i "slim" (It is an example of installing slim). Do not forget that before putting the package that we want to install we put all its dependencies. Now we install the basic programs:

If we use notebook:

sbopkg -i "kcm_touchpad"


sbopkg -i "orc texi2html libebml libmp4v2 libcuefile libreplaygain lame x264 a52dec faad2 speex twolame lua portaudio libass libavc1394 libdc1394 libdca libdvbpsi libdvdcss libdvdnav libmatroska libmpeg2 libshout vcdimager fafropackinger555 tools vprodpackinger libsuplingerXNUMX tools

Compression tools:

sbopkg -i "p7zip rar unrar libtar"


In the case of using a 32 bit system:

Download jdk from oracle in its 7u51 version (jdk-7u51-linux-i586.tar.gz):

http://www.oracle.com/technetwork/java/javase/downloads/java-archive-downloads-javase7-521261.html#jdk-7u51-oth-JPRDescargar slackbuild:

We download the slackbuild:
wget http://slackbuilds.org/slackbuilds/14.1/development/jdk.tar.gz

Unzip jdk.tar.gz

Paste the file jdk-7u51-linux-i586.tar.gz in the jdk folder that we unzipped earlier and run the script:


This will create an installable package like this (you always see the path and name of the generated package) and we install it with:

installpkg /tmp/jdk-7u51-i586-1_SBo.tgz

In the case of using a 64 bit system:

Download jdk from oracle in its 7u51 version (jdk-7u51-linux-x64.tar.gz):

We download the slackbuild:
wget http://slackbuilds.org/slackbuilds/14.1/development/jdk.tar.gz

Unzip jdk.tar.gz

Paste the file jdk-7u51-linux-x64.tar.gz in the jdk folder that we unzipped earlier and run the script:

ARCH=x86_64 ./jdk.SlackBuild

This will create an installable package like this (you always see the path and name of the generated package) and we install it with:

installpkg /tmp/jdk-7u51-x86_64-1_SBo.tgz


sbopkg -i "flashplayer-plugin"


sbopkg -i "libreoffice"

Translate Libreoffice:

We download the slackbuilds from libreoffice-helppack and libreoffice-langpack:

wget http://slackbuilds.org/slackbuilds/14.1/office/libreoffice-helppack.tar.gz wget http://slackbuilds.org/slackbuilds/14.1/office/libreoffice-langpack.tar.gz

We unzip the downloaded files.

We download the libreoffice packages:

32 bit:

wget http://download.documentfoundation.org/libreoffice/stable/4.2.3/rpm/x86/LibreOffice_4.2.3_Linux_x86_rpm_helppack_es.tar.gz
wget http://download.documentfoundation.org/libreoffice/stable/4.2.3/rpm/x86/LibreOffice_4.2.3_Linux_x86_rpm_langpack_es.tar.gz
We paste these files without decompressing them in the corresponding slackbuid folders and execute the script in both:
./libreoffice-helppack.SlackBuild ./libreoffice-langpack.SlackBuild

And we install the generated packages (you always see the path and name of the generated package):

installpkg /tmp/libreoffice-helppack-4.2.3_es-i586-1_SBo.tgz
installpkg /tmp/libreoffice-langpack-4.2.3_es-i586-1_SBo.tgz

64 bit:

wget http://download.documentfoundation.org/libreoffice/stable/4.2.3/rpm/x86_64/LibreOffice_4.2.3_Linux_x86-64_rpm_helppack_es.tar.gz
wget http://download.documentfoundation.org/libreoffice/stable/4.2.3/rpm/x86_64/LibreOffice_4.2.3_Linux_x86-64_rpm_langpack_es.tar.gz

We paste these files without decompressing them in the corresponding slackbuid folders and execute the script in both:

ARCH = x86_64 ./libreoffice-helppack.SlackBuild ARCH = x86_64 ./libreoffice-langpack.SlackBuild

And we install the generated packages (you always see the path and name of the generated package):

installpkg /tmp/libreoffice-helppack-4.2.3_es-x86-64-1_SBo.tgz
installpkg /tmp/libreoffice-langpack-4.2.3_es-x86-64-1_SBo.tgz


sbopkg -i "wxPython filezilla"


sbopkg -i "skype"


wget http://download.teamviewer.com/download/teamviewer_linux.tar.gz

Unzip it and without installing it, we can use it by running the teamviewer package in this folder.


sbopkg -i "ufw"

We add the package to the start list:

nano /etc/rc.d/rc.local

We write this at the end:

if [-x /etc/init.d/ufw]; then /etc/init.d/ufw start fi

We save the document with CTRL + O and close with CTRL + X.

We enable the firewall:

ufw enable

We allow ssh if we use it:

ufw allow ssh

New launcher menu for KDE if you are interested (as in the image):

sbopkg -i "homerun"

And voila .. With this they obtain a system prepared for general use: D. And you see that it is not as difficult as it may seem. Greetings linuxeros and do not forget to comment :).

The content of the article adheres to our principles of editorial ethics. To report an error click here!.

96 comments, leave yours

Leave a Comment

Your email address will not be published. Required fields are marked with *



  1. Responsible for the data: Miguel Ángel Gatón
  2. Purpose of the data: Control SPAM, comment management.
  3. Legitimation: Your consent
  4. Communication of the data: The data will not be communicated to third parties except by legal obligation.
  5. Data storage: Database hosted by Occentus Networks (EU)
  6. Rights: At any time you can limit, recover and delete your information.

  1.   KARLOZ said

    And (vector linux) is like the delicacy of Slackware

    1.    petercheco said

      Yes but it is not the same 😀

    2.    DMoZ said

      I just happened to say hello =) ...


  2.   didaz said

    Slackware will not have a father but I can imagine in a few months that you have tried a "linux from scratch", and that you have changed all your machines and servers ... with the corresponding guide 😉

    1.    petercheco said

      I can't imagine doing such a crazy thing: D. I was thinking about it between Slackware and Gentoo. I went from Debian father to Slackware mother and here I definitely stay: D.
      Take a look at the support time that the Slackware versions have:


      I think it is ideal for use in production.

      1.    dbillyx said

        Debian my respectable and honorable operating system that I doubt one day will be removed from my computer ... The idea of ​​installing slackware also crossed my mind a long time ago, but when I tried it it was at a time that I did not understand some things and the path became difficult for me so abort the operation ... As you say, Gentoo takes a ("little") but it will be later ...

        Anyway, the comments are excellent about slackware, I hope to continue reading more about it and difficult processes with solutions that appear along the way ...

        Long live freedom…!!!

  3.   OtakuLogan said

    Slackware is a distribution that I have thought about installing several times, I have read comments that it is the most stable (but really). Certainly, I would be surprised if it had fewer bugs than CentOS, which gave me 0 issues in the time I tried it.

    However, I always come back to the same thing: outside packaging. The fact that Debian releases stable with outdated packages is not a whim, it is because the freedom of GNU / Linux together with the universal libraries causes that conflicts between programs can arise, and tests and time are needed to detect them. Slackware sure works very well with its official packaging but Slackbuilds is unofficial, they are packages that have probably not been thoroughly tested with each other and that when the time comes they can get stuck. If even in Debian it has happened to me with several packages, I have no confidence that Slackbuilds will not do it. On the other hand, with the external parcel there is also the security problem: if an error is detected, will they update it? Probably yes, but there are always programs that are abandoned (or uploaders abandon), there it is not so good. It is something that I suffered in CentOS: no problem after a week of use (the ONLY distro in which something like this has happened to me and I say it, with all the others something has always come up), but then it is time to pull external repositories where you The central system is very strong but the applications that you are going to use nobody guarantees you anything. Slackware for example has nothing to virtualize (LXC at most), you would have to go to Slackbuilds to get it.

    Would you really deserve to leave Debian behind and make the change with such sacrifice, petercheco?

    1.    petercheco said

      Hi OtakuLogan and thanks for a productive comment: D. I agree that the stability of a Debian or RHEL / CentOS is at a very high level. I went through the two distros that you mention and I can say that as long as you use the official repo you are sure that 99% nothing will happen to you. Of course, if you put the rpmfusion, adobe and epel repos in your CentOS, things change a lot. Not only because of the packages that you are going to install from these repos, but because of the junk packages that these install for you and the gaps that they may contain.
      With slackbuilds the matter is a little different since you know what packages and dependencies you are going to install and that you will never install a package that is not necessary to execute any function of the software you want to install with slackbuilds. Also keep in mind that slackbuilds works with the source code and compiles the package to your system. You also have to keep in mind that only stable versions of packages and tested packages are published in slackbuilds. Example: VLC on the official page is available in version 2.1.3 while in slackbuilds its version is 2.1.1. Regarding the instability of the system .. If you take into account that the packages are compiled for your computer, this reduces to 0 the instability of your pc since in any case the instability would only affect the program itself. I recommend you do a little taste of Virtualbox and you will see what advantages this distro has.
      I also tell you that I myself had the same opinion as you before trying Slackware for myself: D.
      Greetings Linux and I hope I have answered your questions 🙂

      1.    kik1n said

        Come on, it made me want to go back to slackware.

        I would like slackware to install dependencies and be rolling, but not everything can be haha. But I prefer slackware to debian or gentoo.

        1.    petercheco said

          Well, to return it has been said .. Slackware has the current branch and you already have it rolling 🙂

        2.    joakoej said

          For that there is Arch, it is rolling and with ABS and PKGbuilds you can do exactly the same as with Slackbuilds and if you want with the command "makepkg -s" I will also automatically resolve the dependencies.
          From what I see, I prefer Arch Linux, unless you can tell me some advantage that Slackware has with respect to Arch, because until now I have not seen

          1.    didaz said

            all have their grace…. when you get tired of one, then you switch to the other and so on haha

          2.    didaz said

            You use windows 7 and it's not rolling haha

      2.    OtakuLogan said

        Your answer is very interesting, petercheco. I take it into account, at least I will follow your guide to test it virtualized. Thank you!

        1.    petercheco said

          You're welcome 😀

  4.   ianpocks said

    Very good guide, we will have to give it a try. From what you say I imagine that before installing a package you have to look at the dependencies so when you install the packages you will have to install the dependencies. I'll have to look closely. It seems to me more Bsd style than linux ... Thanks 🙂

    1.    petercheco said

      Indeed. You have to install all the dependencies before the program itself. The advantage is with sbopkg since you install it all in one .. Example: Look at the command to install VLC. Everything before vlc (in the same command) are dependencies on VLC or on programs that VLC needs. In other words, you tell sbopkg in a command all the dependencies and the final program at the end and it takes care of downloading, compiling and installing each package by itself. It goes package by package until everything is done. And if Slackware is very close to Unix 😀

  5.   amulet_linux said

    You have to be congratulated because you use Slackware and because there are almost no posts from him. Although it seems to me that you exaggerated with the performance. In theory there should be more, but it is not something so remarkable. And I tell you that I used Arch and Slackware at the same time. Where it is notable is in Gentoo, especially KDE surprises me.
    Although I understand, I also had that higher optimization feeling and it is very good. But it doesn't suit my Slackware style, I got bored and forgot about it, instead I like how everything is done in Gentoo more.

    Gentoo is easier for me to use, it may require a bit more analysis in use, but it is the least of it. If we do not consider the installation.

    1.    petercheco said

      Thank you very much: D. I also congratulate you for using Gentoo and agree that it is very easy to maintain once installed thanks to portage: D. Gentoo attracts me in particular but the Gentoo installation is slow and I don't tell you anything to compile all KDE you have to be very patient: D. As for the performance, I cannot comment since I made a manual selection of packages during the installation so I only have the applications that I was interested in having and as an environment I installed only KDE. The feeling that I have in my laptop with a core and a gig of ram is that Slackware with KDE runs very, very fast and the differences of this distro with Debian, Arch, openSUSE is in my case very notable: D. I think it depends on the hardware that one has to perceive more or less the differences of each distro.
      Greetings 😀

      1.    amulet_linux said

        Thank you too. Now that I think about it, the minimal KDE installation on Debian or Arch forces you to install mandatory packages. On the other hand, in Slackware you can ignore many because it does not require them. Similar to Gentoo, it has 3 different KDE installations, the full one, the basic one, and a superlight one without unnecessary add-ons. Of which I chose the last one. It's excellent.

        1.    petercheco said

          Indeed 😀

        2.    eliotime3000 said

          In my PC that has Debian Wheezy with 1GB of RAM and a Pentium D of 2.8 Ghz, firstly, I installed the KDE-Meta package choosing the most basic ones to work with; Then, I proceeded to crash GNOME 3.4 itself while on the KDE desktop, and indeed, I am comfortable with my KDE on my desktop PC.

          With Slackware, I have tested its performance in virtual machine and KDE, with all its components, literally runs like silk. It's a marvel of a GNU / Linux distro and it's something I don't regret trying.

          Also, Slackpkg gives you the freedom to choose which dependencies you want to install in a binary package (which APT and Pacman never see).

    2.    Dayara said

      Well, the performance is noticeable, and a lot. Everything is very fluid. To give you an example, my Slackware 64bits with XFCE desktop shows a consumption of 245mb of RAM after booting. In OpenSuse or Fedora with the same desktop the consumption of about 354mb (having removed some processes from the start).

      On the other hand, I would not recommend anyone to use the current repositories, because it is quite common that after an update something does not work for you or it simply does not start the system. The last time it happened to me GDM stopped working (I had to use Ctrl + high + F1 to startx and switch to Slim), Gedit, Viewnior and several other programs.


  6.   Mr. Boat said

    Good petercheco, first of all thanks for the guide.

    Reading everything step by step I found meaning in all the steps except one:
    wget http://sbopkg.googlecode.com/files/sbopkg-0.37.0-noarch-1_cng.tgz
    installpkg sbopkg-0.37.0-noarch-1_cng.tgz

    Why do this, depending on googlecode.com, when we can install dbopkg 0.37 from the official repos according to the project web page?
    installpkg sbopkg-version-noarch-1_cng.tgz

    By doing it the other way, don't we risk becoming somewhat out of date for the future?

    A greeting.

    1.    petercheco said

      Hello, it is interesting what you put but on the official Slackware page comes this:

      In the official repos of the distro it is not directly :).

      1.    Mr. Boat said

        What a curious thing, how is it possible that they have not fixed such a huge error in http://www.sbopkg.org/downloads.php?

        Thanks for the quick reply.

        I had another thing to tell you, although I guess I already know the answer to that. One of the reasons that made me leave Arch was the fact that it did nothing more than find security problems everywhere, and I did not like having to become an expert in computer security to be able to configure certain parameters that in other distributions already they came to me by default.
        The same thing happens with Slackware, I guess, there are no security measures from minute 1, right?
        You must configure them yourself.

        1.    eliotime3000 said

          I don't think you have to reject an intervention like in Arch, since, in the same Slackware installer, it gives you the facility to automatically install SELinux and even so, it does not consume resources.

          Regarding Arch, what scared me was the speed with which they updated the versions of their most sensitive components, to such a degree that they made me return to the Three Marys of stability in GNU / Linux (Debian, Slackware and RHEL / CentOS ).

        2.    petercheco said

          Well Eliotime3000 has already answered you, but as you can see in my post I also install an assistant for the configuration more: ufw. This allows you to add parameters to the firewall (netfiter or iptables ... whatever you want to call it) in a very fast and easy way: D.

          Also to obtain even more security, you can for example install fail2ban to protect your pc from attempts by ssh or other services: D.

  7.   Warheart said

    I have wanted to get my hands on this distro for a long time, but I think manually installing the dependencies can become a real annoyance, anyway thanks for the tutorial, maybe one day I will cheer up.

    1.    petercheco said

      You're welcome. See that I go from automated systems to have more control over the system and dependencies 😀

  8.   eliotime3000 said

    My favorite KISS distro ... In truth, it is the best KISS distro I have tried so far, since it has the advantage of using both binaries (such as Debian and others using slapt-get or slackpkg to install from backports) or compilations as Gentoo (sbopkg).

    Anyway, distros like Slackware, there are none, and the official backports (like Slacky.eu) are more aware of bugs and update to the most stable version and edit the source code.

    PS: makes you want to download the Iceweasel source code and install it with sbopkg.

    1.    petercheco said

      Indeed: D. By the way .. What distro do you use now? I know you were around Slackware, Debian and Arch but which one is your chosen one is anyone's guess 😀

      1.    eliotime3000 said

        To tell the truth, my preferred distro is Debian, since it offers me a quick and easy installation to use and adapt (if someone hates the terminal, I install the center software if it is a GTK desktop or Apper if it is KDE).

        On the side of Slackware, I leave it for PC's that do not support kernels with PAE like my old Pentium IV or PC's that barely run with Windows XP.

        Anyway, I hope that my brother manages to migrate all his files from his PC to install Slackware 14.1 and thus, that he continues to enjoy XP with VirtualBox (he liked it as soon as I installed it on his notebook with Windows 7, since it depends on proprietary applications to program PIC's and PLC's).

    2.    patodx said

      eliotime…. forgive my ignorance .. but in slack .. can I install a .deb package… ??????
      it's because of my printer drivers ..

      petercheco .. a great guide to print .. and you made me want to try slack… very grateful ..

      Greetings ..

      1.    eliotime3000 said

        If you use the Alien packet converter, yes; but if you want to use slackpkg to install .deb packages, nope.

      2.    petercheco said

        You're welcome @patodx 😀

  9.   pandev92 said

    A little rudimental ahahaah

    1.    petercheco said

      By? I would say extensive but fast including the software that we use the most 😀

    2.    eliotime3000 said

      Meh, at least he doesn't put other packages you don't want.

      1.    petercheco said

        Indeed .. After each one chooses the packages they want to install .. Just search for them on slackbuilds.org and install them with the command sbopkg -i "package_name" (if it does not have dependencies) or sbopkg -i "name_of_dependency package_name" (for install dependency + package itself) 😀

  10.   r0uzic said

    I tried Slackware many months ago when version 14.0 came out, its installation was different from the other distributions but not as difficult as some people paint it and it gave me a sense of security (at the level of official packages) that few distributions have given me; but I consider it an error and a waste of time not to be able to install by default a system with the most basic nor to have a more optimized kernel and thus reduce loading time. Yes, many of you will tell me that I can do it manually in the installation, but it is precisely what I criticize: deciding with more than 100 packages if I am going to install it or not.

    1.    eliotime3000 said

      Normally, the Slackware installer will show you a list of which group of packages you want to install (from the most basic to the cutest, such as the KDE game packages), but to tell the truth, the kernel boot is up to the system. boot that is similar enough to UNIX / BSD (in fact, OpenBSD takes forever for archers).

      1.    petercheco said

        I can't agree anymore .. You can install the software groups A, AP, D, F, K, L, N, X and you already have a base system to which after restarting you install whatever you want: D.
        A little more about this: http://www.slackwiki.com/Minimal_System

  11.   babel said

    The guide is good, although seeing how slack works, I think I'm more of an Arch user. Another thing that strikes me is that you have many spelling mistakes (especially past simple verbs without accent). I think that is something that is always taken for nothing but any quality page would have to see those errors. Hopefully from Linux they put more effort into that.

    1.    eliotime3000 said

      @Petercheco is from the Czech Republic, so you can't blame him like that for having bad spelling like that (in fact, sometimes having to write in two or more languages ​​is frustrating).

      Anyway, that the article is much more complete than mine, it deserves extra credit.

      1.    Carlos said

        I am a Debian user but I have tried virtualizing almost all the distributions, at least all the original ones from which the rest are derived. Among them Slackware is the one I like the most, the operation of the slackbuilds at the beginning can be complicated but it is not more so than the use of AUR in ArchLinux.
        Slackware like Debian are mostly stability oriented regardless of whether or not it is the latest version if not bug-free, hence it is almost the only distribution that still uses Lilo instead of grub as a bootloader.
        It seems like a very good distribution to me, if I 'went' from Debian I would fall into Slackware networks, because Gentoo is much more complicated to use.

    2.    petercheco said

      Yes, it is true that I will have some other misspelling, but it is what happens when one writes an article at 12:XNUMX pm in the Czech Republic: D. In addition, it must be taken into account that the same Spanish speakers make spelling mistakes to bore: D.

    3.    patodx said

      I agree. Oi en dya the people do not write vien, zon hunos verdaderos hanimales of the lenhua casteyana.

      I think Petercheco should write in Czech from now on, so that we will understand better what our friend means in the tutorials, since Spanish is not his native language.

      Greetings ..

      1.    petercheco said

        Your comment made my afternoon at work happy: D. Thank you :). I'm serious when I say, that I've laughed for ten minutes minutos

  12.   petercheco said


    Hos I recommend in the part of the repository configuration to uncomment the repos of:


    These appear first in the document: D. It is in case the repository of their corresponding countries fails.

    1.    petercheco said

      Sorry "I recommend you"

  13.   Paul said

    I totally agree with this Slackware article, but, I ran into problems when configuring my Lan network, I did not find anywhere, solutions to my network problem, therefore, I have returned to opensuse, which facilitates and much the configuration of a Lan. I congratulate those who want and have time to learn, but as a user looking for quick solutions, I did not find Slackware.

    1.    petercheco said

      Hi, Pablo,
      During the installation process, the installer asks if you want to configure the network. You say yes and then select the Network Manager option. Be careful, there are four options and one of them is DHCP. Don't select DHCP if not Network Manager. Problem solved since your network connections will be managed by Network Manager 😀

      1.    petercheco said

        More info, which might interest you:

  14.   santilin said

    I have installed slackware on a Nec Versa M320 and followed your instructions, especially the sbopkg -i "kcm_touchpad" but my touchpad does not work.

    I've looked around but haven't found any solution for slack 14.1.

    Do I have to edit the x11 configuration file by hand?

    1.    petercheco said

      Hello, when you install this package you will find the options to configure your touchpad in KDE system preferences -> input devices -> touchpad.
      Here you adjust it to your needs: D.

      If instead of using KDE you use XFCE, go to the xfce center -> mouse and touchpad and make the desired settings :).

      1.    santilin said

        The system is not detecting my touchpad. When I enter the touchpad configuration from kde, in informations it tells me Touchpad name: Device not found


        1.    petercheco said

          Is your case very curious .. The touchpad does not work entirely or works half? How did you install the system?

          1.    santilin said

            Nothing at all works. The installation was done by following this tutorial.

            Do you know what to do to check if the kernel loads the touchpad?

        2.    petercheco said

          But I did not talk about the installation .. My post is about the post-installation: D.
          Your touchpad is probably not supported, but this is the first time I've seen it :). If you installed package group X during installation, your touchpad should work fine.

          1.    petercheco said

            In the Slacware installation a moment appears in which it asks you which mouse you want to use. You must choose the default Vídně: imps2mouse.

            If you want to do a manual configuration, you must edit or create the file /usr/lib/X11/xorg.conf.d/10-synaptics.conf


  15.   sandstone said

    Excellent contribution, I had not used slackware for years, with this distribution I started in GNU / Linux with version 10, I had to leave it long ago because before I needed to install everything manually and I had to look for each of the dependencies, but hey I'm going to try it again, Thanks for the Guide

    1.    petercheco said

      You're welcome 🙂

  16.   Percaff_TI99 said

    Very good post; the higher and the better, you can always learn settings that may not be in other tutorials and vice versa.
    Something that stands out in Slackware is the KDE integration and the fluidity with which the applications run, and yes, I also noticed it a little more agile than Archlinux.


    1.    petercheco said

      Thank you very much

  17.   SynFlag said

    The performance thing, I can put you in question, what about Gentoo?
    I will give you a vs of my CentOS with custom kernel vs Slackware with stock kernel ... let's see ram, speed and stability against CPU stress who gets more advantage 🙂

    1.    petercheco said

      Well, install two virtual machines .. One with a minimal CentOS with your custom kernel and the other with a minimal Slackware (install the software groups to have a minimal Slackware installation: http://www.slackwiki.com/Minimal_System) and publish your results 😀

  18.   Essaú said

    excellent article, congratulations, I already wanted to test this distro, and you managed to get me to immediately lower the ISO.
    Just a little question, I'm going to install it on my test machine, where I have several other distros installed, Debian Jessie, Arch, Ubuntu 14.04, OpenSuse, KaOs, Trsiquel, and they all boot from GRUB2. I see that in your article you talk about Lilo (how old is that?).
    The question is, can I choose to install GRUB2 instead of lilo and have it recognize the other distros you already install?

    1.    petercheco said

      Hello Essaú and thank you for your comment: D. During installation the system automatically installs Lilo.
      You can install grub (grub2) which comes on the Slackware DVD with the following steps:

      Once you finish installing Slackware and this message appears: "Installation of Slackware Linux is complete."

      chroot / mnt

      grub-install / dev / sda
      grub-mkconfig -o /boot/grub/grub.cfg

      And voila: D .. More info about this:

    2.    petercheco said

      One more thing ..
      Lilo is not an abandoned project at all. The last stable version was released less than a year ago (June 7, 2013) and today Slackware has UEFI support with Lilo.

      Más info: http://en.wikipedia.org/wiki/LILO_%28boot_loader%29

  19.   Garbage_Killer said

    excellent guide Peter.

    on the other hand, months later he regrets slack and returns to rhel, although in this case centos but on 7 😛

    1.    petercheco said

      Thanks: D. Well hoigo whispers in the wind that they say, that I am staying with Slackware, since I am liking it a lot and having everything in my hands :). In addition, the performance is brutal and I forget about repositories plus the configuration of priorities, deb or rpm packages and their dependencies: D. With the mother Slackware I feel free and more and more I identify with Patrick Volkerding's thinking about linux today.

      It is ideal and the support it has is unmatched:

  20.   Chicxulub Kukulkan said

    One question: can I have two or more desktops installed? For example, start today with KDE, tomorrow with XFCE and next week with Cinnamon.

    1.    petercheco said

      Hello, of course you can have several scripts .. Of course, Cinnamon will have to compile: D.
      More info here: http://slackblogs.blogspot.cz/2014/04/cinnamon-slackbuilds-csb-for-slackware.html

  21.   vidagnu said

    Excellent tutorial, I have been using Slackware since 1998 and I have never had problems with servers, I do not install packages from slackbuilds on them since the packages that are in the official repositories are enough. In my house I also use it and in this case if I use slackbuilds for packages like vlc, although I also make constant use of ./configure && make & make install among others.

    Congratulations again on this tutorial and the choice you have made!

    1.    petercheco said

      Thank you very much Oscar, I am also glad I made the decision to use Slackware. 🙂

    2.    kik1n said

      Wow, you must be quite a hacker :).
      When you upgrade from slackware to another version, do you reinstall or upgrade?

      1.    petercheco said

        Well you can upgrade without problems with:

        1 ° Add the repos of the new version in / etc / slackpkg / mirrors

        2nd Update with:

        slackpkg check-updates
        slackpkg upgrade-all
        Choose the letter K to keep the configuration but looking at the new configuration of the packages

        3rd slackpkg install-new

        Of course, I prefer to do a clean installation since Slackware works very well and it is not necessary to update every two by three from version to version 😀

  22.   amilkar said

    Slackware, great, I'm learning a lot!
    Query, when modifying /etc/profile.d/lang.sh I put:
    export LANG = es_XX.utf8
    export LANGUAGE = es_XX.utf8
    export LINGUAS = es_XX.utf8
    export LC_ALL = es_XX.utf8
    XX: corresponding country
    It worked OK
    The keyboard is the problem, it does not take a Latin American or Spanish keyboard (you can see that I cannot write), I chose olpc / es-olpc | olpc / es-olpc.map which at installation time responded, then no. Can it be fixed in slackbuilds? What did I need to define in the installation? What do I have to modify? Regards.

    1.    petercheco said

      Try opening the terminal without being root (that is, with your username) and write:
      setxkbmap is

      Más info: http://docs.slackware.com/howtos:window_managers:keyboard_layout

      In general, the keyboard can be configured directly in the desktop environment you use.
      You said you set /etc/profile.d/lang.sh, but you set /etc/profile.d/lang.csh as well?

      nano /etc/profile.d/lang.sh
      export LANG = es_ES.utf8

      nano /etc/profile.d/lang.csh
      setenv LANG en_ES.utf8

      a greeting

  23.   Chamaeleonidae said

    Very Useful: 3

  24.   ANIM4 said

    Congratulations on this contribution to the Petercheco slacker community.
    I have been a slackware user since slackware 13 and the truth is that it is the best thing I have had on my hard drive, I have tried others but I have always returned to slackware (Gentoo I want it) and now the only thing I think about is stable or current?

    The only thing I see is missing is a Spanish-speaking community in the irc for example or a good active forum with a lot of participation. To solve everyone's doubts, we all have to learn and it is okay to make mistakes 100 times, so people will lose their fear of this wonderful Gnu / linux distro.

    This occurs to me when I see that people take advantage of congratulating the author and of this post and by the way they drop any doubts, it would be good to have a place so that we can all share our experiences and learn more and not have to throw so much of (linux questions).

    Much higher up someone asked why the sbopkg or slackpkg had not been added, the answer is simple, they are optional packages therefore it breaks the KISS philosophy for the same reason slackware64 does not have compatibility with 32bits, it is "ready" but you have to add a software layer to run / compile 32-bit software.

    And another user asked how to change from kde to a different environment, because as Petercheco said it is compiled and then you run in a terminal: $ xwmconfig
    And a menu appears where you can choose the one you want (previously installed). Then we turn off the X, $ startx next and that's it.


    1.    petercheco said

      Thank you very much for giving your answer and for the evaluation of my post and I agree, more Spanish-speaking websites about Slackware are needed: D.

  25.   ANIM4 said

    You are welcome Petercheco, if it is sad to see that there is no one in # slackware-es de freenode, you could create a different channel, such as Slackeros or Slackos or any other name, the difficult thing about these irc channels is to keep them active and with many users ... .

    Above I put * Slackpkg and it meant slapt-get 🙂 since slackpkg is included.

    Greetings and to continue giving cane to slackware for many more years!

  26.   Xurxo said

    Hello Petercheco 🙂

    I liked this post on what to do after installing Slackware. It is very suitable for everyone who likes to experiment and test OS * Linux.

    I have been using Slackware since 1994. I always have a Slack ready to go; right now a Slackware 14.1.

    However, I have not used it for months because the "nVidia Optimus" card support was not quite as mature as I would require for a Slack.

    I need to install the "bumblebbe and bbswitch" packages for the nVidia card to be disconnected; since most of the time I have left the integrated Intel of the i7.

    Thanks to your post I have remembered something that I did not take into account the last time I tried to install these packages: "the non-compatibility with 32 bits !!"

    I just did a search and found this HOWTO that explains how to install support for nVidia Optimus cards with nVidia drivers; but ... it is still essential to convert the system to "multilib"; and this is what I do not feel like!


    If I have a pure Slackware Linux 64 bit; it's because I want it to be like that. Adding a compatibility layer for 32-bit doesn't seem right to me.


    I know that the underlying problem is that nVidia does not offer adequate support for its graphics cards in GNU / Linux environments.

    I will have to wait for there to be some kind of support, even external, that allows the installation of this software without making a "multilib" system.

    Thanks for reminding me 🙂 I have not started Slack for months because with Linux Mint 17 the support for nVidia Optimos already works (with the Noveau drivers) from the installation and is so comfortable that one ends up forgetting where it comes from: - /

    Best regards.

  27.   Jessie said

    Very good page!
    More and more users are delighted with Slackware !!! 🙂
    Your images would look better with a window manager like Enlightenment 16 😀

    1.    petercheco said

      Thank you very much friend ... I was a while jumping from distro to distro, but I have returned to Slackware with KDE. Of course, this time Slackware Current and I think Slackware 14.2 or 15 we will see, it seems that it is about to caramel: D.

  28.   WSN said

    Excellent petercheco article!

    I had never used this distro until today, I had always opted for others with a graphical installer and theoretically friendlier in regards to the transition between windows and Gnu / Linux, but I am amazed with the performance of Slackware, I still need to configure some important things like keyboard and stuff, but I don't think it's complicated.

    My only regret is that it took so long to try this work of art.

    Greetings and congratulations for the great article, it is a great help.

    1.    petercheco said

      Hello friend and thank you very much for the good rating of my article :). Glad to see that it is helpful for users :). Greetings and enjoy the distro ...

  29.   ADRIAN said


    1.    petercheco said
  30.   antares_alf said

    Thank you very much Peter.

    You've written a great post for those new to slackware. It has also served me a lot and that I use the distro since 2008.
    The great thing about slackware is that it doesn't change much unless it's necessary. Now there is a new release, slackware 14.2. Are we waiting for a new recharge post?

    Thank you very much Peter.

  31.   Vikrand said

    Thanks for the post, it has helped me as you can not imagine.

    I am new to this distro, I have read on LinuxQuestion that KDE Plasma 5 can be installed on Slackware 14.2.

    What I don't understand is how can I install it?
    How do I use the AlienBob repository?

    Thanks in advance!

  32.   JOel said

    I came here by chance, this tutorial has helped me a lot because I wanted to try Slackware.
    To this day I still have it installed on my desktop PC without failures, stable, one pass. And right now I just installed it on my laptop to go deeper into the world of linux especially (Slackware / Zenwalk)
    It is true that at first it was hard, something like when I went from windows to ubuntu / linuxmint ... hahaha. I had to do a lot of research on linux.
    I had tried many distros, but this one for me is the one that adapts to my learning with linux. I still have another one from the old school which is the Freebsd.

  33.   Marlon said

    Does anyone know how to make a custom Slackware distribution? probe liveslak but I don't know what commands are

  34.   josAlz said

    After 12 years of trial and error with various distributions, linux, bsd, windows, osx, I found the system that works for me, I am always disarming client machines installing systems, optimizing, testing, I needed something stable, I am going for the second day of slackware And learning, it all started with wifislax that I saw very quickly when I looked I see that it was based on slackware ... then I read opinions of users of all levels and their experiences ... I felt adrenaline the search ended.
    excellent forum I leave it as final,
    Use the Force, Luke!