Friday, November 8, 2013

Slackware 14.1 is released!

After over a year of development (including the beta release and several release candidates to get everything polished up) we're proud to announce the availability of the new stable release. You'll find updates throughout the system, with the latest compilers and development tools, and recent versions of applications, window managers, desktop environments, and utilities. The Linux kernel is updated to version 3.10.17 (part of the 3.10.x kernel series that will be getting long-term support from the kernel developers). The x86_64 version of Slackware also adds support for installing and booting on systems running UEFI firmware.For additional information, see the official announcement and the release notes. For a complete list of included packages, see the package list.
Build scripts for all kinds of additional software for Slackware 14.1 can be found on the website.
Need help? Check out our documentation site, Stop by and share your knowledge!
Please consider supporting the Slackware project by picking up a copy of the Slackware 14.1 release from the Slackware Store. The discs are off to replication, but we're accepting pre-orders for the official 6 CD set and the DVD. The CD set is the 32-bit x86 release, while the DVD is a dual-sided disc with the 32-bit x86 release on one side and the 64-bit x86_64 release on the other. Thanks to our subscribers and supporters for keeping Slackware going all these years.
Thanks to the Slackware team for all the hard work getting 14.1 ready for action! And of course, thanks to all the open source developers upstream, and to the Slackware community on for all the help with bug reports, suggestions, and patches. We couldn't have done it without you.
Enjoy the new stable release!
Pat and the Slackware crew
Slackware 14.1 for ARM is also available. For details, see:

Tuesday, July 16, 2013

Slackware Linux is 20 years old!

Slackware Linux is 20 years old!

Slackware Linux 1.00 (16 July 1993)

   From: Patrick J. Volkerding (bf703@cleveland.Freenet.Edu)
   Subject: ANNOUNCE: Slackware Linux 1.00
   Newsgroups: comp.os.linux
   Date: 1993-07-16 17:21:20 PST

 The Slackware Linux distribution (v. 1.00) is now available for
 anonymous FTP. This is a complete installation system designed for
 systems with a 3.5" boot floppy. It has been tested extensively with
 a 386/IDE system. The standard kernel included does not support SCSI,
 but if there's a great demand, I might be persuaded to compile a few
 custom kernels to put up for FTP.

 This release is based largely on the SLS system, but has been enhanced and
 modified substantially. There are two main disk series, A (13 disks) and
 X (11 disks). Some of the features:  

 Series A:
   About what you'd expect from SLS series A, B, and C. Plus:
   Source for the Linux DOS emulator version 0.49.
   The FAQ for kernel level 99pl10.
   Kernel source and image at .99pl11 Alpha.
     [compiled with these options: math emulation support, normal hard drive
     support, TCP/IP, System V IPC, -m486, minix fs, ext2 fs, msdos fs, nfs,
     proc support, and PS/2 style mouse support. You may need to recompile if
     you have some other type of busmouse. The kernel was compiled with libc
     4.4.1, g++ 2.4.5]
   The new keytable utilities.
   The NET-2 networking package, preconfigured to use loopback.
   A public domain version of ksh, and tcsh 6.04 (with the bugs worked out)
   GNU gcc, g++, and Objective-C at versions 2.4.5
   Includes and libraries at version 4.4.1
   mailx, quota utilities, experimental winapi source, sound drivers.
   The TCL toolkit and samples.

   In addition, the installation program has been improved to offer more
   information about the packages (and the installation procedure itself)
   as you install.

   The install program can also automatically install LILO, configuring it
   to boot either from your master boot record or from OS/2's Boot Manager.

 Series X:
   Also, all the packages you would get in the SLS X series, plus:
   XFree-86 version 1.3.
   Open Look Virtual Window Manager made the default window manager.
   XS3 server offers support for S3 based video cards.
   XV 3.00 Image viewer is included.
   PEX files from the XFree-86 distribution are included.

 Although TEX support is not included in the Slackware release, the you may
 install the SLS T series from the install program.

 At this point, the install disk itself is running .99pl8. I'm working on it :^)
 Also, installation from other than a 3.5" floppy has not been tested, but might
 work. 5.25" floppy will not work because of file sizes. At this point, I have
 no plans to support a 5.25" version.

 How to get the Slackware(tm) release:

 The Slackware release may be obtained be anonymous FTP from in directory /pub/linux/slackware. At least initially,
 this release will be in the form of 3.5" disk images which should be copied
 to floppies using the RAWRITE.EXE program, or dd under Linux.

 Please note that our FTP software does not support limiting the number of
 concurrent anonymous logins. PLEASE try to go easy on this machine. If things
 get out of hand, access may be restricted.

 Other sites are, of course, welcome to help out with the load by mirroring
 the distribution.

 If you find any problems with the distribution, or if you have any suggestions
 for improvements, please let me know. If you know of more up-to-date versions
 of software in the distribution, I'd like to hear about that, too.

 Patrick Volkerding

