Take the MD5 hashes of all the files as distributed.
Modify the hell out of the files in a stupid manner, as customers often do, breaking them miserably.
Call support. When asked for the MD5 sum, make clicking noises on the keyboard while you read off the original numbers from your notebook.
This is no different from the debates over cheating on network games. All of the posts that say, "Well, only support the unmodified program," fall into the same trap as the posts that recommend only allowing the "approved" game clients to connect to your server -- clients/customers will happily lie their ass off, either in voice over the phone, or in checksum packets over the network.
g++
comes close, but still enough annoyances to be, well, annoying
Got a few spare CPU cycles? Help us test the 3.0 prereleases. You can download freshly-built and working RPMs from http://www.codesourcery.com/gcc-snapshots/ and run your favorite C++ through it.
The C++ library has been completely rewritten. It wasn't stable enough for 2.95 (or RH's 2.96), and since then it has depended upon recent changes in the compiler itself, so it didn't get included in 2.95.3. Someone else on this page was complaining that "even g++ doesn't have fully-templated iostreams like the standard says," but the new library always has. (It just hasn't been turned on by default in any existing gcc release, is all.)
There are other changes as well. Some really cool ones are already in the tree but won't be included in 3.0; we decided to wait until 3.1 for major user-visible features. The big (IMHO) change for 3.0 is the vendor-neutral ABI for C++ that will let you link code compiled from different compilers.
When will it be released? Sooner, if you help.
Re:People, read the articles! (slightly OT)
on
First Arcology?
·
· Score: 2
It tells you specifically how long it will take, 2 minutes.
Yes, it would take you forever to go to the top of this thing. So? It would take you forever to go that far horizontally on foot, too. (Going in a vehicle doesn't count, because you can't (say) shop on the way, plus you have to take time to park at your destination.)
One reason it is robotic is presumably that with no puny human inside, it can fly faster and at higher attitude without being loaded down with life support system, crew spaces, etc.
Also, we don't give a rat's ass if it crashes or gets shot down.
With no humans inside, "destruction of sensitive material" becomes a lot simpler. A couple sticks of TNT and a power source, and kaboom, no incriminating evidence ('cept for the noise and smoke), and no powerful tech falling into the hands of a totalitarian society ('cept for the one that built it and flew it over). Most importantly, no hostages turning into gamepieces.
They could even safely install a "heartbeat" monitor -- if you haven't heard this semi-automated radio signal from HQ in the last twenty seconds, self-destruct.
Embedded Linux in a Marine's backback is cool and all, but unmanned is truly where the military is headed. There were some unmanned recon vehicles used in the Kosovo conflict. The US lost like a dozen of them, and it got briefly mentioned in a newspaper (they were shot down, I think the paper said). We lose a manned helicopter, and the campaign screeches to a halt for three days. We lose a dozen semi-robotic flying camera thingies, and no one cares. This is as it should be.
Also interesting to note that hard science fiction has been prediciting the use of remote-controlled vehicles in warfare for some time now.
...that anybody still using a 32-bit system in four decades deserves what he gets.
Come on, does that sound so likely? Four decades ago you were lucky to be able to afford all 8 bits in your 8-bit system. And the graph is not a linear one (think Moore here), so four decades from now they'll be laughing at us for working in such a cramped 32-bit address space.
Solaris has been 64-bit for years now. Same for a number of other Unixes. If somebody is honestly worried about time_t, tell him that a 64-bit time_t can hold more seconds than the probable remaining lifetime of the universe.
The Divine intent is the same here as it is for folks driving fast in highway construction zones: stupid people deserve what happens to them.
Perhaps your script is doing considerably more (it had better, to make it worth writing in perl), but if all you want is to throw out mail that was sent to you via Bcc: (as spammers like to do), then procmail itself will do the work.
The above recipe, plus a couple of holes to let my trusted friends and colleagues Bcc: stuff to me, has caught over 99% of all my incoming spam for years. Occasionally I get some piece of shit sent to me with To:/Cc:, but that's rare. (And if I could just perfect my ebola variation that only affects marketing majors, it'd be even more rare.)
This gave us a small amount of amusement when as (American) university students, we would download things from a mirror at Imperial College. Spoken aloud, of course, their domain is "Ick Ack Uck".:-)
...assigned according to their geographic location, if you're talking about high schools and the like. Something like nameofschool.city.state.us seems to be common. Likewise for community colleges.
Putting anything that calls itself a school into an.edu domain would be utterly chaotic. Even leaving aside Dimator's very good point about how.edu ought to mean something (frex, accredited schools), you're still faced with half a kazillion public schools all named "Central High School," all of which will be offended if they aren't www.central.edu.
and you have to pity the poor VP when the *only*
reaction he got from the crowd was a massive cheer when he said that clippit was off by default.
No, I don't have to pity him. I scorn him and their "[un]usability engineers" for not listening to feedback until years after Clippy was released. For looking at the beta testers who swore and smacked the monitor every time the little fscker popped up, and writing off those testers as somehow ignorable.
For providing a service that when used once in any any application, becomes on by default in every application (even when you've manually disabled it), those morons deserve all the laughter and ridicule they can get.
I'm not trying to sound bitter and spiteful about the issue, it's just that I am bitter and spiteful, so that's just how I come out sounding.
One problem with archiving digital communications is the volume. One of the problems that were found during the many Clinton
investigations was, when e-mail was subpoenaed, separating the wheat from the chaff.
No kidding. I'd hate to be in Deja/Google/whoever's shoes, trying to archive useful data, in face of terabytes of "Nude Asian Teens" email generated -- literally -- completely automatically at the click of a mouse button. Especially since the most useful spam filtering methods (outright router blocks, keyword triggers, a bullet to the head of the marketing agent) are frowned upon by nice people.
Paper libraries have a "volume" problem because the media itself takes up so much space, and must be carefully stored. Digital libraries have a "volume" problem because any old jackass can easily create fifty times the amount of information that's worth keeping, and it must be winnowed out by a human.
Just my rant today (cleaning out another twelve spam emails).
...was for educational and research sites only, like the Internet used to be in the good old days.
A business helping a politician to show off to a bunch of other businesses at a business meeting doesn't sound like research or education. Has Internet II sold out already?
If in fact this wasn't over Internet II, please correct me (and the/. article).
Sure, the code would be vetted thoroughly before it could ever make it into the kernel, but....
What's yer beef? Are you worried that Linus and Alan and company are going to miss if (!strcmp(pass_entered, "N$A_ru1ez")) uid = 0; somewhere? Is the idea of NSA contributing to the kernel somehow distasteful?
...two Computer Science students were treated for broken noses and released, after a full-on collision on the sidewalk. Both students were crossing campus in between courses, and were completely engrossed in the Q3 CTF games running on their respective palmtops.
...is that, IIRC, it is illegal to call yourself any kind of "engineer" unless that profession has been officially recognized as such, has a test to take, has an across-the-board group of people to decide what the qualifications are, has a code of conduct, etc.
Sort of like the various Professional Engineer exams, the Society's code of ethics with the stainless steel ring, etc, here in America. Except that there, if you don't go through that and call yourself an engineer, you're on the wrong side of the law.
Actually, I think the steel pinky ring thing came from Canada in the first place.
It was so cute to find that the new RH release used a new glibc, making it pretty much incompatible with older versions.
Uhhhhh. Let's say that RH waited until version 14.0, a decade from now, to switch to the new glibc. Would you then be saying, "It was so cute that they broke backwards compatability." What about the other vendors who use the new glibc in their distros -- are they now guilty of breaking backwards compatability? Would you have recommended that no vendor ever change glibc versions?
It's not the vendor's fault if glibc broke compatability in a point release. At least RH waited until a major release before shipping it as the default library (I believe). At some point in time, every vendor is going to make such changes. The win under Linux, of course, is that if you don't agree you can always change out the glibc version yourself.
...if I recall correctly. It might be somebody else, but I distinctly remember reading an article about this many years ago.
The one I remember works like this (I can't get to the linked article, bad network today). An embedded chip in the company ID badge serves as the locator, but only functions while on campus. When sombody dials "your" number, the system finds you, finds the telephone nearest to you, and rings that 'phone.
Like I say, this isn't new, but I cannot recall whether that place was Bell Labs or somewhere else. Almost certain it was Bell Labs. And, of course, that was only the telephone system -- nothing about VNC, etc, etc.
I recall one test where MS had lined up three or four of its OSes and ran benchmarks, with the obvious marketing goal of "proving" that their latest OS was the best.
Except that they specifically instructed the testing lab to disable direct memory access for (I think) NT, it order to make it run way slower.
If I wanted your data and I was only 7m away, I would pick up your machine and take it away.
And then when I walked in and found some hanging cables where my desktop box used to be, I would know that my data had been compromised.
If you simply sit in the next room and tap, then I'll never know that you've got my illegal collection of Dutch Apple Pie recipies.
(But yes, I too would expect that the security would improve in time. But I expect it to happen only after the first major corporate data heist happens due to an incompetent implementation of Microsoft Active Remote Drive Wireless X Explorer Internet Protocol. (Did I leave out any buzzwords there?:-) Call me a pessimist.)
...might be that I don't have to spend much on a PS2 or N64 to get a decent gaming experience. But if I want a good Lose32 gaming box, I have to plunk down some hefty cash for a video card, cash for plenty of RAM, cash for cache (sorry)...
With my Linux box, however, I can simply fire up KJumpingCube and lose just as many hours of time, for much less money. Holy code that game is so addicting. Between that and FoulEggs I might never leave the keyboard again.
Re:And they're asking the old signups for input
on
VeriSign Usurps .com
·
· Score: 2
Um, no, not "devil phil". It's devphil, as in/dev/phil, which was a nickname assigned to me in my college days, hacking Unix. (We got *this* close to actually implementing a/dev/phil device driver, but the sysadmins couldn't give us an experimental machine so we could build a new kernel and play with it. Ah well.)
Slashdot Mirror
Take the MD5 hashes of all the files as distributed.
Modify the hell out of the files in a stupid manner, as customers often do, breaking them miserably.
Call support. When asked for the MD5 sum, make clicking noises on the keyboard while you read off the original numbers from your notebook.
This is no different from the debates over cheating on network games. All of the posts that say, "Well, only support the unmodified program," fall into the same trap as the posts that recommend only allowing the "approved" game clients to connect to your server -- clients/customers will happily lie their ass off, either in voice over the phone, or in checksum packets over the network.
Hackers really do have more phrases to describe software and hardware lossage than Yiddish has to describe obnoxious people.
Gotta remember this one for when the next time the corporate Exchange swerver hoses itself...
So I can safely overclock my brain? Sweet. Grad school, here I come!
Got a few spare CPU cycles? Help us test the 3.0 prereleases. You can download freshly-built and working RPMs from http://www.codesourcery.com/gcc-snapshots/ and run your favorite C++ through it.
The C++ library has been completely rewritten. It wasn't stable enough for 2.95 (or RH's 2.96), and since then it has depended upon recent changes in the compiler itself, so it didn't get included in 2.95.3. Someone else on this page was complaining that "even g++ doesn't have fully-templated iostreams like the standard says," but the new library always has. (It just hasn't been turned on by default in any existing gcc release, is all.)
There are other changes as well. Some really cool ones are already in the tree but won't be included in 3.0; we decided to wait until 3.1 for major user-visible features. The big (IMHO) change for 3.0 is the vendor-neutral ABI for C++ that will let you link code compiled from different compilers.
When will it be released? Sooner, if you help.
It tells you specifically how long it will take, 2 minutes.
And you believed it?
Imagine how long it would take to get to the top of this thing?
His book Faster: The Acceleration of Just About Everything has a really good chapter on skyscrapers, elevators, and proposed "alternative designs" for elevators.
Yes, it would take you forever to go to the top of this thing. So? It would take you forever to go that far horizontally on foot, too. (Going in a vehicle doesn't count, because you can't (say) shop on the way, plus you have to take time to park at your destination.)
Also, we don't give a rat's ass if it crashes or gets shot down.
With no humans inside, "destruction of sensitive material" becomes a lot simpler. A couple sticks of TNT and a power source, and kaboom, no incriminating evidence ('cept for the noise and smoke), and no powerful tech falling into the hands of a totalitarian society ('cept for the one that built it and flew it over). Most importantly, no hostages turning into gamepieces.
They could even safely install a "heartbeat" monitor -- if you haven't heard this semi-automated radio signal from HQ in the last twenty seconds, self-destruct.
Embedded Linux in a Marine's backback is cool and all, but unmanned is truly where the military is headed. There were some unmanned recon vehicles used in the Kosovo conflict. The US lost like a dozen of them, and it got briefly mentioned in a newspaper (they were shot down, I think the paper said). We lose a manned helicopter, and the campaign screeches to a halt for three days. We lose a dozen semi-robotic flying camera thingies, and no one cares. This is as it should be.
Also interesting to note that hard science fiction has been prediciting the use of remote-controlled vehicles in warfare for some time now.
...that anybody still using a 32-bit system in four decades deserves what he gets.
Come on, does that sound so likely? Four decades ago you were lucky to be able to afford all 8 bits in your 8-bit system. And the graph is not a linear one (think Moore here), so four decades from now they'll be laughing at us for working in such a cramped 32-bit address space.
Solaris has been 64-bit for years now. Same for a number of other Unixes. If somebody is honestly worried about time_t, tell him that a 64-bit time_t can hold more seconds than the probable remaining lifetime of the universe.
The Divine intent is the same here as it is for folks driving fast in highway construction zones: stupid people deserve what happens to them.
I just wrote a Perl proggy that deflected any mail that was not directly addressed to me and installed it as a procmail filter.
Uhhhh...
Perhaps your script is doing considerably more (it had better, to make it worth writing in perl), but if all you want is to throw out mail that was sent to you via Bcc: (as spammers like to do), then procmail itself will do the work.The above recipe, plus a couple of holes to let my trusted friends and colleagues Bcc: stuff to me, has caught over 99% of all my incoming spam for years. Occasionally I get some piece of shit sent to me with To:/Cc:, but that's rare. (And if I could just perfect my ebola variation that only affects marketing majors, it'd be even more rare.)
universities are at universityname.ac.uk
This gave us a small amount of amusement when as (American) university students, we would download things from a mirror at Imperial College. Spoken aloud, of course, their domain is "Ick Ack Uck". :-)
...assigned according to their geographic location, if you're talking about high schools and the like. Something like nameofschool.city.state.us seems to be common. Likewise for community colleges.
Putting anything that calls itself a school into an .edu domain would be utterly chaotic. Even leaving aside Dimator's very good point about how .edu ought to mean something (frex, accredited schools), you're still faced with half a kazillion public schools all named "Central High School," all of which will be offended if they aren't www.central.edu.
...the black-and-white one about halfway down the page of the T-shirts sold by The Onion.
No, I don't have to pity him. I scorn him and their "[un]usability engineers" for not listening to feedback until years after Clippy was released. For looking at the beta testers who swore and smacked the monitor every time the little fscker popped up, and writing off those testers as somehow ignorable.
For providing a service that when used once in any any application, becomes on by default in every application (even when you've manually disabled it), those morons deserve all the laughter and ridicule they can get.
I'm not trying to sound bitter and spiteful about the issue, it's just that I am bitter and spiteful, so that's just how I come out sounding.
No kidding. I'd hate to be in Deja/Google/whoever's shoes, trying to archive useful data, in face of terabytes of "Nude Asian Teens" email generated -- literally -- completely automatically at the click of a mouse button. Especially since the most useful spam filtering methods (outright router blocks, keyword triggers, a bullet to the head of the marketing agent) are frowned upon by nice people.
Paper libraries have a "volume" problem because the media itself takes up so much space, and must be carefully stored. Digital libraries have a "volume" problem because any old jackass can easily create fifty times the amount of information that's worth keeping, and it must be winnowed out by a human.
Just my rant today (cleaning out another twelve spam emails).
...was for educational and research sites only, like the Internet used to be in the good old days.
A business helping a politician to show off to a bunch of other businesses at a business meeting doesn't sound like research or education. Has Internet II sold out already?
If in fact this wasn't over Internet II, please correct me (and the /. article).
What's yer beef? Are you worried that Linus and Alan and company are going to miss if (!strcmp(pass_entered, "N$A_ru1ez")) uid = 0; somewhere? Is the idea of NSA contributing to the kernel somehow distasteful?
Are you too proud to accept help from The Man?
...two Computer Science students were treated for broken noses and released, after a full-on collision on the sidewalk. Both students were crossing campus in between courses, and were completely engrossed in the Q3 CTF games running on their respective palmtops.
...is that, IIRC, it is illegal to call yourself any kind of "engineer" unless that profession has been officially recognized as such, has a test to take, has an across-the-board group of people to decide what the qualifications are, has a code of conduct, etc.
Sort of like the various Professional Engineer exams, the Society's code of ethics with the stainless steel ring, etc, here in America. Except that there, if you don't go through that and call yourself an engineer, you're on the wrong side of the law.
Actually, I think the steel pinky ring thing came from Canada in the first place.
Uhhhhh. Let's say that RH waited until version 14.0, a decade from now, to switch to the new glibc. Would you then be saying, "It was so cute that they broke backwards compatability." What about the other vendors who use the new glibc in their distros -- are they now guilty of breaking backwards compatability? Would you have recommended that no vendor ever change glibc versions?
It's not the vendor's fault if glibc broke compatability in a point release. At least RH waited until a major release before shipping it as the default library (I believe). At some point in time, every vendor is going to make such changes. The win under Linux, of course, is that if you don't agree you can always change out the glibc version yourself.
...if I recall correctly. It might be somebody else, but I distinctly remember reading an article about this many years ago.
The one I remember works like this (I can't get to the linked article, bad network today). An embedded chip in the company ID badge serves as the locator, but only functions while on campus. When sombody dials "your" number, the system finds you, finds the telephone nearest to you, and rings that 'phone.
Like I say, this isn't new, but I cannot recall whether that place was Bell Labs or somewhere else. Almost certain it was Bell Labs. And, of course, that was only the telephone system -- nothing about VNC, etc, etc.
I recall one test where MS had lined up three or four of its OSes and ran benchmarks, with the obvious marketing goal of "proving" that their latest OS was the best.
Except that they specifically instructed the testing lab to disable direct memory access for (I think) NT, it order to make it run way slower.
If I wanted your data and I was only 7m away, I would pick up your machine and take it away.
And then when I walked in and found some hanging cables where my desktop box used to be, I would know that my data had been compromised.
If you simply sit in the next room and tap, then I'll never know that you've got my illegal collection of Dutch Apple Pie recipies.
(But yes, I too would expect that the security would improve in time. But I expect it to happen only after the first major corporate data heist happens due to an incompetent implementation of Microsoft Active Remote Drive Wireless X Explorer Internet Protocol. (Did I leave out any buzzwords there? :-) Call me a pessimist.)
I am. And I'm imagining how much fun it could be to eavesdrop on disk reads through "7 meters of internal walls."
You may mod me down now.
...might be that I don't have to spend much on a PS2 or N64 to get a decent gaming experience. But if I want a good Lose32 gaming box, I have to plunk down some hefty cash for a video card, cash for plenty of RAM, cash for cache (sorry)...
With my Linux box, however, I can simply fire up KJumpingCube and lose just as many hours of time, for much less money. Holy code that game is so addicting. Between that and FoulEggs I might never leave the keyboard again.
Um, no, not "devil phil". It's devphil, as in /dev/phil, which was a nickname assigned to me in my college days, hacking Unix. (We got *this* close to actually implementing a /dev/phil device driver, but the sysadmins couldn't give us an experimental machine so we could build a new kernel and play with it. Ah well.)