On 05/22/2016 07:12 AM, Alan Altmark wrote:
On Saturday, 05/21/2016 at 02:00 GMT, WF Konynenberg <[email protected]>
wrote:
That means the "native" way to deal with these on Linux would be
to implement some "cmspack" utility which can pack/unpack such files (as
was indicated, the assembler source code is available so it's easy to
figure out how to do this and reimplement it in a bit of C code), and
teach the file command about this file format so it can correctly report
it.
If folks think having a separate utility and teaching Linux folks to
recognize a packed CMS file when they see it is the right way to go, then
I sure won't stand in the way!
I think the rule should probably be that
- if the "packed" status of a file has always been fully transparent to
CMS applications and users, and handled completely within the file
system code of the operating system, then it would make sense to
implement this as part of the cms-fuse file system, similar to how some
Linux filesystems can transparently compress files internally without
exposing this to applications,
but
- if the "packed" status of a CMS file is user visible to some extent
and requires some explicit handling, e.g. applications or users being
aware that they need to unpack before they can use the data, etc, then
it should probably be handled the same way that the various other
compressed file formats are handled in Linux/Unix, i.e. make sure
users/applications can identify these formats, and have a set of
commands to compress/uncompress the files, which can, if desired, be
used in a pipeline to do so "on the fly".
Willy
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
