On Sun, Jun 1, 2025, at 23:21, Ron Minnich wrote: > One thing I hear a lot: installing Plan 9 is headache for many > people, particularly trying to trace down working docs to produce > working code: "... it's just a maze full of dead ends."
Improving Plan 9 adoption begins not with documentation, but with better workflows built into the software itself. When the process becomes intuitive to follow, guidance becomes a supplement rather than a mandatory reference. Instead of continuing with single-machine installations, it makes more sense to design an installer that reflects the system’s original intent and architectural philosophy. Plan 9 was built for distributed computing environments. Its architecture encourages machines to cooperate closely, each fulfilling a specific role in the broader network. These roles may include terminal, CPU server, or file host, operating together as a coherent and unified system model. A streamlined workflow often begins with PXE boot support. A small network boot image retrieves the kernel and shell. This removes the need for USB media or optical discs. Protocols such as TFTP or HTTP serve files to each client. This makes multi-node deployment fast and repeatable. After boot, each machine constructs its working namespace by mounting user files and system services using the 9P protocol from a configured and centralized file server. Resources appear in the file tree as live remote services. A browser-accessible interface may be made available early. After loading the kernel, the user connects via the LAN. This interface assigns a role, discovers peer services, applies network settings, and completes system preparation. Use of the graphical environment can wait until later. Each installation may follow a predefined role-based file. Terminals provide access to users, CPU servers process jobs, and file servers manage persistence across the workspace. These roles are configured using YAML or similar formats. The structure supports both default and custom profiles. The process works both online and in isolated environments. When the network is available, updates and files download. When disconnected, an ISO offers a complete system base. Both approaches use the same profile and configuration set. By building practical workflows into the system itself, Plan 9 becomes easier to adopt without added complexity. Instead of navigating outdated or scattered instructions, users are guided through a structured and reliable setup. This reflects the clarity and purpose of Plan 9’s design. - vic ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tbe8e5fda6ae62f5c-M2ad71002e631ca2bdb8c6619 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
