Slackware

From Wikipedia, the free encyclopedia
  (Redirected from Slackintosh)
Jump to: navigation, search
Slackware
Slackware Logo alt.jpg
Slackware GNU Linux 14.1.png
Slackware 14.1
Developer Patrick Volkerding
OS family Unix-like (based on Softlanding Linux System)
Working state Current
Source model Open source
Initial release 17 July 1993; 24 years ago (1993-07-17)[1]
Latest release 14.2 / 30 June 2016; 12 months ago (2016-06-30)[2]
Available in Multilingual
Update method pkgtools, slackpkg
Package manager pkgtools, slackpkg
Platforms IA-32, x86-64, ARM
Kernel type Monolithic (Linux)
Userland GNU
Default user interface CLI
License GNU General Public License
Official website www.slackware.com

Slackware is a Linux distribution created by Patrick Volkerding in 1993. Originally based on Softlanding Linux System, Slackware has been the basis for many other Linux distributions, most notably the first versions of SUSE Linux distributions,[3][4] and is the oldest distribution that is still maintained.[5]

Slackware aims for design stability and simplicity and to be the most "Unix-like" Linux distribution.[6] It makes as few modifications as possible to software packages from upstream and tries not to anticipate use cases or preclude user decisions. In contrast to most modern Linux distributions, Slackware provides no graphical installation procedure and no automatic dependency resolution of software packages. It uses plain text files and only a small set of shell scripts for configuration and administration. Without further modification it boots into a command-line interface environment. Because of its many conservative and simplistic features, Slackware is often considered to be most suitable for advanced and technically inclined Linux users.[7][8][9][10][11][12]

Slackware is available for the IA-32 and x86_64 architectures, with a port to the ARM architecture. While Slackware is mostly[13] free and open source software, it does not have a formal bug tracking facility or public code repository, with releases periodically announced by Volkerding. There is no formal membership procedure for developers and Volkerding is the primary contributor to releases.

Name[edit]

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.[14]

Slackware refers to the "pursuit of Slack", a tenet of the Church of the Subgenius. Certain aspects of Slackware graphics reflect this[15]—the pipe which Tux is smoking, as influenced by the image of J. R. "Bob" Dobbs' head.

A humorous reference to the Church of the Subgenius can be found in many versions of the install.end text files, which indicate the end of a software series to the setup program. In recent versions, including Slackware release 14.1, the text is ROT13 obfuscated.[16][17]

History[edit]

Birth[edit]

Slackware was originally derived from the Softlanding Linux System (SLS), the most popular of the original Linux distributions and the first to offer a comprehensive software collection that comprised more than just the kernel and basic utilities,[18] including X11 graphical interface, TCP/IP and UUCP networking and GNU Emacs.[19]

Patrick Volkerding started with SLS after needing a LISP interpreter for a school project at the then named Moorhead State University (MSU). He found CLISP was available for Linux and downloaded SLS to run it. A few weeks later, Volkerding was asked by his artificial intelligence professor at MSU to show him how to install Linux at home and on some of the computers at school. Volkerding had made notes describing fixes to issues he found after installing SLS and he and his professor went through and applied those changes to a new installation. However, this took almost as long as it took to just install SLS, so the professor asked if the install disks could be adjusted so the fixes could be applied during installation. This was the start of Slackware. Volkerding continued making improvements to SLS: fixing bugs, upgrading software, automatic installation of shared libraries and the kernel image, fixing file permissions, and more. In a short time, Volkerding had upgraded around half the packages beyond what SLS had available.

Volkerding had no intentions to provide his modified SLS version for the public. His friends at MSU urged him to put his SLS modifications onto an FTP server, but Volkerding assumed that "SLS would be putting out a new version that included these things soon enough", so he held off for a few weeks. During that time, many SLS users on the internet were asking SLS for a new release, so eventually Volkerding made a post titled "Anyone want an SLS-like 0.99pl11A system?", to which he received many positive responses. After a discussion with the local sysadmin at MSU, Volkerding obtained permission to upload Slackware to the university's FTP server.[14] This first Slackware release, version 1.00, was distributed on 17 July 1993 at 00:16:36 (UTC),[1] and was supplied as 24 3½" floppy disk images.[20] After the announcement was made, Volkerding watched as the flood of FTP connections continually crashed the server. Soon afterwards, Walnut Creek CDROM offered additional archive space on their FTP servers.

Development[edit]

The size of Slackware quickly increased with the addition of included software, and by version 2.1, released October 1994, it had more than tripled to comprise 73 1.44M floppy disk images.[21]

