|
From: <pr...@po...> - 2006-01-03 02:14:34
|
Miklos Szeredi <mi...@sz...> wrote: > Maybe instead of running several sshfs instances, a single process > could handle more then one connection. The advantage would be that > the above problem would go away completely without having to do the > symlink trick. What's your opinion? Yes, I think that's the best way. I guess it would still be a separate program from sshfs, but sharing much of sshfs's code. I had also thought about filling in the root directory at startup with subdirectories named after the hosts mentioned in ~/.ssh/known_hosts or ~/.ssh/config. It's not as important, but might be nice. >> I'd also like to have an option in sshfs to make readlink() prepend >> the mount point to a symlink's target, if the target is absolute - >> this way, the symlink points to the right file within the mount point. >> What would be the best interface for this? Another -o workaround=? > > Possibly. I've resisted this feature, but if you send a patch maybe > I'll add it :) Ok, I'll give it a try. paul |