I just conducted an extensive poll here in Canada. 100% of Canadians surveyed believe Pee Wee Herman would not be a good president of the United States.
You know what you must do! YOUR PATRIOTIC DUTY IS CLEAR!
If you want to play hardball, let them approve silly stuff. Make sure there is a paper trail of who approved what, and make sure they take the heat for whatever problems are caused.
You need the support of your own management, and a evil+political person to prepare the very thorough document describing all the problems caused by $stupid_app. Don't be afraid to estimate costs incurred by the incident.
If management finds their own nuts in the wringer because of a dumb decision, they might not sign off so quickly next time.
(If you don't have the support of your own management, of course you're fucked anyway.)
The companies with hard-ass policies didn't get that way overnight, you need to demonstrate the problem in a way that even senior management can understand.
they'll come up with all kinds of programs that are a business necessity, and get them approved by management, just because they're pissed at being locked down.
It depends on who gets to approve software.
If their management gets to approve software, you're already fucked, and no mere policy will save you.
If your management has to sign off on new software, you've got a faint hope of being able to manage the network.
He isn't running it on your production server, he is running it on his production server.
<SARCASM>Thanks for the clarification.<SARCASM>
If he can "wander around" and install stuff on a server he isn't administering, then it isn't he who should get fired but the server administrator.
IIRC seti@home is just an executable + a config file, the sort of thing that could be simply run from your home directory. Now the admin could mount/home NOEXEC or something, but there are a million legititate reasons to let your programmers run stuff from/home.
Sure, sacking the guy is way out of proportion to what he did. Either that was the last in a string of stupid behaviour, or someone was looking for an excuse to fire him.
But think about this for a minute.
Imagine the most critical server at your job. Should people install no-essential software on it that "probably won't interfere"? Is it good enough that "a lot of people have installed this software, and no-one is complaining"?
The use of the latter kind of software use warrants at most a warning.
I'm sure there's a history there, and someone seized on this as an excuse to fire the guy.
But that doesn't mean it is OK to wander around installing extraneous junk on production equipment.
Please prove to me that seti@home will never interfere with the other software on my production server.
Oh wait, you can't prove that? I therefore conclude we shouldn't run seti@home on my production server. Life is already complicated enough, you don't need to add stupid shit into the mix.
I'm no mainframe expert, but Google shows people used to do this. Heck, there's an announcement about a time-change related system outage dated this spring!
Mainframes are quality kit, but everything has limitations.
A lot of mainframe shops used to IPL (reboot) their big iron every year for daylight savings time - I'm told the s/w got very confused when the time went backwards, so it was easier to just shut down for an hour.
Can any dinosaur herders in the crowd provide details (or maybe refute this info) ?
I'm not saying I like the way the system was put together. That setup was deeply flawed, and should never have been implemented like that.
But the system was already in place, flaws and all.
They had a system with known limitations. They were crazy not to apply whatever bandaids were required to keep the thing tottering along (as well as possible).
So in other words the life of airplane passengers is depending on the fact if a computer is rebooted manually or not. Thank god nothing really bad happened during this radio outage, otherwise some smartass would have blamed it on the tech that forgot to reboot.
Let's do a little thought experiment:
So in other words the life of airplane passengers is depending on the fact
that technicians regularly change the oil in the airplane's engine or not. Thank god nothing really bad happened during this problem, otherwise some smartass would have blamed it on the tech that forgot to change the oil.
Sure, it sucks that mission-critical kit needs to be rebooted. But everyone knew about the constraints, there's no excuse for not doing required maintenance that everyone knew about.
If paper voting can work in dense areas like Toronto/Vancouver, it can certainly work for West Bumfuck North Dakota.
According to this site, Toronto has the second-highest population density in North America. Montreal is #7.
I think the above stats are a little skewed, they lump NY and Newark together. I'm pretty sure that New York would be the most packed place in NA, but what do I know?
> Don't you really mean for servers that have to be configured by GUI > clients on the system console? Aren't we talking primarily Windows > servers, then?
Well, yeah.
This is a discussion about IE. And Win32 software is much more likely to have documentation provided in some sort of bastardized IE-only HTML.
Also, a Win32 admin is much more likely to be physically sitting in the server room.
Heh. Check it out, unless the disclaimer scares you off:
These products are down-revision products that may have various bugs, Y2000, and possibly security issues associated with them. Sun in no way recommends these products be used in a live, production environment. Any use of product on this page is at the sole discretion of the developer and Sun assumes no responsiblity for any resulting problems.
Slashdot Mirror
> There is not enough money in a $50 atx case to allow for any thermal
> design or testing.
I don't know if I should laugh or cry.
You know what you must do! YOUR PATRIOTIC DUTY IS CLEAR!
Everyone should check out that site for the artwork, even if they don't care about the product.
If you want to play hardball, let them approve silly stuff. Make sure there is a paper trail of who approved what, and make sure they take the heat for whatever problems are caused.
You need the support of your own management, and a evil+political person to prepare the very thorough document describing all the problems caused by $stupid_app. Don't be afraid to estimate costs incurred by the incident.
If management finds their own nuts in the wringer because of a dumb decision, they might not sign off so quickly next time.
(If you don't have the support of your own management, of course you're fucked anyway.)
The companies with hard-ass policies didn't get that way overnight, you need to demonstrate the problem in a way that even senior management can understand.
It depends on who gets to approve software.
If their management gets to approve software, you're already fucked, and no mere policy will save you.
If your management has to sign off on new software, you've got a faint hope of being able to manage the network.
No-one said you can win them all...
Also, if you can't figure out an ftp install, you might be barking up the wrong tree.
> In corporate world you don't need to convince much - just fire them.
So, how long have you been in the workforce, Skippy?
Not everyone lives in your neighbourhood.
Those prices vary wildly in different parts of the world.
Sure, sacking the guy is way out of proportion to what he did. Either that was the last in a string of stupid behaviour, or someone was looking for an excuse to fire him.
But think about this for a minute.
Imagine the most critical server at your job. Should people install no-essential software on it that "probably won't interfere"? Is it good enough that "a lot of people have installed this software, and no-one is complaining"?
Hell no!
But that doesn't mean it is OK to wander around installing extraneous junk on production equipment.
Please prove to me that seti@home will never interfere with the other software on my production server.
Oh wait, you can't prove that? I therefore conclude we shouldn't run seti@home on my production server. Life is already complicated enough, you don't need to add stupid shit into the mix.
> Maybe the best thing to do is just get in yourself and do a format c:. ...
> I work in the network security industry
With friends like that, who needs enemies?
Mainframes are quality kit, but everything has limitations.
You'd be surprised.
A lot of mainframe shops used to IPL (reboot) their big iron every year for daylight savings time - I'm told the s/w got very confused when the time went backwards, so it was easier to just shut down for an hour.
Can any dinosaur herders in the crowd provide details (or maybe refute this info) ?
But the system was already in place, flaws and all.
They had a system with known limitations. They were crazy not to apply whatever bandaids were required to keep the thing tottering along (as well as possible).
I was actually replying to the AC...
Aha, a reasonable explanation. Thank you, sir!
I browse in light mode, so I haven't seen the icons in years. The games icon is sort of cute, eh?
I clicked the little checkbox that is supposed to prevent me from seeing all this Star Wars trivia.
Why am I still seeing these stories?
How much does it cost to incorporate in your jurisdiction?
In these parts, I think it costs a few hundred bucks, maybe more.
A previous poster has an excellent reply to your question.
If paper voting can work in dense areas like Toronto/Vancouver, it can certainly work for West Bumfuck North Dakota.
According to this site, Toronto has the second-highest population density in North America. Montreal is #7.
I think the above stats are a little skewed, they lump NY and Newark together. I'm pretty sure that New York would be the most packed place in NA, but what do I know?
> Don't you really mean for servers that have to be configured by GUI
> clients on the system console? Aren't we talking primarily Windows
> servers, then?
Well, yeah.
This is a discussion about IE. And Win32 software is much more likely to have documentation provided in some sort of bastardized IE-only HTML.
Also, a Win32 admin is much more likely to be physically sitting in the server room.