In 1999, Slackware saw its version jump from 4 to 7. Slackware version numbers were lagging behind other distributions, and this led many users to believe it was out of date even though the bundled software versions were similar. Volkerding made the decision to bump the version 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. He chose 7 estimating that most other distributions would soon be at this release number.[22]

In April 2004, Patrick Volkerding added X.Org Server packages into the testing/ directory of -current as a replacement for the XFree86 packages currently being used, with a request for comments on what the future of the X Window System in Slackware should be. A month later, he switched from XFree86 to X.Org Server after stating that the opinions were more than 4 to 1 in favor of using the X.org release as the default version of X. He stated the decision was primarily a technical one, as XFree86 was proving to cause compatibility problems. Slackware 10.0 was the first release with X.Org Server.[23]

In March 2005, Patrick Volkerding announced the removal of the GNOME desktop environment in the development ChangeLog. He stated this had been in consideration for more than 4 years and that there were already projects that provided a more complete version of GNOME for Slackware than what Slackware provided itself. Volkerding stated future GNOME support would rely on the community.[24] The community responded and as of October 2016, there are several active GNOME projects for Slackware. These include: Cinnamon, Dlackware, Dropline GNOME, MATE, and SlackMATE. The removal was deemed significant by some in the Linux community due to the prevalence of GNOME in many distributions.[25]

In May 2009, Patrick Volkerding announced the public (development) release of an official x86_64 variant, called Slackware64, maintained in parallel with the IA-32 distribution.[26] Slackware64 is a pure 64-bit distribution in that it does not support running or compiling 32-bit programs, however, it was designed as "multilib-ready". Eric Hameleers, one of the core Slackware team members, maintains a multilib repository that contains the necessary packages to convert Slackware64 to multilib to enable running of 32-bit software.[27] Hameleers started the 64-bit port as a diversion from the pain of recovering from surgery in September 2008. Volkerding tested the port in December 2008, and was impressed when he saw speed increases between 20 and 40 percent for some benchmarks compared to the 32-bit version. To minimize the extra effort of maintaining both versions in parallel, Slackware's build scripts, called SlackBuilds, were slowly transitioned to supporting either architecture, allowing for one set of sources for both versions.[28] Slackware64 saw its first stable release with version 13.0.

Between the November 2013 release of 14.1 and June 2016, Slackware saw a 31-month gap between releases, marking the longest span in release history. During this time the development branch went without updates for 47 days. However, on 21 April 2015, Patrick Volkerding apologized on the ChangeLog for the absence of updates and stated that the development team used the time to get "some good work done." There were over 700 program changes listed on that ChangeLog entry, including many major library upgrades. In January 2016, Volkerding announced the reluctant addition of PulseAudio, primarily due to BlueZ dropping direct ALSA support in v5.x. while various other projects were in turn dropping support for BlueZ v4.x. Knowing some users would not be happy with the change, he stated that "Bug reports, complaints, and threats can go to me." These changes culminated in the release of Slackware 14.2 in June 2016.[29]

Design philosophy[edit]

The design philosophy of Slackware is oriented toward simplicity, software purity,[clarification needed] and a core design that emphasizes lack of change to upstream sources. Many design choices in Slackware can be seen as a heritage of the simplicity of traditional Unix systems and as examples of the KISS principle.[30] In this context, "simple" refers to the simplicity in system design, rather than system usage. Thus, ease of use may vary between users: those lacking knowledge of command line interfaces and classic Unix tools may experience a steep learning curve using Slackware, whereas users with a Unix background may benefit from a less abstract system environment.[citation needed] In keeping with Slackware's design philosophy, and its spirit of purity, most software in Slackware uses the original configuration mechanisms supplied by the software's authors; however, for some administrative tasks, distribution-specific configuration tools are delivered.

Development model[edit]

There is no formal issue tracking system and no official procedure to become a code contributor or developer. The project does not maintain a public code repository. Bug reports and contributions, while being essential to the project, are managed in an informal way. All the final decisions about what is going to be included in a Slackware release strictly remain with Slackware's benevolent dictator for life, Patrick Volkerding.[31][32][33]

The first versions of Slackware were developed by Patrick Volkerding alone. Beginning with version 4.0, the official Slackware announce files list David Cantrell and Logan Johnson as part of the "Slackware team".[34] Later announce statements, up to release version 8.1, include Chris Lumens.[35] Lumens, Johnson and Cantrell are also the authors of the first edition of "Slackware Linux Essentials", the official guide to Slackware Linux.[36] The Slackware website mentions Chris Lumens and David Cantrell as being "Slackware Alumni", who "worked full-time on the Slackware project for several years."[32] In his release notes for Slackware 10.0 and 10.1 Volkerding thanks Eric Hameleers for "his work on supporting USB, PCI, and Cardbus wireless cards".[37][38] Starting with version 12.0 there is, for a second time, a team building around Volkerding. According to the release notes of 12.2, the development team consists of seven people. Future versions added people.[39] Since version 13.0, the Slackware team seems to have core members. Eric Hameleers gives an insight into the core team with his essay on the "History of Slackware Development", written on 3–4 October 2009 (shortly after the release of version 13.0).[31]

