From: Thomas Walker Lynch
Date: Wed, 14 Oct 2026 05:00:47 +0000 (+0000)
Subject: updateding doc format
X-Git-Url: https://git.reasoningtechnology.com/sitemap.xml?a=commitdiff_plain;h=247512cc30237f2f89254551005b2ac934e24eb6;p=AccountTree
updateding doc format
---
diff --git a/document/doc_1.html b/document/doc_1.html
index 813f900..bcef89c 100644
--- a/document/doc_1.html
+++ b/document/doc_1.html
@@ -3,31 +3,41 @@
Subu User Containers
-
-
-
+
-
-
+
+
-
+
Introduction
- A Subu is an isolated user environment operating within a broader parent system. It functions as a strict User Container. Each subu possesses its own namespace, isolated processes, and dedicated I/O resources.
+ A Subu is an isolated user environment operating within a broader parent system. It functions as a strict User Container. Each subu possesses its own namespace, isolated processes, and dedicated I/O resources.
- The core architectural goal of the subu system is administration without elevation. A Master User has the ability to completely administer a subordinate user environment without requiring sudo privileges or system-wide root access. The master user accomplishes this through a dedicated suite of tools and a specialized file system architecture.
+ The core architectural goal of the subu system is administration without elevation. A Master User has the ability to completely administer a subordinate user environment without requiring sudo privileges or system-wide root access. The master user accomplishes this through a dedicated suite of tools and a specialized file system architecture.
Design Decisions and Architecture
@@ -35,25 +45,25 @@
Namespacing
- Subu accounts require a naming convention that links them logically to their master user while remaining fully compliant with standard Linux utilities. The system utilizes the middle dot (·) as the namespace separator.
+ Subu accounts require a naming convention that links them logically to their master user while remaining fully compliant with standard Linux utilities. The system utilizes the middle dot (·) as the namespace separator.
- An example account name is Thomas·developer.
+ An example account name is Thomas·developer.
- The middle dot offers several distinct advantages over traditional separators. The colon (:) is strictly forbidden, as it acts as the field delimiter in /etc/passwd and will corrupt the system configuration. The hyphen (-) and underscore (_) are heavily utilized in standard user naming conventions, increasing the probability of accidental collisions. The middle dot is visually clean, requires a specific --badname flag during account creation, and presents a typing barrier for standard users, practically eliminating accidental naming conflicts.
+ The middle dot offers several distinct advantages over traditional separators. The colon (:) is strictly forbidden, as it acts as the field delimiter in /etc/passwd and will corrupt the system configuration. The hyphen (-) and underscore (_) are heavily utilized in standard user naming conventions, increasing the probability of accidental collisions. The middle dot is visually clean, requires a specific --badname flag during account creation, and presents a typing barrier for standard users, practically eliminating accidental naming conflicts.
The File System Dilemma
- Attempting to nest subu home directories within the master user's home directory (e.g., /home/Thomas/subu/developer) creates an intractable conflict with POSIX permissions and Access Control Lists (ACLs).
+ Attempting to nest subu home directories within the master user's home directory (e.g., /home/Thomas/subu/developer) creates an intractable conflict with POSIX permissions and Access Control Lists (ACLs).
- If a subu is nested, the operating system requires group execute permissions on the master's home directory to allow traversal. If a person attempts to restrict this using ACL masks, the subu retains sovereign control over its own files. A subu executing a standard chmod 600 on a file recalculates the ACL mask to zero, instantly severing the master user's access to that file and causing subsequent system backups to fail with permission errors.
+ If a subu is nested, the operating system requires group execute permissions on the master's home directory to allow traversal. If a person attempts to restrict this using ACL masks, the subu retains sovereign control over its own files. A subu executing a standard chmod 600 on a file recalculates the ACL mask to zero, instantly severing the master user's access to that file and causing subsequent system backups to fail with permission errors.
The Dual Layer Architecture
@@ -65,13 +75,13 @@
The Physical Layer
- Every subu home directory resides directly under /home, entirely flat and parallel to the master user account.
+ Every subu home directory resides directly under /home, entirely flat and parallel to the master user account.
-
+
/home/Thomas
/home/Thomas·developer
-
+
Placing the directories side by side eliminates traversal conflicts. The subu relies purely on standard POSIX ownership of its dedicated path, ensuring absolute sovereign control over its workspace and preventing permission changes from breaking the directory structure.
@@ -80,15 +90,15 @@
The Management Layer
- To grant the master user administrative access without violating the physical layer permissions, the system utilizes ID-mapped mounts.
+ To grant the master user administrative access without violating the physical layer permissions, the system utilizes ID-mapped mounts.
A system service establishes a mount point within the master user's workspace, pointing to the subu's physical directory:
The kernel translates the subu's user ID to the master user's user ID in real-time. Through this mount, the master user perceives absolute ownership of all subu files. If the subu locks down a file in the physical layer, the master user retains the ability to read, modify, or repair it through the management layer.
@@ -97,7 +107,7 @@
Hardware Access and Audio Seating
- Because subu accounts utilize logind to acquire their own session seats, they inherit strict hardware isolation rules. Modern Linux dynamically assigns hardware ACLs (such as audio and graphics nodes) to the active seated user. The first user to claim the audio socket locks out all other background sessions.
+ Because subu accounts utilize logind to acquire their own session seats, they inherit strict hardware isolation rules. Modern Linux dynamically assigns hardware ACLs (such as audio and graphics nodes) to the active seated user. The first user to claim the audio socket locks out all other background sessions.
@@ -111,11 +121,11 @@
- If a subu or master user creates an ID-mapped mount directly during their session, the Linux login daemon (systemd-logind) will aggressively terminate the background FUSE processes upon logout, destroying the management layer.
+ If a subu or master user creates an ID-mapped mount directly during their session, the Linux login daemon (systemd-logind) will aggressively terminate the background FUSE processes upon logout, destroying the management layer.
- The system setup process executes independently of user sessions. It queries a central SQLite database to determine the registered subu relationships, constructs the /home/master/subu directory structures, and establishes the ID-mapped mounts. Crucially, the setup process assigns ownership of these mounts to the master account. Because the mounts are created by a boot-level service, they persist indefinitely, surviving all individual user logouts.
+ The system setup process executes independently of user sessions. It queries a central SQLite database to determine the registered subu relationships, constructs the /home/master/subu directory structures, and establishes the ID-mapped mounts. Crucially, the setup process assigns ownership of these mounts to the master account. Because the mounts are created by a boot-level service, they persist indefinitely, surviving all individual user logouts.
User Manual
@@ -128,32 +138,28 @@
For the Subu
-
Home Directory:/home/Thomas·developer
+
Home Directory:/home/Thomas·developer
Perspective: The subu operates in a standard Linux environment. Files are owned by the subu. All paths behave normally.
Perspective: The master user navigates into the subu directory to administer subordinate accounts. All files within this directory appear to be owned by the master user. Modifying a file here instantly modifies the physical file for the subu.
Perspective: The master user navigates into the subu directory to administer subordinate accounts. All files within this directory appear to be owned by the master user. Modifying a file here instantly modifies the physical file for the subu.
Backups
- When a master user initiates a backup of their home directory, they must instruct the archiving tool (such as tar or rsync) to respect filesystem boundaries. Passing the --one-file-system flag prevents the backup utility from traversing into the /home/Thomas/subu mounts, avoiding infinite recursion loops and duplicate data capture. The physical subu directories (/home/Thomas·developer) are backed up via separate, independent archive routines.
+ When a master user initiates a backup of their home directory, they must instruct the archiving tool (such as tar or rsync) to respect filesystem boundaries. Passing the --one-file-system flag prevents the backup utility from traversing into the /home/Thomas/subu mounts, avoiding infinite recursion loops and duplicate data capture. The physical subu directories (/home/Thomas·developer) are backed up via separate, independent archive routines.
-
-
Hardware Access and the Virtualization Horizon
- Currently, because subu accounts utilize logind to acquire their own session seats, they inherit strict hardware isolation rules. Modern Linux dynamically assigns hardware ACLs (such as audio and primary graphics nodes) to the active seated user.
+ Currently, because subu accounts utilize logind to acquire their own session seats, they inherit strict hardware isolation rules. Modern Linux dynamically assigns hardware ACLs (such as audio and primary graphics nodes) to the active seated user.
@@ -168,6 +174,6 @@
Fundamentally, hardware virtualization and user process or memory virtualization are identical solutions. The historical separation between a virtual machine and a user namespace represents an incomplete modernization of the operating system user model. The subu architecture views these concepts as a unified system. Future iterations will seek to integrate an existing Linux GPU virtualization layer directly into the user container, granting each subu parallel, isolated access to the underlying hardware substrate.