On Thu, Feb 21, 2013 at 5:45 PM, Rob Townley <[email protected]> wrote: > > > On Thursday, February 21, 2013, Jeremy Allison <[email protected]> wrote: >> On Thu, Feb 21, 2013 at 04:38:13PM -0600, Rob Townley wrote: >>> On Wednesday, February 20, 2013, Jeremy Allison <[email protected]> wrote: >>> > On Wed, Feb 20, 2013 at 11:30:37AM +0100, Sven Tegethoff wrote: >>> >> >>> >> What we have here is a problem of two incompatible text fields, and >>> >> it does not make a difference if that incompatibility is a filenames >>> >> in a file system or some table in some kind of non-filesytem media >>> >> library. If you can't fix the incompatibility and if you can't >>> >> change the underlying process that generates the data to only create >>> >> names that fit the lowest common denominator all systems can handle, >>> >> the obvious solution is to put in some kind of translation rule. >>> > >>> > The only question is whether that translation rule belongs in Samba >>> > :-). >>> > >>> > It used to, but now I think it's better for it to be done externally >>> > :-). >>> > >>> > Jeremy. >>> > -- >>> >>> >>> Could there be an add-on module such as >>> samba-enforce-dumb-filefolder-names ? >>> Is Samba written in a modular enough way to add in a filesystem layer? >> >> Samba is *designed* to allow this :-). Check out the VFS >> module interface. You'd have to catch all the path-based >> calls. >> >> Jeremy. >>
Sorry i fat fingered gmail on my smartphone web browser. Now, i am thinking it would be better as an ext2/3/4 module for those cases the Linux users are accessing the same file hierarchy but not via Samba. Maybe it has to be in Samba as well to satisfy all the different file systems available to Linux servers. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
