Ah... I've been waiting for an article just like this to ease that "I should drink less coffee" feeling. Now everytime I have such a foolish thought, I can remind myself that coffee is good for me, and I would be hurting myself if I didn't drink 2.5 gallons a day.
Actually, I find updating our linux servers over a zillion times easier than Microsoft updates. With a linux update I am confident that it is going to work and do what it says. I don't have that faith in microsoft products. I have been screwed WAY to many times with microsoft "fixes" (read breaks). The funny thing is that I use linux 98% of the time, and I've still been screwed by windows more times than with linux.
Deep sleep has never been a problem for me. Ask my wife. OR my employers. Can I record my brainwaves when I am wide awake, and put them on my alarm clock?
Heh... If they don't do anything about the spam that comes from those domains, the government won't have to do anything. The rest of the world with firewall them off.
I am in the inverse position. You forgot one HUGE factor. dollars X hours you waste building/repairing/studying them etc... There are about 80 systems where I work, and it is a royal pain. Rolling your own systems looks good at first but actual cost labor cost goes through the roof.
What they SHOULD do is look at the percentage that were FIXED. Linux development rolls out more stuff each year, so naturally, there are more security notices. But they get fixed. Micro$oft drops a golden turd every few years, calls it an operating system, and pays people to keep quiet about the exploits.
Studies have shown that the human mind can re-allocate sections for other uses... perhaps instead of isolating the specific centers that perform these functions, they should find the general area and work on 'training the brain' It would be a hell of a lot easier and I bet the advances would move faster as well.
But I am just an idiot with a computer. No medical training here other than Discovery and TLC.
I am in the same boat. I am pretty successful now at 23, but I never finished college. On the surface, this would not seem to be a problem. I am married and buying a house, and all seems well... however, in the back of my mind, I remember recessions past when the labor market was tight. Between two qualified candidates, the one with the degree always wins. I know I am going back. At least for something. It doesn't even matter so much what your degree is in. Just that you have it. If you really want to continue upwards, consider (gasp!) a business degree. If you already know CS, learn something new. Make yourself more versatile. You never know, they may just give you your very own flock of geeks to govern or turn into a primitive society as you see fit.
Well please forgive me then. In your first post you certainly made it sound like you were pointing the finger at Qwest DSL customers. The attacks can come from any computer on the net. running IIS. The whole confusion over the IIS issue vs. the DSL router issue has caused me no end of grief... most of it coming from my own users. Sorry bout that.
It wasn't Qwest DSL routers that attacked your system dumbass. It was unpatched IIS servers that did. DSL routers only get kicked offline when Code Red tries to infect them the way they would an NT IIS server. And that was even a side effect of the virus.
Do your homework.
again I feel I must state that IIS didn't have ANYTHING to do with the outage. IIS only propagates the virus. Certain Cisco DSL routers (specifically the pre-cbos-2.4 types) get knocked offline due to the way the virus tries to infect other hosts. You could have Commodore64 plugged into the other end of a suceptible router, and you would still be affected by the Qwest outage.
IIS and Cisco's DSL problem have nothing to do with each other except that they are both affected by Code Red. You only need one or the other to get hit. IIS servers are the worst player, since the propagate the virus at an incredible rate. Pre CBOS 2.4 Cisco Routers get nailed by the way the virus tries to infect other machines.
Also, I happen to be a resedential Qwest DSL customer as well, and I made DAMN sure there was nothing in the language of the contract that restricted me from running a webserver, mailserver, or any other server I might get a hankerin' for. So no, you can't charge people for abusing thier lines.
I will grant that they were probably pretty busy during all this so I could understand the 2 and 3 hour wait times. I wasn't really expecting techs to be able to help me anyway. ("poorly trained" was a really NICE way of putting it.)
I just don't think that Qwest was proactive enough in coming to a solution. They tossed out "patches" and "quick-fixes" without really testing them. I just think that the whole issue could have been resolved much faster than it was. They *should* be handing out refunds, but they never will. I for one am looking into new ISP alternatives. This is not the first time my company has gotten screwed by Qwest.
Slashdot Mirror
Ah... I've been waiting for an article just like this to ease that "I should drink less coffee" feeling. Now everytime I have such a foolish thought, I can remind myself that coffee is good for me, and I would be hurting myself if I didn't drink 2.5 gallons a day.
Actually, I find updating our linux servers over a zillion times easier than Microsoft updates. With a linux update I am confident that it is going to work and do what it says. I don't have that faith in microsoft products. I have been screwed WAY to many times with microsoft "fixes" (read breaks). The funny thing is that I use linux 98% of the time, and I've still been screwed by windows more times than with linux.
Won't that make flying a bit of a nightmare? Last September, I wasn't even allowed to bring my Zippo aboard. I doubt I'll ever see that lighter again.
except that yours was't first. :P
Because the MPAA/RIAA lawyers are going to have a hayday with this.
What, choking the life out of e-mail isn't good enough? Now we have to make the entire web unusable as well?
Don't they realize how many people go out of their way to NOT buy things that have annoying advertising?
Deep sleep has never been a problem for me. Ask my wife. OR my employers. Can I record my brainwaves when I am wide awake, and put them on my alarm clock?
Heh... If they don't do anything about the spam that comes from those domains, the government won't have to do anything. The rest of the world with firewall them off.
I am in the inverse position. You forgot one HUGE factor. dollars X hours you waste building/repairing/studying them etc...
There are about 80 systems where I work, and it is a royal pain. Rolling your own systems looks good at first but actual cost labor cost goes through the roof.
Vikings were here about 400 years before that!
What they SHOULD do is look at the percentage that were FIXED. Linux development rolls out more stuff each year, so naturally, there are more security notices. But they get fixed. Micro$oft drops a golden turd every few years, calls it an operating system, and pays people to keep quiet about the exploits.
Studies have shown that the human mind can re-allocate sections for other uses... perhaps instead of isolating the specific centers that perform these functions, they should find the general area and work on 'training the brain' It would be a hell of a lot easier and I bet the advances would move faster as well.
But I am just an idiot with a computer. No medical training here other than Discovery and TLC.
Does this remind anyone of the very first 2 hour episode of Lexx?
I am in the same boat. I am pretty successful now at 23, but I never finished college. On the surface, this would not seem to be a problem. I am married and buying a house, and all seems well... however, in the back of my mind, I remember recessions past when the labor market was tight. Between two qualified candidates, the one with the degree always wins. I know I am going back. At least for something. It doesn't even matter so much what your degree is in. Just that you have it. If you really want to continue upwards, consider (gasp!) a business degree. If you already know CS, learn something new. Make yourself more versatile. You never know, they may just give you your very own flock of geeks to govern or turn into a primitive society as you see fit.
Well please forgive me then. In your first post you certainly made it sound like you were pointing the finger at Qwest DSL customers. The attacks can come from any computer on the net. running IIS. The whole confusion over the IIS issue vs. the DSL router issue has caused me no end of grief... most of it coming from my own users. Sorry bout that.
It wasn't Qwest DSL routers that attacked your system dumbass. It was unpatched IIS servers that did. DSL routers only get kicked offline when Code Red tries to infect them the way they would an NT IIS server. And that was even a side effect of the virus.
Do your homework.
Dude... Nobody is dying over this.
again I feel I must state that IIS didn't have ANYTHING to do with the outage. IIS only propagates the virus. Certain Cisco DSL routers (specifically the pre-cbos-2.4 types) get knocked offline due to the way the virus tries to infect other hosts. You could have Commodore64 plugged into the other end of a suceptible router, and you would still be affected by the Qwest outage.
IIS and Cisco's DSL problem have nothing to do with each other except that they are both affected by Code Red. You only need one or the other to get hit. IIS servers are the worst player, since the propagate the virus at an incredible rate. Pre CBOS 2.4 Cisco Routers get nailed by the way the virus tries to infect other machines.
Also, I happen to be a resedential Qwest DSL customer as well, and I made DAMN sure there was nothing in the language of the contract that restricted me from running a webserver, mailserver, or any other server I might get a hankerin' for. So no, you can't charge people for abusing thier lines.
I will grant that they were probably pretty busy during all this so I could understand the 2 and 3 hour wait times. I wasn't really expecting techs to be able to help me anyway. ("poorly trained" was a really NICE way of putting it.)
I just don't think that Qwest was proactive enough in coming to a solution. They tossed out "patches" and "quick-fixes" without really testing them. I just think that the whole issue could have been resolved much faster than it was. They *should* be handing out refunds, but they never will. I for one am looking into new ISP alternatives. This is not the first time my company has gotten screwed by Qwest.