On Thu, Jun 19, 2008 at 5:11 PM, Malcolm Beattie <[EMAIL PROTECTED]> wrote:
> I wrote writetrack and readtrack kernel modules for Linux 5 years > ago which implement ioctls to do that along with simplistic userland > utilities and they worked OK for me to transfer various VM and z/OS > disks as images via plain Linux files. The internal kernel API for > DASD driver disciplines was a bit icky back then so they would need a > good polish (or simply a rewrite based on the existing template). IMHO the disadvantage of that approach is that you need another userspace tool to get the data in and out of the driver. It is harder to integrate in existing backup processes. The design we discussed back then was to show the cylinders of the volume as files in a directory (bonus points when arranged according to CMS formatted minidisks). That way you could backup the data as any other Linux data, and have automatically a way for incremental (per cylinder) backups etc. -Rob ---------------------------------------------------------------------- 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
