> EricVH's /srv replacement. See > http://graverobbers.blogspot.com/2008/12/srv-next-generation-service-registry.html
perhaps i don't understand the srv² proposal, to which there are many parts, but part of the problem seems to be finding a service. generally this is mediated by /net/cs. i wonder if thinking of it that way might help? > Assuming that the resource can be named in the plumber's namespace? This > works out less well for things like ramfs's that were told where to mount > (-m) and not to use /srv (-s). Or is there something really sneaky going on > here that I don't know? by definition it must be. the rule is this: type is text data matches 'Local (.*)' plumb to none plumb start rc -c $1 it executes the mount in the plumber's namespace, which is helpfully shared by rio. (Local in acme is interpteted by acme, not sent to the plumber.) - erik
