Subject rfork N

I want to construct a new namespace for an app, including a new root dir.
I was hoping to do this with a few lines of script starting with rfork N,
however this seems to be a dead end.

I can still access kernel devices directly using the # escape in filenames,
which includes '#s/fossil' for my file server. However I cannot get access
to mount(1) so I can never access any files in that fossil.

is rfork N in rc useless, and do I get a prize for noticing?

(or is it a lack of vision on my behalf as usual?)

-Steve

Reply via email to