From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 6 Jan 2009 15:13:37 -0800 From: "Roman V. Shaposhnik" In-reply-to: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-id: <1231283617.5141.74.camel@goose.sun.com> MIME-version: 1.0 Content-type: text/plain Content-transfer-encoding: 7BIT References: Subject: Re: [9fans] Why do we need syspipe() ? Topicbox-Message-UUID: 7b0bfb0a-ead4-11e9-9d60-3106f5b1d025 On Tue, 2009-01-06 at 20:37 +0000, Charles Forsyth wrote: > >This just means that these services need to be mounted at the canonical > > there is no point binding #a or #D into the name space. > they can be used only locally and might as well > be accessed directly. they might be considered similar to > "push" in streams. #s has a similar difficulty to #a and #D when creating the names, > and requires special hacks to make existing files usable when exported. Well, that's been the case for as long as Plan9 existed, and I don't want to say that it doesn't work. Although in the alternative universe I can see how implementing #X as *channels* capable of 9P messages, could enable things like mounting them on external hosts and letting these hosts manipulate physical devices attached to yours (I agree that remote mounting of the kernel services, which do not correspond to physical devices, is less useful). Just like exporting my *local* /srv can be a useful things at times. Thanks, Roman.