The white rabbit stuff is wonderful, commentary and audio-only tracks are great, and the movie plays and searches nice and fast. For me, this is one of the best DVD's as far as features goes that I own! Haven't tested it in the PC DVD player yet, but the pioneer works great!
This is a wonderful example of an ethical code for Systems Admins. The third paragraph of Canon 1 is especially apt in this instance. It boils down to 'A sysadmin should follow the policies given by the company as law, but should attempt to properly see those laws changed when needed'. UNTIL the policies of the network are changed, the sysadmin should follow them, or explain in writing why s/he believes there may be an issue with the way they are to be carried out. Then, the Systems Admin must make a choice on whether to enforce the company policies until they are changed or refuse at the risk of his/her job. S/he should explain fully in writing the reasoning behind and state EXPLICITLY why and how s/he believe this violates his/her code of ethics, either personally or professionally. That way, if the systems admin does lose his/her position, at his/her next post that systems admin can reference this ethical conflict and back it up with a written statement.
This sounds like my life. I'm a sysadmin, not the network engineer, but I've spent my fair share of time switching out VIP cards in a Cisco 7513 or making a 100 foot crossover cable at 3 AM when the FDDI module in a catalyst failed. I'm also on call 24/7, and so is another sysadmin here who works with me. It's true, the company OWNS you night and day, around the clock. Heck, I'm just getting over a serious case of bronchitis so bad I was coughing up blood, and I was WORKING FROM HOME! And I'm salaried, so what's OT? The difference in pay VS hours worked means I'm making about the same per hour as my mother, who's a secretary with no computer skills.
The problem is I'm making squat compared to a lot of other people with my experience, and for some dumb reason I'm putting up with it. Call it loyalty to a company I was one of the first 20 employees for, I guess (even though we've been bought and had the company that bought US bought out).
Why do we keep doing this? Anyone know a good shrink?
Rob, I think it's great. You started all this, and it's your baby. I'd say 'our baby' since the community does make slashdot what it is, but like the linux kernel, we need a point of control.
The reason, it seems to me, this is such a big problem is that every time this happens, all the counselors, media, and parents look for the person to blame. However could these little darlings do something like this?! Obviously, it can't be their fault.
Magic words, to people who're still growing up. Take away the blame, and a lot of things can start percolating in heads. I'm only 22, so High School and such wasn't THAT long ago. The people at fault are the little bastards involved, the ones doing the shooting. Leave the rest of us who play quake, use the internet, wear black trenchcoats and basically went thru the same problems while growing up *out of it*. Put the blame back where it belongs; on the head of the little psycho's pulling the trigger.
I went through high school, and never killed a single person. Yes, I had access to guns (pistols and rifles; been shooting since I could keep the barrel from dragging the ground). Yes, I used the internet (Terrorists handbook was around 6 or 8 years ago, too! And yes, if I'd wanted to plan an attack and build bombs and kill a huge quantity of people, it would have been possible to do it in a much larger blaze of media attention that these guys pulled.
But I never did it, because I'm not a complete wacko.
So, this seems to be turning into a terrible situation. Just remember, until you start installing Linux, it ain't Linux's fault:-)
I feel for you Jon. I've just had to perform major surgery on 2 of my Linux machines after one of them experienced a serious thrombosis of the CPU, and the other quickly offered to give some spare parts for a transplant. *sniff* That little guy is so noble...
Well, we'll see how much got fixed. I've read through the patch, but not being a coder menas I'll wait till one of the patch summaries goes up to see what I've missed. A lot of it looks like the Cyrix and TCS stuff, along with just simple doc fixes.
Slashdot Mirror
The white rabbit stuff is wonderful, commentary and audio-only tracks are great, and the movie plays and searches nice and fast. For me, this is one of the best DVD's as far as features goes that I own! Haven't tested it in the PC DVD player yet, but the pioneer works great!
Jees, I opened the story, saw 1 comment, hit the link, *thud*.
/. codebase that auto emaisl any email href=addy on the page linked to :-)
Maybe we need to have a thing in
http://www.usenix.org/sage/publications/code_of_et hics.html
This is a wonderful example of an ethical code for Systems Admins. The third paragraph of Canon 1 is especially apt in this instance. It boils down to 'A sysadmin should follow the policies given by the company as law, but should attempt to properly see those laws changed when needed'. UNTIL the policies of the network are changed, the sysadmin should follow them, or explain in writing why s/he believes there may be an issue with the way they are to be carried out. Then, the Systems Admin must make a choice on whether to enforce the company policies until they are changed or refuse at the risk of his/her job. S/he should explain fully in writing the reasoning behind and state EXPLICITLY why and how s/he believe this violates his/her code of ethics, either personally or professionally. That way, if the systems admin does lose his/her position, at his/her next post that systems admin can reference this ethical conflict and back it up with a written statement.
This sounds like my life. I'm a sysadmin, not the network engineer, but I've spent my fair share of time switching out VIP cards in a Cisco 7513 or making a 100 foot crossover cable at 3 AM when the FDDI module in a catalyst failed. I'm also on call 24/7, and so is another sysadmin here who works with me. It's true, the company OWNS you night and day, around the clock. Heck, I'm just getting over a serious case of bronchitis so bad I was coughing up blood, and I was WORKING FROM HOME! And I'm salaried, so what's OT? The difference in pay VS hours worked means I'm making about the same per hour as my mother, who's a secretary with no computer skills.
The problem is I'm making squat compared to a lot of other people with my experience, and for some dumb reason I'm putting up with it. Call it loyalty to a company I was one of the first 20 employees for, I guess (even though we've been bought and had the company that bought US bought out).
Why do we keep doing this? Anyone know a good shrink?
Rob, I think it's great. You started all this, and it's your baby. I'd say 'our baby' since the community does make slashdot what it is, but like the linux kernel, we need a point of control.
I'm glad you were willing to take the jump!
Backtick
The reason, it seems to me, this is such a big problem is that every time this happens, all the counselors, media, and parents look for the person to blame. However could these little darlings do something like this?! Obviously, it can't be their fault.
Magic words, to people who're still growing up. Take away the blame, and a lot of things can start percolating in heads. I'm only 22, so High School and such wasn't THAT long ago. The people at fault are the little bastards involved, the ones doing the shooting. Leave the rest of us who play quake, use the internet, wear black trenchcoats and basically went thru the same problems while growing up *out of it*. Put the blame back where it belongs; on the head of the little psycho's pulling the trigger.
I went through high school, and never killed a single person. Yes, I had access to guns (pistols and rifles; been shooting since I could keep the barrel from dragging the ground). Yes, I used the internet (Terrorists handbook was around 6 or 8 years ago, too! And yes, if I'd wanted to plan an attack and build bombs and kill a huge quantity of people, it would have been possible to do it in a much larger blaze of media attention that these guys pulled.
But I never did it, because I'm not a complete wacko.
http://babelfish.altavista.digital.com/cgi-bin/tra nslate?lp=de_en&urltext=http%3a%2f%2fwww %2eheise%2ede%2fnewsticker%2fdata%2frh-09.03.99-00 0>Bablefish
:-)
Munges it a bit, but you can get the idea
Cool! /. kicks major tail, and this goes to show, some people notice! Keep it up, Rob & Crew!
So, this seems to be turning into a terrible situation. Just remember, until you start installing Linux, it ain't Linux's fault :-)
I feel for you Jon. I've just had to perform major surgery on 2 of my Linux machines after one of them experienced a serious thrombosis of the CPU, and the other quickly offered to give some spare parts for a transplant. *sniff* That little guy is so noble...
Well, we'll see how much got fixed. I've read through the patch, but not being a coder menas I'll wait till one of the patch summaries goes up to see what I've missed. A lot of it looks like the Cyrix and TCS stuff, along with just simple doc fixes.