The trouble with this approach is the small but vocal minority of people who absolutely insist on running their own mail server. Maybe they don't trust the ISP's mail server. Maybe it's a stand on principle - just because they're on dialup shouldn't mean they can't run a mail daemon.
When you (as an ISP) decide to block outbound port 25 from dialups, you have to be aware that you will alienate these people. That may be a tradeoff you're willing to make - but you shouldn't just assume they don't exist.
Use a pair of binoculars to project the sun onto a large sheet of cardboard. (Only uncap one side of the binoculars.) The projection is safe to look at, and the spot should be visible if you make the projection large enough. As someone else said, it'll look like a freckle.
If you don't have any binoculars, you can use a sheet of paper with a pinhole in it instead. You won't be able to make the projection as large though.
This is one of those irritating laws of physics. You can't ever destroy heat. You can spread it into a large volume, which is what the heatsink and the fan on your computer do, but it never ever goes away.
What happens if you try to destroy heat? Whatever gadget you build to do the job will turn out to generate more heat than it destroys. In your example, you'd have to have nanospeakers - probably piezoelectric disks stuck on the end of each tube - to do the cancellation with. And driving the nanospeakers will generate more heat than is destroyed by cancelling the sound waves.
Yes, Red Hat (formerly Cygnus) does host gcc.gnu.org for the GCC project. And it does happen to be the same machine as sources.redhat.com (formerly sourceware.cygnus.com). If you look back through the archives, you'll notice that it used to be called egcs.cygnus.com. RMS required that it be given a name in the gnu.org domain when the EGCS steering committee took over official maintenance of GCC.
It's my understanding that the difficulties are mostly organizational, not technical. Dumping the GCC sources into the big combined CVS archive is easy. Adjusting the way the GCC, GDB, and binutils developers work, so they don't step on each others' toes, is somewhat harder.
Regarding Bitkeeper, yeah it's nice, but it isn't free software, and the FSF requires the official archives of GNU projects to be run with 100% free software. So it is not an option at this time.
I don't follow all the math on the site, but it seems to me that all they are doing is applying another force, counter to gravity. Just basic Newtonian physics. It works great in the lab, but the ship won't go anywhere.
Slashdot Mirror
The trouble with this approach is the small but vocal minority of people who absolutely insist on running their own mail server. Maybe they don't trust the ISP's mail server. Maybe it's a stand on principle - just because they're on dialup shouldn't mean they can't run a mail daemon.
When you (as an ISP) decide to block outbound port 25 from dialups, you have to be aware that you will alienate these people. That may be a tradeoff you're willing to make - but you shouldn't just assume they don't exist.
Use a pair of binoculars to project the sun onto a large sheet of cardboard. (Only uncap one side of the binoculars.) The projection is safe to look at, and the spot should be visible if you make the projection large enough. As someone else said, it'll look like a freckle.
If you don't have any binoculars, you can use a sheet of paper with a pinhole in it instead. You won't be able to make the projection as large though.
This is one of those irritating laws of physics. You can't ever destroy heat. You can spread it into a large volume, which is what the heatsink and the fan on your computer do, but it never ever goes away.
What happens if you try to destroy heat? Whatever gadget you build to do the job will turn out to generate more heat than it destroys. In your example, you'd have to have nanospeakers - probably piezoelectric disks stuck on the end of each tube - to do the cancellation with. And driving the nanospeakers will generate more heat than is destroyed by cancelling the sound waves.
You might want to look at:
- http://gcc.gnu.org/steering.html
- http://gcc.gnu.org/gccmission.html
- http://gcc.gnu.org/releases.html#timeline
for more details on the exact relationship between GCC development, the FSF, and Red Hat.It's my understanding that the difficulties are mostly organizational, not technical. Dumping the GCC sources into the big combined CVS archive is easy. Adjusting the way the GCC, GDB, and binutils developers work, so they don't step on each others' toes, is somewhat harder.
Regarding Bitkeeper, yeah it's nice, but it isn't free software, and the FSF requires the official archives of GNU projects to be run with 100% free software. So it is not an option at this time.
I don't follow all the math on the site, but it seems to me that all they are doing is applying another force, counter to gravity. Just basic Newtonian physics. It works great in the lab, but the ship won't go anywhere.