[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
Next revisionBoth sides next revision
howtos:slackware_admin:systemupgrade [2012/10/01 17:34 (UTC)] – [System Upgrade using SlackPkg] tommychowtos:slackware_admin:systemupgrade [2013/02/03 21:06 (UTC)] – Moved "Java considerations" to bottom of article. alienbob
Line 30: Line 30:
  
  
-===== System Upgrade Using SlackPkg =====+===== System Upgrade using SlackPkg =====
  
 The following steps should work for all situations: The following steps should work for all situations:
Line 47: Line 47:
 [0-9]+alien [0-9]+alien
 [0-9]+compat32 [0-9]+compat32
-</code> 
-   
-  * You can also blacklist packages that you don't want to upgrade.<code> 
-hal                     # hald is no longer in Slackware 14.0 and above, but some may still want it. 
-kde/*                   # This will blacklist all the packages in the kde directory of the slackware tree. 
-kdei/                 # Although you can use wildcards as shown above and on this line, it is NOT recommended. 
-xfce/                 # The xfce directory is new in Slackware 14.0. In 13.37 and below, xfce is its own package. 
 </code> </code>
  
Line 142: Line 135:
 # upgradepkg --install-new slackware64-compat32/*-compat32/*.t?z # upgradepkg --install-new slackware64-compat32/*-compat32/*.t?z
 </code> Alternatively you can run the "''massconvert32.sh''" script which will have been installed as part of the ''compat32-tools'' package. Pass it a 32-bit Slackware package directory (or a 32-bit Slackware mirror URL) as parameter and that will create a set of converted "''compat32''" packages which you can then install. You would only have to do this if you suspect that the content of the "''slackware64-compat32''" directory is not up to date. </code> Alternatively you can run the "''massconvert32.sh''" script which will have been installed as part of the ''compat32-tools'' package. Pass it a 32-bit Slackware package directory (or a 32-bit Slackware mirror URL) as parameter and that will create a set of converted "''compat32''" packages which you can then install. You would only have to do this if you suspect that the content of the "''slackware64-compat32''" directory is not up to date.
 +
 +
 +===== Java considerations =====
 +
 +Slackware used to install a //Java Run-time Engine// prior to the 14.0 release (the JRE binaries were originally Sun's and later distributed by Oracle after it bought Sun). \\ But Oracle changed the re-distribution license so that Slackware (just like all other distributions) was no longer permitted to ship these Java binaries as part of the distribution. When you perform a //system upgrade// to Slackware 14.0, an old version of the //JRE// will stay behind on your system. This version "6u25" has several critical vulnerabilities and you should remove it manually from your computer as fast as possible, using the command <code>removepkg jre</code> If you need Java then please have a look in the "''/extra/source/java''" directory of the Slackware 14 release. You will find a script there to create a Slackware package from the most recent Java software from Oracle, which you can then install using the "''installpkg''" command. See also our Wiki article "[[howtos:software:java|Java in Slackware]]"
  
  
 howtos:slackware_admin:systemupgrade ()