Enjoy the Holiday season!

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
talk:howtos:slackware_admin:systemupgrade [2012/09/29 03:19 (UTC)]
escaflown
talk:howtos:slackware_admin:systemupgrade [2018/04/23 21:41 (UTC)] (current)
rkfb
Line 14: Line 14:
 Hi Eric. Very nice job. Just a question here: shouldn't slackpkg be updated using the slackware media before its first usage? My reasoning is that at the first usage the mirrors file won't have 14.0 mirrors for example if I'm upgrading from 13.37 to 14.0.   --- //[[wiki:user:escaflown|escaflown]] 2012/09/28 21:18// Hi Eric. Very nice job. Just a question here: shouldn't slackpkg be updated using the slackware media before its first usage? My reasoning is that at the first usage the mirrors file won't have 14.0 mirrors for example if I'm upgrading from 13.37 to 14.0.   --- //[[wiki:user:escaflown|escaflown]] 2012/09/28 21:18//
  
 +------------------------------------------
 +I believe, its worth to mention that, the user must change the file in /etc/slackpkg/mirrors ,to make sure that the version link, they are trying is in the list.
 +I just blanked for some minutes, when I did the upgrade process, since every thing for 13.37 is up-to-date. After changing a mirror link to 14.0, things started to progress... - [[http://docs.slackware.com/wiki:user:crond|crond]]
 +
 +> Hi crond, I hope I addressed your concerns properly in my update. \\  --- //[[wiki:user:alienbob|Eric Hameleers]] 2012/10/01 13:23//
 +------
 +
 +TommyC, please respect the [[slackdocs:styleguide#policy_rule|policy rule]] and suggest your changes in the discussion page instead of recklessly editing an article which is not yours. I have issues with these additions: \\ 
 +//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> First, __**not**__ removing ''hal'' is an advice I do not want to see in an upgrade guide. Instead, it should be listed as a suggestion in this article's discussion page. \\ Second, the use of //asterisks// in the ''slackpkg'' blacklist does not work reliably (for instance it will not have the desired effect on the ''slackpkg install-new'' command). Therefore it does not belong in article which promises the reader a "painless" upgrade. \\ Also, why would you want to blacklist KDE and XFCE? If you did not have it installed, it will not be upgraded anyway, you don't have to blacklist it. And anyway, with a blacklist in place the ''slackpkg install-new'' command will still list all the new KDE and XFCE packages, which will lead to confusion. \\  --- //[[wiki:user:alienbob|Eric Hameleers]] 2012/10/01 13:23//
 +
 +A very useful page, thank you Eric. Just a small suggestion I would like to make: maybe you could add a note to the section where you suggest that the user keeps a working kernel listed in lilo.conf, just in case, to say that it is advisable to list it first before any other entries. That way, if there is a problem with the new kernel this working kernel will boot as the default. In my case I had listed the new kernel first and as the keyboard not responding was one of the issues I had, I was unable to select the old kernel at the prompt.
 +--- //[[wiki:user:rkfb|Robert Frost-Bridges]] 2018/04/23 21:38 (UTC)//

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