Actually, he now insists that you should not install it as a separate library, but should include the code with your own programme — http://cr.yp.to/mac.html:
My fast poly1305aes library is in the public domain. You can and should include it in your own programs, rather than going to the effort of linking to a shared library; the compiled code is between 6 and 10 kilobytes, depending on the CPU.
Of course, it being in the public domain, this is merely a suggestion, and, as a developer, one could basically use it in whatever way one sees fit (although djb's advice does seem quite reasonable).
The nginx on BXR had a soft FD limit of 128 (:openfiles-cur=128:) through the default login.conf(5), which it doesn't seem to increase automatically, and which it was hitting at 17:59 (if not earlier) as per fstat(1), and which applies to internet sockets, too, so, during some time between 17:52 and 18:03, when nginx was manually restarted with the increased soft limit, BXR was indeed slashdotted!
BTW, this was probably due to the HTTP keep-alive feature, and not the raw number of requests, which are all served up very quickly due to mfs and good caching. No other problems to report since then; even the search is still very fast, as it should be.
Recent `fstat | fgrep nginx` runs indicate the highest FD is around 200 now, but it did quickly jump to around 400 right after the 128 limit was lifted (within ten minutes of the story being published).
The nginx had a soft limit of 128 file descriptors through daemon::openfiles-cur=128: in login.conf(5), which it apparently doesn't increase automatically, and which were quickly exhausted for internet stream FDs, as per fstat(1). But it's been resolved at 10:03 PT / 18:03 GMT, and there were no known problems since then.
Software Freedom Law Center gave some very nice advice on how to wrap new licenses around old code -- let's fork Linux and make the new changes available only under a BSD licence!
We can then ask SFLC for legal advice in case anyone disagrees, right?:)
Heh, he was interviewed by his local newspaper!!! It's even more tactful than professors putting anti-Bush comics on their doors in the hallway! He didn't post it to a web-site, nor did he campaigned against it, he simply answered the question in a good faith!
Did you expect him to be dishonest and lie on the matter? How would one respect oneself after that?
He did what he should have done -- exercised his right to free speech. He did not badmouth anyone, he just told the newspaper what already more than 50% of North American population think.
These lads from the Register don't know that China has.cn as its top level domain. Their screenshot lists the top-level domain for Switzerland instead.:)
Slashdot Mirror
Dumping the cheese cultures all over town, with the mold-inducing bacteria, what could possibly go wrong?!
Of course, it being in the public domain, this is merely a suggestion, and, as a developer, one could basically use it in whatever way one sees fit (although djb's advice does seem quite reasonable).
The nginx on BXR had a soft FD limit of 128 (:openfiles-cur=128:) through the default login.conf(5), which it doesn't seem to increase automatically, and which it was hitting at 17:59 (if not earlier) as per fstat(1), and which applies to internet sockets, too, so, during some time between 17:52 and 18:03, when nginx was manually restarted with the increased soft limit, BXR was indeed slashdotted!
BTW, this was probably due to the HTTP keep-alive feature, and not the raw number of requests, which are all served up very quickly due to mfs and good caching. No other problems to report since then; even the search is still very fast, as it should be.
Recent `fstat | fgrep nginx` runs indicate the highest FD is around 200 now, but it did quickly jump to around 400 right after the 128 limit was lifted (within ten minutes of the story being published).
Those other files are the libraries, the protocol itself is about 100 lines of commented code.
The nginx had a soft limit of 128 file descriptors through daemon: :openfiles-cur=128: in login.conf(5), which it apparently doesn't increase automatically, and which were quickly exhausted for internet stream FDs, as per fstat(1). But it's been resolved at 10:03 PT / 18:03 GMT, and there were no known problems since then.
Software Freedom Law Center gave some very nice advice on how to wrap new licenses around old code -- let's fork Linux and make the new changes available only under a BSD licence!
:)
We can then ask SFLC for legal advice in case anyone disagrees, right?
Here is their advice: http://lwn.net/Articles/248223/
Heh, he was interviewed by his local newspaper!!! It's even more tactful than professors putting anti-Bush comics on their doors in the hallway! He didn't post it to a web-site, nor did he campaigned against it, he simply answered the question in a good faith! Did you expect him to be dishonest and lie on the matter? How would one respect oneself after that?
He did what he should have done -- exercised his right to free speech. He did not badmouth anyone, he just told the newspaper what already more than 50% of North American population think.
These lads from the Register don't know that China has .cn as its top level domain. Their screenshot lists the top-level domain for Switzerland instead. :)