I almost never use commands. I used to use apt-get update and upgrade but now I just use the GUI software updater.
The one command I find essential is āsudo dpkg --configure -aā if you have a problem downloading and installing software like a power failure while upgrading or dependency problems. I keep a cheat sheet for that and anything else I might need.
Though you may not notice it, there are spaces in front of the command, as with my current profile that means the command doesnāt get stored in my .bash_history and so itās less cluttered.
There also isnāt any -y, so I can actually read the output (esp. given Iām using apt full-upgrade) & accept it only if Iām happy.
The apt autoremove I think is helpful, as if Iāve laid a āmineā for myself (through stupid prior apt remove), Iād rather notice it āsoonerā than ālaterā, as there is more chance Iāll remember what I did that caused it..
The apt autoclean is out of habit as Iāve had disk space issues somewhat often. I peruse the output (apt autoremove; apt autoclean) before I accept the full-upgrade command too.
The fastfetch just gives me a reminder of how long the machine has been up (I reboot it every ~14 days; switching to dual boot install first & updating it), and it gives my $HOSTNAME & some machine detail (to ensure Iām on the correct box at a minimum; that Iām not ssh'd into another box OR my keyboard/mouse/screens arenāt controlling another box (KVM switches here).
I also donāt really have one fixed command I use at the start of my day. Sometimes itās going into a directory, sometimes itās activating a conda environmentā¦
However, usually, at the end of the day, before I shut down my computer I run update-system, which is an alias for sudo apt update && sudo apt upgrade && sudo apt autoremove && flatpak update.
This is an intriguing question. And like some it depends on what work or problem I am trying to solve. So with that said the most popular for me to start with are ping, drill, and ssh.
.. but I ssh into other boxes, and Iāve made mistakes before in not noticing $PS1; thus I also scan Host [field], OS & even the Display lines (eg. current box lists 5; HDMI-(1-3) & DVI-I-(1-2), and whilst this box does share 3 of those screens with other boxes, it doesnāt share all 5 & that count is the easiest ātellā for this box.. ie. fastfetch (or neofetch in older releases) gives a load of detail that allows me to confirm (pretty well) which box Iām actually typing commands into.
Iām actually running fastfetch (or neofetch) before I do most changes (significant or unique changes to confirm box), but not just after a box has been turned on as Iād expect I know which box I just turned on or woke. I like how it presents its data; but thatās mostly (I think) as I can usually detect the box, even if Iām not wearing my glasses (logo shows Ubuntu, Debian etc, number of display lines etc).
For me, the idea of a āfirstā command I use every day doesnāt really fit my habits, because I am not in āwork lifeā anymore.
When I was, I did have a canned routine which would
verify āupā status of a list of ācompute serversā for CAD/CAM export
verify available disk space of the compute transient files
verify that the processes for feeding files to remote DBs and file cashe storage were functional and reporting no glitches
generate the statistical chart of times for phases of compute process, including āper item wait in queueā; āitems in wait queueā; total MB of data files retrieved for the compute phase; RAM and VM status at regular intervals; numbers of and MB of, data files generated from compute jobs; average total time for compute jobs for different classes of items (Pro/ENG PROP, Pro/Eng PEAM, Catia, Unicad, Versacad) for remote replication. Those charts were also published for viewing by the entire internal engineering/manufacturing organization at Nortel, so that they would get a āpulseā of our compute operations and develop a sense of when to expect their jobs to be completed.
So, in home life, I have two personalities, regular user and root, and my command usage āprofileā is as follows:
For regular user ā¦
2273 ls
881 sync
752 gvim
733 cd
553 .
237 vi
221 mv
211 rm
176 more
169 grep
152 man
131 chmod
122 cp
113 sudo
92 find
77 clear
As root user ā¦
7007 ls
3697 sync
3669 cd
2619 gvim
1754 .
1543 man
861 Admin.sh
770 more
625 grep
546 cp
536 myDf.sh
504 mv
455 rm
382 cat
375 find
362 ./UTIL__SearchIndexes.sh
349 USER__Find_IndexedFiles.sh
289 ps
272 chmod
262 inxi
232 diff
202 history
199 which
193 systemctl
146 echo
145 HW_Admin__Power_SetFreqCPU.sh
141 lsblk
134 apt-get
125 swapon
I run a lot of commands, and I donāt care if my command aliases are familiar to anyone else or not because they are my aliases, but hereās mine, and then Iāll explain it:
u;d;re
alias u=āsudo apt-get update; sudo apt-get dist-upgrade;
sudo update-grub;sudo apt-get autoremoveā # I use this to upgrade my system and update my boot loader, then autoremove any software no longer needed.
alias d=ādoom sync; doom upgradeā # This updates my Doom Emacs configuration.
alias re=ārestartEmacsā # I have a function in my .bashrc called restartEmacs; the purpose is to start, stop, or restart my Emacs server; in this case, Iām restarting it.