Hi Leland. >I have looked into this, but from a z/VM standpoint. I had to table it >until I got some other things cleaned up. If interest is high, I will move >it closer to the edge of the table and it might fall off sooner. ;-)
Cool. >What I had planned was this... >Port portions of the e2fsprogs distro, mainly the ext2fs library >Provide the necessary lowlevel I/O routines I like to remind folks that file systems live within logical volumes. In a simple world your ext2/3 fs would be habitating within a single disk partition. However, what do you do for md, lvm or evms volumes? You would not have the logical volume manager code that is capable of understanding metadata and building the logical volumes. And a 390 that isn't using linear or lvm volumes just isn't being used to its potential. >Create simple command line utes like "ls", "cp", "chmod", and such to access >the filesystem Port busybox. Don't know about soft links on vm or mvs though. >Ultimately, create a Rexx function package to directly access the file >system >Any suggestions, comments, rants? Well, how do you build a fs on VM or MVS? I think most everything lives in your addr space and the i/o is the only thing that trancends. Like you could memory map the dasd partition into a dataspace or build a logical volume using several dataspaces and then run your linux fs in the process space ... kinda like a flattened fs. This would be like running device mapper and evms in the process space and having the device mapper code build the dataspaces for you when evms sends it target mappings. -Don
