For a long time, progress on Dwarf Goats was measured by individual boundaries. Could GNU Mach reach the hardware? Could the Hurd come up natively? Could the network carry a real session? Each result mattered, and each had to be demonstrated on the Raspberry Pi 4 rather than inferred from a build or a virtual environment. But a collection of proven subsystems is not yet a machine a builder can settle into.
The recent work changed that relationship. A compact Dwarf Goats image was provisioned onto different removable media, read back in full, and cryptographically verified against its source. The new medium then completed two standalone hardware boots. On those boots, GNU Mach and the GNU Hurd reached a writable persistent root, the system retained its writable state, and its SSH server identity remained stable.
That portability result matters because the operating environment is no longer tied to one historical card that happened to survive the laboratory. The runtime storage policy now accommodates the intended class of removable media. The proof was physical: a different medium, a complete verified write, repeated boots, and state that was still there afterward.
The next boundary was entry. Earlier remote access proved important network and process behavior, but routine use still carried laboratory conditions around it. Dwarf Goats now stores local password authentication persistently. A normal network client can connect directly, authenticate with the password held by the system, and arrive at an interactive dwarf shell. The password, SSH server identity, and writable state all survive reboot.
Ordinary login no longer depends on a project-specific client private key, a proxy hop, or an auxiliary authentication service. For the final direct-login demonstration, the recovery bridge was powered off. The accepted session belonged to the standalone machine and the client connecting to it, with no hidden laboratory dependency completing the path.
The important change is simple: I am no longer only proving that pieces of the operating system work. I am beginning to use the operating system itself.
That changes the texture of the project. Persistence means a session can leave useful state behind. Stable server identity means the machine presents continuity across boots. Direct login means entering the system can be ordinary instead of ceremonial. Media portability means the working environment is a reproducible physical system, not an accident preserved on one irreplaceable device.
None of those statements rests on a screenshot or an expected code path. The image was fully read back and checked. The hardware booted twice. State was written, the machine was rebooted, and the state was observed again. A normal client authenticated directly while the recovery bridge was off. The evidence is the behavior of the machine.
Dwarf Goats remains built on upstream free software, including GNU, GNU Mach, GNU Hurd, and Dropbear, with Dwarf Goats-developed GNU Mach/Hurd support implemented by the Dwarf Goats project. Credit belongs to the upstream contributors whose work makes this laboratory possible; no endorsement or affiliation is implied.
There is still a great difference between a physically usable research system and a finished general-purpose operating system. This entry does not erase that distinction. It records the moment the machine became somewhere I can enter, do work, leave state, and return. For a builder, that is a different kind of milestone.