sanitizing_slackware
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| sanitizing_slackware [2016/01/16 22:42] – [Upgrading] connie | sanitizing_slackware [2018/04/09 16:49] (current) – connie | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Sanitizing Slackware ====== | ====== Sanitizing Slackware ====== | ||
| - | The steps to deblob an existing Slackware installation would be quite easy if not for the necessity to replace the non-free kernel. While the task of rebuilding the kernel is arguably easier in Slackware than in many other GNU/Linux distributions, | + | The steps to deblob an existing Slackware installation would be quite easy if not for the necessity to replace the non-free kernel. While the task of rebuilding the kernel is arguably easier in Slackware than in many other GNU/Linux distributions, |
| That being said, you can de-blob Slackware in a completely manual fashion by doing this: | That being said, you can de-blob Slackware in a completely manual fashion by doing this: | ||
| Line 17: | Line 17: | ||
| ===== Caveats ===== | ===== Caveats ===== | ||
| - | Please be aware that as long as you keep using the official repository, non-free packages may still creep in during updates, unlikely as it is. We see no easy cure for this, short of switching to a free repository. | + | Please be aware that as long as you keep using the official repository, non-free packages may still creep in during updates, unlikely as it is. We see no easy cure for this, short of switching to a [[Free Repository|free repository]]. |
sanitizing_slackware.1453002120.txt.gz · Last modified: 2016/01/16 22:42 by connie