Welcome to Slackware!
Originally Posted by mreff555
Me too. I haven't completely figured out how they work yet but they are much simpler than e-builds making them easier to tweak.
Oh btw, is there a standardized place I should be keeping my builds? Right now I just have them in a directory I set up called "/root/packages".
Personal choice, maybe on a secondary storage for future use elsewhere so you can build on other installs.
Slackware Doc Project
The Slackware Way Slackware maintains a KISS philosophy. It uses text files for configuration instead of GUI configuration programs like many other distributions.
The main highlights and features of Slackware and the philosophy behind the distribution can be summarized as below.
- A distribution that can be installed entirely offline with the CD/DVD set.
- A distribution which is released when stable and not according to a fixed schedule. Every release of Slackware Linux is thoroughly tested by the Slackware team and the community. Slackware places high value on stability rather than the “newness” or “freshness” of software.
- A distribution where “simplicity” is preferred over “convenience.” The lack of GUI helpers (common in many other commercial distributions) for system administration tasks is a case in point.
- A distribution where system configuration and administration is done through simple ncurses helper scripts or by directly editing well-commented configuration files through a text editor.
- A distribution that prefers to package “vanilla” software or software that hasn't been modified from upstream development. Little or no patching is done to upstream software and as a result, the software found in Slackware works as closely to what was intended by the original creators as practically possible.
- 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 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 focused 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.
is a very useful tool for everyone.