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

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
slackware:package_management [2012/12/30 05:57 (UTC)] – correcting the headings mfillpotslackware:package_management [2013/02/20 20:10 (UTC)] – [Brief Explanation of Slackware Packages] Typo fixes alienbob
Line 13: Line 13:
  
 In terms of security and accountability Slackware is excellent because it In terms of security and accountability Slackware is excellent because it
-beings you software in the condition that the authors intended. What this+brings you software in the condition that the authors intended. What this
 means is that the Slackware community does not modify the source or add and means is that the Slackware community does not modify the source or add and
 remove functions from software beyond the author's design, unless a small remove functions from software beyond the author's design, unless a small
Line 29: Line 29:
 result in exploits that only effect the specific distribution which can result in exploits that only effect the specific distribution which can
 remain unseen remain unseen
-for some time because the original authors (those who know the applicationss best)+for some time because the original authors (those who know the applications best)
 were not responsible for the changes or aware of the changes. This additional were not responsible for the changes or aware of the changes. This additional
 liability is something that an administrator does not want hanging over their liability is something that an administrator does not want hanging over their

Trace:

slackware:package_management ()