The storage layer gains its policy home (storage-architecture.md): a new system/services/volume-manager, spawned by init, that acquires the mass- storage block channel through the device manager (the same lineage a filesystem uses), reads block 0, and parses the first volume out of it. The partition-table walk that lived in the FAT engine moves here, above the driver where it belongs (partition.zig, host-tested: MBR entry, bare-FAT, no-signature). Identity is the MBR disk signature + partition index — the weak rung of the ladder; GPT GUID and FAT serial refine identityOf without changing shape. This increment is discovery + probe + log only, additive: the FAT service still acquires its own volume, so nothing changes for it. Confining each filesystem to its partition and spawning one per volume (the flip) lands next, keeping fat working throughout. Grants + wiring: init.csv spawns it after the device manager; protocol.csv grants bind volume-manager + open device-manager. Verified: volume-probe asserts the parse (bare-FAT volume at lba 0), neutral 10/10 across storage, restart, display, logging, confinement — the volume manager now runs in every boot and disturbs nothing.
17 lines
717 B
Zig
17 lines
717 B
Zig
.{
|
|
.name = .volume_manager,
|
|
.version = "0.0.0",
|
|
.fingerprint = 0x911b01e1eaeabcf5, // Changing this has security and trust implications.
|
|
.minimum_zig_version = "0.16.0",
|
|
.dependencies = .{
|
|
// build-support supplies the shared recipe; kernel is implicit in every
|
|
// binary. device (block, driver) and protocol (device-manager-protocol,
|
|
// envelope) are the homes of this service's remaining imports.
|
|
.@"build-support" = .{ .path = "../../../build-support" },
|
|
.kernel = .{ .path = "../../../library/kernel" },
|
|
.device = .{ .path = "../../../library/device" },
|
|
.protocol = .{ .path = "../../../library/protocol" },
|
|
},
|
|
.paths = .{""},
|
|
}
|