nelsonmarcos

Man, it's good to know I am not alone.

Do you have any suggestion?

I see this as a very important example of how dangerous the mindset "We have always done it this way" is.

It's a long article written on April 1st. Please, don't say it's an april's fool joke.

If we only had listened our sysadmin...

I can’t help but think about “flying car” on 2010.

* understand the basic directory structure (/, /boot/, /var, /usr, /opt, /etc) * file management (commands: tail, head, cat, awk, sed) * process management (commands: ps, top, kill) * package management (yum, dpkg) * one configuration manager (puppet, chef, ansible) * basics of tcp/ip network management (ifconfig/ip, netstata/ss, ping, trace) addiontal commands if you want to be more than a junior (strace, lsof, iostat, vmstat)

I'd like to point out that some sysadmins are focused on linux internals while others focus on application in production. So, of course, the list may vary according to the position you're looking to be hired.