[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/20 07:30 (UTC)] – [Community] vharishankar | slackware:philosophy [2012/08/23 00:26 (UTC)] – [Distribution philosophy] - capitalization correction nocturnal.slacker | ||
---|---|---|---|
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 when stable and does not have a fixed schedule of updates. Every release of Slackware Linux is thoroughly tested by the Slackware team and the community. | + | * A distribution which releases when stable and does not have a fixed schedule of releases. Every release of Slackware Linux is thoroughly tested by the Slackware team and the community. Slackware places high value on stability in preference to " |
* 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. | ||
* A distribution that prefers to package " | * A distribution that prefers to package " | ||
* 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 where the chief 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 focussed on its core strengths and values and does not cater to every preference of its community or others. For this reason, there is less pressure on the Slackware development team to be popular and cater to the larger mass market. | + | |
+ | | ||
===== Community ===== | ===== Community ===== | ||
- | 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 DVD for supporting | + | 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 |
The availability of a large number of [[slackware: | The availability of a large number of [[slackware: | ||
+ | |||
+ | =====Sources===== | ||
+ | * Originally written by [[wiki: |