>>> On 5/22/2016 at 09:01 PM, WF Konynenberg <[email protected]> wrote: > So if cmsfslst can find all the relevant bits & bytes in the CMS file > system that indicate what sort of file this is, and how it is to be > read/parsed by programs, then cmsfs-fuse should be able to somehow (by > whatever feasible means) pass the info from these bits & bytes to the > Linux program accessing the file system through cmfsf-fuse.
Which is typically not done by the various file systems because the usual intent is that no real changes will have to be made to the various tools that people are accustomed to using. Things like ls, cat, file, vi, etc., etc. The more involved something like this becomes, at least in terms of the number of tools that have to be modified, the less likely anyone is going to be willing to attempt any of it. Particularly if they're not coming from a mainframe background. I recently came across a question in an online forum where the poster was asking how to tell if the input their program was reading was base64 encoded. The various responders were suggesting all sorts of things they could check to get some idea if it might be or not. My suggestion would have been "try to decode it and see if it works. If it does, it was base64 encoded." I suspect something similar is going to wind up having to be done here. Mark Post ---------------------------------------------------------------------- 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/