Packages[edit]

Management[edit]

The Slackware mascot: Tux smoking a pipe

Slackware's package management system, collectively known as pkgtools, can administer (pkgtool), install (installpkg), upgrade (upgradepkg), and remove (removepkg) packages from local sources. It can also uncompress (explodepkg) and create (makepkg) packages. The official tool to update Slackware over a network or the internet is slackpkg. It was originally developed by Piter Punk as an unofficial way to keep Slackware up-to-date. It was officially included in the main tree in Slackware 12.2,[40] having been included in extras/ since Slackware 9.1.[41] When a package is upgraded, it will install the new package over the old one and then remove any files that no longer exist in the new package. When running upgradepkg, it only confirms that the version numbers are different, thus allowing downgrading the package if desired.

Slackware packages are tarballs compressed using various methods. Starting with 13.0, most packages are compressed using xz (based on the LZMA compression algorithm), utilizing the .txz filename extension.[42] Prior to 13.0, packages were compressed using gzip (based on the DEFLATE compression algorithm), using the .tgz extension. Support for bzip2 and lzma compression was also added, using the filename extensions .tbz and .tlz respectively, although these are not commonly used.

Packages contain all the files for that program, as well as additional metadata files used by the package manager. The package tarball contains the full directory structure of the files and is meant to be extracted in the system's root directory during installation. The additional metadata files, located under the special install/ directory within the tarball, usually include a slack-desc file, which is a specifically formatted text file that is read by the package manager to provide users with a description of the packaged software,[43] as well as a doinst.sh file, which is a post-unpacking shell script allowing creation of symbolic links, preserving permissions on startup files, proper handling of new configuration files, and any other aspects of installation that can't be implemented via the package's directory structure.[44]

The package manager maintains a directory, /var/log/packages, where each package installed will have a corresponding install log file that lists the package size, both compressed and uncompressed, the software description, and the full path of all files that were installed.[45] It also maintains the directory /var/log/scripts containing all doinst.sh files to allow proper removal of installed symlinks. When a package is removed or upgraded, the old install logs and doinst.sh files are moved to /var/log/removed_package and /var/log/removed_scripts respectively, making it possible to review any previous packages and see when they were removed.

Dependency resolution[edit]

The package management system does not track or manage dependencies; however, when performing the recommended full install, all dependencies of the stock packages are met. For custom installations or 3rd-party packages, Slackware relies on the user to ensure that the system has all the supporting system libraries and programs required by the program. Since no official lists of dependencies for stock packages are provided, if users decide to install a custom installation or install 3rd-party software, they will need to work through any possible missing dependencies themselves. Since the package manager doesn't manage dependencies, it will install any and all packages, whether or not dependencies are met. A user may find out that dependencies are missing only when attempting to use the software.

While Slackware itself does not incorporate official tools to resolve dependencies, some unofficial, community-supported software tools do provide this function, similar to the way APT does for Debian-based distributions and yum does for Red Hat-based distributions. They include:

  • slapt-get is a command line utility that functions in a similar way to APT. While slapt-get does provide a framework for dependency resolution, it does not provide dependency resolution for packages included within the Slackware distribution. However, several community package sources and Slackware based distributions take advantage of this functionality. Gslapt is a graphical interface to slapt-get.
  • Swaret is a package management tool featuring dependency resolution. It was originally included in Slackware version 9.1 as an optional package, but did not contain dependency resolution at that time.[46] It was removed from the distribution with Slackware 10.0 and turned over to the community. It eventually added dependency resolution and roll-back functionality; however, as of May 2014, there are no active developers.[47]
  • NetBSD's pkgsrc provides support for Slackware, among other Unix-like operating systems. pkgsrc provides dependency resolution for both binary and source packages.

Repositories[edit]

There are no official repositories for Slackware. The only official packages Slackware provides are available on the installation media. However, there are many third-party repositories for Slackware; some are standalone repositories and others are for distributions that are Slackware-based but retain package compatibility with Slackware. Many of these can be searched at once using pkgs.org, which is a Linux package search engine. However, mixing and matching dependencies from multiple repositories can lead to two or more packages that require different versions of the same dependency, which is a form of dependency hell. Slackware itself won't provide any dependency resolution for these packages, however some projects will provide a list of dependencies that are not included with Slackware with the files for the package, commonly with a .dep extension.

