# Network File System The Network File System is a distributed filesystem protocol for accessing remote files over a network; it matters here as part of the Linux service and RPC stack. ## Historical and Technical Context The page reads like notes taken while reviewing a Linux boot log, service list, or filesystem inventory. I2C and SMBus are low-speed hardware buses used for sensors, controllers, batteries, and board-management devices; Linux exposes user-space access through device interfaces. [S09] RealtimeKit brokers limited real-time scheduling for desktop audio and related processes. `systemctl`, `sulogin`, `udev`, and `ifupdown` belong to boot, emergency access, dynamic device management, and network configuration. `rpc_pipefs` mediates kernel/user-space RPC exchanges used by NFS. The page therefore maps the **control plane below the desktop**—the machinery that discovers hardware, brings up networks, authenticates emergency access, and mounts remote filesystems. ## Role in Scanned_20260730-1802 The primary identifying evidence appears on PDF page 8. A clean vertical list of Linux subsystem terms. The first three are separated slightly from service and filesystem entries below. Capitalization varies, but most items are recognizable from system service descriptions or package documentation. Within that page, Network File System helps the notebook move from a visible name or artifact toward the underlying identity, protocol, ownership, or control structure. ## Notebook Evidence - `Scanned_20260730-1802.pdf`, PDF page 8: "RPC Pipe File System" - `Scanned_20260730-1802.pdf`, PDF page 8: "RPC + NFS Server" **Evidentiary status:** Visible evidence: terminology characteristic of service descriptions. Strong inference: copied from a system-service viewer, package list, or boot diagnostics. The phrase “watchdog daemon” is approximately right for RealtimeKit’s policy role but not a complete description. The canonical name **Network File System** is normalized outside the quotations. The quoted lines preserve the completed reconstruction's spelling, capitalization, and uncertainty markers. ## Relationships On PDF page 8, Network File System appears in the same evidentiary cluster as [[I2C|I2C]], [[System Management Bus|System Management Bus]], [[Linux Userspace|Linux Userspace]], [[RealtimeKit|RealtimeKit]], [[cpio|cpio]], [[systemd|systemd]], [[ifupdown|ifupdown]], [[utmp|utmp]], [[sulogin|sulogin]], [[udev|udev]]. These links record page-level proximity and the reconstruction's systems map; they do not by themselves prove corporate ownership or a direct technical dependency. ## Cross-Notebook Significance This Linux substrate reappears in pages 26, 28-30, and 32, where BlueZ, UFW, Raspberry Pi gadget modes, and Linux-based industrial controllers are examined as interoperable components. ## Scanned_20260730-1706 Overlay **Source overlay:** [[Scanned_20260730-1706|Scanned_20260730-1706]] (specific PDF page references follow). `Scanned_20260730-1706.pdf`, PDF page 14 places NFS file servers beside Remmina and multiprotocol remote administration. `Scanned_20260730-1802.pdf`, pages 8–9 descends into NFS client services and `rpc_pipefs`. Together they connect the kernel/RPC implementation layer to the operator’s remote-storage and network-appliance workflow. ## Missed Signals and Open Leads Identify the originating distribution and exact service names. Determine whether “cpio” was a command, archive format, initramfs component, or a misread term. ## Sources - [[Scanned_20260730-1802|Scanned_20260730-1802]], especially PDF pages 8, 9. - `Scanned_20260730-1802.pdf`, cited as a plain archival filename; the PDF is not stored in `wiki-notes`. - **[S09]** Linux Kernel Documentation, “I2C/SMBus Subsystem”. https://docs.kernel.org/i2c/