TheIPW

joined 1 month ago
[–] TheIPW@lemmy.ml 1 points 22 minutes ago

No, apt isn’t just a rename. apt upgrade largely replaces apt-get upgrade, but it’s a bit more aggressive: it may install new packages if required as dependencies (it still won’t remove packages). If an upgrade needs to remove packages to resolve dependencies, use apt full-upgrade (same as apt-get dist-upgrade).

[–] TheIPW@lemmy.ml 3 points 2 hours ago (1 children)

dist-upgrade and full-upgrade are essentially the same command but yeah, I won't be using apt upgrade again in the future! Like I said in my post, the joys of being self taught is that you learn by my making mistakes and that's part of the "fun" 🤣

[–] TheIPW@lemmy.ml 5 points 12 hours ago

Glad you found it useful. I'm the same, I can't stand those long posts that make you read a life story before getting to the commands, even worse when a page is riddled by ads or behind a paywall!

I figured if I’d missed it, a few other people probably had too.

[–] TheIPW@lemmy.ml 1 points 12 hours ago

I've not come across this with my non Debian based systems. Only use Debian for servers because it's so stable, Arch and Fedora everywhere else!

[–] TheIPW@lemmy.ml 2 points 12 hours ago (1 children)
 

I’ve been running my home lab since 2021 and honestly thought my update routine was solid: apt update && apt upgrade, reboot, job done.

Turns out I was wrong. I was checking CVE‑2026‑31431 (Copy Fail) this morning and realised that despite my “successful” updates, I was still running a vulnerable kernel from March.

I’ve had to rethink how I handle host updates. If you’re relying on a standard upgrade and a reboot to keep Proxmox or Debian hosts safe, you might want to check if yours is lying to you as well.

 

I’ve been using Linux for years, but as the proprietary alternatives get more aggressive with telemetry and adverts, I wanted to document the choices that actually keep my desktop predictable.

This isn't a manual, but a practical overview of my setup. From why I’ve settled on CachyOS and KDE Plasma for my main rig, to the reality of dealing with proprietary software and app compatibility in 2026. It’s just an honest look at the transition and why I’m done with the corporate defaults.

[–] TheIPW@lemmy.ml 1 points 3 weeks ago

I think that’s a dangerous assumption to make. If the OS is tied to your physical identity, the 'VPN' layer becomes much less of a shield. Once the kernel level is 'compliant' with an ID check, the metadata being leaked or even the hardware ID itself makes anonymity a lot harder to maintain.

You’re right about the social media risk, but the OS is the foundation. If you give up the keys to the house, it doesn't matter how many extra locks you put on the individual room doors. That 'disappointing risk' is exactly how the 'invisible borders' start getting built.

 

I’ve spent years championing Linux as the only escape from Big Tech, but I’m starting to get twitchy.

While we’re distracted by the Steam Deck making Linux "mainstream," the corporate players and politicians are busy building a digital cage. Between California’s AB-1043 mandates and Microsoft’s "Face Check" infrastructure, I’m worried we’re heading for a hard schism: "Sanitised Linux" vs the "Free Rebel" distros.

If the compliant, age-gated version becomes the industry standard, where does that leave the rest of us? Digital exile?

I’ve put some thoughts together on why the "Golden Cage" is closing in and why education, not mandates, is the only real fix.

 

LinkedIn is using hidden JS to scan your browser for over 6,000 specific extension IDs via a known Chromium vulnerability. By inventorying your local software, they can infer highly sensitive "Special Category" data like health status, religion, and political advocacy without consent.

I’ve joined the dots on why Chromium-based "Shields" fail here and how to harden your home lab/network to stop the leak.