Due to the possibility of dependency issues, many users choose to compile their own programs using community-provided SlackBuilds. SlackBuilds are shell scripts that will create an installable Slackware package from a provided software tarball. Since SlackBuilds are scripts, they aren't limited to just compiling a program's source; they can also be used to repackage pre-compiled binaries provided by projects or other distributions' repositories into proper Slackware packages. SlackBuilds that compile sources have several advantages over pre-built packages: since they build from the original author's source code, the user does not have to trust a third-party packager; furthermore the local compilation process allows for machine-specific optimization. In comparison to manual compilation and installation of software, SlackBuilds provide cleaner integration to the system by utilizing Slackware's package manager. Some SlackBuilds will come with an additional file with metadata that allows automated tools to download the source, verify the source is not corrupted, and calculate additional dependencies that are not part of Slackware.[48] Some repositories will include both SlackBuilds and the resulting Slackware packages, allowing users to either build their own or install a pre-built package.

The only officially endorsed[49] SlackBuilds repository is SlackBuilds.org, commonly referred to as SBo. This is a community-supported project offering SlackBuilds for building software not included with Slackware. Users are able to submit new SlackBuilds for software to the site and, once approved, they become the "package maintainer". They are then responsible for providing updates to the SlackBuild, either to fix issues or to build newer versions provided by upstream. To ensure all programs can be compiled and used, any required dependencies of the software not included with Slackware are required to be documented and be available on the site. All submissions are tested by the site's administrators before being added to the repository. The administrators intend for the build process to be nearly identical to the way Slackware's official packages are built, mainly to ensure Volkerding was "sympathetic of our cause". This allows SlackBuilds that Volkerding deems worthy to be pulled into regular Slackware with minimal changes to the script. It also prevent users from suggesting Volkerding to change his scripts to match SBo's.[50] SBo provides templates[51] for SlackBuilds and the additional metadata files and they encourage package maintainers to not deviate unless necessary.[52]

Two Slackware team members, Eric Hameleers and Robby Workman each have their own repository of pre-compiled packages along with the SlackBuilds and source files used to create the packages. While most packages are just additional software not included in Slackware that they felt was worth their time to maintain, some packages are used as a testbed for future upgrades to Slackware, most notably, Hameleers provides "Ktown" packages for newer versions of KDE.[53] He also maintains Slackware's "multilib" repository, enabling Slackware64 to run and compile 32bit packages.[27]

Releases[edit]

Slackware's release policy follows a feature and stability based release cycle, in contrast to the time-bound (e.g., Ubuntu) or rolling release (e.g., Gentoo Linux) schemes of other Linux distributions. This means there's no set time on when to expect a release. Volkerding will release the next version after he feels a suitable number of changes from the previous version have been made and those changes lead to a stable environment. As stated by Patrick Volkerding, "It's usually our policy not to speculate on release dates, since that's what it is — pure speculation. It's not always possible to know how long it will take to make the upgrades needed and tie up all the related loose ends. As things are built for the upcoming release, they'll be uploaded into the -current tree."[54]

Throughout Slackware's history, they generally try to deliver up-to-date software on at least an annual basis.[31] However, between Slackware 14.1 and 14.2, there was more than a 2-year gap between releases. From its inception, other than 2014 and 2015, Slackware had at least one release per year. Release activity peaked in 1994, 1995, 1997 and 1999, with three releases each year. Starting with version 7.1 (22 June 2000) the release progression became more stable and tended to occur once a year. Since then, the only years with two releases were 2003, 2005 and 2008.

Slackware's latest 32bit x86 and 64bit x86_64 stable releases are at version 14.2 (released on 30 June 2016), which include support for Linux 4.4.14.[2]

Volkerding also maintains a testing/developmental version of Slackware called "-current"[55] that can be used for a more bleeding edge configuration. This version will eventually become the next stable release, at which point Volkerding will start a new -current to start developing for the next release of Slackware. While this version is generally known to be stable, it is possible for things to break, so -current tends to not be recommended for production systems.[56]

x86 release history
Version Release date End-of-life date Kernel version Notable changes
Old version, no longer supported: 1.00[1] 1993-07-17 No EOL specified 0.99.11 Alpha
Old version, no longer supported: 1.1 1993-11-05 No EOL specified 0.99.13
Old version, no longer supported: 2.0 1994-07-02 No EOL specified 1.0.9
Old version, no longer supported: 2.1 1994-10-31 No EOL specified 1.1.59
Old version, no longer supported: 2.2 1995-03-30 No EOL specified 1.2.1
Old version, no longer supported: 2.3 1995-05-24 No EOL specified 1.2.8
Old version, no longer supported: 3.0 1995-11-30 No EOL specified 1.2.13 Transitioned from a.out to Executable and Linkable Format (ELF) and first release to be offered on CD-ROM[57]
Old version, no longer supported: 3.1 1996-06-03 No EOL specified 2.0.0 Named "Slackware 96", an allusion to Windows 95[58][59]
Old version, no longer supported: 3.2 1997-02-17 No EOL specified 2.0.29
Old version, no longer supported: 3.3 1997-06-11 No EOL specified 2.0.30
Old version, no longer supported: 3.4 1997-10-14 No EOL specified 2.0.30 Introduced ZipSlack[60]
Old version, no longer supported: 3.5 1998-06-09 No EOL specified 2.0.34
Old version, no longer supported: 3.6 1998-10-28 No EOL specified 2.0.35
Old version, no longer supported: 3.9 1999-05-10 No EOL specified 2.0.37pre10
Old version, no longer supported: 4.0 1999-05-17 No EOL specified 2.2.6 First release to require 1GB of space for full install and added KDE[33]
Old version, no longer supported: 7.0 1999-10-25 No EOL specified 2.2.13
Old version, no longer supported: 7.1 2000-06-22 No EOL specified 2.2.16 Added GNOME[33]
Old version, no longer supported: 8.0 2001-07-01 No EOL specified 2.2.19 Added Mozilla Browser and optional Linux 2.4
Old version, no longer supported: 8.1 2002-06-18 2012-08-01[61] 2.4.18 Switched from package naming from 8.3 to name-version-arch-build.tgz and evolved hdsetup to pkgtools
Old version, no longer supported: 9.0 2003-03-19 2012-08-01 2.4.20 (patched to 2.4.21)[62]
Old version, no longer supported: 9.1 2003-09-26 2012-08-01 2.4.22 (patched to 2.4.26)[41] Switched from OSS to ALSA[63]
Old version, no longer supported: 10.0 2004-06-23 2012-08-01 2.4.26 Switched from XFree86 to X.org Server
Old version, no longer supported: 10.1 2005-02-02 2012-08-01 2.4.29
Old version, no longer supported: 10.2 2005-09-14 2012-08-01 2.4.31 Removed GNOME desktop environment
Old version, no longer supported: 11.0 2006-10-02 2012-08-01 2.4.33.3 First release offered on DVD
Old version, no longer supported: 12.0 2007-07-01 2012-08-01 2.6.21.5 Switched from Linux 2.4 to 2.6 and added support for HAL and removed floppy disk installation support (except for PXE)
Old version, no longer supported: 12.1 2008-05-02 2013-12-09[64] 2.6.24.5
Old version, no longer supported: 12.2 2008-12-10 2013-12-09[65] 2.6.27.7 (patched to 2.6.27.31)[65]
Older version, yet still supported: 13.0 2009-08-26 No EOL announced 2.6.29.6 Added 64bit version and switched from KDE 3.5 to 4.x and switched from gzip to xz compressed packages
Older version, yet still supported: 13.1 2010-05-24 No EOL announced 2.6.33.4 Added PolicyKit and ConsoleKit and switched to the libata subsystem
Older version, yet still supported: 13.37 2011-04-27 No EOL announced 2.6.37.6 Added support for GPT and utilities for the Btrfs filesystem
Older version, yet still supported: 14.0 2012-09-28 No EOL announced 3.2.29 (patched to 3.2.83)[66] Added NetworkManager. Removed HAL as its functionality was merged into udev
Older version, yet still supported: 14.1 2013-11-04 No EOL announced 3.10.17 (patched to 3.10.104)[67] Added support for UEFI hardware
Current stable version: 14.2 2016-06-30 No EOL announced 4.4.14 (patched to 4.4.74)[29] Added PulseAudio and VDPAU and switched from udev to eudev and ConsoleKit to ConsoleKit2
Latest preview version of a future release: -current rolling N/A 4.9.34[68] Switched default encoding from ASCII to UTF-8, Python compiled using ucs4, and added system's lame, vulkansdk, SDL2, and FFmpeg[68]
Legend:
Old version
Older version, still supported
Latest version
Latest preview version
Future release

Support[edit]

