Recent content by BobhWasatch

The post you responded to is 2 years old. That said, /etc/pve directory isn't a real directory, it is a fuse mount of a database. So you probably should be excluding it from etckeeper. I don't use that software so can't tell you how to do it. Sorry.

It looks like you have repositories configured in both /etc/apt/sources.list and /etc/apt/sources.list.d. Having everything in the sources.list file is the "old way" while files in /etc/apt/sources.list.d is the "new way". I suggest to temporarily rename /etc/apt/sources.list (the file) to...

Well, it is incorrect to have both regardless of why you did it and now you have a different set of errors. Fix that and post the results of what @Neobin asked for. The most common reason for the error you are getting is incorrect repositories. There are other reasons though, such trying to...

You have both trixie and bookworm configured on the proxmox enterprise repo.

Wow, how old is that thing? I haven't seen "turbo mode" in years.

Proxmox VE can be configured to update automatically (see "apt info unattended-upgrades"). This is a Debian feature and I think there are good reasons for it to not be enabled by default (e.g. you don't know what else the admin has installed, do you want it to reboot automatically or not, etc)...

But that wasn't the only bug found in SSH over the last five years.

Only to you, unless you are claiming that it affects an up-to-date version of PVE. PVE 7 is based on Debian 11, PVE 8 on Debian 12. So they would be affected by that bug unless they were updated since the bug was fixed.

I don't know about that, but it is the case that once the chip is damaged it stays damaged. Changing voltages won't fix it.

Maybe it would help people to help you if you were to explain what isn't working.

That post is 2 years old. And there are multiple current threads about getting pass-thru working on a laptop.

AI psychosis incoming.

I guess you mean you're amazed that whatever is writing these broken VMDK files isn't fixed. If a field is supposed to be quoted, and isn't, that's not a problem with the parser, it is a problem with the writer. The only complaint you should have with the parser is that it didn't give a good...

On the master that is serving time to clients you need the "allow" line at least. In addition, IF the master does NOT have NTP available and you want to use the local clock instead, then you also need "local", but the stratum needs to be less than 10. See here for an example...

Most NTP servers will say their time is invalid or a high stratum unless they are synchronized to an external source like another NTP server or a GPS clock. One common symptom of this is that the clients of that server will refuse to synchronize. You can check the status of the clock with...