> All of the same comments apply to /srv (though srv^2 is trying to solve > this).
not true. import $server / /n/$server will give you access to srv on $server as /n/$server/srv. what is "srv^2"? > 1) Sending files across namespaces so that I can spawn acme at rio startup > and plumb to it without having to recreate mounts in its namespace. plumb "Local (bind|mount) args" will accomplish this. > 2) Sending parts of namespaces around locally without needing to run an > exportfs in that namespace. (i.e. open() a directory && sendfd() that to > another process who can mount() it.) Among other things, this allows the > shell (and others) to easily offer the current working directory fd (rather > than path) to rio for tab completion. you can't mount a random directory. > 3) Some small thought about being able to implement srv^2 entirely in > userland, and what the primitives would look like. sendfd() or the above > outlined devcapsrv seems better than the current devsrv to me, but I confess > I might be mistaken. what's the advantage of implementing srv entirely in userland? - erik
