| commit | 03387a0f5886d449eda359a5acecd830f3bd35bc | |
| author | Alexander Bokovoy <ab@samba.org> | |
| Thu, 17 Jan 2008 13:51:14 +0000 (17 16:51 +0300) | ||
| committer | Alexander Bokovoy <ab@samba.org> | |
| Thu, 17 Jan 2008 13:59:29 +0000 (17 16:59 +0300) | ||
| tree | eff51ba251254ee3954f60b557ec4d1ff9aa553c | treesnapshot (tar.gz zip) |
| parent | 026a66abecea3e3a54cdbfb97129d5e65608e5df | commitdiff |
Remove is_remotestorage() call from VFS. We already have statvfs() there to handle FS capabilities.
As discussed with Volker, it is better to calculate FS capabilities at
connection time. We already do this with help of VFS statvfs() call
which allows to fill-in system-specific attributes including FS
capabilities. So just re-use it if you want to represent additional
capabilities in your modules. The only caution is that you need to
call underlying statvfs() call to actually get system-specific
capabilities (and other fields) added. Then add module-specific ones.
(This used to be commit e342ca0d931f9a5c8ec9e472dc9c63f1fe012b3a)
As discussed with Volker, it is better to calculate FS capabilities at
connection time. We already do this with help of VFS statvfs() call
which allows to fill-in system-specific attributes including FS
capabilities. So just re-use it if you want to represent additional
capabilities in your modules. The only caution is that you need to
call underlying statvfs() call to actually get system-specific
capabilities (and other fields) added. Then add module-specific ones.
(This used to be commit e342ca0d931f9a5c8ec9e472dc9c63f1fe012b3a)