I think one very legitimate use being forgotten here is import games. If I get a PS2, I will most likely get a modchip and buy the Naruto fighting game from Japan, because it's pretty likely that the game will never be released in the States. So maybe backup purposes is a little hard to defend, but imports are a little stronger.
second of all, this would be interesting to mix with a car exhaust, if you can find components that wouldn't die in the heat. imagine straight-pipe exhausts that are quieter than today's systems with mufflers!
This strategy didn't necessarily work for Sega with the Dreamcast. It came out first, and had the edge over the PS2 in certain aspects, yet it still lost.
Ever since I found out Windows XP Service Pack 1 supports IPv6, I've been using it on my Windows XP box. From what I've seen, my Zaurus with OpenZaurus also supports IPv6. So, I guess I've already migrated to IPv6. I still use mainly IPv4 apps, but it's nice to know that I'm already there in readiness for the migration.
I think that would be because "everybody gets caught eventually." The fact that somebody got caught doesn't say that their skill is inferior, but rather it could be a number of factors that put them away. They could have been having an off day, a loved one turned them in for their own good, they weren't paying attention, etc.
Okay, I'm seeing a lot of people reply to this post, but they're not making a whole bunch of sense. So in order to clarify things for people who replied, I thought I'd say a few things. First of all, BJH is talking about knowing the encryption mechanism in SSH to crack the communications. If I'm interpreting him correctly, he's saying that with the public key encryption mechanisms that SSH uses, it's not possible to crack the encryption, even if you know the public key and the mechanism (namely because the best known algorithms for figuring the private key are intractable in runtime). So, if Microsoft had any sort of brains about them, they would have used an encryption scheme that would allow them to produce a key, where even if the algorithm is known, it would still take an unreasonable amount of computing power to figure out how to generate one's own keys.
Unfortunately, I don't see anything mentioning open source. However, I can point you to more info. For information on the Authentication Web Server that AirBears uses to authenticate users from a web page, look at http://www.net.berkeley.edu/kerberos/documents/AWS AppSetup.html. Also, this is part of CalNet, which is our one-login setup that uses kerberos. For information on its architecture, look at https://calnet.berkeley.edu/architecture.html. Also, try e-mailing calnet-admin[at]uclink.berkeley.edu. Finally, you could try e-mailing the developers at airbears, their address is nsweb[at]berkeley.edu. Hope that helps.
Here at UC Berkeley, we have a thing called AirBears (http://airbears.berkeley.edu/). Before you can use the net, you have to login through a web page, which is a proxy to kerberos authentication. This is a pretty easy to use setup, and I'm pretty sure that the login is simple enough that even something like lynx or w3m could use it. The only problem is that there is more than one wireless net access service on campus, and they don't all use the same authentication method as AirBears.
If you really want to get into it, the 600cc engine of a Yamaha YZF-R6 gets in over 200hp/L. It uses ram air intake, if you want to disqualify it from natural aspiration. Otherwise, yes, that's efficiency.
Slashdot Mirror
I think one very legitimate use being forgotten here is import games. If I get a PS2, I will most likely get a modchip and buy the Naruto fighting game from Japan, because it's pretty likely that the game will never be released in the States. So maybe backup purposes is a little hard to defend, but imports are a little stronger.
second of all, this would be interesting to mix with a car exhaust, if you can find components that wouldn't die in the heat. imagine straight-pipe exhausts that are quieter than today's systems with mufflers!
Hey, if somebody could organize this data into histograms, it'd be a lot easier to interpret the results..
Forty-Second Post!
Geeks come in all sizes.. We're geeks because we DON'T know how to use it.
Posting a story on the front page of slashdot sure is a very nice gesture to the sysadmins of philly.com, you retards.
Uma? Giving head? where!?
maybe Ben Stiller can work as Ben Affleck's stunt double!
I prefer to think of it as sorta like Pocket PC, except even shittier.
Uh, ever heard of situational ("cosmic") irony?
This strategy didn't necessarily work for Sega with the Dreamcast. It came out first, and had the edge over the PS2 in certain aspects, yet it still lost.
Ever since I found out Windows XP Service Pack 1 supports IPv6, I've been using it on my Windows XP box. From what I've seen, my Zaurus with OpenZaurus also supports IPv6. So, I guess I've already migrated to IPv6. I still use mainly IPv4 apps, but it's nice to know that I'm already there in readiness for the migration.
I think that would be because "everybody gets caught eventually." The fact that somebody got caught doesn't say that their skill is inferior, but rather it could be a number of factors that put them away. They could have been having an off day, a loved one turned them in for their own good, they weren't paying attention, etc.
Isn't there some way to tell them, fuck you, stay away from our OS? Stupid double-edged sword of open source...
Okay, I'm seeing a lot of people reply to this post, but they're not making a whole bunch of sense. So in order to clarify things for people who replied, I thought I'd say a few things. First of all, BJH is talking about knowing the encryption mechanism in SSH to crack the communications. If I'm interpreting him correctly, he's saying that with the public key encryption mechanisms that SSH uses, it's not possible to crack the encryption, even if you know the public key and the mechanism (namely because the best known algorithms for figuring the private key are intractable in runtime). So, if Microsoft had any sort of brains about them, they would have used an encryption scheme that would allow them to produce a key, where even if the algorithm is known, it would still take an unreasonable amount of computing power to figure out how to generate one's own keys.
Somebody please mod this up... People don't realize that this is not an April Fool's joke, even though it does seem fairly inane.
Not quite. CNN says that it's all on one chipset. So CNN is also to blame for misreporting.
Unfortunately, I don't see anything mentioning open source. However, I can point you to more info. For information on the Authentication Web Server that AirBears uses to authenticate users from a web page, look at http://www.net.berkeley.edu/kerberos/documents/AWS AppSetup.html. Also, this is part of CalNet, which is our one-login setup that uses kerberos. For information on its architecture, look at https://calnet.berkeley.edu/architecture.html. Also, try e-mailing calnet-admin[at]uclink.berkeley.edu. Finally, you could try e-mailing the developers at airbears, their address is nsweb[at]berkeley.edu. Hope that helps.
Here at UC Berkeley, we have a thing called AirBears (http://airbears.berkeley.edu/). Before you can use the net, you have to login through a web page, which is a proxy to kerberos authentication. This is a pretty easy to use setup, and I'm pretty sure that the login is simple enough that even something like lynx or w3m could use it. The only problem is that there is more than one wireless net access service on campus, and they don't all use the same authentication method as AirBears.
This really depends on how you define natural aspiration. Ram air is a form of forced induction, isn't it?
If you really want to get into it, the 600cc engine of a Yamaha YZF-R6 gets in over 200hp/L. It uses ram air intake, if you want to disqualify it from natural aspiration. Otherwise, yes, that's efficiency.
I have IPv6 (I know this because I'm chatting on an IPv6 IRC server), but the link doesn't work..
Let's just all get our RTFM's out of system now.
Whatever you're going to do with them, I'd hope that you didn't need more than 64mb of ram per box, because that's all you're getting.
How the FUCK are you going to enforce a patent when prior art is both well-known and documented? Are these people retarded?