On Jan 5, 2009, at 3:00 AM, Charles Forsyth wrote:
Things like
term% cd '#|'
term% pwd
#|
just don't seem right.
you ask for fish; you get fish.
what's the trouble?
I supposed this is a matter of taste. There's as little
trouble with the above as with //foo != /foo on certain
legacy systems. Or, as was pointed out by Roman Z,
with MS-DOS drive nomenclature. They all work fine.
Yet, the closer I can get to a single namespace rooted
at / the better I feel. With #X I get at least two: one rooted
at / and the other one rooted at #.
And just to be completely clear: the #X notation doesn't
bother me when #X can be thought of as a weird cousin
of '/srv/#X'. Both are simply channels that need to be
mounted in order for the file hierarchy to appear. See,
I would go even as far as to say that, even though I know
there's no 9P involved with #X, I wouldn't mind at all
if open("#X", ORDWR) gave me an illusion of 9P messages
being exchanged.
The implicit attach that happens behind my back
when I access #X/foo is what makes me cringe.
Thanks,
Roman.
