Join GitHub today
[RFE] provide sub-directory mount option in fuse, for a given volume #175
Thanks for all these pointers. Yes, I am aware of client side approach being not good enough.
But i still believe this is a good enough solution if on the client machines admin has not given access to people to mount.
I like the tenant approach @jdarcy did. Will need further discussion on this.
Can we list down the basic necessity of the feature?
referenced this issue
May 2, 2017
pushed a commit
May 30, 2017
pushed a commit
Jun 13, 2017
What is pending is, how will we handle the authentication options for this at each subdir level?
I propose to keep the current option and extending it to handle new feature with proper backward compatibility.
For example the current option looks likes this:
In future, it may look like:
so each entries will be separated by ';'. And in each entry, first part (" =") is address list and second part is directory. If directory is empty, its assumed as '/'. (Handles the backward compatibility). And if there is no entry for a $subdir here, that $subdir won't be mountable.
(The above format is handled properly already at  in addr.c, the pending thing is to handle the option properly in options.c's validate).
If everyone agrees to this, I guess we can pull it off before absolute feature freeze date for 3.12 branch.
Let me know the feedback.
NOTE: I thought of using ':' (colon) as field separator between addr_list and subdir entry, but with IPv6 ':' is valid character in string. Hence using ' ='.