Currently, Slackware has no officially stated support term policy. However, on 14 June 2012, notices appeared in the changelogs for versions 8.1,[69] 9.0, 9.1, 10.0, 10.1, 10.2, 11.0, and 12.0 stating that, effective 1 August 2012, security patches would no longer be provided for these versions. The oldest release, version 8.1, was released on 18 June 2002 and had over 10 years of support before reaching EOL. Later, on 30 August 2013, announcements were made on the changelogs of 12.1[70] and 12.2 stating their EOL on 9 December 2013. It was stated in the changelog entries that they had at least 5 years of support. As of November 2015, there have been no announcements from the Slackware team on when any versions of Slackware from 13.0 and up will be EOL.

While there has been no official announcements for versions prior to 8.1, they are no longer maintained and are effectively EOL.

Hardware architectures[edit]

Historically, Slackware concentrated solely on the IA-32 architecture and releases were available as 32-bit only. However, starting with Slackware 13.0, a 64-bit x86_64 variant is available and officially supported in symmetrical development with the 32-bit platform. Prior to the release of Slackware64 users wanting 64-bit were required to use unofficial ports such as slamd64.

Slackware is also available for the IBM S/390 architecture in the form of Slack/390 and for the ARM architecture under Slackware ARM (originally known as 'ARMedslack'). Both ports have been declared "official" by Patrick Volkerding.[71][72] However, the S/390 port is still at version 10.0 for the stable version and 11.0 for the testing/developmental version, and has had no updates since 2009.[73][74] Also, on 7 May 2016, the developer of Slackware ARM announced 14.1 will be EOL on 1 September 2016 and development of -current will cease with the release of 14.2, however support for 14.2 will be maintained for the foreseeable future.[75] The EOL announcement for 14.1 was added to the changelog on 25 June 2016.[76]

In July 2016, the developer of Slackware ARM announced that the development and build tools had been enhanced to reduce the manual effort involved in maintaining the ARM port, and proceeded to announce that a 32-bit hardware floating port was in development. The port was released in August 2016 in "current" form.[77]

Slackintosh is an unofficial port of Slackware to the "New World" Macintosh's PowerPC architecture. Slackintosh's final release was 12.1. Slackintosh is no longer being maintained.[78]

Distribution[edit]

The latest stable version of Slackware can be ordered from the official Slackware store as a 6-CD set or as a single Dual-DVD. The CD set is targeted at the 32bit IA-32 platform but also runs on 64bit x86_64 processors in 32-bit mode. The DVD contains both the 32bit and 64bit versions.

Slackware ISO images for the CD set and the DVD can also be downloaded for free via BitTorrent or from various FTP and HTTP mirrors.

The distributions of the ports for the ARM architecture and for IBM S/390 are neither available as CD/DVDs nor as ISO images, but can be downloaded. Slackware S/390 installs from a DOS Partition or from floppy disk.[79] Slackware ARM does not distribute ISO files because most ARM devices can not boot from a CD or DVD.[80] Instead, it is installed off a network, using Das U-Boot and a TFTP boot server[81] or from a mini-root filesystem.[82] Slackware ARM can also be installed on a PC running QEMU[83] using the same technique.

Use[edit]

Slackware family tree

DistroWatch shows a decreasing but still substantial interest regarding Slackware. In 2002 the Slackware page was ranked as number 7,[84] but dropped to number 10 by 2005.[85] In 2006 it reached number 9,[86] whereas since then being constantly below the ten most popular pages. In 2010 it had been listed as number 11,[87] in the years 2011[88] and 2012[89] as number 12, and in 2015 as number 33.[90]

However, since DistroWatch only tracks visitors to the various distributions' pages, they state their ranking doesn't always correlate with the usage of a distribution, only the popularity of that distribution on their site. Because of this, their rankings "should not be used to measure the market share of distributions."[91] Many people who are already familiar with a distribution may have no need to visit DistroWatch, so their trends could be applied more toward either new or potentially new users who are curious about a distribution.

Currently, there is no official method to track the usage or number of installs of Slackware.

