> I hope there's no hard reason for that. It ought to be possible to set > up some bridging (similar to what vmware does between host and guest os). > > But sure, that's a project for the future. Having the parent hurd > provide a "fake" device port for the subhurd to use, not giving it > direct access to the real Mach device port, would be a start, I guess. > But I'm mostly ignorant about Mach device access.
This is exactly what `boot' does for the root device and the console already. It would be straightforward to make it intercept other device_open calls and provide other virtual devices, like a fake ethernet. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]