Slackware

infobox OS
name = Slackware



caption = Slackware 12.1
developer = Patrick Volkerding
family = Linux, Unix-like
source_model = Free and open source software
working_state = Current
released = date|1993|07|16
latest_release_version = 12.1
latest_release_date = release date|2008|05|02
kernel_type = Monolithic kernel (Linux)
license = GNU General Public License
website = [http://www.slackware.com/ www.slackware.com]

Slackware is an operating system created by Patrick Volkerding of Slackware Linux, Inc. Slackware was one of the earliest distributions, and is the oldest currently being maintainedFact|date=August 2008. Slackware aims for design stability and simplicity, and to be the most Unix-like Linux distribution.Slackware website [http://slackware.com/info General Information] ]

Name

The name "Slackware" stems from the fact that the distribution started as a private side project with no intended commitment. To prevent it from being taken too seriously at first, Volkerding gave it a humorous name, which stuck even after Slackware became a serious project. [cite web | url=http://www.linuxjournal.com/article/2750 | title=Interview with Patrick Volkerding | accessdate=2007-07-03 | last=Hughes | first=Phil | date=1994-04-01 | work=Linux Journal ] The "Slack" in Slackware is a reference to the term "Slack" as used by the Church of the SubGenius. [ cite web | title=Volkerding answers Slashdot questions | url=http://slashdot.org/interviews/00/03/17/1120205.shtml ]

History

Slackware was originally descended from the Softlanding Linux System, the most popular of the original Linux distributions. SLS dominated the market until the developers made a decision to change the executable format from a.out to ELF. This was not a popular decision amongst SLS's user base at the time. Patrick Volkerding released a modified version of SLS, which he named Slackware. [ [http://lwn.net/Articles/91371/ A Short History of Linux Distributions [LWN.net ] ] The first Slackware release, 1.00, was on 16 July 1993. [ [http://www.slackware.com/announce/1.0.php The Slackware Linux Project: Slackware Release Announcement ] ] It was supplied as 3½" floppy disk images that were available by anonymous FTP.

In 1999, Slackware's release numbers saw a large increment from 4 to 7. This was explained by Patrick Volkerding as a marketing effort to show that Slackware was as up-to-date as other Linux distributions, many of which had release numbers of 6 at the time (such as Red Hat releasing each revision of its distribution with an increment of 4.1 to 5.0 instead of 3.1 to 3.2 as Slackware did). [ [http://www.slackware.com/faq/do_faq.php?faq=general#0 The Slackware Linux Project: Frequently Asked Questions ] ] Slackware did have some Beta releases in the 6.x range, but these are not counted as official releasesClarifyme|date=August 2008.

In 2005, the GNOME desktop environment was removed from the pending future release, and turned over to community support and distribution. [ftp://ftp.slackware.com/pub/slackware/slackware-10.2/ChangeLog.txt] The removal of GNOME was seen by some in the Linux community as significant because the desktop environment is found in many Linux distributions. In lieu of this, several community-based projects began offering complete GNOME distributions for Slackware.

Design philosophy

Many design choices in Slackware can be seen as examples of the KISS principle. [ [http://www.slackbasics.org/html/chap-intro.html#chap-intro-slackware Chapter 2. An introduction to Slackware Linux ] ] In this context, "simple" refers to the viewpoint of system design, rather than ease of use. Most software in Slackware uses the configuration mechanisms supplied by the software's original authors; there are few distribution-specific mechanisms. This is the reason there are so few GUI tools to configure the system. This comes at the cost of user-friendliness. Critics consider the distribution time-consuming and difficult to learn, whereas advocates consider it flexible and transparent and like the experience gained from the learning process.

Package management

Slackware's package management system can install, upgrade, and remove packages from local sources, but makes no attempt to track or manage "dependencies", relying on the user to ensure that the system has all the supporting system libraries and programs required by the new package. If any of these are missing, there may be no indication until one attempts to use the newly installed software.

Slackware packages are gzipped tarballs with filenames ending with .tgz. The package contains the files that form part of the software being installed, as well as additional files for the benefit of the Slackware package manager. The files that form part of the software being installed are organized such that, when extracted into the root directory, their files are placed in their installed locations. The other files are those placed under the install/ directory inside the package.

Two files are commonly found in the install/ directory, which are the slack-desc and doinst.sh files. These are not placed directly into the filesystem in the same manner as the other files in the package. The slack-desc file is a simple text file which contains a description of the package being installed. This is used when viewing packages using the package manager. The doinst.sh file is a shell script which is usually intended to run commands or make changes which could not be best made by changing the contents of the package. This script is run at the end of the installation of a package. [ cite web | url = http://www.linuxpackages.net/howto.php?page=package&title=Package+Howto | title = Building a Slackware Package ]

Dependency resolution

While Slackware itself does not incorporate tools to automatically resolve dependencies for the user by automatically downloading and installing them, some 3rd-party software tools exist that can provide this function similar to the way APT does for Debian.

Slackware 9.1 included Swaret and slackpkg as extra packages on its second CD, [ [http://slackware.com/announce/9.1.php The Slackware Linux Project: Slackware Release Announcement ] ] but did not install either by default. Swaret was removed from the distribution as of Slackware 10.0 but is still available as a 3rd party package.

slapt-get does not provide dependency resolution for packages included within the Slackware distribution. It instead provides a framework for dependency resolution in Slackware compatible packages similar in fashion to the hand-tuned method APT utilizes. Several package sources and Slackware based distributions take advantage of this functionality.

Alternatively, NetBSD's pkgsrc provides support for Slackware, among other UNIX-like operating systems. pkgsrc provides dependency resolution for both binary and source packages.

Releases

Slackware's latest stable x86 release is 12.1 [http://www.slackware.com/announce/12.1.php The Slackware Linux Project: Slackware Release Announcement ] ] (as of 2008-05-02), which includes support for ALSA, GCC 4.2.3, Linux 2.6.24.5, KDE 3.5.9 and Xfce 4.4.2.

There is also a testing / developmental version of Slackware called '-current' [ [http://slackware.com/changelog/ The Slackware Linux Project: Slackware ChangeLogs ] ] that can be used for a more bleeding edge configuration.

Hardware architectures

Slackware is primarily developed for the x86 PC hardware architecture. However there have previously been official ports to the DEC Alpha and SPARC architectures. As of 2005, there is an official port to the System/390 architecture. There are also unofficial ports to the ARM [http://armedslack.org/] , Alpha, SPARC [http://www.splack.org/] , PowerPC [http://workaround.ch/] and x86-64 (Slamd64 and Bluewhite64 [http://www.bluewhite64.com] ) architectures.

Third-party

Dropline GNOME, [http://gnomeslackbuild.org/ GSB: GNOME SlackBuild] , [http://gware.org GWARE] and [http://www.slacky.eu/index.php?option=com_content&task=view&id=2475 Gnome-Slacky] are projects intended to offer Slackware packages for GNOME. These projects exist because Slackware does not officially include GNOME, but a large number of users would prefer to have GNOME installed without having to go through the lengthy process of compiling it from source code.

Another project for building GNOME is the SlackBot automated build script system.

In addition to the unofficial package repositories listed above, there is a relatively new project called [http://slackbuilds.org SlackBuilds.org] whose goal is to provide build scripts for compiling add-on software and creating Slackware packages.

References

See also

* Patrick Volkerding
* List of Linux distributions based on Slackware

External links

* [http://www.slackware.com/ Slackware website]
* [http://www.slackbook.org/ The Revised Slackware Book Project]
* [http://www.slackbasics.org/ The Slackware Linux Basics book]
* [http://slackware.wordpress.com/ Unofficial Slackware Blog]
*
* [http://slackworld.berlios.de/ The Slack World (Magazine)]
* [http://www.jeepster.org.uk/history.html Unofficial History of Slackware releases]
* [http://theage.com.au/articles/2002/10/04/1033538761935.html Interview with Slackware founder Patrick Volkerding]