References[edit]

  1. ^ a b c Patrick J. Volkerding (17 Jul 1993). "ANNOUNCE: Slackware Linux 1.00". Newsgroupcomp.os.linux. Usenet: 227gd4$jtq@usenet.INS.CWRU.Edu. Retrieved 5 December 2014. 
  2. ^ a b Slackware Release Announcement, The Slackware Linux Project, 30 June 2016 
  3. ^ SUSE distributions (Slackware-based)
  4. ^ Slackware-based Linux Distributions
  5. ^ Distrowatch.com. "Top Ten Distributions". Retrieved 2017-07-22. 
  6. ^ "The Slackware Linux Project: General Information". Slackware.com. Retrieved 2017-07-22. 
  7. ^ Slackware Inc. "Slackware FAQ: Slackware Linux has a reputation for being tough for newbies. Is this true?". 
  8. ^ Datamation. "Top Linux Distros For Every Level User". 
  9. ^ Linux.org. "Which Distro is Right for Me?". 
  10. ^ Tech Radar. "Power user Linux distros: 5 reviewed and rated". 
  11. ^ IT Pro. "Slackware Linux - Less is more". 
  12. ^ PC World. "A Guide to Today's Top 10 Linux Distributions". 
  13. ^ "FreeSlack". FreeSlack,net. Retrieved 2017-07-22. 
  14. ^ a b Hughes, Phil (1 April 1994). "Interview with Patrick Volkerding". Linux Journal. Retrieved 3 July 2007. 
  15. ^ "Slackware Graphics and Link Banners". Slackware.com. Retrieved 2017-07-22. 
  16. ^ [1][dead link]
  17. ^ "This file must be present to signal to 'setup' that this is the last directory in this package series." (TXT). Mirrors.slackware.com. Retrieved 2017-07-22. 
  18. ^ "A Short History of Linux Distributions". Lwn.net. Retrieved 2017-07-22. 
  19. ^ Stefan Strobel; Volker Elling (1 January 1997). LINUX. Springer. pp. 82–83. ISBN 978-0-387-94880-5. Retrieved 4 August 2013. 
  20. ^ "The Slackware Linux Project: Slackware Release Announcement". Slackware.com. 1993-07-16. Retrieved 2017-07-22. 
  21. ^ "README.210 Slackware Release 2.1". Ftp.df.lth.se. Retrieved 2017-07-22. 
  22. ^ "The Slackware Linux Project: Frequently Asked Questions". Slackware.com. Retrieved 2017-07-22. 
  23. ^ [2][dead link]
  24. ^ [3][dead link]
  25. ^ "Gnome Removed From Slackware - Slashdot". tech.slashdot.org. 
  26. ^ [4][dead link]
  27. ^ a b "Index of /~alien/multilib". Slackware.com. Retrieved 2017-07-22. 
  28. ^ "Interview with Eric Hameleers: Why You Should Try Slackware". Linux Magazine. 
  29. ^ a b "This update contains security fixes and improvements." (TXT). Slackware.cs.utah.edu. Retrieved 2017-07-22. 
  30. ^ "Slackware Linux Basics, Chapter 2" (PDF). Rlworkman.net. Retrieved 2017-07-22. 
  31. ^ a b c "History of Slackware Development" (PDF). Connie.slackware.com. Retrieved 2017-07-22. 
  32. ^ a b "Slackware Alumni". slackware.com. Retrieved 20 September 2014. 
  33. ^ a b c "Stories of Linux: A Look at Slackware Linux". linux.com. 
  34. ^ Announcement of Slackware 4.0
  35. ^ Announcement of Slackware 8.1
  36. ^ "The Revised Slackware Book Project". Slackbook.org. Retrieved 26 May 2015. 
  37. ^ [5][dead link]
  38. ^ [6][dead link]
  39. ^ [7][dead link]
  40. ^ "This file documents the instructions for upgrading to Slackware 12.1, the packages added, removed, renamed, and/or split during the development cycle from Slackware 12.1 through 12.2, and some potential "gotchas" that users can avoid by arming themselves with a little knowledge." (TXT). Slackware.mirrors.tds.net. Retrieved 2017-07-22. 
  41. ^ a b "Fixed incorrect type (int copy should be png_size_t copy) in png_inflate() : (fixes CVE-2011-3045)." (TXT). Slackware.cs.utah.edu. Retrieved 2017-07-22. 
  42. ^ "Fixes security issues including : External entity infinite loop DoS" (TXT). Slackware.cs.utah.edu. Retrieved 2017-07-22. 
  43. ^ "Slack-desc - SlackWiki". Slackwiki.com. Retrieved 2017-07-22. 
  44. ^ "Doinst.sh - SlackWiki". Slackwiki.com. Retrieved 2017-07-22. 
  45. ^ "slackware:package_management_hands_on - SlackDocs". Docs.slackware.com. Retrieved 2017-07-22. 
  46. ^ "The Slackware Linux Project: Slackware Release Announcement". Slackware.com. Retrieved 26 May 2015. 
  47. ^ "SWareT / Discussion / Open Discussion:Is swaret dead?". sourceforge.net. 
  48. ^ websightdesigns.com, WebSight Designs -. "SlackBuilds.org". slackbuilds.org. 
  49. ^ "Slackware 14.2 is coming , but will the slackbuilds will also be updated accordingly?". Linuxquestions.org. 
  50. ^ "Ten years of SlackBuilds.org". Alien.dslackbook.org. 10 June 2016. Retrieved 2017-07-22. 
  51. ^ "Index of /templates". slackbuilds.org. 
  52. ^ websightdesigns.com, WebSight Designs -. "SlackBuilds.org". slackbuilds.org. 
  53. ^ "Index of /ktown". alien.slackbook.org. 
  54. ^ "The Slackware Linux Project: Frequently Asked Questions". Slackware.com. Retrieved 26 May 2015. 
  55. ^ "The Slackware Linux Project: Slackware ChangeLogs". Slackware.com. Retrieved 26 May 2015. 
  56. ^ "slackware:current - SlackDocs". Docs.slackware.com. Retrieved 2017-07-22. 
  57. ^ "CDROM.txt file in the Slackware 3.0 repository". Slackware.cs.utah.edu. Retrieved 2017-07-22. 
  58. ^ [8][dead link]
  59. ^ 2002-2012 Andrew Maltsev, 2012-2013 Derek J. Curtis. "Linux Slackware 96". Isbndb.com. Retrieved 26 May 2015. 
  60. ^ "zipslack/: Added a super-easy to install UMSDOS installation -- zipslack.zip, a 33 megabyte complete Linux system as a Zip file. The installation will fit on a FAT formatted Zip disk, or works on any FAT or FAT32 filesystem in a \LINUX directory. This is based on the soon-to-be-released Slackware 3.5-beta, with 2.0.33, egcs-1.0.2, libc-5.4.44" (TXT). Slackware.cs.utah.edu. Retrieved 2017-07-22. 
  61. ^ 8.1 ChangeLog.txt
  62. ^ [9][dead link]
  63. ^ "Release Notes for Slackware 9.1". Mirrors.slackware.com. Retrieved 2017-07-22. 
  64. ^ 12.1 ChangeLog.txt
  65. ^ a b 12.2 ChangeLog.txt
  66. ^ [10][dead link]
  67. ^ [11][dead link]
  68. ^ a b "The Slackware Linux Project: Slackware ChangeLogs". Slackware.com. Retrieved 2017-05-29. 
  69. ^ [12][dead link]
  70. ^ [13][dead link]
  71. ^ "The Slackware Linux Project: Slackware Ports". Slackware.com. Retrieved 26 May 2015. 
  72. ^ Stuart Winter. "Slackware ARM". Slackware.com. Retrieved 26 May 2015. 
  73. ^ "Change log of Slack390". Ftp.nluug.nl. Retrieved 2017-07-22. 
  74. ^ "Change log of Slack390x". Ftp.nluug.nl. Retrieved 2017-07-22. 
  75. ^ "Slackware ARM 14.1 and -current End of Life Announcement". www.linuxquestions.org. 
  76. ^ [14][dead link]
  77. ^ "Hard float port now available". www.linuxquestions.org. 
  78. ^ "Slackintosh homepage". 
  79. ^ "Search results for "slack390"". Distro.ibiblio.org. Retrieved 26 May 2015. 
  80. ^ Stuart Winter. "Slackware ARM: Get Slack". Arm.slackware.com. Retrieved 26 May 2015. 
  81. ^ "Slackware Arm: Installation". Arm.slackware.com. Retrieved 28 May 2015. 
  82. ^ README.txt file for mini-root filesystem, Slackware ARM
  83. ^ Installation instructions for Slackware ARM (Qemu)
  84. ^ "DistroWatch.com: Put the fun back into computing. Use Linux, BSD.". Distrowatch.com. Retrieved 2017-07-22. 
  85. ^ "DistroWatch.com: Put the fun back into computing. Use Linux, BSD.". Distrowatch.com. Retrieved 2017-07-22. 
  86. ^ "DistroWatch.com: Put the fun back into computing. Use Linux, BSD.". Distrowatch.com. Retrieved 2017-07-22. 
  87. ^ "DistroWatch.com: Put the fun back into computing. Use Linux, BSD.". Distrowatch.com. Retrieved 2017-07-22. 
  88. ^ "DistroWatch.com: Put the fun back into computing. Use Linux, BSD.". Distrowatch.com. Retrieved 2017-07-22. 
  89. ^ "DistroWatch.com: Put the fun back into computing. Use Linux, BSD.". Distrowatch.com. Retrieved 2017-07-22. 
  90. ^ "DistroWatch.com: Put the fun back into computing. Use Linux, BSD.". Distrowatch.com. Retrieved 2017-07-22. 
  91. ^ "DistroWatch.com: Put the fun back into computing. Use Linux, BSD.". Distrowatch.com. Retrieved 2017-07-22. 

External links[edit]