Knowledge Base

This month in Devuan ceres, usrmerge bit me in the rear, in multiple ways!

Mount.nfs

The main was that mount.nfs couldn't operate due to something not found in /bin. So I, using my extremely acute sense of logical deduction, had to go apt-get install usrmerge and delete a few random udev rules that are duplicated between /lib and /usr/lib or some baloney so it would install (well, dpkg-configure) correctly.

I saved this script as the filename indicated below, which of course is on my nfs server which is inaccessible until you solve the problem. So I had to copy-paste it into each ssh session to the affected (all) systems.

sudo rm -f /lib/udev/rules.d/99-libsane1.rules /lib/udev/rules.d/60-libsane1.rules /lib/udev/hwdb.d/20-sane.hwdb
sudo apt-get install -y usrmerge

And then mount.nfs works again.

/run is gone

One one particularly remote system (where I had to involve others to access a shell), the /etc/resolv.conf file which is symlinked to ../run/resolvconf/resolv.conf pointed to nowhere. There was no /run. The system was on its local network, but due to name resolution failures, it was unable to establish the vpn connection back to the Internal network. So we set up a hardcoded resolv.conf:

search ipa.example.com #useless with the following, though
nameserver 8.8.8.8
nameserver 8.8.4.4

I benefit from google's generosity.

So, then we got wireguard back up, wg-quick up wg0. And then I took over the rest of the efforts, which included the same copy-pasted instructions. And now I've left that hardcoded resolv.conf on server2, so that it will not fail in this manner again. Although I suppose it will never have to undergo that particular lobotomy again. Until I decide to risk changing it back, it'll never get the name resolution across the vpn like before. Ah, well.

References

Internal files

1. file:///mnt/public/Support/Platforms/devuan/scripts/merge-usr.sh