#TIL

* `/etc/sub{uid,gid}` to map user ids in containers to host ids. https://rootlesscontaine.rs/getting-started/common/subuid/

The Polls app on Liberta Cloud has been disabled after several breakages and bugs during update.

We'll wait for the app to stabilize before enabling it again.

L'application de construction de sondages Polls sur Liberta Cloud a été désactivée suite à plusieurs échecs de mises à jour de l'application et de nombreux bugs.

Nous attendons que l'application soit enfin stabilisée avant de la réactiver.

Yes, yes, I write entire books as pranks. But it's rare that even the book's title is a lie.

This is one of those times.

Coming 16 September on #Kickstarter: "Networking for System Administrators, 2nd ed." #sysadmin

https://mwl.io/ks

Sigh. So apparently Microsoft bounces e-mail to a non-existing recipient with 550 5.4.1 Recipient address rejected: Access denied.

How vague could they be? Something like "550 Requested action not taken: mailbox unavailable" or "550 5.1.1 Mailbox "nosuchuser" does not exist" is clear and standardised.

New post on I Fixed It and I Don’t Know How

A real-life case: mysterious OneDrive/SharePoint access issues that resisted every fix. After endless troubleshooting, the culprit was hidden deep inside the UserInfo list.

If you’ve ever faced ghost permissions or broken access in Microsoft 365, this one’s worth reading

https://tinyurl.com/fw87b32s

Nuevo artículo en Lo Arreglé y No Sé Cómo

Un caso real de esos que hacen sudar: problemas de acceso en OneDrive/SharePoint que no se resolvían con nada. Tras pruebas, errores y horas de búsqueda, la clave estaba en algo tan simple (y tan escondido) como la lista UserInfo.

Si alguna vez te has topado con accesos fantasma o permisos que no cuadran, este post es para ti

https://tinyurl.com/43ur89ps

Your path to decommissioning that last on-prem Exchange server is here. With cloud-managed remote mailboxes, you can now shift attribute authority to Exchange Online and manage everything in the cloud. Time to power it down. https://pupuweb.com/why-it-teams-struggle-on-premise-local-servers-exchange-online-cloud-managed-remote-mailboxes-exists/ #ExchangeServer #SysAdmin #M365

Tonight I made a simple, yet destructive (or at least partly) mistake: when I told FreeBSD which disk to destroy, I accidentally gave it the system disk of my little home server. This happened because it had the same size as the external SSD I had just plugged in, and I got confused.

I lost some reproducible configurations (the server’s name was in fact tempfbsd01), but I took the chance to run an experiment. My home server runs FreeBSD in read-only mode (that's the part I destroyed). From there, I manually enable the external drives (encrypted with GELI) and, in turn, the ZFS pools. Then I start the various jails and the (single, Proxmox Backup Server) VM.

Since I also have another test box running SmartOS, I decided to experiment: I connected the disks to it, created a FreeBSD bhyve VM on SmartOS, and passed the entire disks through to the VM. I reconfigured the FreeBSD VM with the bare minimum and booted it all up. The jails with BastilleBSD started without any issues - obviously the Proxmox Backup Server VM itself is still missing, but I’ll deal with that later.

I’m tempted to leave everything like this for a while.

And yes, for anyone wondering: I had fun

Dat gifft so Tage, da fühlt sich der Kopf an wie ein System mit einem fiesen, tief sitzenden Bug. Ist kein klarer 404-Error, wo de genau weißt, wat fehlt. Es ist eher eine stille Kernel-Panic in der Seele. Alles läuft noch, die Basisfunktionen sind da – aufstehen, Kaffee kochen. Aber die CPU-Last für diese simplen Prozesse ist bei 99 Prozent. Für alles andere? Ach, egal.

https://nerdbear.de/maschinenraum/logbuch-eintrag-kernel-panic-im-kopf.shtml

¿Sabén la diferencia entre procesos y jobs en GNU/Linux?

En el nuevo post de #juncotic les explico la diferencia entre jobs y procesos, y cómo gestionarlos para aumentar tu productividad en la línea de comandos!

Leelo acá https://juncotic.com/jobs-y-procesos-en-la-shell-de-gnu-linux/

¿Saldrá grabado en video para youtube? Probablemente

jiangcuo/pxvirt: A fork of Proxmox VE for ARM and LoongArch architectures - #PXVIRT is an open-source virtualization platform derived from #Proxmox VE, specifically adapted to support ARM and LoongArch architectures. This project originally began as "Proxmox-Port" and has now evolved into a fully independent fork under the new name PXVIRT.
https://github.com/jiangcuo/pxvirt
#Proxmox #virtualization #sysadmin #networking #freesoftware #arm
via https://magicfab.ca/liens

GitHub Copilot for Azure Arrives in Visual Studio to Automate Cloud Management

#AI #Azure #GitHubCopilot #VisualStudio #Cloud #SysAdmin #DevTools #Microsoft

https://winbuzzer.com/2025/08/26/github-copilot-for-azure-arrives-in-visual-studio-to-automate-cloud-management-xcxwbn

strace is a Linux diagnostic tool that traces system calls and signals made by a process to help debug and analyze its interaction with the kernel

Here are useful strace command examples #sysadmin #cybersecurity #infosec

Find a high-res pdf book with all my #Linux related infographics from https://study-notes.org/linux-ebook.html

I have a client who uses Proxmox and its backup server. Last week, I upgraded the backup server from Debian 12 to 13. The backup server "sleeps" most of the day, so it also runs Docker for a Gitea runner. Everything seemed fine initially.

Then, my client messaged me yesterday because the runner had stopped working. When I logged in, I found that for some reason, the runner could no longer connect to the Docker socket, even though I was passing it the official way. I tried the same thing on a different Debian 13 server and got the same result. But, on a Debian 12 VM using the (old) Docker from the Debian repos, everything worked perfectly.

This incident just reinforces my point that for production servers, it’s crucial to use solutions that don't introduce breaking changes between releases. It seems to be an Apparmor issue (thanks @gyptazy for the head up!).

Because this component was non-critical and easily replaceable, I didn't pay much attention to testing it right after the server upgrade.

Hey #windows11 people, do NOT install KB5063878 or KB5062660 (preview).

It's bricking SSDs and I'm currently dealing with rolling back damage from this.

If you already have it installed, roll back with: wusa.exe /uninstall /KB:5063878

and: wusa.exe /uninstall /KB:5062660

Time for today's edition of the #TechIsShitDispatch. Here's the tech-related shit I've had to wade through since yesterday.
Part of why I post these is for the catharsis, but I am also absolutely trying to make a point here. I want more people to wake up to how bad things are and get more people agitating and demanding better.
We deserve better.
So let's dive in.
#SysAdmin #ITDIY #HealthInsurance #GitHub #Microsoft #Windows11
1/10

"Make the adjustment in Zabbix," he said.
"It'll be really quick and then you can get back to your actual work," he said.

Man, FUCK Mondays.
#sysadmin

My first #OPNsense contribution - a small addition of used/total GB disk space used info to the Disk widget in the dashboard.

https://github.com/opnsense/core/pull/9131

Bright and early Monday morning?

Yippee.

You're probably at work. My next book supposedly teaches networking for #sysadmin types, but really, it's about how to survive employment. Coming to #Kickstarter 16 September.

https://mwl.io/ks