Language Selection

English French German Italian Portuguese Spanish

The beginner's guide to Slackware Linux

Filed under
Slack
HowTos

Give a man Ubuntu, and he'll learn Ubuntu. Give a man SUSE, and he'll learn SUSE. But give a man Slackware, and he'll learn Linux. Well, so the old internet maxim goes, but while it's normally used with a touch of humour, there's a great deal of truth in it too.

Slackware is a curious animal, minding its own business while other distros roam the popularity plain and strive for dominance among their peers.

It's not trying to win enormous desktop market share, nor is it loaded with blinking lights, hold-your-hand graphical wizards and package managers that change with every release. Slackware is about as pure a GNU/Linux system as you can get – at least, without all the arduous leg work of Linux From Scratch.

There are many reasons why Slackware has a devoted base of hardcore fans, usually Linux old-timers but occasionally newcomers too. The top four:

It's almost entirely developed by one man.
The packages are not patched to the hilt.
It's comfortable in its own distrosphere.
It's very, very, very stable.

Let's look at these in more detail.




More in Tux Machines

Android Leftovers

today's howtos

Mozilla News

  • WebExtensions in Firefox 48
  • Mozilla's WebExtensions API Is In Good Shape For Firefox 48
    Mozilla has announced that for Firefox 48 their WebExtensions API is considered to be in a stable state. They encourage developers looking to develop browser add-ons to begin using this new API. WebExtensions is an API for implementing new browser add-ons/extensions that makes it easier to port to/from other browsers, is compatible with Firefox's Electroloysis, and should be easier to work with than the current APIs. In particular, Google designed portions of the WebExtensions API around Google's Blink extension API.
  • Mozilla a Step Closer to Thunderbird Decision
    The good news is that the folks at Mozilla seem to be determined to find Thunderbird a good home where it will be able to grow and find newfound success. This isn’t surprising. As Surman pointed out in his post, the project is quite popular among those associated with the foundation — but that popularity is also contributing to the problem Mozilla has with keeping the project in-house.