One virtual tree, several kinds of content
GhostFrame presents Unix-style paths. Your home directory is a place for notes and practice files. /etc contains configuration, /var/log contains system evidence, and /var/www contains supported virtual web content. Paths refer to GhostFrame’s filesystem, rather than equivalent folders on your Windows desktop.
pwd, ls, and cd help establish context. cat reads text. mkdir and touch create practice content, while cp and mv copy or move it. Relative paths begin at your current directory; absolute paths begin at /. ~ points to your current home.
The simulated files have real persistence
The main Ghost OS filesystem is backed by an application-owned virtual disk in GhostFrame’s local learner data. Files you create are meaningful stored work. Learner profiles and progress also have local persistence, so treat backups as part of working with the beta.
The beta preserves its GhostFrame AppData folders after uninstalling to allow work to survive reinstallation. Removing retained data deletes the contained learner state and virtual disk. See the privacy policy for the current storage and removal details.
Learn to distinguish access from existence
A file can exist without being readable or writable by the active identity. Supported local file operations use owner, group, and mode-bit checks, while protected or read-only providers can impose additional limits. Symbolic links refer to virtual paths; following a link does not give the caller a different identity.
chmod, chown, and chgrp provide supported metadata exercises. Privileged operations may require permitted elevation. This is a bounded educational permission model, with limits across different session and interpreter workflows; it is not a claim of complete Linux security or host isolation.
Explore disks and mounts deliberately
Supported storage exercises include inspecting virtual disks and partitions, formatting supported data volumes, mounting them into the virtual tree, and examining capacity. Simulated RAID exercises add member and degraded-state concepts. These are GhostFrame-owned storage workflows, rather than tools for repartitioning your Windows disks.
A mount changes what content a path exposes. A read-only mount and a full mounted volume can both reject a write for different reasons. Use disposable practice data and read the supported command help before any formatting, deletion, or storage change.
Files are part of the scenario
Configuration can explain a network result: inspect /etc/hosts and /etc/resolv.conf when investigating a name-resolution problem. Logs can explain a denied action. Virtual HTTP content under a service’s web root can explain what a client retrieves.
Keep local Ghost OS files distinct from the generated filesystem views of remote lab devices and from machine-console storage. Their supported operations and persistence differ. A useful exercise is to record the active prompt and path alongside every piece of evidence.