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 revision Previous revision
Next revision
Previous revision
howtos:slackware_admin:systemupgrade [2013/02/03 21:06 (UTC)]
alienbob Moved "Java considerations" to bottom of article.
howtos:slackware_admin:systemupgrade [2018/11/17 00:25 (UTC)]
enzuru [System Upgrade using SlackPkg]
Line 60: Line 60:
 </​code>​ That final ''​new-config''​ command is there so that you can view the difference betweeen your old and the new ''​slackpkg''​ configuration files, in particular ''/​etc/​slackpkg/​mirrors''​ and ''/​etc/​slackpkg/​blacklist''​ are files you have to check. Overwriting ''/​etc/​slackpkg/​slackpkg.conf''​ is usually recommended. </​code>​ That final ''​new-config''​ command is there so that you can view the difference betweeen your old and the new ''​slackpkg''​ configuration files, in particular ''/​etc/​slackpkg/​mirrors''​ and ''/​etc/​slackpkg/​blacklist''​ are files you have to check. Overwriting ''/​etc/​slackpkg/​slackpkg.conf''​ is usually recommended.
  
-  * A new Slackware release usually has a newer version of the GNU C libraries. The new packages are compiled against that new ''​glibc''​ version. In order to prevent an upgrsde ​failure, you need to upgrade the ''​glibc-solibs''​ package manually, immediately after upgrading ''​slackpkg'':​ <​code>​+  * A new Slackware release usually has a newer version of the GNU C libraries. The new packages are compiled against that new ''​glibc''​ version. In order to prevent an upgrade ​failure, you need to upgrade the ''​glibc-solibs''​ package manually, immediately after upgrading ''​slackpkg'':​ <​code>​
 # slackpkg upgrade glibc-solibs # slackpkg upgrade glibc-solibs
 </​code>​ Let me give an example of such potential failure: when ''​slackpkg install-new''​ installs the ''​libusb-compat''​ package, your ''​gpg''​ command stops working because it links against libusb.so which will be overwritten with the version from the new ''​libusb-compat''​ package. The new library needs the new ''​glibc''​ package, ''​gpg''​ stops working because of the library linking error, and ''​slackpkg''​ will stop the system upgrade because it wants to check every package'​s gpg signature before upgrading it. Upgrading the ''​glibc-solibs''​ package prevents the library linking errors by providing the correct "''​GLIBC''"​ symbols. </​code>​ Let me give an example of such potential failure: when ''​slackpkg install-new''​ installs the ''​libusb-compat''​ package, your ''​gpg''​ command stops working because it links against libusb.so which will be overwritten with the version from the new ''​libusb-compat''​ package. The new library needs the new ''​glibc''​ package, ''​gpg''​ stops working because of the library linking error, and ''​slackpkg''​ will stop the system upgrade because it wants to check every package'​s gpg signature before upgrading it. Upgrading the ''​glibc-solibs''​ package prevents the library linking errors by providing the correct "''​GLIBC''"​ symbols.
Line 106: Line 106:
 </​code>​ Note that this command adds a "​initrd"​ line to the kernel section. If you let ''​mkinitrd''​ create a unique name for your initial ramdisk, then be sure to apply that name in the above section. \\ The "​initrd"​ line is not needed if you are going to run a "​huge"​ kernel. </​code>​ Note that this command adds a "​initrd"​ line to the kernel section. If you let ''​mkinitrd''​ create a unique name for your initial ramdisk, then be sure to apply that name in the above section. \\ The "​initrd"​ line is not needed if you are going to run a "​huge"​ kernel.
  
-  * Finally, run the "''​lilo''"​ command to make the change permanent and add the new kernel to the lilo boot menu. \\ Remember, you should always be able to boot back into a previous kernel in case the new Slackware kernel gives you a hard time.+  * Finally, run the "''​lilo''"​ command to make the change permanent and add the new kernel to the lilo boot menu. You can just run "''​eliloconfig''"​ if you are using EFI after upgrading Slackware and that will itself install the latest kernel on the EFI partition. \\ Remember, you should always be able to boot back into a previous kernel in case the new Slackware kernel gives you a hard time.
  
  

In Other Languages
QR Code
QR Code howtos:slackware_admin:systemupgrade (generated for current page)