User Tools

Site Tools


sanitizing_slackware

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
sanitizing_slackware [2016/01/16 22:39] conniesanitizing_slackware [2018/04/07 18:36] 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, it is not for beginners. If you don't feel like learning to build the kernel, feel welcome to use our [[free repository]] to obtain binary kernel packages. As a middle ground, you can use our [[http://freeslack.net/fxp/slackware64-14.1/source/fxp/build/linux-libre/|kernel build script]] to make your own packages from [[http://www.fsfla.org/ikiwiki/selibre/linux-libre/|Linux-libre]] source.+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, it is not for beginners. If you don't feel like learning to build the kernel, feel welcome to use our [[free repository]] to obtain binary kernel packages. As a middle ground, you can use our [[http://www.freenix.net/fxp/freeslack64-14.2/source/fxp/build/linux-libre/|kernel build script]] to make your own packages from [[http://www.fsfla.org/ikiwiki/selibre/linux-libre/|Linux-libre]] source.
  
 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 8: Line 8:
   - Regardless of its status, keep using the stock kernel headers package ''kernel-headers'' as if it was free. It is in fact free, and replacing it manually is a pain.    - Regardless of its status, keep using the stock kernel headers package ''kernel-headers'' as if it was free. It is in fact free, and replacing it manually is a pain. 
   - Blacklist the offending Slackware packages in ''/etc/slackpkg/blacklist''. Make sure package names occupy separate lines, and avoid white space.   - Blacklist the offending Slackware packages in ''/etc/slackpkg/blacklist''. Make sure package names occupy separate lines, and avoid white space.
-  - Build and install a free kernel together with modules (for example, [[http://www.fsfla.org/ikiwiki/selibre/linux-libre/|Linux-libre]]). See [[http://alien.slackbook.org/dokuwiki/doku.php?id=linux:kernelbuilding|here]] for some kernel-building tips. Do not uninstall the stock kernel yet, in case the new kernel throws a fit.+  - Build and install a free kernel together with modules (for example, [[http://www.fsfla.org/ikiwiki/selibre/linux-libre/|Linux-libre]]). The official documentation provides a [[http://docs.slackware.com/start?id=howtos%3Aslackware_admin%3Akernelbuilding|description of this process]]. Do not uninstall the stock kernel yet, in case the new kernel throws a fit.
   - Boot into the free kernel and remove the non-free Slackware packages with ''removepkg''.   - Boot into the free kernel and remove the non-free Slackware packages with ''removepkg''.
  
 ===== Upgrading ===== ===== Upgrading =====
  
-We haven't tried this, but we don't know of a reason why it wouldn't work. Get the Slackware DVD, unpack it into a directory, remove all non-free packages, and then upgrade as usual.+We haven't tried this, but we don't know of a reason why it wouldn't work. Make a local copy of the Slackware repository, remove all non-free packages, and then upgrade as usual.
  
 ===== 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.txt · Last modified: 2018/04/09 16:49 by connie