[Info-vax] fixing a saveset's attributes: attachment, not ftp

[hb]

On 06/22/2015 07:05 PM, Stephen Hoffman wrote:
> But the implementation of BACKUP here is... broken.   Or we wouldn't
> still be having this discussion.  Again.

You mean the "solution" /REPAIR is broken, or? Obviously backup can read
a Stream_LF file and find the backup header and its data. Why should it
"REPAIR" the file, aka change the file attributes?

And in case the save-set is read-only (on a CD/DVD...) backup can't
"REPAIR" it anyway:
-RMS-E-PRV, insufficient privilege or file protection violation

For the blocksize, if one extracts the octet-stream on a Linux box and
uses 'file', one gets this:

$ file x.bck
x.bck: OpenVMS backup saveset data (block size 32256, original name
'VOIT-150513.BCK', AXP generated)
$

unfortunately I can't use GNV for that (or is GNV mis-configured on that
system, EISNER?):

$ @GNV$GNU:[lib]GNV_SETUP
$ bash
bash-4.3$ file x.bck
file: could not find any magic files!
bash-4.3$

On the other hand, what should be the "natural" RMS record format for
"Content-Type: application/octet-stream;"?

To me UDF seems more appropriate than any of STM[CR|LF]. OK, that
doesn't change the backup problem, but I wouldn't expect any record
structure in an octet-stream at all.