5 ms·

* understand the basic directory structure (/, /boot/, /var, /usr, /opt, /etc) * file management (commands: tail, head, cat, awk, sed) * process management (com

* 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.

caw 9y ago
Good list, I'd also say permissions. The number of problems I fix by understanding users/groups and assigning the appropriate permission (not `chmod 777 *`) is huge. It shows up in a variety of "Cannot access file" type messages or "File does not exist" application errors and people sometimes freak out because the file is there.
- autotune 9y ago
  Also relavent to permissions: https://people.redhat.com/duffy/selinux/selinux-coloring-book_A4-Stapled.pdf https://people.redhat.com/duffy/selinux/selinux-coloring-boo...
  - punchclockhero 9y ago
    Definitely. If something's not working in a Red Hat based distro, it's usually stopped by SElinux.
    - zlynx 9y ago
      And the right answer is never "Disable SELinux"
- himlion 9y ago
  To be fair 'chmod 777 *' fixes those issues as well, just at a big cost to security.
  - Jugurtha 9y ago
    I don't know if "fix" is the right word. Chopping your right arm off "fixes" the itch, although you're literally giving your right arm.
Lordarminius 9y ago
> understand the basic directory structure... I agree with this. Anyone interested in command line hacking can find everything nelsonmarcus recommends (and a bit more) in this very readable book: The Linux Command Line A complete Introduction By Shotts https://www.amazon.com/Linux-Command-Line-Complete-Introduction/dp/1593273894 https://www.amazon.com/Linux-Command-Line-Complete-Introduct...
- ashconnor 9y ago
  Brian Ward's - How Linux Works is also very good https://www.nostarch.com/howlinuxworks2 https://www.nostarch.com/howlinuxworks2

caw 9y ago

Good list, I'd also say permissions. The number of problems I fix by understanding users/groups and assigning the appropriate permission (not `chmod 777 *`) is huge. It shows up in a variety of "Cannot access file" type messages or "File does not exist" application errors and people sometimes freak out because the file is there.

autotune 9y ago
Also relavent to permissions: https://people.redhat.com/duffy/selinux/selinux-coloring-book_A4-Stapled.pdf https://people.redhat.com/duffy/selinux/selinux-coloring-boo...
- punchclockhero 9y ago
  Definitely. If something's not working in a Red Hat based distro, it's usually stopped by SElinux.
  - zlynx 9y ago
    And the right answer is never "Disable SELinux"
himlion 9y ago
To be fair 'chmod 777 *' fixes those issues as well, just at a big cost to security.
- Jugurtha 9y ago
  I don't know if "fix" is the right word. Chopping your right arm off "fixes" the itch, although you're literally giving your right arm.

Lordarminius 9y ago

> understand the basic directory structure... I agree with this. Anyone interested in command line hacking can find everything nelsonmarcus recommends (and a bit more) in this very readable book: The Linux Command Line A complete Introduction By Shotts https://www.amazon.com/Linux-Command-Line-Complete-Introduction/dp/1593273894 https://www.amazon.com/Linux-Command-Line-Complete-Introduct...

ashconnor 9y ago
Brian Ward's - How Linux Works is also very good https://www.nostarch.com/howlinuxworks2 https://www.nostarch.com/howlinuxworks2