The reason SSH performance sucks on SPARC is because by default on most platforms, OpenSSL is optimized for sun4/sun4c. If you're using a sun4m (such as SS5), you can optimize for that, which makes SSH go a LOT faster.
If you're using sun4u (i.e., Sun Ultra series), you could optimize it further, too.
Disclaimer: This isn't about the RIAA, it's about the Interactive Digital Software Association. It could have happened with RIAA, though.
A client of mine got an email from their cable ISP yesterday, claiming they were violating their agreement by offering copyrighted materials (computer games) on KaZaA. The attached log (from the IDSA) had a timestamp of June 30th, three days before my client's new firewall picked up the IP in question.
A simple phone call cleared the matter up, but what if the copyright holder demanded contact information, instead? I'd hate to end up in court just because DHCP handed me a "dirty" IP.
Slashdot Mirror
Funny, those commands work just fine on my RedHat, Fedora, Aurora, and Yellow Dog boxen. Then again, I'm using apt4rpm.
Nice job, Chip. And you already have it packaged, don't you?
BTW: First post?
Some localities have passed laws permitting motorcyclists to run red lights for this very reason.
Here are a couple of links on the subject.
The reason SSH performance sucks on SPARC is because by default on most platforms, OpenSSL is optimized for sun4/sun4c. If you're using a sun4m (such as SS5), you can optimize for that, which makes SSH go a LOT faster.
If you're using sun4u (i.e., Sun Ultra series), you could optimize it further, too.
Not the original poster, but here's my 386 or so:
My Wang
Disclaimer: This isn't about the RIAA, it's about the Interactive Digital Software Association. It could have happened with RIAA, though.
A client of mine got an email from their cable ISP yesterday, claiming they were violating their agreement by offering copyrighted materials (computer games) on KaZaA. The attached log (from the IDSA) had a timestamp of June 30th, three days before my client's new firewall picked up the IP in question.
A simple phone call cleared the matter up, but what if the copyright holder demanded contact information, instead? I'd hate to end up in court just because DHCP handed me a "dirty" IP.