On 2023-03-29 15:46, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-03-29 14:53, Per Jessen wrote:
That can not be done now, if it lives under /run.
If I were to write everyone of my resolv.conf files manually, it would probably take me a day or two. But you can still write it manually, with your favourite editor.
No, you can't. It lives under /run, it is volatile.
Well, that does not actually mean you cannot edit it.
Ok, right. Did I say "permanently edit" somewhere? :-?
You can break the symlink and write an actual file in /etc, perhaps.
For instance.
Yeah, sure, but that is under the eat my kittens warning board. :-p (I may have done it somewhere and forgotten, mind)
No idea what it was, and can't find out because I reinstalled fully.
Provided it works now, the problem/culprit has been identifed - the operator.
LOL. And what did the operator do to cause this, so that he doesn't do it again? :-)
Uncritically copied over a load of old sh*te, I think I saw him say.
:-D Not uncritically... just not sufficiently checked, rather. I copied file by file, under /etc, /usr/local/, /var/log, /root, maybe some other. I decided what files to copy. I did not write anything in /boot, or bins. Maybe something happened accidentally.
Every time I boot the machine, I tremble. I don't feel safe.
Yeah, it might explode. I would quickly just start the boot process, then go to another room.
It may eat your kittens :-D Common, it may force me to do another reinstall.
Carlos, sigh. You forced yourself to do another install.
How, exactly? Per, I'm not as bright as I was, age takes its toll, but I am experienced. I don't know of anything I did that would cause a kernel panic. The only thing new is, aside of the machine, using full disk encryption. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)