Three years ago, I started a personal project related to my favorite GNU/Linux, Slackware, this distribution was created in 1993 by Patrick Volkerding.
Originally based on SLS Linux, Slackware is the oldest GNU/Linux distribution still in maintenance.
The main philosophy is based on principles such as KISS (Keep it simple stupid) or keep it simple and stable,
referring to a design point of view, instead of being easy to use.
Your init scripts are init of BSD, this allows that in a transparent and simple way be
create or changed, unlike System V.
The package system is also minimalist, it has dependency managers such as slackpkg, slapt-get,
Some of these tools determine the dependencies by analyzing the installed packages,
determining what libraries are needed, and then discovering which packages are available.
This automatic process, very similar to the Debian APT and generally produces satisfactory results.
Slackware is a distribution that does not focus on having the latest versions of the programs,
but its focus is to have a stable system. The new packages are tested and are not delivered
until they are stable (this does not imply that it is the latest available version of the program),
for example, the Linux 2.6 kernel was not included until 2007, having been released
version 2.6.0 in the year 2003.
But when some package has an update for bugs or
security improvements, these are incorporated into the Slackware packages and advertised through
from a mailing list of those updates and in the change log that is
found on the website. Slackware includes inside the / extra directory of the installation CD
the Slackpkg program that helps keep the system updated.
To keep up-to-date with new security updates, I created a bot called Slackawaresa.
This bot read from changes list(changelog) and posts the messages in the SlackwareSecAdv twitter account.
Please, feel free to follow the SlackwareSecAdv on twitter to get the latest security updates advisors.
Git Hub SourceCode
Twitter Account Link