Challenger - If the crew had been in a smaller craft on top, an explosion in a lower stage could have been escapable if the smaller craft could separate and land.
That sounds like a relatively small improvement in the odds. If two pounds of foam can make such a big hole, imagine what a chunk of metal shrapnel from an exploding rocket would do.
Columbia - If the craft that was to be used for re-entry had been on top, it would never have had the risk of freaking insulation (two pounds!? still drives me nuts) falling onto and damaging its heat shielding.
I agree with that, but ST-107 wouldn't have been at risk of flying foam if NASA had addressed the problem. They should have grounded it until they found a fix. The stuff isn't supposed to come off, and they ignored the fact that it does.
Disregarding the two catastrophes which were attributed to mismanagement, the system is 105 for 105.
Dell tech support was great... when they were selling UNIX. I had never touched *nix and their sales dept promised me i'd get the box with the OS installed. Naturally it arrived with only DOS installed and UNIX on floppies. I made those poor tech support bastards walk me thru every step including a kernel recompile.
dell: ok now edit the blah file me: what's the command for edit? them: oh shit
Challenger blew up when management ignored the facts about the srb o-rings in cold weather. The srbs leaked and burned thru the external tank. I can't see how having the bird on top would have helped.
Columbia was doomed because they ignored the warning signs of past missions. They knew that foam had damaged the orbiter on previous missions. It's too bad that 7 people had to die, and we had to lose an orbiter to wake them up.
IMO, the design is not the cause of these failures. It might be fair to say "it's always grounded because the design sucks and they can never get an all systems go", but the designers don't make the launch decisions.
Every report i've seen on this is saying the kid was about to be arrested for sobig. One of them opened with a headline about blaster, then started showing screenshots about sobig and talking about spam.
In other news, whooping cranes have been spotted flying out of tom brokaw's ass.
3+ years ago I went out on a limb. The bosses expected me to use an expensive solaris/sparc server and scsi, but I saved them a bundle with lintel/3ware.
About 3 months after the server went into production, the controller started disabling drives and going into degraded mode. At one point, something happened (fat fingers maybe) and the whole array disappeared. I was really sweating because IS hadn't been backing it up properly.
3ware support was great. They recovered the metadata for the raid and cross-shipped me a replacement controller. The new controller acted the same, but in the end the problem turned out to be bad ide cables. The company that built the server hadn't used 3ware's included cables; they had in fact charged us extra for "upgraded cables".
The performance was great (raid 10). Escalades look like a scsi controller to linux, and I'm not sure, but i think the newer versions implement command queueing.
"People keep running the damned attachment like morons."
Why do windows techies insist on packaging things as executables?
For example, I downloaded an addon track for a Windows racing game I like. It's a single.trk file. But instead of just telling me to put the file in my "tracks" folder, they package it as a damned.exe install "wizard" that's so stupid, it has to ask the user where to install the file.
Not only that, but they add another layer of bs to the mix by putting the.exe in a zip file. So naturally, some people have to go install winzip, probably break someone's eula, run yet another POS installer.
Of course users click anything that says OK. That's what you do with windows. Click, click, crash, reboot, click, click, reinstall. It's just the way windows is done, sucky.
Japanese PM Koizumi introduced Asimo to the president of the US. Upon hearing the word "Bush-san" the robot promptly puked its guts out all over the world's most powerful man.
Slashdot Mirror
Challenger - If the crew had been in a smaller craft on top, an explosion in a lower stage could have been escapable if the smaller craft could separate and land.
That sounds like a relatively small improvement in the odds. If two pounds of foam can make such a big hole, imagine what a chunk of metal shrapnel from an exploding rocket would do.
Columbia - If the craft that was to be used for re-entry had been on top, it would never have had the risk of freaking insulation (two pounds!? still drives me nuts) falling onto and damaging its heat shielding.
I agree with that, but ST-107 wouldn't have been at risk of flying foam if NASA had addressed the problem. They should have grounded it until they found a fix. The stuff isn't supposed to come off, and they ignored the fact that it does.
Disregarding the two catastrophes which were attributed to mismanagement, the system is 105 for 105.
Dell tech support was great... when they were selling UNIX. I had never touched *nix and their sales dept promised me i'd get the box with the OS installed. Naturally it arrived with only DOS installed and UNIX on floppies. I made those poor tech support bastards walk me thru every step including a kernel recompile.
dell: ok now edit the blah file
me: what's the command for edit?
them: oh shit
Yeah but...
Challenger blew up when management ignored the facts about the srb o-rings in cold weather. The srbs leaked and burned thru the external tank. I can't see how having the bird on top would have helped.
Columbia was doomed because they ignored the warning signs of past missions. They knew that foam had damaged the orbiter on previous missions. It's too bad that 7 people had to die, and we had to lose an orbiter to wake them up.
IMO, the design is not the cause of these failures. It might be fair to say "it's always grounded because the design sucks and they can never get an all systems go", but the designers don't make the launch decisions.
ok, now i've found one ;-)
I was getting a little irked at the spreading misconception that people couldn't get to some of the big sites like rpmfind.
Yeah, the statement is returned, but you can click thru it. The site is not "shut down".
wrong
+5 informative?
Go to the gimp.org and click where it says "proceed to the site".
It's not closed. On the warning page there's a link "click here to enter this site". Try putting your mouse over the link and clicking on it.
Windows and Linux users should click with button-1. Mac users should be able to figure out for themselves which button to use.
and don't forget clippy.
I've been to several sites with the protest page, but they all had a "click here to enter" link.
springtime of your life
got in way over your head
now squeal like a pig
incarcerated? how about incinerated? burn baby burn!
Every report i've seen on this is saying the kid was about to be arrested for sobig. One of them opened with a headline about blaster, then started showing screenshots about sobig and talking about spam.
In other news, whooping cranes have been spotted flying out of tom brokaw's ass.
Me too.
3+ years ago I went out on a limb. The bosses expected me to use an expensive solaris/sparc server and scsi, but I saved them a bundle with lintel/3ware.
About 3 months after the server went into production, the controller started disabling drives and going into degraded mode. At one point, something happened (fat fingers maybe) and the whole array disappeared. I was really sweating because IS hadn't been backing it up properly.
3ware support was great. They recovered the metadata for the raid and cross-shipped me a replacement controller. The new controller acted the same, but in the end the problem turned out to be bad ide cables. The company that built the server hadn't used 3ware's included cables; they had in fact charged us extra for "upgraded cables".
The performance was great (raid 10). Escalades look like a scsi controller to linux, and I'm not sure, but i think the newer versions implement command queueing.
digilantism
"I haven't seen this sucker in action"
Stealth pun.
War Operations Play and Response
Imagine a cluster of IMSAI's.
I doubt it could even turn Boston harbor and the Charles river into water.
That's when her head starts spinning around like Linda Blair.
"People keep running the damned attachment like morons."
.trk file. But instead of just telling me to put the file in my "tracks" folder, they package it as a damned .exe install "wizard" that's so stupid, it has to ask the user where to install the file.
.exe in a zip file. So naturally, some people have to go install winzip, probably break someone's eula, run yet another POS installer.
Why do windows techies insist on packaging things as executables?
For example, I downloaded an addon track for a Windows racing game I like. It's a single
Not only that, but they add another layer of bs to the mix by putting the
Of course users click anything that says OK. That's what you do with windows. Click, click, crash, reboot, click, click, reinstall. It's just the way windows is done, sucky.
lemme do some cypherin...
Twofaces gozinta 52 cards 26 times. That ain't so many. Let's go a feuding... it's the Redhatfields aginst the McBrides.
I'll take that with a grain of rice.
[DUCKS]
Are you saying that Bush is a robot?
"Dick Cheney?"
No, Bush. Cheney had a massive coronary on the spot.
Japanese PM Koizumi introduced Asimo to the president of the US. Upon hearing the word "Bush-san" the robot promptly puked its guts out all over the world's most powerful man.