You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
which was okay until -C option (mount target AKA local chroot) was introduced
now it is well feasible that several different folders be mounted on the same server.
perhaps it would be nice if yafsw would change default label then (but - potentially a filename length limit? dunno).
maybe it would be nice if yafsw would provide an option to override default volume label
also, if i change volume label from Explorer it seems to work and propagate across applications.
So, maybe (if we assume yasfw to be called by design from script files) it is of lesser use, we could run label command in a "parallel thread" to yasw, except that yasfw does not warrant to actually use the provided, fixed drive letter (#29), D'oh...
Also, BTW, what happens with the changed volume label? is it somehow propagated to SSH server and change somethign there? i wonder. Probably not, probably it is RAM-only thing, but being not documented anywhere leaves me with a bit of F.U.D.
The text was updated successfully, but these errors were encountered:
I'm not sure what's happening under the hood for renaming. My code always returns the "user@host:ip" string. Probably there's some magic in Dokan or Windows.
Anyways, it sounds good to add an option to customize the label.
when mounted the volume label is set like
[email protected]:22
which was okay until
-C
option (mount target AKA local chroot) was introducednow it is well feasible that several different folders be mounted on the same server.
perhaps it would be nice if
yafsw
would change default label then (but - potentially a filename length limit? dunno).maybe it would be nice if yafsw would provide an option to override default volume label
also, if i change volume label from Explorer it seems to work and propagate across applications.
So, maybe (if we assume yasfw to be called by design from script files) it is of lesser use, we could run
label
command in a "parallel thread" to yasw, except that yasfw does not warrant to actually use the provided, fixed drive letter (#29), D'oh...Also, BTW, what happens with the changed volume label? is it somehow propagated to SSH server and change somethign there? i wonder. Probably not, probably it is RAM-only thing, but being not documented anywhere leaves me with a bit of F.U.D.
The text was updated successfully, but these errors were encountered: