[arch-general] Any special reason for /etc/shadow.pacnew, or just normal pacman behavior.
Guys, I always diff any new .pacnew files when they are created during an update. Today I got /etc/shadow.pacnew which was a little surprising given that replacing shadow would be bad. The diff showed that the .pacnew entries were already in shadow (except for the root password of course) So this is just normal expected behavior by pacman right? shadow was there, pacman new it, so the new file was just installed as .pacnew. Anything else there I need to look at? Thanks. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Tue, Sep 21, 2010 at 16:02, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
Guys,
I always diff any new .pacnew files when they are created during an update. See "man pacman", under HANDLING CONFIG FILES. It explains the behavior in detail.
On 09/21/2010 04:02 PM, David C. Rankin wrote:
Guys,
I always diff any new .pacnew files when they are created during an update. Today I got /etc/shadow.pacnew which was a little surprising given that replacing shadow would be bad. The diff showed that the .pacnew entries were already in shadow (except for the root password of course)
So this is just normal expected behavior by pacman right? shadow was there, pacman new it, so the new file was just installed as .pacnew. Anything else there I need to look at? Thanks.
It's nothing major, the last modified date for each password was set from the future (999999) to the past...
participants (3)
-
Daenyth Blank
-
David C. Rankin
-
Matthew Monaco