[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.
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
talk:howtos:slackware_admin:systemupgrade [2012/09/30 07:59 (UTC)] – crond | talk:howtos:slackware_admin:systemupgrade [2018/04/23 21:41 (UTC)] (current) – rkfb | ||
---|---|---|---|
Line 18: | Line 18: | ||
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:// | 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:// | ||
+ | > Hi crond, I hope I addressed your concerns properly in my update. \\ --- // | ||
+ | ------ | ||
+ | TommyC, please respect the [[slackdocs: | ||
+ | //You can also blacklist packages that you don't want to upgrade.// < | ||
+ | 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/ | ||
+ | xfce/ | ||
+ | </ | ||
+ | |||
+ | 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. | ||
+ | --- // |