That site doesn't define 3-manifold and 3-sphere. Is it a 3D sphere in 4D or a 2D sphepe in 3D? It it's the former, then the result hardly has any practical use, since we live in 3D and mostly deal with 2D manifolds:-)
Your comment shows that your are not a developer. It's much easier to develop on a 500 MHz machine than on a 100 MHz machine. Less time to compile. Usually less time to reboot if the system crashes. Less time between the idea and the implementation. And you don't necessarily have to support all new hardware - you don't need the new soundcard to compile stuff.
Note that such jokes can only fool those who think that it's so easy to kill an open source project like CPAN. Obviously Slashdot editors think that everybody with a clue has switched to better sites already.
gcc and gcc3 are different packages on RedHat 7.2 and above. I guess you have a problem understading it. I'm using the deafult compiler (gcc-2.96) to compile everything and I don't have the gcc3 package installed.
Despite being a "bastard", gcc-2.96 does a pretty decent job. The only problem I have ever had with it is that it doesn't always warn about unused static functions.
Why wait just because of one package? It is not nearly as important as the kernel of gcc (without 3) which is used to build the system. As another poster noticed, even KDE was updated to another major release (1.x to 2.x) in RedHat 7.1, and gcc3 is way more optional that KDE, yet the update would be (in the worse case) in the second number from 3.0.x included in RedHat 7.2 to 3.1 in RedHat 7.3.
Of course if you think that gcc3 will be the default compiler on RedHat 7.3 then I'm sorry, I should have ignored your comment.
You can have a desktop full of open windows that survives when you reboot your PC or turn it off for the weekend.
When I worked in New Hamphire, we had power outages quite often, but the server had a UPS. Users could continue to edit the same documents or even continue debugging after the power was restored.
The server was running Linux, the clients were both Linux and Windows based.
Very interesting discussion between two people who didn't read the article.
With our adapter, the flexCD plays in most existing CD and DVD devices. Made from a clear polycarbonate disc (or lens), plus a cover that acts like a sandwich over the flexCD, the adapter can be reused indefinitely.
Not exactly "protective cases".
I hate to say it, but it looks like that morons are winning the battle for Slashdot:-(
No, it's shameless karma whoring. Note complete lack of serious arguments and links to the benchmarks. Note that the Microsoft's product (Visual Source Safe?) is not called by name.
This comment is a perfect example why Slashdot comments should not be trusted any more than a spam that promises you penis enlargement and millions of dollars.
Because the Linux users are smart enough to, and unfortunately often required to, lie about their browser/OS for online banking, etc., which will often dump a user if the User Agent string doesn't report a blessed version of IE or NS >= 4 running on Windows or Macintosh.
So what? How does it prevents them from having MathML? UNIX version of Mozilla is not just for commercial UNIX systems - it's actually developed primarily for Linux, and *BSD, but should also compile on "legitimate" UNIX heirs.
Maybe it's just a talk of trolls/idiots who either don't understand the original comment or pretend to be dumb. Then I'm sorry, I didn't mean to participate:-)
When I was about to read the comments to this story, I was sure that there will be comments at +3 and above implying that RedHat is going to make a distribution for PowerPC.
The moderation system on/. is broken. Moderation is done by amateurs randomly getting mod points. An average/. reader doesn't have sufficient qualification to moderate. Maybe frequent posters with good karma could moderate better?
In this case, it's just a lame attempt of Slashdot to be "provocative". However, there is some truth in saying that it's a Linux (actually, GNU/Linux and Linux kernel) problem.
As other posters noticed, GNU libc defaults to an unsafe but faster free() implementation that can damage the heap if called more than once on the same pointer. Other operating systems are said to default to a safer malloc() implementation.
The question is, if, and to which extent, potential extra security justifies real trade-offs in speed.
Using shared libraries is not free of trade-offs. Position independent code (PIC) used in them is slower on many architectures, including x86. However, shared libraries are preferred because, should anything like this bug in zlib be found, the only package to replace will be the faulty library (and the "offenders" linking to it statically, like CVS and rsync).
But the measure that could have prevented this bug from being an issue on GNU/Linux has not been taken on the same grounds of speed! Yet I think that a lot of programs suffer (in terms of speed) more from slower PIC code than from safer malloc(). No I'm not suggesting going back to static libraries. Rather, we should acknowledge that there is a price tag attached to the peace of mind.
Linux kernel developers should have examined the zlib code for compatibility with Linux kernel-space memory management.
No, it's not the site, it's the poster who is suffering from the/. effect (actually, syndrome). The/. syndrome is: post as fast as possible and get tons of karma from moderators who don't check the links.
The article says that Netscape goes to Google by loading a URL beginning with "http://info.netscape.com/"
Therefore, the temporary workaround would be to set info.netscape.com to 127.0.0.1 in your/etc/hosts (or c:\windows\hosts or whatever).
The solution is to use Mozilla and remove Netscape 6.
Slashdot Mirror
Well, then the pilot won't be able to download the safety manual. Who needs those manuals?
That site doesn't define 3-manifold and 3-sphere. Is it a 3D sphere in 4D or a 2D sphepe in 3D? It it's the former, then the result hardly has any practical use, since we live in 3D and mostly deal with 2D manifolds :-)
By the way, by reading this comment you agree to give me your first child.
cyberpunk63/cyberpunk63
Your comment shows that your are not a developer. It's much easier to develop on a 500 MHz machine than on a 100 MHz machine. Less time to compile. Usually less time to reboot if the system crashes. Less time between the idea and the implementation. And you don't necessarily have to support all new hardware - you don't need the new soundcard to compile stuff.
Note that such jokes can only fool those who think that it's so easy to kill an open source project like CPAN. Obviously Slashdot editors think that everybody with a clue has switched to better sites already.
Your grammar, punctuation (no comma here) and spelling make me cry.
Despite being a "bastard", gcc-2.96 does a pretty decent job. The only problem I have ever had with it is that it doesn't always warn about unused static functions.
Of course if you think that gcc3 will be the default compiler on RedHat 7.3 then I'm sorry, I should have ignored your comment.
2004-08-01 15:00:12 Comet misses earth (science,news) (rejected)
2005-01-12 01:51:02 Another stealth asteroid misses earth (science,news) (rejected)
2007-12-23 23:33:58 Asteroid hits earth, wipes out civilization (science,news) (rejected)
I still have no idea why the last story was rejected.
When I worked in New Hamphire, we had power outages quite often, but the server had a UPS. Users could continue to edit the same documents or even continue debugging after the power was restored.
The server was running Linux, the clients were both Linux and Windows based.
I hate to say it, but it looks like that morons are winning the battle for Slashdot :-(
Just wait until Intel releases 2.4GHz Pentium 4. I wonder if FCC will tell Intel to use another frequency.
This comment is a perfect example why Slashdot comments should not be trusted any more than a spam that promises you penis enlargement and millions of dollars.
Moderators, learn the difference between a troll and a fish :-)
nslookup wasn't ported by fanboys. It was ported by Microsoft employees or contractors.
Motors with magnets are generators. Motors with electromagnets are not (if the electromagnets are turned off).
Maybe it's just a talk of trolls/idiots who either don't understand the original comment or pretend to be dumb. Then I'm sorry, I didn't mean to participate :-)
Not much, and this is already being done. The real problem is with "free(ptr); free(ptr);"
The moderation system on /. is broken. Moderation is done by amateurs randomly getting mod points. An average /. reader doesn't have sufficient qualification to moderate. Maybe frequent posters with good karma could moderate better?
As other posters noticed, GNU libc defaults to an unsafe but faster free() implementation that can damage the heap if called more than once on the same pointer. Other operating systems are said to default to a safer malloc() implementation.
The question is, if, and to which extent, potential extra security justifies real trade-offs in speed.
Using shared libraries is not free of trade-offs. Position independent code (PIC) used in them is slower on many architectures, including x86. However, shared libraries are preferred because, should anything like this bug in zlib be found, the only package to replace will be the faulty library (and the "offenders" linking to it statically, like CVS and rsync).
But the measure that could have prevented this bug from being an issue on GNU/Linux has not been taken on the same grounds of speed! Yet I think that a lot of programs suffer (in terms of speed) more from slower PIC code than from safer malloc(). No I'm not suggesting going back to static libraries. Rather, we should acknowledge that there is a price tag attached to the peace of mind.
Linux kernel developers should have examined the zlib code for compatibility with Linux kernel-space memory management.
No, it's not the site, it's the poster who is suffering from the /. effect (actually, syndrome). The /. syndrome is: post as fast as possible and get tons of karma from moderators who don't check the links.
It's not a gnome. It's a crossdressed troll.
Therefore, the temporary workaround would be to set info.netscape.com to 127.0.0.1 in your /etc/hosts (or c:\windows\hosts or whatever).
The solution is to use Mozilla and remove Netscape 6.
Four days without a remote hole in the default install!
Not sure if OpenSSH is enabled by default though.