[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 revision
Previous revision
howtos:slackware_admin:using_slackwares_kernel_build_scripts [2019/04/24 18:47 (UTC)] divehowtos:slackware_admin:using_slackwares_kernel_build_scripts [2019/04/25 04:10 (UTC)] (current) – Added note about slackpkg blacklisting. dive
Line 75: Line 75:
 will only upgrade another huge kernel with the same local version. However, the will only upgrade another huge kernel with the same local version. However, the
 headers and source packages //will// upgrade the currently installed stock headers and source packages //will// upgrade the currently installed stock
-packages. If you use slackpkg then these will need blacklisting to avoid being +packages. 
-downgraded back to the stock versions.+ 
 +<note> 
 +If you use slackpkg then the kernel-source and kernel-headers will need 
 +blacklisting to avoid being downgraded back to the stock versions. 
 + 
 +If upgrading the stock kernels then you would also need to blacklist those for 
 +the same reason. 
 +</note>
  
 **Assumptions:** **Assumptions:**
Line 128: Line 135:
 Default if not set: automatic from `uname -m` Default if not set: automatic from `uname -m`
  
 +There are other variables used in the Slackbuilds but these are the most significant for our purpose.
 ==== Mirroring The Kernel Slackbuild Directory ==== ==== Mirroring The Kernel Slackbuild Directory ====
  
Line 268: Line 276:
 (The generic script is also used to make the huge kernel.) (The generic script is also used to make the huge kernel.)
  
-=== The Variables ===+=== Setting The Variables ===
  
 After placing the relevant configs in k/kernel-configs/ and the kernel source After placing the relevant configs in k/kernel-configs/ and the kernel source
Line 479: Line 487:
 /boot/vmlinuz /boot/vmlinuz
  
-This saves having to re-edit /etc/lilo.conf at every upgrade, though **lilo still+This saves having to re-edit /etc/lilo.conf at every upgrade, although **lilo still
 needs running afterwards.** needs running afterwards.**
  
 howtos:slackware_admin:using_slackwares_kernel_build_scripts ()