> Yeah, I was thinking of that. In fact, the reason I became aware of that is > that I wanted to use another pseudo device with no ops for the proxy memory > objects (but for those I need a close function, so I made my own device ops > structure). I know that this is lame, as one reason against a new kernel > object type for iopb was that it is machine-specific, and I don't have this > argument here.
There is no excuse for that. They have nothing whatsoever to do with each other. The proxy object changes should be in vm/ and I can't see why they shouldn't work back-ported to 1.x (not that we care to do it). There are IKOT_* values already unused and it's easy enough to add another anyway. The ipc glue code you need is trivially copied from the other ones. _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
