Garrett D'Amore writes: > Right now, they are less than useful to my needs, because I actually > *need* to encode sizes, and the sizes that I need to encode are > 255 > bytes. Frankly, the current definitions are dangerous, because I
Why do you need to do this? Why is it something that has not bothered anyone else in the past 20+ years? > But if the issue is to contentious, then I will abandon any effort to > clean this up, and just use my own private definitions, and resign > myself to the idea that truss and such tools will just be stuck when it > comes to decoding my ioctls. That's not true. I pointed out earlier that you can add your own decoder into truss, and do anything you like with ioctl arguments. Just add a new case to show_ioctl(), and use Pread to grab the data you want. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
