mirror of
https://github.com/BoredDevNL/BoredOS.git
synced 2026-05-15 18:58:40 +00:00
DOC: Adjust filesystem documentation
This commit is contained in:
parent
60ab70a49d
commit
1e19963a8d
1 changed files with 11 additions and 8 deletions
|
|
@ -19,16 +19,19 @@ Key VFS functionalities include:
|
||||||
|
|
||||||
## 💾 FAT32 Implementation
|
## 💾 FAT32 Implementation
|
||||||
|
|
||||||
The primary filesystem logic in `fat32.c` is currently built as a RAM-based filesystem simulation.
|
The primary filesystem logic in `fat32.c` handles both in-memory RAM-based filesystem simulation and physical ATA block devices.
|
||||||
|
|
||||||
### 💿 Booting and the RAMFS
|
### 💿 Storage Support
|
||||||
Since BoredOS boots from a CD-ROM ISO image generated by `xorriso`, it does not read directly off the CD to execute applications.
|
|
||||||
|
|
||||||
1. **ISO Booting**: During boot, Limine loads necessary files (such as userland `.elf` binaries, fonts, and wallpapers) into memory as standard boot modules.
|
BoredOS supports two main types of storage for its FAT32 implementation:
|
||||||
2. **RAM Simulation**: The FAT32 filesystem code parses these loaded memory modules and automatically constructs a synthetic FAT32 directory tree inside RAM.
|
|
||||||
3. **Root Filesystem**: All active execution of built-in GUI and CLI apps occurs off this read-only, in-memory FAT32 simulation.
|
1. **RAMFS (Boot Modules)**: During boot, Limine loads necessary files (such as userland `.elf` binaries, fonts, and wallpapers) into memory as standard boot modules. The FAT32 code parses these loaded memory modules and automatically constructs a synthetic FAT32 directory tree inside RAM (mounted as `A:`).
|
||||||
|
2. **ATA Drives**: The kernel includes a basic PIO-based ATA driver that can detect and read/write to physical IDE/PATA hard disks.
|
||||||
|
- **GPT is NOT supported**: Currently, only **MBR (Master Boot Record)** partition tables or **raw (partitionless)** disks are supported.
|
||||||
|
- **Filesystem**: The partition must be formatted as **FAT32**.
|
||||||
|
|
||||||
|
### 🔍 Auto-detection
|
||||||
|
The `Disk Manager` automatically probes primary and secondary IDE channels during initialization. If a valid FAT32 partition is found (either directly at sector 0 or via an MBR partition table), the disk is assigned a drive letter (starting from `B:`) and becomes accessible to the VFS.
|
||||||
|
|
||||||
> [!WARNING]
|
|
||||||
> **Limitations:** The current `fat32.c` implementation in BoredOS is strictly a RAM-based filesystem simulation. It **does not support** reading from actual block devices (real disks). Consequently, external disk images are not recognized, and any operations requiring persistent storage are unsupported.
|
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue