[OpenAFS-devel] Thoughts on a pioctl() document, part II

Jake Thebault-Spieker summatusmentis@gmail.com
Tue, 24 Jun 2008 14:13:03 -0400


------=_Part_29058_16527376.1214331183744
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-----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 <jhutz@cmu.edu> wrote:

> --On Saturday, June 21, 2008 11:01:14 AM -0400 Jason Edgecombe <
> jason@rampaginggeek.com> 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

------=_Part_29058_16527376.1214331183744
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-----BEGIN PGP SIGNED MESSAGE-----<br>Hash: SHA1<br><br>That that is what this document was originally based off of, and from<br>there I went through the code, and gave some more detail as to what<br>the pioctl()s did. I&#39;ll credit the numbers page on the wiki version of<br>
this doc.<br><br><br>-----BEGIN PGP SIGNATURE-----<br>Version: GnuPG v1.4.8 (Darwin)<br>Comment: <a href="http://getfiregpg.org">http://getfiregpg.org</a><br><br>iEYEARECAAYFAkhhOS4ACgkQT1NNAgG+H+yaWgCfU2a5SLUhTGKz+SYb8+S+fXdX<br>
2qUAoIxyHC8vo4t7TsawGdnPFTB0xUCe<br>=XwQj<br>-----END PGP SIGNATURE-----<br><div class="gmail_quote">On Tue, Jun 24, 2008 at 1:44 PM, Jeffrey Hutzelman &lt;<a href="mailto:jhutz@cmu.edu">jhutz@cmu.edu</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="Wj3C7c">--On Saturday, June 21, 2008 11:01:14 AM -0400 Jason Edgecombe &lt;<a href="mailto:jason@rampaginggeek.com" target="_blank">jason@rampaginggeek.com</a>&gt; wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Jake Thebault-Spieker wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
It&#39;s come to my attention that i apparently have no idea how to use GnuPG<br>
and Gmail, and therefore, encrypted the pioctl_doc.txt that I sent out<br>
yesterday. I&#39;ve attached it again, and won&#39;t be cryptographically signing<br>
this. My apologies for any iconvenience. Please see attached.<br>
<br>
<br>
</blockquote>
Where should this document live? Should it be standalone in CVS or<br>
encoded as doxygen-style comments in the source code and automatically<br>
generated or something else?<br>
<br>
I sincerely thank you for documenting this. I just want to capture and<br>
store it in the best way.<br>
</blockquote>
<br></div></div>
See also &lt;<a href="http://grand.central.org/numbers/pioctls.html" target="_blank">http://grand.central.org/numbers/pioctls.html</a>&gt;<br>
</blockquote></div><br><br clear="all"><br>-- <br>Jacob Thebault-Spieker<br>Cell: (207) 717-5114<br>
<br><br>

------=_Part_29058_16527376.1214331183744--