Articles are paginated with only three posts here for example. You can set the number of entries to show on this page with the “pagination” setting in the config file.

When initramfs drops into emergency mode after a kernel upgrade: how to recover the root partition on Ubuntu 24.04

 Posted on 30 September 2026  |  4 minutes  |  671 words  |  Carla Brown

After a kernel upgrade, Ubuntu 24.04 can sometimes drop straight into emergency mode if the initramfs can’t mount the root filesystem. The prompt usually looks like:

Emergency mode
You are in emergency mode. The root filesystem is mounted read‑only.

Below is a practical walk‑through of the most common culprits and how to bring the root back online without compromising security.

Why emergency mode happens

  • UUID mismatch – The kernel’s root= parameter points at a UUID that no longer exists (think LVM snapshot churn or a fresh partition).
  • Missing drivers – The initramfs was rebuilt without the modules needed for your storage controller or filesystem.
  • Secure‑boot hiccups – A signed kernel gets rejected because the firmware can’t find the signing key or the initramfs isn’t signed.
  • Filesystem corruption – Bad blocks or a half‑finished update can stop the kernel from mounting the root.

The emergency shell gives you a minimal environment with the root filesystem mounted read‑only, which is perfect for debugging without risking further damage.

[Read More]
linux  ubuntu  emergency-mode  initramfs  rootfs 

Granting Group Write Access on a Shared /srv/web Directory Using ACLs Without Changing File Ownership

 Posted on 29 September 2026  |  4 minutes  |  804 words  |  Carla Brown

The /srv/web directory is usually the spot where you keep static assets, CMS themes, or a shared workspace for a handful of developers. In most setups the files are owned by root or a dedicated web user, but the team still needs to edit or upload content without juggling ownerships. That’s where Access Control Lists (ACLs) come in handy: they let you grant a specific group write rights while keeping the original ownership hierarchy intact.

[Read More]
linux  open-source 

Hardening a Home Assistant Docker Container with User Namespaces and Read‑Only Volumes

 Posted on 28 September 2026  |  1 minutes  |  66 words  |  Carla Brown

I only have the opening paragraph of the article. To rewrite it while keeping all the commands, links, and the final TAGS line intact, I’ll need the complete draft. Could you paste the rest of the article (or at least the sections that follow the “Enable user namespaces” heading)? Once I have the full text, I can apply the style and technical preservation rules you specified.

linux  open-source 

Fixing the “Permission denied” error when mounting a host directory into a rootless Podman container

 Posted on 26 September 2026  |  3 minutes  |  502 words  |  Carla Brown

Rootless Podman runs containers as an unprivileged user, so a bind‑mount that works for root often fails with “Permission denied.” That error is usually a mismatch between the host directory’s ownership/permissions and the container’s user namespace. Below is a quick checklist that gets the mounts working again while keeping the isolation tight.

Common Causes

Cause Why it happens Typical symptom
File ownership The host directory is owned by root or another UID that the container’s user can’t read/write. mount: permission denied or open /data/file: Permission denied inside the container.
SELinux/AppArmor context The host directory’s security context blocks the container’s process. Same “Permission denied” even when file permissions look right.
User‑namespace mapping Podman maps container UID 0 to a non‑zero host UID. If the host directory is owned by root, the mapped UID has no rights. Error appears only when --userns=keep-id is omitted.
Mount options Using :Z/:z incorrectly or omitting them when SELinux is enabled. SELinux denies the mount, causing the error.

Quick Fixes

  1. Match ownership

    [Read More]
linux  containers  podman  security 

Recovering a Linux system that stuck in emergency mode after an initramfs update

 Posted on 24 September 2026  |  4 minutes  |  835 words  |  Carla Brown

Emergency mode after an initramfs update

After a kernel upgrade the initramfs is rebuilt automatically.
If a module slips through the cracks or a hook gets mis‑configured, the machine will drop into emergency mode with a terse prompt:

Emergency mode – root account password required

You’re not stuck forever; the problem is almost always a missing or mis‑mounted filesystem, a bad fstab, or a broken initramfs that can’t mount the root partition. Below is a practical walk‑through that keeps your data safe and pays attention to security.

[Read More]
linux  open-source 

Silence the Endless “dhclient” Logs in Systemd’s Journal with a One‑Line syslog.d Rule

 Posted on 22 September 2026  |  2 minutes  |  369 words  |  Carla Brown

The Problem

dhclient is the classic DHCP client on most distributions.
When a network interface comes up, it writes a line for every lease request, renewal, and release. On a busy server or in a homelab with multiple interfaces, those lines can fill the journal within minutes, making journalctl -b noisy and slowing down log‑based monitoring.

Why It Matters

  • Log Volume – A full journal consumes disk space and can trigger automatic rotation or deletion, potentially discarding useful diagnostics.
  • Performance – Writing thousands of lines per boot can add a few milliseconds to the boot time, which matters for high‑availability systems.
  • Security – While the messages themselves are harmless, a cluttered journal can mask real events, and excessive logging can expose sensitive data if the logs are forwarded to an insecure remote collector.

The One‑Line Solution

Systemd’s syslog.d directory lets you filter messages before they reach the journal. A single rule is enough to silence all dhclient output:

[Read More]
linux  systemd  journald  dhclient  logging