> non-kernel resources. Consequently, if the non-kernel 'root' is lost, > the dead processes can be killed off, another root acquired, and work > resumed. If no local resources are available, a srv and mount of > sources allows access to the tools of the full distribution.
would the dead processes include everything but the boot-time helpers? from the perspective of any users of the system, wouldn't this be equivalent to a reboot? > As an example of the flexibility of this approach, I have tested this > scenario: a rootless system starts up with interactive=yes set in the > plan9.ini. It starts factotum, ipconfig, and then a venti server, and > then pauses its bootup process. A second machine is then started as > the fossil file server, and it is instructed to dial the venti and > begin serving fossil and its normal startup. Once the fossil is > serving, we return to the machine serving venti, and continue through > the bootup process, and choose to imitate tcp-booting - and select the > external fossil for the external service to mount. The fossil is > dialed and bootup continues as if it was a standard tcp root cpu > server. The end result is that even the system hosting the venti is > still "rooted" via an external fossil which is in turn using the venti > as a backing store. have you tested rebooting either machine while the other is running? have you tested a three machine scenario? this reminds me of nfs cross mounting. how is this different? - erik
