On 2021/03/14 18:34, David T-G wrote:
Is there any way to keep them from being dropped again so that I don't have to deal with this over and over? *sigh*
I've occasionally had some files that kept being mung'd or replaced. Depending on what you want to do, you could create a directory where the file would go, but many install progs will deleted that. One persistent option I've used. I had some config I wanted to keep in my network area and it kept trying to overwrite it and/or change the name of the device. While I'd solved the prob in earlier releases, it became a case of new features forcing an overwrite. So...I set the immutable bit on the problematic files. So far, that's kept them intact. Another option replace the dir with an empty dir or one that only has the files/changes you want. Then add that to a a disk image that gets mounted read-only. Those are semi-rogue options to protect files. Some might say there should be an OS way to protect them -- and there usually is -- problem is that such a way often changes between releases, so moving your enforcement mechanism out of the way of an update helps.