[Info-vax] Is there a way to enabling versioning in Samba

Jan-Erik Soderholm jan-erik.soderholm at telia.com
Fri Jul 21 08:56:47 EDT 2017


Den 2017-07-21 kl. 14:30, skrev Craig A. Berry:
> On 7/21/17 3:56 AM, Jan-Erik Soderholm wrote:
>> Den 2017-07-21 kl. 05:41, skrev Craig A. Berry:
>>> On 7/20/17 10:31 PM, David Froble wrote:
>>>> don.zong at gmail.com wrote:
>>>>> My impression with Samba is that the file is always overridden, no 
>>>>> versioning. revision number might change though. Wondering if there is 
>>>>> a way to enable versioning in Samba - so that whenever there is a 
>>>>> change in the file, it will create a new file with a new version.
>>>>
>>>> My impression is that you're asking the wrong question.
>>>>
>>>> When using Samba, you're accessing files on a VMS system from an OS 
>>>> that doesn't have versioning in it's file system. 
>>>
>>> How do you know that? Wouldn't he likely be using Windows, which does
>>> have file versions? See, for example:
>>>
>>> <https://msdn.microsoft.com/en-us/library/windows/desktop/ms646981(v=vs.85).aspx> 
>>>
>>
>> But that is an file attribute, not part of the filename specification.
>> More like the link data in a VMS EXE file, than the VMS file version.
> 
> Yes, sorry, that link isn't to the feature I was thinking of. I think
> it's called file history or something. In any case, recent releases of
> Windows do have a sort of file versioning. The semantics are likely a
> lot different (I've never used it) but there are certainly ways of
> maintaining multiple versions of files.
> 
>>> Dunno if it's in SMB, much less Samba.
>>
> 

Anyway...

For a SAMBA share, that is used to load data from external sources
into some VMS system, it can make sense to have new version created
instead of simply overwriting the previous version.

For a SAMBA share where you expect some external system to access and
"use" the files on the share, multiple versions does not make any sense.





More information about the Info-vax mailing list