10 *nix Tips

http://www.ibm.com/developerworks/aix/library/au-badunixhabits.html

Seems like an interesting list. Some of it was definitely beyond me

Find more posts tagged with

Free for TechExams community: Cybersecurity salary guide

Compare cert salaries and plan your next career move

Button

Comments

shednik

dynamik wrote:

http://www.ibm.com/developerworks/aix/library/au-badunixhabits.html

Seems like an interesting list. Some of it was definitely beyond me

Ahh come on Mr. RHCE in training you should know all of those haha j/k nice little list some of it went above me as well.

undomiel

You can use a number of those in a Windows CLI as well. I actually use a few of these tricks in some of my own scripts (windows and non) such as && or ||. I'm guilty of the cat + grep though.

It's just what I grew up knowing! Good tips there.

TechJunky

Wow, I have some bad habits.

Great link. Bookmarked.

Grynder

Thanks. Definately will save the link.
The tar -C option comes in very handy. It took me forever to find it when I was studying for my Linux+ exam. It just seemed that there would be such an option but it is obviously not in common use

darkerosxx

The grep -c option is a cool one I didn't know about. I've always used wc to to count.

Thank for posting that Dynamik

Talic

lol @ piping cats. It sounds just funny. But I really didn't think people would use cat when greping files, I wonder how that bad habit comes along.

dynamik

I've seen it in a lot of introductory resources. It's probably nothing more than an example of how piping works, but I can see how it would stick with someone who's just starting out.

rbutturini

That's pretty good stuff. I'm going to pass that along to some folks I know who need a little "penguin education".

undomiel

I still have to stop and remind myself not to cat that file through grep or through less. That's pretty much how it happened for me like dynamik said. Back in high school when I had my first shell account I either saw someone look through files that way or read it somewhere and it has stuck ever since. Probably because it is related to "type <file> | more" back in DOS I think.