Friday, July 5, 2013

Ten reasons to choose Slackware Linux (by Niki Kovacs)

This summer, the Slackware Linux distribution will celebrate its twentieth anniversary. Patrick Volkerding's official release announcement for Slackware 1.0 on July16th 1993 is still online. Read it here.

Here's a list of ten reasons why Slackware is still the perfect choice on servers, desktops and workstations.
  1. Experience. Slackware is the oldest surviving Linux distribution, it's been around even before Debian and Red Hat. There's a famous Nutella ad in France: Twenty years of experience make all the difference. The same thing applies to Slackware. The odd critic may have been pointing out the fact that Patrick Volkerding's favourite hobby is blindfolded jogging in front of buses. In the meantime, he's managed to avoid them all, and Slackware is here to last.
  2. Perennity. The Slackware installer and the collection of basic administration tools remain the same proven tools that have been shipping over the years. Which means that if you're a system administrator, you won't have to relearn your basic skills from scratch every time a distributor decides on a whim to switch init systems like he would change his underwear. Changes to the distribution only happen in small incremental steps and without drama, like the addition of slackpkg to Slackware 12.2. Some folks like to complain that Slackware tools like the installer or the package management tools are bone-headed dinosaurs. Remind them curtly that it still takes a meteor strike to wipe them. 
  3. Stability. Only proven and tested software gets added to a release. One thing you'll never find in Slackware is the unholy collection of half-assed technology previews sported by the more popular distributions, which tend to make your admin's life a misery.
  4. Flexibility. As an admin, I have a pretty good idea of what I want on a LAN server, on a public server or on a desktop. Unfortunately, no canned distribution ships these configurations out of the box. But Slackware is pretty much the only distribution that doesn't make me jump through burning loops to simply configure things like I want to configure them. 
  5. Flexibility (cont'd). If a package is not included in the distribution, I can be pretty sure has a build script for it. Otherwise, I'll just write one myself. Right now I have a collection of about 140 extra packages, and every single one built just fine. No distribution makes building stuff from source so easy.
  6. Simplicity. I often install desktops and workstations on old and/or exotic hardware, and Slackware lets me configure the more problematic stuff where the usual suspects among the installers just choke on it. The KISS principle reveals its full strength here, the more so since you won't find any DO NOT EDIT THIS BY HAND nonsense in Slackware.
  7. Humanity. I know, this is a word the Ubuntu folks claim for themselves, but one of the things I like about Slackware is its human size. Small distro, not too many packages, but carefully tendered. Folks in the Slackware forum at are a nice and competent crowd, and I like the general tone and no-bullshit attitude. Plus, the average Slackware user doesn't have the GNU/Linux taliban touch to it, which you see all too often here in France. Last but not least, Ubuntu is an old african word meaning I can't configure Slackware :o)
  8. Transparency. This one's obvious, but one less obvious factor is that it makes Slackware a great tool for actually learning Linux. Earlier this year, I've been teaching a class of ten sysadmins, and most of the course was based on Slackware.
  9. Efficiency. My Xfce-based desktop runs great on twelve year old hardware, and that's something I could only achieve with Debian or a handful of lightweight distros like Puppy or Slitaz, but not with the mainstream stuff like Ubuntu or openSUSE.
  10. Release policy. Slackware Linux pushes out a new release roughly once a year, when it's ready. Every release gets security updates for at least five years. Which makes Slackware perfectly fit for your business. 

Thursday, May 2, 2013

NetworkManager: A new option for the Slackware Linux network configuration!

Wicd (in "/extra" directory) is a good option for managing network connections. Until Slackware Linux 14.0 release, it was the only official graphical network configuration service option for managing the network connections besides the traditional CLI (Command Line Interface) based manual configuration. Together with the Slackware Linux 14.0 release, a Network Manager (NetworkManager) was integrated to the main tree of the release for easy setup and management of wired and wireless networking retaining full support for the traditional Slackware Linux networking scripts and for the wicd network manager. 

Before configuring network connections, open a terminal emulator and become root by,

$ su 

The NetworkManager daemon will not be started by default at boot, because the other network management options are still retained and users may want to prefer them instead of the NetworkManager. To start the network daemon automatically at boot, make the NetworkManager initialization script executable by using below command.

# chmod +x /etc/rc.d/rc.networkmanager

Start the NetworkManager daemon manually by,

# /etc/rc.d/rc.networkmanager start


# NetworkManager

The NetworkManager will appear in system tray by default even without starting the NetworkManager daemon, but you need to start the NetworkManager daemon for configuring the network connections.

Slackware Linux 14.0 comes with KDE widget for the Network Manager. Graphical configuration part of this guide is completely valid for the KDE.

Click on the NetworkManager icon in system tray. 

Make sure that "Enable networking" and "Enable wireless" boxes are checked and click on the "Manage Connections" tab on the right side. 

