Linked by David Adams on Mon 4th Aug 2008 18:56 UTC
Internet & Networking In technology environment, keeping things simple takes lot more effort and maturity than keeping it complex. These 10 items are guidelines more than rules, that I have learned over the years doing intensive work on the IT infrastructure. These guidelines are mostly common sense and can be helpful for anybody who administers an IT system, including Linux/Windows Administrator, Network Administrator and DBA.
Thread beginning with comment 325558
To read all comments associated with this story, please click here.
My kneejerk reaction
by IanSVT on Mon 4th Aug 2008 19:49 UTC
IanSVT
Member since:
2005-07-06

1. Yes, as simple as you can be and still get the job done. Although security is never simple and not something you should keep simple(because that means no passwords!)
2. Yes.
3. Having a backup you haven't tested is better than nothing at all. Although you should absolutely test it.
4. Yes.
5. Oh god yes, for the sake of whoever comes after you and maybe even for your own sanity.
6. Sure. But problems will arise.
7. No. Just typing crap into a command line won't necessarily teach you anything just like compiling a program in freebsd won't teach you anything about *nix. "I see scrolling compiler text, I'm a hackerz!!one"
8. Yes.
9. Yes. Complain about them later while you're having a beer.

Reply Score: 2

RE: My kneejerk reaction
by Doc Pain on Mon 4th Aug 2008 23:35 in reply to "My kneejerk reaction"
Doc Pain Member since:
2006-10-08

1. Yes, as simple as you can be and still get the job done. Although security is never simple and not something you should keep simple(because that means no passwords!)


As always in regards of security, you're not alone. If everything would just depend on yourself, well, you could guarantee almost 99% security. But there usually are other users who don't understand why their password can't just be their name or empty.

2. Yes.


Backups. I should have known earlier... :-( (Total desaster here on July 2nd.)

When you're making backups, your disks will never fail. But they will as soon as you leave out one backup session. It's the same as with umbrellas and rain. :-)

More here: http://www.rinkworks.com/stupid/cs_backups.shtml

3. Having a backup you haven't tested is better than nothing at all. Although you should absolutely test it.


If the backup works if needed, it doesn't matter if you've tested it. But when you insist on having a backup, and it won't work, then...

5. Oh god yes, for the sake of whoever comes after you and maybe even for your own sanity.


It's good when you do documentation on paper. Electronic media can always fail (maybe due to the media itself or due to a malfunctioning drive), but paper can be read with only using your eyes.

6. Sure. But problems will arise.


Of course, no matter how good you think you've planned. But I think it's about how you manage upcoming problems, too.

7. No. Just typing crap into a command line won't necessarily teach you anything just like compiling a program in freebsd won't teach you anything about *nix. "I see scrolling compiler text, I'm a hackerz!!one"


Hehe, that's right. Using the command line properly involves learning. The CLI is just a means to get work done, nothing more, nothing less. It's not a holy grail to make you any smarter. But in most cases, you can see an implication the other way round: Those who use the command line usually have skills that are valuable.

8. Yes.


Involves number 7, in most cases.

9. Yes. Complain about them later while you're having a beer.


Or put this onto your wall: http://web.gnuer.org/blog/uploads/pictures/stupidamouse.jpg :-)

You forgot number 10, in my opinion one of the most important things. You can only keep up in business if your knowledge is up to date, and you can stand all the problems, all the learning and all the typing if you're really having fun doing these things. A saying I've heared on this topic: "A system administrator is a person who is paid to do the things he would do anyway at home without payment." If you don't like the job, it will make you sick one day, and you don't want to see these stupid computers anymore. :-)

Reply Parent Score: 2