On 21.08.20 22:23, Manuel Reimer wrote:
A diff between the actuall file and its ".pacnew":
$ diff -U 8 -p 00-dns.sh 00-dns.sh.pacnew
--- 00-dns.sh 2013-05-30 19:35:30.000000000 +0200
+++ 00-dns.sh.pacnew 2020-02-20 22:37:04.000000000 +0100
@@ -1,7 +1,11 @@
#!/bin/sh
if [ "$USEPEERDNS" = "1" -a -f /etc/ppp/resolv.conf ]; then
- [ -e /etc/resolv.conf ] && mv /etc/resolv.conf
/etc/resolv.conf.backup.${IFNAME}
- mv /etc/ppp/resolv.conf /etc/resolv.conf
- chmod 644 /etc/resolv.conf
+ if [ -x /usr/bin/resolvconf ]; then
+ /usr/bin/resolvconf -a ${IFNAME} </etc/ppp/resolv.conf
+ else
+ [ -e /etc/resolv.conf ] && mv /etc/resolv.conf
/etc/resolv.conf.backup.${IFNAME}
+ mv /etc/ppp/resolv.conf /etc/resolv.conf
+ chmod 644 /etc/resolv.conf
+ fi
fi
And here the dates of the files:
$ ls -lh
total 8,0K
-rwxr-xr-x 1 root root 229 30. Mai 2013 00-dns.sh
-rwxr-xr-x 1 root root 344 20. Feb 2020 00-dns.sh.pacnew
So when copying over from HDD to SSD I seem to have taken care of
keeping the filestamps as I did not have my SSD in year 2013.
If pacman had a bug in the past which did not properly move .pacnew into
place (or maybe the "move into place feature" came some time later).
Could a existing ".pacnew", created from older pacman versions, cause
issues here?
This is a pretty old Arch install. Never reinstalled. Always just
updated. The oldest date I could find is August 2012.
Manuel
