It's long been common knowledge that Sendmail requires proper configuration to use safely. The system's not compromised in the sense that the spammer has root access, but in the sense that the email server on the system automatically relays any mail sent to it.
You don't want to set up factories in China. The Chinese government has been known to demand copies of all onsite manuals, and set up their own competing shop within a mile of the original site.
The terrorists could get control of the planes by demanding that the pilots come out. Human sympathy is sufficient that one eviscerated flight attendent, and the threat of a second, will cause just about any sane man to submit.
I've always thought that the best method to keep planes safe is to eliminate the door between the cockpit and passenger compartments. keep all the food/water/toiletries the pilots need in their own compartment, and force anyone wants to get in to go through a separate door on the outside of the plane.
Dial-up Ain't Gone...
on
Online! The Book
·
· Score: 2, Interesting
...and it may never be. I still help out at a dial-up ISP that's been open for business since 1989. We're a local mom and pop shop.
We have a lot of customers. There's seniors who don't do anything but email, so our "PAYING" rate works well, at $5 for 20 hours of connection time, tracked by the second. (Who'd have thought $5 could last you six months?) Then there's joe and jane parent who don't want their kid on Kazaa all the time.
All in all, dial-up still fills a niche. The low-bandwidth, low-cost niche. That's not going to be satisfied until there's datacount-based wireless service.
Build your own kernel.:) It's the ultimate in geek self-esteem boosting.:) (At least, when you do it the first time, with help, then with the first time, all on your lonesome.)
I see it as a rather good thing. The more organizations SCO is tied up in lawsuits with, the more taxed their lawyers are, and the fewer the resources they'll have.
If I recall my middle school history class properly, that's how Napoleon failed. And I wouldn't count Dear Darl as intelligent as Napoleon.
Every company makes mistakes. Running Windows XP is a mistake a lot of companies and people make.
The reason this is Slashdotworthy is that it is the same Diebold. The people who submit stories are hostile towards Diebold, and it's only to be expected that some of those hostile stories would make it through.
I'm sure a lot more vital-service machines than just those built by Diebold were hit. A story on the range of systems, maybe with ATMs as a highlight, would have been more appropriate.
Not ranting at you, just wasting karma, that's all.
My apologies. I was replying, long after I had last posted in the thread. I should have paid more attention the the context than just reading your post.
Mixing up nm and mm was rampant in this story. I was beginning to think nobody had a frigging clue what they were talking about. If a guy just reads the background articles on Ars Technica, they're a veritable authority compared to the average discussion participant.
ouch. He was also testing relatively small programs on large machines. You're still looking at a pretty nasty performance hit.
I wouldn't, for example, try this on the Linux kernel. It'd require serious hardware to compile within a reasonable time, and enough identical machines with virtualization software to benchmark the compiles within a reasonable time.
All in all, I'd say it's something for IBM to try, not me.
First, you were getting nanometers (nm) and millimeters (mm) mixed up. nm refers to the minimum feature size. (Or your resolution, if you will.) the 300mm slabs refer to the size of the entire wafer, on many dies are fit.
Have you ever seen a picture of a circular piece of silicon? That's a wafer. All of the rectangles you see on the wafer are the individual dies, which are placed in a plastic(If you're really cheap, and you're not worried about static in handling) or ceramic(what's normally used) casing. Once you place the die in the casing, and perform a little bit of wiring inside, you have your chip.
I think (firefighting and telecom) (training and experience) trump one misinformed article. The insulation on plenum cable does not "burn" in an "inflammable" sense, but id does smolder. (Meaning that it still combusts, but it's much too slow to provide visible flame.)
Unfortunately, the cumbustion does produce toxic smoke, but that's true of nearly all general cumbustion. We don't completely understand pyrolisis in the "real world" yet, so producing a product whose smoke is non-toxic is an empiracle persuit, at best.
There are important points in the article, though. The one that strikes me first is airflow blockage. In fires, there are times when you don't want to ventilate an area, and times when you do. Airflow blockage prevents gases from reaching some places. While this is bad if you need oxygen (for a human), it could be good in the sense that the hot gasses from the fire may not penetrate the building as quickly. (HVAC systems are notorious for that.)
There was an article recently about matching client feature/bugfix needs with OSS developers. I'd like to see that take off. (Hell, I'd like to participate!)
As another poster pointed out, the move to 300mm wafers is intended to reduce wasted space.
AMD's die size has gotten large lately, so they need to increase the overall die size so that more dies will fit as opposed to areas where a die wouldn't fit. You can't run on half a CPU.
I don't have any control over what the company runs (except for my personal workstation, which I brought in from home.)... Until last week, the NT4 box worked pretty much flawlessly for over a year.
Slashdot Mirror
Is how you can test if a number is prime without finding all prime numbers less than half of that one.
Minor technical nitpick:
If you want your memory to run at core speed (drool...), it'll generate just as much (if not more) heat than the computational parts of the core.
Also, you'll need to put the memory controller on the die, too, else communications between CPU and memory would have to be routed off-die.
It's long been common knowledge that Sendmail requires proper configuration to use safely. The system's not compromised in the sense that the spammer has root access, but in the sense that the email server on the system automatically relays any mail sent to it.
Balmer's a Microsoft Man
He plugs them whenever he can
But with Linux about
He started to shout
And his mouth spouted much "slight-of-hand"
Now I can get my 2000 word English research paper up to the required 3000 words, and have the required unreadability!
As a hack, you could replace /sbin/shutdown with a shell script that pops up a dialog (If $DISPLAY is set) or asks on the console.
You don't want to set up factories in China. The Chinese government has been known to demand copies of all onsite manuals, and set up their own competing shop within a mile of the original site.
The terrorists could get control of the planes by demanding that the pilots come out. Human sympathy is sufficient that one eviscerated flight attendent, and the threat of a second, will cause just about any sane man to submit.
I've always thought that the best method to keep planes safe is to eliminate the door between the cockpit and passenger compartments. keep all the food/water/toiletries the pilots need in their own compartment, and force anyone wants to get in to go through a separate door on the outside of the plane.
...and it may never be. I still help out at a dial-up ISP that's been open for business since 1989. We're a local mom and pop shop.
We have a lot of customers. There's seniors who don't do anything but email, so our "PAYING" rate works well, at $5 for 20 hours of connection time, tracked by the second. (Who'd have thought $5 could last you six months?) Then there's joe and jane parent who don't want their kid on Kazaa all the time.
All in all, dial-up still fills a niche. The low-bandwidth, low-cost niche. That's not going to be satisfied until there's datacount-based wireless service.
True, true. But if I mentioned it, I'd have to admit that's something I haven't accomplished yet. :)
Build your own kernel. :) It's the ultimate in geek self-esteem boosting. :) (At least, when you do it the first time, with help, then with the first time, all on your lonesome.)
I see it as a rather good thing. The more organizations SCO is tied up in lawsuits with, the more taxed their lawyers are, and the fewer the resources they'll have.
If I recall my middle school history class properly, that's how Napoleon failed. And I wouldn't count Dear Darl as intelligent as Napoleon.
Whoa, flashback to Lazarus Long's memoirs!
Every company makes mistakes. Running Windows XP is a mistake a lot of companies and people make.
The reason this is Slashdotworthy is that it is the same Diebold. The people who submit stories are hostile towards Diebold, and it's only to be expected that some of those hostile stories would make it through.
I'm sure a lot more vital-service machines than just those built by Diebold were hit. A story on the range of systems, maybe with ATMs as a highlight, would have been more appropriate.
Not ranting at you, just wasting karma, that's all.
My apologies. I was replying, long after I had last posted in the thread. I should have paid more attention the the context than just reading your post.
Mixing up nm and mm was rampant in this story. I was beginning to think nobody had a frigging clue what they were talking about. If a guy just reads the background articles on Ars Technica, they're a veritable authority compared to the average discussion participant.
It's not a torpedo. There's no explosive in it.
Heck, it hardly makes any sound, so the sonar man isn't likely to know it's there until it taps the hull.
ouch. He was also testing relatively small programs on large machines. You're still looking at a pretty nasty performance hit.
I wouldn't, for example, try this on the Linux kernel. It'd require serious hardware to compile within a reasonable time, and enough identical machines with virtualization software to benchmark the compiles within a reasonable time.
All in all, I'd say it's something for IBM to try, not me.
First, you were getting nanometers (nm) and millimeters (mm) mixed up. nm refers to the minimum feature size. (Or your resolution, if you will.) the 300mm slabs refer to the size of the entire wafer, on many dies are fit.
Have you ever seen a picture of a circular piece of silicon? That's a wafer. All of the rectangles you see on the wafer are the individual dies, which are placed in a plastic(If you're really cheap, and you're not worried about static in handling) or ceramic(what's normally used) casing. Once you place the die in the casing, and perform a little bit of wiring inside, you have your chip.
I think (firefighting and telecom) (training and experience) trump one misinformed article. The insulation on plenum cable does not "burn" in an "inflammable" sense, but id does smolder. (Meaning that it still combusts, but it's much too slow to provide visible flame.)
Unfortunately, the cumbustion does produce toxic smoke, but that's true of nearly all general cumbustion. We don't completely understand pyrolisis in the "real world" yet, so producing a product whose smoke is non-toxic is an empiracle persuit, at best.
There are important points in the article, though. The one that strikes me first is airflow blockage. In fires, there are times when you don't want to ventilate an area, and times when you do. Airflow blockage prevents gases from reaching some places. While this is bad if you need oxygen (for a human), it could be good in the sense that the hot gasses from the fire may not penetrate the building as quickly. (HVAC systems are notorious for that.)
Actually, "plenum spaces" are supposed to have plenum cable, according to fire code. Plenum cable doesn't burn, it just smolders.
If that's what you meant by "inflammable," sorry. The word is "nonflammable."
Well, why don't you try fixing it?
(That's the generic answer.)
There was an article recently about matching client feature/bugfix needs with OSS developers. I'd like to see that take off. (Hell, I'd like to participate!)
As another poster pointed out, the move to 300mm wafers is intended to reduce wasted space.
AMD's die size has gotten large lately, so they need to increase the overall die size so that more dies will fit as opposed to areas where a die wouldn't fit. You can't run on half a CPU.
It was the technician performing maintenence, if you read the report.
I don't have any control over what the company runs (except for my personal workstation, which I brought in from home.) ... Until last week, the NT4 box worked pretty much flawlessly for over a year.
So you advocate protecting the user from himself?
Maybe we need some sort of computer-related Darwin Awards system.