-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 That that is what this document was originally based off of, and from there I went through the code, and gave some more detail as to what the pioctl()s did. I'll credit the numbers page on the wiki version of this doc.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: http://getfiregpg.org iEYEARECAAYFAkhhOS4ACgkQT1NNAgG+H+yaWgCfU2a5SLUhTGKz+SYb8+S+fXdX 2qUAoIxyHC8vo4t7TsawGdnPFTB0xUCe =XwQj -----END PGP SIGNATURE----- On Tue, Jun 24, 2008 at 1:44 PM, Jeffrey Hutzelman <[EMAIL PROTECTED]> wrote: > --On Saturday, June 21, 2008 11:01:14 AM -0400 Jason Edgecombe < > [EMAIL PROTECTED]> wrote: > > Jake Thebault-Spieker wrote: >> >>> It's come to my attention that i apparently have no idea how to use GnuPG >>> and Gmail, and therefore, encrypted the pioctl_doc.txt that I sent out >>> yesterday. I've attached it again, and won't be cryptographically signing >>> this. My apologies for any iconvenience. Please see attached. >>> >>> >>> Where should this document live? Should it be standalone in CVS or >> encoded as doxygen-style comments in the source code and automatically >> generated or something else? >> >> I sincerely thank you for documenting this. I just want to capture and >> store it in the best way. >> > > See also <http://grand.central.org/numbers/pioctls.html> > -- Jacob Thebault-Spieker Cell: (207) 717-5114
