Mike Wyer wrote:
[------ %< snip snip %< -------------]
>
> It's one of the more common complaints we get from new users:
> "/vol/bitbucket isn't there on my machine!"
> "Try cd'ing into it"
> "Oohhh."
>
> But people get used to it pretty quickly.
>
IMO, expecting users to navigate a file system in the dark is a **huge**
deficiency in usability. If it is technically possible to fix this
problem it should be done.
One way I've worked around this stupid behavior is to make a symbolic
link to a top level directory. For example, research directories are
auto mounted in /res. User's have a symbolic link from /res/<user> to
/home/<user>/research. When they do a directory listing in /home/<user>
they see the directory "research" along with everything else.
Application programs that are shared cluster wide are mounted in the
same way so that curious users, who have no idea about 'ypcat -k
auto.misc', can browse the filesystem and discover software.
my $0.02 worth,
Rich
