Or you could just run `ldconfig` to clean the library cache, go down to single user mode, and then back into multiuser mode. Everything but init restarts, and init can already restart itself if it detects a change.
What part of ``don't admit to knowing anything'' is confusing you? If you tell them that you know that they're an officer, they'll know that you know. Now they have the upper hand!
Yes, yes, yes. Even if he was not found guilty, the failure to document this stuff (even for the more innocent reason of getting hit by a bus) should make this guy unemployable in IT for the rest of his life.
I'd call him unethical for not ensuring that the passwords were documented. What if he got hit by a bus and died? Then his replacements would be toast.
Agree. Even if he wasn't guilty, the owners of the equipment need enough information to keep running if he gets hit by a bus, and any ethical admin would be quite willing to oblige (our typically large egos imply wanting others to view our work positively).
Even if he wasn't convicted, he should not have ever gotten a job in IT again.
It was set up so that a password reset would conveniently wipe the firmware and settings. A perfectly good and quite complex configuration down the drain. And that would mean downtime.
Except that the contract of Childs said that he was not allowed to tell anyone but the mayor. They were asking him over a teleconference, where he didn't know who was on the other side (except that the mayor was not). He was thinking that he would be liable if he did give over the password.
Of course, California's also the state where you can be ticketed at the same time for impeding traffic and speeding. Yes, going too slowly and going too quickly. At the same time.
No problem for me. Even though I am a computer science student, I take notes on paper. Then I transcribe it into my personal wiki, getting twice the exposure to the material.
He gave the password to the only person allowed by his contract, the mayor.
He did not give the password over the speakerphone to a room full of other people, including quite possibly some people to whom he was not allowed to give the password. This was the incident that got him arrested.
A supervisor should have had the password all along. If he was innocently hit by a bus, then the city's network would really be hurting. IT people need to learn that refusal to document does not make job security.
Agree. Even if they had the right to the passwords (and any admin worth his salt would ensure that someone else had them, in case he gets hit by a bus:
They demanded them over speakerphone. There's no way that he could verify that the people on the other end of the line were all able to have that password.
He is not liable to tell them how to let them in. If I don't document something, they have no ability to come back and make me do it. Their only recourse is not giving me a good reference for my next attempt at a job.
Slashdot Mirror
Or you could just run `ldconfig` to clean the library cache, go down to single user mode, and then back into multiuser mode. Everything but init restarts, and init can already restart itself if it detects a change.
Fixed that for you.
What part of ``don't admit to knowing anything'' is confusing you? If you tell them that you know that they're an officer, they'll know that you know. Now they have the upper hand!
Learn Slackware and you learn Linux. Learn Gentoo and you are Linux.
I am Boris Johnson...and I am HUNGRY! HUNGRY!
Chrome's AdBlock still downloads the offending components; it just hides them from the user.
KVM over IP is your friend.
Or just the fact that he didn't make an I-got-hit-by-a-bus contingency plan.
Yes, yes, yes. Even if he was not found guilty, the failure to document this stuff (even for the more innocent reason of getting hit by a bus) should make this guy unemployable in IT for the rest of his life.
I'd call him unethical for not ensuring that the passwords were documented. What if he got hit by a bus and died? Then his replacements would be toast.
Even if he wasn't convicted, he should not have ever gotten a job in IT again.
It was set up so that a password reset would conveniently wipe the firmware and settings. A perfectly good and quite complex configuration down the drain. And that would mean downtime.
The soldier's choice: disobey and take a bullet from your commander now, or follow the order and stretch rope later.
Except that the contract of Childs said that he was not allowed to tell anyone but the mayor. They were asking him over a teleconference, where he didn't know who was on the other side (except that the mayor was not). He was thinking that he would be liable if he did give over the password.
That only works if you can convince the stupid people too.
Of course, California's also the state where you can be ticketed at the same time for impeding traffic and speeding. Yes, going too slowly and going too quickly. At the same time.
Actually most won't activate until you're pushing the pedal yourself to around 20 mph or so.
Then they both confess, and you're exactly where you are now.
No problem for me. Even though I am a computer science student, I take notes on paper. Then I transcribe it into my personal wiki, getting twice the exposure to the material.
Epic win: he also put the passwords in public court records, so the new IT staff had to scramble.
And just you watch the US shoot down a Canadian passenger jet. That's one way to make enemies of lots of countries, very quickly.
Actually their first work was the Declaration of Independence, but your point still stands.
These are from Wikipedia.