>Hi > >Thanx for the quick answer.. > >> The fix is using the new "F" mode character which tells fopen that it is >> fine to open files with a file descriptor > 255. >> >> The actual fix is: >> >> - add support for "F" etc in fopen() >> - add "F" when it is needed (basically everything in libraries >> which uses fopen() internally) >> - remove several pseudo fopens which worked around fopens >> limitations > >Ah I see, didn't notice the extra F in the mode strings ;-) > >Do you have any idea if this fix can be "installed" on a solaris 9 ? >can I e.g. take the fixed stidio (libc ?) and the kerberos library and >install on Solaris 9 ?
Only if you have the Solaris 9 source; the libc stdio bits dealing with FILE *s haven't changed all that much but you can't use the Solaris 10 or OpenSolaris libc because the rest is rather different from Solaris 9. >Is this fix something that will make its way into the MIT kerberos ? I >have tried googleing for any backport/upstream fix, but found nothing >so far > >As I understand it 32bit solaris (9) has the fopen issue because some >field holding the file descriptor is only a byte long. Just for >curiosities sake: I assume this field is still only byte sized, so how >does this F mode help ? It's no longer kept in fp->_file but that means there's a problem with older binaries (i.e., by adding a "F" to the mode string you are guaranteeing that you will not look at/touch fp->_file.) Casper _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