Click on the "Add" button.

Rename the wired connection, check the "Connect automatically" box (this will provide an automatic network connection on every login) and click on the "OK" button.

Click on the "OK" button.

Click on the "NetworkManager" icon in system tray.

Click on the wired connection you named previously on the right side and wait until the wired connection to be established.

Now, you are successfully connected to the wired network. To connect a wireless network, click on the WLAN interface tab on the left side. Then, SSIDs (names of the wireless networks) in the coverage of your WLAN network adapter will be listed.

Click on the SSID of the wireless network you want to connect.

Check the "Connect automatically" box (this will provide an automatic network connection on every login), enter the security password and click on the "OK" button.

Click on the "NetworkManager" icon in system tray.

Click on the wireless connection you configured previously on the right side and wait until the wireless connection to be established.

Now, you are successfully connected to the wireless network. 

NOTICE: If you are using XFCE, Slackware Linux 14.0 full installation includes NetworkManager applet (nm-applet) that works well under the XFCE. After initializing the NetworkManager daemon and relogging on, applet icon will appear in the system tray of the XFCE. Configuration GUI (Graphical User Interface) of the applet differs slightly from the KDE NetworkManager widget.  

Friday, March 8, 2013

Slackware Linux Graphics v1.3

Slackware Linux Graphics Project aims to provide a set of visual components related to GNU/Linux Slackware in both vector and raster graphics formats for its users. Source SVG graphics and exported PDF and PNG graphics in the project were all generated by using Inkscape under the GNU/Linux Slackware. 

Thanks to contributors for getting v1.3 ready!






Version 1.3

* Slackware.Linux.Domed.Tux.Logo
* Slackware.Linux.Eggstone.Tux.Logo
* Slackware.Linux.Power.Button.Logo
* Slackware.Linux.Power.Button.Logo.with.It.powers.up.freedom
* Slackware.Linux.Classic.SuperTux.Logo.with.Pelerine
* Slackware.Linux.Crystallized.SuperTux.Logo.with.Pelerine
* Slackware.Linux.Classic.SuperTux.Logo.without.Pelerine
* Slackware.Linux.Crystallized.SuperTux.Logo.without.Pelerine
* Slackware.Linux.Superman.Logo
* Slackware.Linux.GNU.Logo.with.Classic.Tux
* Slackware.Linux.GNU.Logo.with.Crystallized.Tux
* Slackware.Linux.System.Case.Sticker.Logo
* Slackware.Linux.GNU.Linux.Slackware.Three-digit.Black.Logo
* Slackware.Linux.GNU.Linux.Slackware.Three-digit.Grey.Logo
* Slackware.Linux.Traditional.Logo.with.Classic.Tux
* Slackware.Linux.Traditional.Logo.with.Crystallized.Tux
* Slackware.Linux.Traditional.Logo.with.Domed.Tux
* Slackware.Linux.Traditional.Logo.with.Eggstone.Tux

Version 1.2

* Slackware.Linux.Phear.the.Penguin.Logo.with.Classic.Tux
* Slackware.Linux.Phear.the.Penguin.Logo.with.Crystallized.Tux
* Slackware.Linux.Classic.Tux.Logo
* Slackware.Linux.Crystallized.Tux.Logo
* Slackware.Linux.Download.Logo
* Slackware.Linux.ARMedslack.Logo
* Slackware.Linux.ARMedslack.Logo.with.Home.Page
* Slackware.Linux.slackARM.Logo
* Slackware.Linux.slackARM.Logo.with.Home.Page
* Slackware.Linux.slack390.Logo
* Slackware.Linux.slack390.Logo.with.Home.Page
* Slackware.Linux.Powered.Logo.with.Classic.Tux
* Slackware.Linux.Powered.Logo.with.Crystallized.Tux

Version 1.1

* Slackware.Linux.KDE.Logo
* Slackware.Linux.XFCE.Logo
* Slackware.Linux.Documentation.Project.Logo
* Slackware.Linux.Traditional.Logo.v2
* Slackware.Linux.Bag.Badge.Logo.v2
* Slackware.Linux.Current.Branch.Logo
* Slackware.Linux.Current.Branch.Logo.v2
* Slackware.Linux.Current.Branch.Logo.v3
* Slackware.Linux.Current.Branch.Logo.v4

Version 1.0

* Slackware.Linux.Traditional.Logo
* Slackware.Linux.Traditional.Logo.with.Home.Page
* Slackware.Linux.Traditional.Logo.with.Because.It.Works
* Slackware.Linux.Traditional.Logo.with.Because.It.Secures
* Slackware.Linux.Traditional.Logo.with.Tux
* Slackware.Linux.Spherical.Logo
* Slackware.Linux.Blurred.Spherical.Logo
* Slackware.Linux.Favicon.Logo
* Slackware.Linux.Bag.Badge.Logo
* Slackware.Linux.Security.Shield.Logo