SH> Or do you mean the programmers will see that and be able to tell SH> more easiliy where in ptrace.h the corresponding union is? Right, I was thinking about it from the point of view of letting the user of that structure (which could be in userspace) know what the contents are. In other words, I don't see why we should have some of the fields be opaque outside of the kernel and not others (not including any that really can't be interpreted by userspace in a meaningful way). -- Dan Smith IBM Linux Technology Center email: danms@xxxxxxxxxx _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
