File: TODO

package info (click to toggle)
bindfs 1.8.4-1
  • links: PTS
  • area: main
  • in suites: squeeze
  • size: 1,328 kB
  • ctags: 247
  • sloc: sh: 10,179; ansic: 1,524; ruby: 236; makefile: 61
file content (25 lines) | stat: -rw-r--r-- 945 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25

Soon:
- chmod-x-only = only allow +-x on files.

Major (i.e. probably not very soon):

- Applying options to a subset of all files;
  something like --if-file-matches '*.md5' { -u checksummer -p u+rw }
  - This would make for some new useful options like --hide or --deny
  - We could also have special xattrs like 'bindfs:perms' that
    don't get propagated to the base directory but control bindfs behaviour
    instead.
  - All this leads to the thought of an integrated minilanguage.
    Taken to the extreme, would this make bindfs almost yet another scripting
    language binding for FUSE and is that a bad thing?
    - Stackable/pluggable scripts? Any benefit over a remount?

Minor:

- Decide what to do with the fuse options uid=N and gid=N, or at least
  mention them in the docs.

- Look at capabilities instead of uid==0 when checking for special privileges.
  Do this in a portable way and fall back to uid==0 if not available.