I’m on the other side of the coin, I really don’t know how I’m supposed to learn to use the terminal. I can do sudo apt get to get some programs and updates, as well as mv and cp, but that’s where it stops for me.
You need a purpose. For instance I needed to copy and edit config files for a bunch terminals my company has deployed last week. Instead of manually copying the template directory 80 times and editing the 2 lines that needed to be changed in the parameter file for each one I used powershell to extract the name and id for each terminal from the log files and create copy of the template directory for each one, then replace the terminal name and id in the parameter file of the new directory with the ones extracted from the logs. This would have taken me all day to do manually and it only took about 45 minutes to write up the script and run it. I did have some prior experience with doing this kind of thing but hadn’t tied them all together lile that before so i learned some stuff.
I literally only use it when a how-to guide explains exactly what to do and why. Then I forget what I did and look up how to do it again six months later. I’m fine with this arrangement, though I will prefer to have to use it less.
Maybe you need to have some sort of objective before you get started, otherwise yeah, you don’t have much to do in the console :)
In my case I only use linux for work, so I’m ssh-ing away and running commands to compile this, apply that, show me the logs for this, grep that, etc.
I’m on the other side of the coin, I really don’t know how I’m supposed to learn to use the terminal. I can do sudo apt get to get some programs and updates, as well as mv and cp, but that’s where it stops for me.
You need a purpose. For instance I needed to copy and edit config files for a bunch terminals my company has deployed last week. Instead of manually copying the template directory 80 times and editing the 2 lines that needed to be changed in the parameter file for each one I used powershell to extract the name and id for each terminal from the log files and create copy of the template directory for each one, then replace the terminal name and id in the parameter file of the new directory with the ones extracted from the logs. This would have taken me all day to do manually and it only took about 45 minutes to write up the script and run it. I did have some prior experience with doing this kind of thing but hadn’t tied them all together lile that before so i learned some stuff.
I literally only use it when a how-to guide explains exactly what to do and why. Then I forget what I did and look up how to do it again six months later. I’m fine with this arrangement, though I will prefer to have to use it less.
Maybe you need to have some sort of objective before you get started, otherwise yeah, you don’t have much to do in the console :) In my case I only use linux for work, so I’m ssh-ing away and running commands to compile this, apply that, show me the logs for this, grep that, etc.