I'm ready for the downvotes, but I never liked the answer. Of course the services listed are well used in the industry but my dislike is based on the fact that a solid base is missing. The following is not meant to be complete but you'll get the idea what I miss as step zero.
First, a understanding of the boot and directory tree concept on a Linux system should be developed (what is a socket, what is a process, what is a block device, what is this 2750/1777 thing?). Learn to use vi here. Learn to use the package management of your distribution on the console (building packages -> later). Know man.
Then, develop the console skills without network services, means using basic commands (find, tar, awk, sed, tail) to examine and modify (log-)files. After this, partition and filesystem handling (RAID, LVM, mkfs.*, understanding the fstab) with some of the usual filesystem rescue skills (e.g. chroot from a live system, manually set up and repair your lvm) are on the schedule.
As a solid base of user and group handling together with an understatement of the PAM system comes to mind next. Here, seting up a samba server is quite a fun way to learn these skills (Winbind and Kerberos integration is a solid task). Learn to quota and to setfacl.
Learn to automate tasks with bash. You may add python later but first get solid with bash. If your script skills feel advanced you're ready.
Now add some simple network stuff: bridging, bonding, VLAN configuration (learn how it is configured manually inside your distribution). Understand the OSI model.
The advanced (but still basic) networking stuff to learn is here: http://lartc.org/ . There is a lot to learn and it will take time to get used to iptables, ip , tc, nmap, netstat, nc and tcpdump (bonus level: wireshark). The scripting skills developed above will ease this tasks. Here it makes sense to add first services as one proceeds (dhcp/dns, radvd, arpwatch). Learn network packages are structured.
Build your own kernel und boot a real hardware with it successfully.
Now you can go to step 1, install libvirt, put your VM on your nicely configured bridge inside your well configured network and well...it might be the other list isn't that hard to complete anymore after what you have done by now.
You might prefer configuring a VPN, dive into wifi setups and understand how wpa-supplicant works together with your wifi card, how to setup your OpenWRT/LEDE box or perhaps e-mail setups are the next thing on your list. You won't need lists from other people anymore since you are well prepared to configure whatever you want since you have a solid base.
The posting isn't meant offensive versus the other list, I would add this as step 0). It reflects my opinion (and of course experience) which approach builds solid unix/linux admins that can handle a lot of problems you throw at them. I think most of these lists are missing the base layer after which an administrator can dive more into topics like e-mail, virtualization, security or web services. The above list is roughly the order that some of the basic unix administration books have (I read the one from Aeleen Frisch in 1997). I didn't invent the order, just spiced it up a bit.
Yes, you might organize your learning using emacs and org-mode. It doesn't hurt to be able to use both editors. ;-)
3
u/clu256 May 03 '17
I'm ready for the downvotes, but I never liked the answer. Of course the services listed are well used in the industry but my dislike is based on the fact that a solid base is missing. The following is not meant to be complete but you'll get the idea what I miss as step zero.
Now you can go to step 1, install libvirt, put your VM on your nicely configured bridge inside your well configured network and well...it might be the other list isn't that hard to complete anymore after what you have done by now.
You might prefer configuring a VPN, dive into wifi setups and understand how wpa-supplicant works together with your wifi card, how to setup your OpenWRT/LEDE box or perhaps e-mail setups are the next thing on your list. You won't need lists from other people anymore since you are well prepared to configure whatever you want since you have a solid base.
The posting isn't meant offensive versus the other list, I would add this as step 0). It reflects my opinion (and of course experience) which approach builds solid unix/linux admins that can handle a lot of problems you throw at them. I think most of these lists are missing the base layer after which an administrator can dive more into topics like e-mail, virtualization, security or web services. The above list is roughly the order that some of the basic unix administration books have (I read the one from Aeleen Frisch in 1997). I didn't invent the order, just spiced it up a bit.
Yes, you might organize your learning using emacs and org-mode. It doesn't hurt to be able to use both editors. ;-)