guideXOS Server File System and Storage
Purpose: document storage controllers, filesystem layers, package locations, and current disk tooling.
Kernel storage stack
The current kernel initializes a block-device layer, ATA/SATA, NVMe, RAM disks, VFS, and multiple filesystem drivers. The hardware support report also documents storage-controller and filesystem support with much more breadth than the old placeholder suggested.
Current status: broad storage and filesystem work is already present in the current Server source tree.
Known gaps: some filesystems and installer workflows still need more validation before they should be treated as polished end-user paths.
Back to /Wiki/Server
| Area | Status | Notes |
|---|---|---|
| ATA / IDE | Implemented | Explicit kernel initialization and hardware-report coverage. |
| AHCI / SATA | Implemented | Documented in the hardware support report and part of the storage initialization story. |
| NVMe | Implemented | Kernel init path and report coverage are both present. |
| RAM disk | Implemented | The kernel creates a RAM disk and also supports boot-time wallpaper pack handoff. |
| VirtIO block | Partial / evolving | Kernel includes VirtIO block code, while the hardware support report still warns against overclaiming support maturity. |
| VFS | Implemented | Mount points, path resolution, file handles, and directory operations are documented. |
| FAT32 / exFAT / ext2/4 / UFS | Implemented | Documented by the hardware support report and reflected in kernel source layout. |
| NTFS / XFS | Partial | Kernel source includes NTFS and XFS files; the hardware support report is more conservative, so these should be discussed carefully until broader validation is surfaced. |
Disk Manager
disk_manager.cpp clearly distinguishes host and bare-metal modes. In hosted Windows mode it supports host image attachment workflows;
in bare-metal mode it uses the kernel block layer. That makes it a real bridge between test-harness development and OS-side storage work.
HD Installer
hd_installer.cpp is a real installer UI path, but the inspected code still contains TODO-style placeholders such as fake disk discovery and future partitioning/USB work.
Application package storage
The package manager installs .gxapp packages under /system/apps and stages them under /system/apps/.staging.
The install flow validates architecture compatibility, writes a staged copy, reopens it for validation, and then renames it into place without silently overwriting an existing package.