> > The existing convention appears to be that "fs type" programs
> > such as mount, umount, go in /usr/lib/fs/$FSTYPE whereas
> > other FS support programs [go] in /usr/lib/$FSTYPE, such as
> > /usr/lib/nfs/{mountd,nfsmapid} etc.
> >
> > I just followed that convention.
>
> As Jim already commented, there seems to be confusion here what the actual
> convention is. Apart from /usr/lib/fs/ufs, another case in point (which
> doesn't only contain filesystem-specific plugins, but also e.g. cachefsd),
> is /usr/lib/fs/cachefs.
>
> I suppose it makes more sense to collect everything in one place
> (/usr/lib/fs/<filesystem>) than to randomly scatter them over two different
> ones.
>
> Comments?
>
> Rainer
It appears that cachefs is the "odd man out" here.
I'd rather follow the precedent of autofs, nfs, zfs,
unless someone can point to rules to the contrary.
Here are the current usr/lib/fs and usr/lib files:
usr/lib/fs/autofs:
automount dfshares mount share unshare
usr/lib/autofs:
automountd
usr/lib/fs/cachefs:
cachefsd cachefslog cachefspack cachefsstat cachefswssize
cfsadmin cfsfstype cfstagchk dfshares fsck mount share
umount unshare
usr/lib/fs/nfs:
amd64 dfmounts dfshares libshare_nfs.so.1 mount nfsfind
showmount umount
usr/lib/nfs:
libmapid.so libmapid.so.1 llib-lmapid llib-lmapid.ln
lockd mountd nfs4cbd nfsd nfslogd nfsmapid rquotad statd
usr/lib/fs/zfs:
fsimage.so fstyp fstyp.so.1 mount umount
usr/lib/zfs:
availdevs pyzfs.py pyzfs.pyc
