#system administration

Mastering the Linux Filesystem Hierarchy Guide 2026

Understanding the Root Architecture

The Linux filesystem follows a strictly organized structure known as the Filesystem Hierarchy Standard or FHS. Every file and directory on your system begins at the root directory, represented by a single forward slash.

The root partition is the foundation for all other mounted filesystems.

Standardized locations ensure compatibility across different Linux distributions.

Consistent paths allow system administrators to automate tasks reliably.

Key Directories You Must Know

Navigating the Linux directory tree requires understanding where specific data resides. While modern operating systems evolve, the core FHS locations remain essential for day-to-day administration.

/etc: Houses system-wide configuration files and scripts.

/var: Stores variable data such as system logs, databases, and cache files.

/bin and /sbin: Contain essential binary executables and administrative system commands.

/home: Holds personal user files and individual configuration settings.

Evolution of Linux Storage in 2026

In 2026, the traditional hierarchy continues to adapt to new technologies like immutable operating systems and containerization. Modern systems often treat parts of the filesystem as read-only to improve security and stability.

Immutable distributions may use overlay filesystems to separate system files from user changes.

Containers frequently mount virtual directories to isolate application dependencies from the host environment.

A question I get a lot as a tech enabler is whether you can buy PC's with Linux installed out of the box instead of Windows.

There is a situation that repeats itself across many organizations, often without being fully questioned. Sales commits to a date based on what they see in the CRM, finance validates something different, and operations tries to reconcile everything in between. No one is wrong—each team is simply working with the information available to them. The issue arises when that information does not come from a shared, connected source, but from systems operating independently.

In theory, both the ERP and the CRM are doing their job. They capture, organize, and manage critical business data. In practice, however, they can end up functioning as separate environments that do not share context, forcing teams to manually fill the gaps the systems fail to bridge. This is where delays, repeated validations, and uncertainty begin to appear.

When this happens, organizations gradually start operating with fragmented information. What should move seamlessly across processes becomes duplicated, delayed, or rebuilt multiple times along the way. This is what data silos look like in reality—not as a technical failure, but as a structural gap where information is unable to flow consistently across the business.

The impact is not always immediate, but it compounds over time. Processes slow down, visibility decreases, and decision-making becomes less reliable. Many organizations interpret this as a technology limitation, when in reality it is a direct consequence of how their systems are connected—or not connected—within the operation.

For that reason, before considering replacing an ERP or switching CRMs, it is worth stepping back and looking at something more fundamental: whether information truly flows across systems, or whether each one operates as an isolated island. That distinction completely changes how the problem should be approached.

In the full article, I go deeper into how these silos are created, why they are more common than they seem, and what it actually takes to reconnect your systems and restore operational flow without rebuilding your entire stack.

👉 Read the full article here: https://suriservices.com/erp-crm-no-esta-vi/

With apologies to George and Marcia Lucas.

[Luke is training with his father’s LinuxSaber ... and a temp file.]

Ben: Remember, Luke: a sysadmin can *feel* the Kernel *flowing* through him.

Luke: You mean, it prompts you for input?

Ben: Partly. But it also obeys your commands.

[Luke attempts to delete the file and a gets a “permission denied” error.]

Han: [amused] Hokey system calls and ancient command shells are no match for Windows Explorer on your desktop, kid.

Luke: You don't believe in the Kernel, do you?

Han: Kid, I've surfed from one end of the Web to the other. I've seen lots of strange stuff, but I've never seen anything to make me believe there's one all-powerful Kernel controlling everything. There are no drivers for *my* HDD. It's all a bunch of registry hacks and nonsense.

Ben: [opens a terminal window] I suggest you try it again, Luke. This time, let go of your mouse and use the keyboard. [He maximizes the window.]

Luke: But with this window maximized, I can't even see the desktop! How am I supposed to delete the file?

From Desktop Support to System Administration – A Real Career Transformation

In this blog, we break down a reality that is already happening across organizations of all sizes:

AI agents with excessive permissions

Little to no visibility into what agents do or what they access

A lack of governance, identity, and continuous monitoring

New attack vectors that didn’t exist in traditional IT environments

When an AI agent fails—or is exploited—the impact is not theoretical: ⚠️ exposure of sensitive information ⚠️ flawed operational decisions ⚠️ legal, reputational, and business continuity risks

In the article, we explain how organizations are addressing these risks by adopting a security-by-design approach, using Microsoft Agent 365 as a centralized control plane to:

Manage agent identities

Enforce the principle of least privilege

Monitor agent activity in real time

Detect anomalous or risky behavior

Integrate security, compliance, and governance directly into Microsoft 365

This is not about slowing innovation. It’s about allowing AI to scale without losing control.

👉 If your organization already uses AI agents—or plans to—this is required reading. 🔗 Read the full analysis here:

Some of the difficulties I'm having with macOS seem to be related to a feature called System Integrity Protect (SIP). SIP interferes with building and installing applications as Administrator.