<voice-of-narrator> We interrupt our regularly scheduled nation bashing to bring you a real question. </voice-of-narrator>
to the good folks in Boeblingen ... Okay ... the CDL mode of the current DASD driver rams the key and data content together. Yuck! That is, if I read from offset 0x2000, I don't get the data from "record 3", but I get the key content followed by the data content. This is not what I would have expected. Would have thought that count and key would be available thru some ioctl(). But ... now that it's done ... is it likely to stay that way? Or will I have to re-code later?? More importantly, is the key info used in CDL constant? Right now, I can detect CDL and offset my reads by four bytes. Will that offset be the expected behaviour going forward? We just gotta know. Thanks. And keep up the great work. We appreciate y'all. -- R;
