You need to add some more stuff into your figures.
You can't get security or bug updates after 12 months on plain Red Hat anymore.
So also add in the cost of your time, packaging up all those fixes into RPMs (including the time learning how to make proper RPMs), and either installing them by hand onto all of your systems, or setting up your own apt-rpm repository for them.
For me and many others who have the knowledge to support RH, it's not a question of tech support, it's a question of patches and fixes.
I think the main issue is that we want to run Red Hat, but even with extra geeks, it's not going to help the security patch issue. Phone or email support isn't a big deal for people that already know how to support Linux in house.
After 12 months, you either upgrade, to the new buggy unstable version, or you stare at bugtraq all day and hope that nothing you are running comes up with a new security hole.
That's really not an option. RH is screwing up big time.
I agree, I think Red Hat is really leaving small/medium businesses out in the cold with their new policies.
One example, I set up a server/firewall for a small business as a contract job on the side. It runs all their stuff, web, email, etc. They really don't have a need for more than one server.
Last year when I set it up, I told them it would be good for at least three years. I don't like it that Red Hat made a liar out of me.
At my real job, we have more than a dozen Red Hat servers, and I'm stuck in the same dilemma. We can't afford to destabilize servers by putting essentially beta software on them, that the 12 month EOL requires. I used to let RH releases age about 3 or 4 months to get the major bugs out before I even considered using them in production.
So now I'm faced with either spending tons more time patching the servers by hand (even though we pay for RHN), or spending tons more money, buying RHEL which would cost at least 10 times more than the ~$1000 a year we spend on RHN now.
I really hope something gives on this situation. Red Hat better think twice before they alienate small to medium businesses. I don't need support. I do need updates. I do need more than 12 months before EOL.
What? You mean 1000MW dummy load resistors are hard to find?:)
Thanks for the explanation. I guess you don't want to lower the rods partially, because that might risk them getting stuck that way? (partially educated guess)
You have a really cool job. Even if you never make it to engineering there, you could always just write a book about your job, and it would probably sell very well.
I'm not really anti-nuke, I just asked because I hadn't seen anything in the news about it since the original story. You can see from my site, I do have concerns about nuclear things, but my research has taught me more than anything that radiation is not as dangerous as some make it out to be (like that old saw about plutonium being the most potent poison on earth).
What ever happened with that pile of powder they found under that reactor? Are they going to have to retrofit all the plants to fix the problem with the stuff eating through the sensor holes?
Wouldn't it be possible to just let most of the turbines freewheel, leaving the reactor running at nearly full output, rather than dropping the control rods?
I know little about the details of a nuke plant, I'm just curious.
I just remember taking a first aid class years ago, and we spent a good chunk of the time just talking about liability. Maybe that was before the laws were passed widely.
The problem is the same as phone deregulation, as long as you only have one wire coming into your house, you still have to pay that company, one way or another.
I'm generally libertarian, but I'm in favor of something someone else posted on Slashdot a while back. The local government should just own the natural monopoly on the last mile, and the power/phone companies should be given non-descriminatory access to the system, free to compete with one another.
The way it stands now, the incumbents hold all the cards on these "deregulation efforts". It's not practical to try to run multiple wires (or pipes for water) to every house for this stuff.
the more common case was photoshopping a kid's head onto an adult's body
If I recall correctly, that part of CPPA wasn't challenged, an "identifiable" minor depicted in a sexual situation (even if simulated) is still illegal.
You couldn't make "Mary Kate and Ashley's *big* adventure", even if it was completely simulated, since there would be identifiable minors involved.
Anyway, this is from memory. Talk to a lawyer if you really want to know the details.
I don't know about that, but I do know someone was convicted for photoshopping a minor's head onto a porn actress's body.
I know they tried to pass a law about anyone "appearing to be a minor", but I think that either didn't pass or was struck down when the supreme court ruled that "simulated kiddy porn" is legal.
What gets me is that the insanity of our current "child protection" laws seems to be a totally taboo subject.
It's really time that attitudes need to change, and people need to realize that just because someone wants reform of child protection laws, doesn't mean they are some sort of child molestor.
The problem is especially rampant in legislative bodies. Virginia just could not get the bill to repeal our oral and anal sex felony laws passed, because every time someone introduced the bill, some other legislator would talk about how it would make child molesting and incest legal, and no one dared vote for it.
At least the supreme court made the law irrelevant now.
2kw is very close to the 20 amps max on 12 guage wire at 110 volts in the US. It would at the very least need a circuit all to itself. Some older houses use 15 amp circuits on 14 guage wire, but in new construction mostly lighting only circuits use 15 amp lines.
Or in 1990 when AT&T had a cascading phone failure that took out phone service for a big chunk. Or in 1996, when power for much of the West Coast went out for nine hours after a tree branch fell on some power lines, causing a cascade failure.
We've chained up high end UPSs before. High end UPS's have a "bypass" mode which is designed to be used when you plug it into another UPS. It's only the cheapo ones that you shouldn't plug into each other.
This is, however, a different matter than plugging a UPS into itself, which could damage any UPS.
I've not tried this, but I've seen specific warnings against it in the manual for whole house UPSs.
Assuming the normal arrangement of a standby UPS rather than one that runs the inverter all the time, this is what I think would happen.
The UPS is unplugged, the inverter is on and unloaded. You plug it into itself, it sees the voltage coming in and assumes the power is back on. It will sync to that sine wave (assuming it isn't an el-cheapo), and then turn off. Then it will see that the power is off, and turn back on. Rinse, repeat.
All this would happen every few milliseconds. Would be very stressful for the components most likely. Something might burn out pretty fast with it oscillating that quickly.
Anyway, like I said, I never tried this, but this seems like the most likely outcome. Someone should try it (outside!) with a UPS you don't care about anymore. Post results.:)
Ordinary people are directing traffic as well, and you know what? They're pretty good at it
Those people should get the "Huge Balls Award". I don't even want to think about the potential lawsuits should one of them fuck up and cause an accident. Not to mention the balls it takes just to stand in the middle of a New York intersection during a blackout.:)
It was fixed months ago. It was the local root ptract exploit.
The only reason they got cracked was because they allowed local shell accounts, and due to questionable reporting practices, an exploit was released before linux kernel people had a chance to fix it.
Slashdot Mirror
You need to add some more stuff into your figures.
You can't get security or bug updates after 12 months on plain Red Hat anymore.
So also add in the cost of your time, packaging up all those fixes into RPMs (including the time learning how to make proper RPMs), and either installing them by hand onto all of your systems, or setting up your own apt-rpm repository for them.
For me and many others who have the knowledge to support RH, it's not a question of tech support, it's a question of patches and fixes.
I think the main issue is that we want to run Red Hat, but even with extra geeks, it's not going to help the security patch issue. Phone or email support isn't a big deal for people that already know how to support Linux in house.
After 12 months, you either upgrade, to the new buggy unstable version, or you stare at bugtraq all day and hope that nothing you are running comes up with a new security hole.
That's really not an option. RH is screwing up big time.
I agree, I think Red Hat is really leaving small/medium businesses out in the cold with their new policies.
One example, I set up a server/firewall for a small business as a contract job on the side. It runs all their stuff, web, email, etc. They really don't have a need for more than one server.
Last year when I set it up, I told them it would be good for at least three years. I don't like it that Red Hat made a liar out of me.
At my real job, we have more than a dozen Red Hat servers, and I'm stuck in the same dilemma. We can't afford to destabilize servers by putting essentially beta software on them, that the 12 month EOL requires. I used to let RH releases age about 3 or 4 months to get the major bugs out before I even considered using them in production.
So now I'm faced with either spending tons more time patching the servers by hand (even though we pay for RHN), or spending tons more money, buying RHEL which would cost at least 10 times more than the ~$1000 a year we spend on RHN now.
I really hope something gives on this situation. Red Hat better think twice before they alienate small to medium businesses. I don't need support. I do need updates. I do need more than 12 months before EOL.
What? You mean 1000MW dummy load resistors are hard to find? :)
Thanks for the explanation. I guess you don't want to lower the rods partially, because that might risk them getting stuck that way? (partially educated guess)
You have a really cool job. Even if you never make it to engineering there, you could always just write a book about your job, and it would probably sell very well.
I'm not really anti-nuke, I just asked because I hadn't seen anything in the news about it since the original story. You can see from my site, I do have concerns about nuclear things, but my research has taught me more than anything that radiation is not as dangerous as some make it out to be (like that old saw about plutonium being the most potent poison on earth).
Actually, someone came back from the future and plugged in a 1000 jigawatt hair dryer.
What ever happened with that pile of powder they found under that reactor? Are they going to have to retrofit all the plants to fix the problem with the stuff eating through the sensor holes?
You're just boiling water though, right?
Wouldn't it be possible to just let most of the turbines freewheel, leaving the reactor running at nearly full output, rather than dropping the control rods?
I know little about the details of a nuke plant, I'm just curious.
That's cool.
I just remember taking a first aid class years ago, and we spent a good chunk of the time just talking about liability. Maybe that was before the laws were passed widely.
$800 for 10 watts, and you say you can power a house on 10,000 dollars?
Yeah, maybe if your house has a single light bulb, and that's it.
X follows Y, therefore X caused Y!
The problem is the same as phone deregulation, as long as you only have one wire coming into your house, you still have to pay that company, one way or another.
I'm generally libertarian, but I'm in favor of something someone else posted on Slashdot a while back. The local government should just own the natural monopoly on the last mile, and the power/phone companies should be given non-descriminatory access to the system, free to compete with one another.
The way it stands now, the incumbents hold all the cards on these "deregulation efforts". It's not practical to try to run multiple wires (or pipes for water) to every house for this stuff.
the more common case was photoshopping a kid's head onto an adult's body
If I recall correctly, that part of CPPA wasn't challenged, an "identifiable" minor depicted in a sexual situation (even if simulated) is still illegal.
You couldn't make "Mary Kate and Ashley's *big* adventure", even if it was completely simulated, since there would be identifiable minors involved.
Anyway, this is from memory. Talk to a lawyer if you really want to know the details.
I don't know about that, but I do know someone was convicted for photoshopping a minor's head onto a porn actress's body.
I know they tried to pass a law about anyone "appearing to be a minor", but I think that either didn't pass or was struck down when the supreme court ruled that "simulated kiddy porn" is legal.
What gets me is that the insanity of our current "child protection" laws seems to be a totally taboo subject.
It's really time that attitudes need to change, and people need to realize that just because someone wants reform of child protection laws, doesn't mean they are some sort of child molestor.
The problem is especially rampant in legislative bodies. Virginia just could not get the bill to repeal our oral and anal sex felony laws passed, because every time someone introduced the bill, some other legislator would talk about how it would make child molesting and incest legal, and no one dared vote for it.
At least the supreme court made the law irrelevant now.
2kw is very close to the 20 amps max on 12 guage wire at 110 volts in the US. It would at the very least need a circuit all to itself. Some older houses use 15 amp circuits on 14 guage wire, but in new construction mostly lighting only circuits use 15 amp lines.
Or in 1990 when AT&T had a cascading phone failure that took out phone service for a big chunk. Or in 1996, when power for much of the West Coast went out for nine hours after a tree branch fell on some power lines, causing a cascade failure.
I read about you!
You run 24/7 generators? Isn't that kinda expensive? I'd think you'd still want UPSs in case of generator failure, right?
We've chained up high end UPSs before. High end UPS's have a "bypass" mode which is designed to be used when you plug it into another UPS. It's only the cheapo ones that you shouldn't plug into each other.
This is, however, a different matter than plugging a UPS into itself, which could damage any UPS.
Bad, bad things.
:)
I've not tried this, but I've seen specific warnings against it in the manual for whole house UPSs.
Assuming the normal arrangement of a standby UPS rather than one that runs the inverter all the time, this is what I think would happen.
The UPS is unplugged, the inverter is on and unloaded. You plug it into itself, it sees the voltage coming in and assumes the power is back on. It will sync to that sine wave (assuming it isn't an el-cheapo), and then turn off. Then it will see that the power is off, and turn back on. Rinse, repeat.
All this would happen every few milliseconds. Would be very stressful for the components most likely. Something might burn out pretty fast with it oscillating that quickly.
Anyway, like I said, I never tried this, but this seems like the most likely outcome. Someone should try it (outside!) with a UPS you don't care about anymore. Post results.
Ordinary people are directing traffic as well, and you know what? They're pretty good at it
:)
Those people should get the "Huge Balls Award". I don't even want to think about the potential lawsuits should one of them fuck up and cause an accident. Not to mention the balls it takes just to stand in the middle of a New York intersection during a blackout.
He also said that there was no grid overload, it was just being shut down for regular maintenance.
I hear Iraq is looking for a new information minister.
Actually it was Linux. A local-only kernel exploit.
It was fixed months ago. It was the local root ptract exploit.
The only reason they got cracked was because they allowed local shell accounts, and due to questionable reporting practices, an exploit was released before linux kernel people had a chance to fix it.