I tried to find a place to e-mail this to ya, Clump, but I couldn't. Hope you're reading.
I'm linking directly in these posts and not doing the normal goatse.cx paranoid stuff. Anybody providing goatse.cx links on a topic like this should be hunted down and eviscerated.
The World Trade Center houses 350 tenants within the 16-acre complex, which includes approximately 12 million square feet of rentable office space, including the two collapsed 110-story office towers, a 47-story office building, two nine-story office buildings, an eight-story U.S. Customhouse and a 22-story Marriott hotel.
Among the largest tenants is Morgan Stanley, which has its retail trading operation headquartered in the south tower of the World Trade Center.
The story also lists a couple of websites, one of which is a list of tenants that "is not clear how often" it is updated. The list doesn't appear to be responding at this moment.
I think it's a statement to the far-reaching devestation of this cowardly attack.
I attempted to go to CNN, Fox News and MSNBC this morning and could get no response from their servers.
I do find it heartwarming that sites that normally have nothing to do with most types of news ( Slashdot, CNET, ESPN, etc.) are doing their best to help keep the flow of information going during this tragedy.
I totally understand and agree with this, however I can't help but want to brainstorm some ideas around this.
Couldn't we add a boatload of root servers? This approach will open up another can of worms; namely synchronization of roots. With all the advances and brains going into P2P lately, couldn't a decent replication scheme be put into effect to minimize this?
Imagine, if you will, a root server with an "update" server handling all of the replication transactions. Bandwidth would go up, but the root server itself would be able to devote its processor to dealing with DNS lookups.
Maybe I'm just blowing smoke, but I'd love to find a way to dodge the ICANN bullet.
Also, how does this prevent the RIAA from shutting down <insert favorite music trading post> for not being able to track 100% of the transfers?
I believe that Napster can't be accountable for unauthorized transfers conducted on their network. Open Source or cloned clients wouldn't be an authorized source of traffic on the network. Granted, they'd have to prove that they're doing everything they can to prevent unauthorized access, but that's fairly trivial.
I do seem to remember reading several stories about AOL not being responsible for the child pr0n that is somewhat pervasive in their service.
Please correct me if I'm wrong, but a provider like AOL, Earthlink or even the phone company is not responsible for illegal activities conducted on their networks as long as they're not complicit in the commission of the activity.
Standard IANAL fine print included standard on all legalish-sounding posts.
What if I wish to modify and redistribute my own version of kylix? I have paid for it and I still don't even have a copy of the source, let alone the right to modify and redistribute it.
Obligatory "I do believe in OSS" notice here.
For OSS to really succeed and quash closed-source software, it needs the backing of Big Business. Nothing's going to hurt the movement more than 843 derrivitave code patches that aren't merged into the main branch of the application.
Give Joe Coder the ability to modify the environment that a business uses and there goes the upgrade path. Granted, if the patch is submitted and accepted, fine and good. But what happens when he's written the entire application using the Mystical Wiget extensions that he developed in the environment, rather than as an add-on, and it's rejected as a main patch? Is he going to stop and re-code the application?
I just see a ton of bad things coming from a casual "I want to modify the source" attitude.
... I missed The Party At The End Of The Universe!
On to a more serious note, though. According to some scientists, this was supposed to be capable of yielding either a singularity (black-hole) or strangelets. Of the two, strangelets would be by far the worst. Some very well renowned physicists came back and said that the chance "was extremely small"
One thing to remember (I think Einstein said it, actually): in Quantum mechanics, if it can happen, it will.
I can't wait! I'll be playing Tool's AEnima as the stranglets obliterate normal matter.
"Mom, please flush it all away..."
Re:Curiosity killed the cat
on
Star In A Jar
·
· Score: 1
I seem to remeber them saying that they had "effective countermeasures" they could use during wartime to scramble an enemy's use of GPS...
You betcha! The GPS P(Y) system (or is it Y(P)) has two different informational systems in it. At the moment, the drift and error rating in the civilian system is turnned off and a commercial Garman unit is every bit as accurate as a military unit.
Military units have some sort of special stuff in them that allow them to be accurate for a fixed period of time, rendering captured units unusable after a while.
All the military has to do is turn off the non-parenthesized portion of the system ( the P in P(Y)) and there goes GPS for all but the allies with enabled military grade GPS units.
Pretty neat system, actually.
... and I believe the most common DLLs have already been built to unique addresses to minimize the need for relocation/redundant copies.
I haven't actually checked the address spaces of my MS DLL's (MFC42.dll, etc.) to see if they're different, but I believe they are since the Visual C++ documentation recommends doing that.
There's only one little problem with that method, though... There's nothing to prevent anybody else from assigning their DLL base address to one already used by a very higly used library, i.e. the MFC runtimes.
In fact, I'd be willing to bet that most of the ActiveX controls, DLL's and such compiled under Visual Basic keep the default base address.
Next time, I'll try to look for it before I post a reply.
The reasons were listed in a C|Net News.com article on March 12 of this year. Here's the relevant link and the quoted text (it's the second from the last paragraph in the article):
Napster has contacted some of the people spreading these anti-filter technologies and asked them to stop. Aimster confirmed late Monday that it was taking its Pig Latin system down at Napster's request and had stopped development of a more powerful program for evading the filters that had been dubbed "Scorpion."
So it looks like the hillarious Pig Latin encoder is no more, as well as their next generation technology. Ah, well...
Man, I wish I could remember where I read this... It was either on the News.com website a few days ago (Monday or Tuesday) or Aimster's site; I'm leaning towards the C|Net site.
Accorting to the article I read, they were asked (politely, no C&D orders were mentioned) to remove the Pig Latin scheme. To avoid a potentially nasty fight, the dropped it.
Yes, that is how most overclockers do things. All but one of my systems are OC'd that way.
But I gotta tell you the look on people's faces when you tell them you have an 8 stage cooling system manufactured out of assorted car radiators, oil coolers and an old refigerator hooked up to the heasink on your computer is well worth the effort.
In reality, the More Insane Cooling Setup is a very close analogy to the old "My dick is bigger than your dick" game.
And, of course, your/. reading friends all grin from ear to ear while they ask you, "Can you imagine a Beowolf cluster of those?!"
The drawbacks to overclocking are really few, if you're careful. For example, overclocking my early Athlon (Slot A) from 550 to 750 megahertz was quite a process. The packaging wasn't meant to be opened and the processor was "locked" to the 550 setting with some surface mount resistors. Overclocking this monster required cracking (literally, not figuratively) the sealing tabs from the plastic case and some dainty surgery with a very high quality soldering iron. If I hadn't been overclocking for several years, I wouldn't have attempted it.
The Athlon was also bleeding-edge overclocking; they now have a device for $20 to $50 US that will allow you to overclock a Slot A Athlon without cracking the case and desoldering and resoldering resistors.
The only real drawback I've seen to overclocking is the possiblity of frying your processor, motherboard or other components. The person who got me into overclocking toasted 6 Abit BP6 motherboards trying to figure out how to get a Coppermine Celeron to work in the board. While studing the pin diagrams and attempting to reroute traces on the motherboard isn't the norm, it does happen.
Aside from horror stories like the one above, there are two things to watch for when overclocking: heat and over-voltage.
As for heat, don't skimp on the heat sinks and check a page like [H]ard|OCP or Toms Hardware (links below) for heatsink information, case modifications and the like.
Voltage can be trickier to deal with. As bus and processor speeds become higher and higher, the transistor count rises and, hence, the current required by the processor, chipset and other components of the system. Modern processors lower the voltage significantly in order to conserve current. Some processors require 2 volts (or less!) in the core. If you're familiar with electronics at all, you'll soon see that the signal to noise ratio becomes a real factor. The solution is to increase the signal by raising the voltage. It's a tightrope act; raise the voltage too high and you could fry your chip in microseconds, not high enough and it doesn't add any noise rejection but does add heat.
Something that used is cited as a factor now that I don't really find relavent is processor life. Transistors do not last forever. Stuff that goes on at the quantum level degrades the PNP/NPN junctions over time. Granted, in most situations this can be over the course of years or decades, but with transistors as small as those in a typical processor die, it's generally on the lines of 5 to 7 years. That's if you run them at the manufacturer's suggested voltage. Increase the voltage, decrease the life.
That being said, with processors doubling in speed every 18 months or so, I don't really see any current chip being in service on a desktop 7 years from now. Even if you were to cut the operating life of your processor in half from 7 to 4.5 years, would it matter much? Incedentally, I have a Linux box here running on a Pentium 166MMX overclocked to 233. I bought the processor and motherboard in '97 or '98, if I remember correctly. It's been on 24/7 for all but the few days it took to move from California to Phoenix.
If you're interested in overclocking, the best way to get into it is to search the hardward sites, read their guides and try it.
It will also help to know a bit more about the x86 architecture. For example, understanding the workings of SDRAM fetch settings in your BIOS, how to figure out the PCI bus speed after overclocking your motherboard's bus from 133 to 145 and so on. [H]ard|OCP and Toms Hardware (links I promised above =) have some very good information on just that sort of thing.
If I missed anything or blew a couple of concepts, feel free to offer a friendly correction. If you have any more questions, feel free to ask!
I had Win 3.1 on the desktop at work and when we got internet access, we had a single-disk upgrade to add TCP connectivity. If I remember the label correctly, it was an upgrade to 3.11.
Wrong about the Win2k TCP/IP stack, it sure spanks Linux 2.4 in performance(Note, this is using the same software. Not cheating buy comparing IIS to Tux on different hardware setups(Two wrongs doesn't make right.)!!!)
I'm not running 2.4, I'm on 2.2.16 or somewhere there-abouts; I can't speak with any authority on 2.4.
But what I can say, as I said in my original post, is that in my experience, the Win2K TCP stack performs worse than my Linux box. And it's identical hardware, i.e. a dual boot machine.
I've done testing on my setup using ftp, Apache and a couple of raw TCP writing scripts. Granted, the raw TCP might be a bit skewed because of the difference in library access, optimized code and the like between the different systems. But the FTP implimentation, if I recall, was a port of a POSIX ftp server from a BSD version. And Apache - It's comparing apples to apples.
The stack in Win3.1 was Trumpet(http://www.trumpet.com.au), it was really good, but 3.1 wasn't preemtive and it couldn't show it's glory.), Win9X stack sucked though.
I really don't know what stack came with 3.1, but I do recall getting much better performance after purchasing Trumpet. It wouldn't supprise me if Microsoft bought the source to an older version of Trumpet and just recompiled it to run under '95, though.
Granted, this is all personal experience talking here, but from the LDS strongholds I visited there (including Salt Lake City), the people, not the laws were the problem.
If you're a tourist and don't walk around with an "Elder [insert your name here]" badge on, you're treated as if you have some horrible communicable disease, walk around drinking cheap whiskey from the bottle, smoke 38 packs of cigs a day and attempt to get their children going on it and want to have sex with anything that moves and some things that don't.
The skiing is nice, but not good enough to make me ever want to go back.
Personally, I'm sick and tired of liberal-slanted, goodie-goodie, gotta-help-everybody, politically-correct sewage spewing.
Yes, I find sweatshop working conditions deplorable. Yes, I'd love to do something to rectify the situation. But you know what? The money that I'd be using to do this with is already involuntarily pilfered from my paychecks at the rate of $30,000 to $40,000 per year by the same jackasses who say I need to contribute to their causes!
Until they stop with their stupid police-action politics and money grubbing, my money stays where it belongs: in my wallet.
Get rid of the stupid, illegal taxes and allow us to put that portion of my income to the causes we hold near and dear to our hearts, and I promise you we'll be more effective that some bloated, red-tape ridden government entity ever could be.
Slashdot Mirror
I'm linking directly in these posts and not doing the normal goatse.cx paranoid stuff. Anybody providing goatse.cx links on a topic like this should be hunted down and eviscerated.
Source: C|Net News.com website.
Story lead in:
The story also lists a couple of websites, one of which is a list of tenants that "is not clear how often" it is updated. The list doesn't appear to be responding at this moment.
Hope this helps.
I attempted to go to CNN, Fox News and MSNBC this morning and could get no response from their servers.
I do find it heartwarming that sites that normally have nothing to do with most types of news ( Slashdot, CNET, ESPN, etc.) are doing their best to help keep the flow of information going during this tragedy.
Couldn't we add a boatload of root servers? This approach will open up another can of worms; namely synchronization of roots. With all the advances and brains going into P2P lately, couldn't a decent replication scheme be put into effect to minimize this?
Imagine, if you will, a root server with an "update" server handling all of the replication transactions. Bandwidth would go up, but the root server itself would be able to devote its processor to dealing with DNS lookups.
Maybe I'm just blowing smoke, but I'd love to find a way to dodge the ICANN bullet.
I seem to remember seeing a Weird Al "Behind The Music" episode on VH1 where he addressed this, albeit very hazily.
Extrapolating and paraphrasing the points, I understood his reasons for going to the artist for permission to parody to be
- It is most times easier to get the artists to talk to their own record companies;
- It tends to prevent the bad feelings on deals like Amish Paradise.
That being said, somebody seriously dropped the ball on the whole Gangster Paradise/Amish Paradise deal.I do seem to remember reading several stories about AOL not being responsible for the child pr0n that is somewhat pervasive in their service. Please correct me if I'm wrong, but a provider like AOL, Earthlink or even the phone company is not responsible for illegal activities conducted on their networks as long as they're not complicit in the commission of the activity.
Standard IANAL fine print included standard on all legalish-sounding posts.
Obligatory "I do believe in OSS" notice here.
For OSS to really succeed and quash closed-source software, it needs the backing of Big Business. Nothing's going to hurt the movement more than 843 derrivitave code patches that aren't merged into the main branch of the application.
Give Joe Coder the ability to modify the environment that a business uses and there goes the upgrade path. Granted, if the patch is submitted and accepted, fine and good. But what happens when he's written the entire application using the Mystical Wiget extensions that he developed in the environment, rather than as an add-on, and it's rejected as a main patch? Is he going to stop and re-code the application?
I just see a ton of bad things coming from a casual "I want to modify the source" attitude.
On to a more serious note, though. According to some scientists, this was supposed to be capable of yielding either a singularity (black-hole) or strangelets. Of the two, strangelets would be by far the worst. Some very well renowned physicists came back and said that the chance "was extremely small"
One thing to remember (I think Einstein said it, actually): in Quantum mechanics, if it can happen, it will.
I can't wait! I'll be playing Tool's AEnima as the stranglets obliterate normal matter.
"Mom, please flush it all away..."
But how do you know that the cat is dead?
You betcha! The GPS P(Y) system (or is it Y(P)) has two different informational systems in it. At the moment, the drift and error rating in the civilian system is turnned off and a commercial Garman unit is every bit as accurate as a military unit.
Military units have some sort of special stuff in them that allow them to be accurate for a fixed period of time, rendering captured units unusable after a while.
All the military has to do is turn off the non-parenthesized portion of the system ( the P in P(Y)) and there goes GPS for all but the allies with enabled military grade GPS units.
Pretty neat system, actually.
There's only one little problem with that method, though... There's nothing to prevent anybody else from assigning their DLL base address to one already used by a very higly used library, i.e. the MFC runtimes.
In fact, I'd be willing to bet that most of the ActiveX controls, DLL's and such compiled under Visual Basic keep the default base address.
Man, there's something I haven't heard in about 8 years...
David: ICANN set up us the bomb.
ICANN: All your domains are belong to us.
Sorry... I couldn't resist...
A company called Exponent got the project after Raytheon lost it.
Evidentally, the initial solution made the soldiers look like a Teenage Mutant Ninja Turtle and, once the fell down, they couldn't get up.
This has got to be the funniest post I've seen in months...
The reasons were listed in a C|Net News.com article on March 12 of this year. Here's the relevant link and the quoted text (it's the second from the last paragraph in the article):
So it looks like the hillarious Pig Latin encoder is no more, as well as their next generation technology. Ah, well...Accorting to the article I read, they were asked (politely, no C&D orders were mentioned) to remove the Pig Latin scheme. To avoid a potentially nasty fight, the dropped it.
I guess I was just wishing for that "feature" on my kids N64 system.
No matter where I hide the cartriges or controllers, they always seem to find them...
Now I can prevent my kids from playing the next Pokemon game without having to take it away from them!
But I gotta tell you the look on people's faces when you tell them you have an 8 stage cooling system manufactured out of assorted car radiators, oil coolers and an old refigerator hooked up to the heasink on your computer is well worth the effort.
In reality, the More Insane Cooling Setup is a very close analogy to the old "My dick is bigger than your dick" game.
And, of course, your /. reading friends all grin from ear to ear while they ask you, "Can you imagine a Beowolf cluster of those?!"
The Athlon was also bleeding-edge overclocking; they now have a device for $20 to $50 US that will allow you to overclock a Slot A Athlon without cracking the case and desoldering and resoldering resistors.
The only real drawback I've seen to overclocking is the possiblity of frying your processor, motherboard or other components. The person who got me into overclocking toasted 6 Abit BP6 motherboards trying to figure out how to get a Coppermine Celeron to work in the board. While studing the pin diagrams and attempting to reroute traces on the motherboard isn't the norm, it does happen.
Aside from horror stories like the one above, there are two things to watch for when overclocking: heat and over-voltage.
As for heat, don't skimp on the heat sinks and check a page like [H]ard|OCP or Toms Hardware (links below) for heatsink information, case modifications and the like.
Voltage can be trickier to deal with. As bus and processor speeds become higher and higher, the transistor count rises and, hence, the current required by the processor, chipset and other components of the system. Modern processors lower the voltage significantly in order to conserve current. Some processors require 2 volts (or less!) in the core. If you're familiar with electronics at all, you'll soon see that the signal to noise ratio becomes a real factor. The solution is to increase the signal by raising the voltage. It's a tightrope act; raise the voltage too high and you could fry your chip in microseconds, not high enough and it doesn't add any noise rejection but does add heat.
Something that used is cited as a factor now that I don't really find relavent is processor life. Transistors do not last forever. Stuff that goes on at the quantum level degrades the PNP/NPN junctions over time. Granted, in most situations this can be over the course of years or decades, but with transistors as small as those in a typical processor die, it's generally on the lines of 5 to 7 years. That's if you run them at the manufacturer's suggested voltage. Increase the voltage, decrease the life.
That being said, with processors doubling in speed every 18 months or so, I don't really see any current chip being in service on a desktop 7 years from now. Even if you were to cut the operating life of your processor in half from 7 to 4.5 years, would it matter much? Incedentally, I have a Linux box here running on a Pentium 166MMX overclocked to 233. I bought the processor and motherboard in '97 or '98, if I remember correctly. It's been on 24/7 for all but the few days it took to move from California to Phoenix.
If you're interested in overclocking, the best way to get into it is to search the hardward sites, read their guides and try it.
It will also help to know a bit more about the x86 architecture. For example, understanding the workings of SDRAM fetch settings in your BIOS, how to figure out the PCI bus speed after overclocking your motherboard's bus from 133 to 145 and so on. [H]ard|OCP and Toms Hardware (links I promised above =) have some very good information on just that sort of thing.
If I missed anything or blew a couple of concepts, feel free to offer a friendly correction. If you have any more questions, feel free to ask!
Good luck!
I had Win 3.1 on the desktop at work and when we got internet access, we had a single-disk upgrade to add TCP connectivity. If I remember the label correctly, it was an upgrade to 3.11.
Another post to mod down... :)
But what I can say, as I said in my original post, is that in my experience, the Win2K TCP stack performs worse than my Linux box. And it's identical hardware, i.e. a dual boot machine.
I've done testing on my setup using ftp, Apache and a couple of raw TCP writing scripts. Granted, the raw TCP might be a bit skewed because of the difference in library access, optimized code and the like between the different systems. But the FTP implimentation, if I recall, was a port of a POSIX ftp server from a BSD version. And Apache - It's comparing apples to apples.
The stack in Win3.1 was Trumpet(http://www.trumpet.com.au), it was really good, but 3.1 wasn't preemtive and it couldn't show it's glory.), Win9X stack sucked though.
I really don't know what stack came with 3.1, but I do recall getting much better performance after purchasing Trumpet. It wouldn't supprise me if Microsoft bought the source to an older version of Trumpet and just recompiled it to run under '95, though.
Granted, this is all personal experience talking here, but from the LDS strongholds I visited there (including Salt Lake City), the people, not the laws were the problem.
If you're a tourist and don't walk around with an "Elder [insert your name here]" badge on, you're treated as if you have some horrible communicable disease, walk around drinking cheap whiskey from the bottle, smoke 38 packs of cigs a day and attempt to get their children going on it and want to have sex with anything that moves and some things that don't.
The skiing is nice, but not good enough to make me ever want to go back.
Yes, I find sweatshop working conditions deplorable. Yes, I'd love to do something to rectify the situation. But you know what? The money that I'd be using to do this with is already involuntarily pilfered from my paychecks at the rate of $30,000 to $40,000 per year by the same jackasses who say I need to contribute to their causes!
Until they stop with their stupid police-action politics and money grubbing, my money stays where it belongs: in my wallet.
Get rid of the stupid, illegal taxes and allow us to put that portion of my income to the causes we hold near and dear to our hearts, and I promise you we'll be more effective that some bloated, red-tape ridden government entity ever could be.
I like getting coupons for imported escargo, matzo ball boxes and parakeet shampoo...