[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
slackware:philosophy [2012/08/21 08:27 (UTC)] – [Sources] vharishankar | slackware:philosophy [2012/08/23 15:24 (UTC)] – ben | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== The Slackware | + | ====== The Slackware |
Line 6: | Line 6: | ||
The main highlights and features of Slackware and the philosophy behind the distribution can be summarized as below. | The main highlights and features of Slackware and the philosophy behind the distribution can be summarized as below. | ||
- | ===== Distribution | + | ===== Distribution |
- | Slackware is, | + | Slackware is: |
* A distribution that can be installed entirely offline with the CD/DVD set. | * A distribution that can be installed entirely offline with the CD/DVD set. | ||
- | * A distribution which releases | + | * A distribution which is released |
* A distribution where " | * A distribution where " | ||
* A distribution where system configuration and administration is done through simple ncurses helper scripts or by by directly editing well-commented configuration files through a text editor. | * A distribution where system configuration and administration is done through simple ncurses helper scripts or by by directly editing well-commented configuration files through a text editor. | ||
Line 16: | Line 16: | ||
* A distribution that does not add layers of abstraction or complexity on top of existing solutions. For instance, Slackware package management is handled by simple scripts acting on compressed tarball package files (*.tgz, *.txz, *.tbz) and there is no dependency handling for package management. | * A distribution that does not add layers of abstraction or complexity on top of existing solutions. For instance, Slackware package management is handled by simple scripts acting on compressed tarball package files (*.tgz, *.txz, *.tbz) and there is no dependency handling for package management. | ||
* A distribution which abides by the common-sense dictum "if it's not broken, don't fix it." | * A distribution which abides by the common-sense dictum "if it's not broken, don't fix it." | ||
- | * A distribution where the major decisions are taken by the BDFL (Benevolent Dictator for Life, the current chief maintainer Patrick Volkerding) and where the development process is more closed than purely community based distributions. As a result, Slackware is highly | + | * A distribution where the major decisions are taken by the BDFL (Benevolent Dictator for Life, the current chief maintainer Patrick Volkerding) and where the development process is more closed than purely community based distributions. As a result, Slackware is highly |
===== Community ===== | ===== Community ===== | ||
Line 22: | Line 22: | ||
A few highlights of the Slackware Linux community may be mentioned. Even though technically a commercial distribution (the chief maintainer of Slackware, Patrick Volkerding sells the product on CD/DVD to support himself and the project financially, | A few highlights of the Slackware Linux community may be mentioned. Even though technically a commercial distribution (the chief maintainer of Slackware, Patrick Volkerding sells the product on CD/DVD to support himself and the project financially, | ||
- | The availability of a large number of [[slackware: | + | The availability of a large number of [[slackware: |
=====Sources===== | =====Sources===== | ||
* Originally written by [[wiki: | * Originally written by [[wiki: |