Slackware 12.1/12.2 pine/alpine users pay attention!
I noticed when I upgraded my 12.1 install to 12.2 that pine has /etc/pine.conf while alpine has the now typical /etc/pine.conf.new.
The unwary admin might accidentally have their pine.conf file deleted if they remove obolete packages after upgrading as per the UPGRADE.TXT. Of course everyone is backing up their system before upgrading, right? ;) |
How did you do the upgrade?
The .new files are normally the result of upgrades and need to be checked before substituting the original .conf files. The slackpkg tool (now part of the base install of Slackware 12.2) automatically checks for .new files after upgrading and gives you the option to check the differences, overwrite the original file (renaming it to .orig), delete the .new file or keep both to check later. |
Quote:
Code:
*** PACKAGE REMOVALS SINCE 12.1 *** Thanks for this tip shadowsnipes. |
OK, it is not an upgrade, but alpine is the evolution of pine and uses pine.conf as its configuration file.
I followed the -current branch and don't remember having problems with the change from pine to alpine (which I do use) while upgrading with slackpkg in August. Slackpkg probably found the .new file (it uses 'find') and I probably used the 'diff' option of slackpkg to check the differences. Nothing 'scary' happened here :) |
OK, it is not an upgrade, but alpine is the evolution of pine and uses pine.conf as its configuration file.
I followed the -current branch and don't remember having problems with the change from pine to alpine (which I do use) while upgrading with slackpkg in August. Slackpkg probably found the .new file (it uses 'find') and I probably used the 'diff' option of slackpkg to check the differences. Nothing 'scary' happened here :) |
All times are GMT -5. The time now is 01:33 AM. |