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

[Jan-Erik Soderholm]

Den 2017-07-22 kl. 04:52, skrev David Froble:
> Jan-Erik Soderholm wrote:
>> Den 2017-07-21 kl. 15:25, skrev David Froble:
>>> Craig A. Berry wrote:
>>>> 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> 
>>>>
>>>>
>>>> Dunno if it's in SMB, much less Samba.
>>>
>>> Interesting reading.  However, while some capability may potentially be 
>>> there, I sure don't see multiple versions of a file in Windows 
>>> Explorer.  Didn't read all of the info, but, I'm not sure it's the same 
>>> as VMS file versions?
>>
>> It is definitely not, as I explained in another post. It is more like
>> pulling an "old version" from a BACKUP save set. And you must specify
>> an alternative directory, if you do not want your current file to be
>> (permanently) over written.
>>
>>
> 
> Yes, I saw your posts, and it seems clear that from a standard weendoze 
> utility, such as Windows Explorer, versions cannot be seen, or specified.  
> To me, that means weendoze does not support file versions, at least in the 
> filespec.
> 
> Getting back to Samba, even if it somehow supported file versions, there is 
> no way to specify them from normal weendoze utilities.

Sorry for the empty post...

I really doesn't have to "support" file versions. I'd guess that is is more
a question of how a "new" file is created. If it is possible to write it as
a "create a new version" without the client even knowing about that, it
would at least be better than today.

As I wrote, multiple versions is probably mainly of some interest for
inbound files, where some VMS routines/process can see each file and
process/delete them.

For outbound files, there is little use of file versioning, since the
clients doesn't support it anyway.

Trying to convert VMS files with versions into client filenames is
a dead end, as I see it.