New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
lol, the term debugging is from a similar story that there were really bugs inside a computer rack, causing errors on the mainframe.
That's a myth. The term "bug" meaning a problem in a mechanism has existed long before mainframes, all the way back in the 1800s. The myth came from a bug caused by a literal bug in the Harvard Mark II which led the developers to call it the first computer bug in jest. It was a moth found in relay 70 in panel F, and they wrote: "First actual case of bug found".
The term "debug" was first used in aeronautics in the 1940s referring to fixing flaws in aircraft engines.
there was an actual moth in one of the first computers, they used the term debugging for the first time in a computing context.
Source? Everything I find say that the first documented use of debugging referring to computers was in 1952 and the 1947 incident with the moth never used that term. They just referred to it as an "actual bug".
I just ask what is patch and i got summoned on almost every comments 😭
@nghialele
@nghialele
Thanks for always remember me @zed @rpqu
link? or was it some promo?
OK, the next one? proxmox-kernel-7.0.14-5 fixes CVE-2026-53362...
Only an issue for containers like LXC (and for guests of all kinds themselves), but that can't be used to escape KVM.
here we go again with the patching
OK - had only a quick look at the ProxMox release notes for the -5 and thought "hopefully we won't go through all the "emergency maintenance" (announced, shortly announced and just done without announcement) things again...
Should only have to go through that again for LXC providers. But then again they have to go through that for nearly every privesc!