12-09-2015, 12:56 AM
I'm guessing that the point of this is to set one or two commands that you use often as the first and second commands stored in bash history so they're easy to duplicate quickly -- correct? Interesting idea.
Just keep in mind that bash history will overwrite those if the default limit of command history saved is reached. (I think it's set to save up to 500 lines initially.) So if you use the terminal a lot, check how many lines that history is up to every once in a while or you could be in for a surprise one day and execute commands that you didn't mean to. Just open a terminal and enter history to see list of commands you've entered and how many lines have been saved so far.
NOTE: for anyone who may not already know, you can re-run any command listed in history by preceding it's line number with a "!" and hitting enter. Eg. If you ran dpkg -l | grep 'flash' somewhere along the line to find out if you had flash installed and it showed up as line #235 in history, you'd just enter this in the terminal to re-run that command:
Just keep in mind that bash history will overwrite those if the default limit of command history saved is reached. (I think it's set to save up to 500 lines initially.) So if you use the terminal a lot, check how many lines that history is up to every once in a while or you could be in for a surprise one day and execute commands that you didn't mean to. Just open a terminal and enter history to see list of commands you've entered and how many lines have been saved so far.
NOTE: for anyone who may not already know, you can re-run any command listed in history by preceding it's line number with a "!" and hitting enter. Eg. If you ran dpkg -l | grep 'flash' somewhere along the line to find out if you had flash installed and it showed up as line #235 in history, you'd just enter this in the terminal to re-run that command:
Code:
!235
Try Linux Beginner Search Engine for answers to Linux questions.