Useful Linux commands - Revision history

Fdchild22: Made some syntax changes to the scp and pacman entries

2026-10-15T18:33:57Z

Made some syntax changes to the scp and pacman entries

← Older revision		Revision as of 18:33, 15 October 2026
Line 1,032:		Line 1,032:
	=== scp ===		=== scp ===

	<code>scp<code> (<u>S</u>ecure <u><code>cp</code</u> allows for files and directories to be copied to and from a remote system using the same kind of encrypted connection as <code>ssh</code>.		<code>scp</code> (<u>S</u>ecure <u><code>cp</code></u> allows for files and directories to be copied to and from a remote system using the same kind of encrypted connection as <code>ssh</code>.

	<pre>		<pre>
Line 1,094:		Line 1,094:
	<code>lsof</code> prints a list of currently open files on a given system along with the processes that opened them.		<code>lsof</code> prints a list of currently open files on a given system along with the processes that opened them.

	Because of the Unix philosophy that ~~<a href="~~https://en.wikipedia.org/wiki/Everything_is_a_file">everything on a system should have a manifestation in the file system~~</a>~~, <code>lsof</code> is insanely useful as a troubleshooting tool as it can be used to monitor and find details about file usage, system resources, network connections, and so on.		Because of the Unix philosophy that [https://en.wikipedia.org/wiki/Everything_is_a_file everything on a system should have a manifestation in the file system], <code>lsof</code> is insanely useful as a troubleshooting tool as it can be used to monitor and find details about file usage, system resources, network connections, and so on.
	-->		-->

Line 1,113:		Line 1,113:
	=== pacman ===		=== pacman ===

	The pacman package manager is characteristic to Arch Linux and its derivatives (e.g. Manjaro Linux, EneavourOS, Cachyos), and is the core package manager on these systems. For a more detailed overview, ~~<a href="~~https://wiki.archlinux.org/title/Pacman">read the pacman page on the Arch Wiki~~</a>~~. ~~Some of the core functions will be detailed below:~~		The pacman package manager is characteristic to Arch Linux and its derivatives (e.g. Manjaro Linux, EneavourOS, Cachyos), and is the core package manager on these systems. For a more detailed overview, [https://wiki.archlinux.org/title/Pacman read the pacman page on the Arch Wiki].

	<~~pre~~>		Some useful flags and commands to know for pacman include:
	~~pacman~~ -S ~~packageName # Downloads~~ and ~~installs packageName~~ and its dependencies		* <code>-S</code> to download and install a package and its dependencies
	~~pacman~~ -Ss ~~packageName # Searches~~ for ~~packageName~~ in the Arch~~'s package database~~		* <code>-Ss</code> to search for a package in the official Arch repositories
	~~pacman~~ -U /link/to/packageName ~~# Installs~~ from a designated local file		* <code>-U /link/to/packageName</code> installs a package from a designated local file
	~~pacman~~ -Syu ~~# Upgrade~~ every package on ~~the~~ system		* <code>-Syu</code> upgrades every package on a system
	~~pacman~~ -R ~~packageName # Remove~~ a single package		* <code>-R</code> removes a single package
	~~pacman~~ -Rs ~~packageName # Remove~~ a single package and all its dependencies		* <code>-Rs</code> removes a single package and all its dependencies
	~~</pre>~~

	==== yay ====		==== yay ====

	yay is a wrapper for pacman that adds support for ~~<a href="~~https://wiki.archlinux.org/title/Arch_User_Repository")the AUR~~</a>~~ (<u>A</u>rch <u>U</u>ser <u>R</u>epository) to allow for the installation and management of user-compiled packages in addition to official releases.		yay is a wrapper for pacman that adds support for [https://wiki.archlinux.org/title/Arch_User_Repository the AUR] (<u>A</u>rch <u>U</u>ser <u>R</u>epository) to allow for the installation and management of user-compiled packages in addition to official releases.

	While files from the AUR overwhelmingly tend to be safe—many of the packages in the official repositories started from the AUR—caution should always be observed when downloading community-driven packages.		While files from the AUR overwhelmingly tend to be safe—many of the packages in the official repositories started from the AUR—caution should always be observed when downloading community-driven packages.

	Every pacman command is compatible for use with yay, though yay has a few of its own functionalities, many of which can be found in ~~<a href="~~https://github.com/Jguer/yay">its GitHub page~~</a>~~.		Every pacman command is compatible for use with yay, though yay has a few of its own functionalities, many of which can be found in [https://github.com/Jguer/yay its GitHub page].


Line 1,158:		Line 1,157:

	-- Major Overhaul: March 2025 by Tyler Jones [tdjones22] --		-- Major Overhaul: March 2025 by Tyler Jones [tdjones22] --
			<br>
	-- Latest Edits: October 2026 by Felix Childress [fdchild22] --		-- Latest Edits: October 2026 by Felix Childress [fdchild22] --

Fdchild22: Added entries on ping, traceroute, scp, pacman, yay. Began entry for lsof.

2026-10-15T18:23:02Z

Added entries on ping, traceroute, scp, pacman, yay. Began entry for lsof.

@@ Line 1,002: / Line 1,002: @@
 === ping ===
 === curl ===
@@ Line 1,008: / Line 1,031: @@
 === scp ===
 === rsync ===
@@ Line 1,018: / Line 1,051: @@
 === traceroute ===
@@ Line 1,032: / Line 1,091: @@
 === dmesg ===
-=== lsof ===
+<!--
 === vmstat ===
@@ Line 1,049: / Line 1,112: @@
 === pacman ===
@@ Line 1,076: / Line 1,158: @@
 -- Major Overhaul: March 2025 by Tyler Jones [tdjones22] --

Tdjones22: Added examples for -l and -L flags in grep command

2025-12-21T22:24:59Z

Added examples for -l and -L flags in grep command

@@ Line 937: / Line 937: @@
 tdjones22@bowie:~/grep_test$ grep -i -c "python" test2.txt
 </pre>
    </blockquote>

Tdjones22: Added examples for -c flag for grep

2025-12-21T21:30:28Z

Added examples for -c flag for grep

@@ Line 912: / Line 912: @@
 :pythons
 :python
 </pre>
    </blockquote>

Tdjones22: Added examples for -e and -E flags for grep

2025-12-19T23:28:26Z

Added examples for -e and -E flags for grep

@@ Line 877: / Line 877: @@
 more_more_code.c
 some_code.py
 </pre>
    </blockquote>

Tdjones22: Added examples for -v flag in grep command

2025-12-17T21:01:20Z

Added examples for -v flag in grep command

@@ Line 830: / Line 830: @@
 :Pythons
 :pythons
 </pre>
    </blockquote>

Tdjones22: Added i and w flags for grep

2025-12-01T19:15:37Z

Added i and w flags for grep

@@ Line 777: / Line 777: @@
 :Pythons kill prey by squeezing them really tight.
 :Pythons incubate their eggs by shivering.
 </pre>
    </blockquote>

Tdjones22: Started grep command

2025-10-07T13:54:15Z

Started grep command

← Older revision		Revision as of 13:54, 7 October 2025
Line 757:		Line 757:

	=== grep ===		=== grep ===

			<code>grep</code> is a tool used to match words, strings, or patterns in text files. The command works with any <code>ASCII Text</code> files, so extensions like .txt, .c, .py, .log, .config, etc all work with <code>grep</code>.

			* <code>grep "<desired text>" <file></code> - Using <code>grep</code> to find something in a file will output ''all'' lines that contain a case-sensitive match. Here's the output if I run <code>grep "Python" test2.txt</code>:
			<blockquote>
			<pre>
			tdjones22@bowie:~/grep_test$ grep "Python" test2.txt
			This is test file 2. Here are some Python facts:
			Pythons kill prey by squeezing them really tight.
			Pythons incubate their eggs by shivering.
			</pre>
			</blockquote>

			* <code> grep -n "<desired text>" <file></code> - Sometimes simply outputting the lines containing the match isn't enough, and you want to know ''where'' in the file it is. That's where the <code>-n</code> flag comes in. It outputs the line number along with the line. Here's <code>grep -n "Python" test2.txt</code>:
			<blockquote>
			<pre>
			tdjones22@bowie:~/grep_test$ grep -n "Python" test2.txt
			1:This is test file 2. Here are some Python facts:
			2:Pythons kill prey by squeezing them really tight.
			6:Pythons incubate their eggs by shivering.
			</pre>
			</blockquote>

	=== egrep ===		=== egrep ===

Tdjones22: Finish nano

2025-10-07T13:10:46Z

Finish nano

← Older revision		Revision as of 13:10, 7 October 2025
Line 722:		Line 722:
	</blockquote>		</blockquote>

	=== nano ~~(NEEDS FINISHED)~~ ===		=== nano ===
	<code>nano</code> is a terminal-based text editor in its simplest form. The editing style is much more straightforward than other editors, like <code>Vim</code>, making it an easy choice for Linux beginners (and me, who's been using Linux for a few years, and still only uses Nano). Since it's just a text editor, I can't really 'show' you how to use it, but I can tell you about some really helpful shortcuts included in <code>nano</code>:		<code>nano</code> is a terminal-based text editor in its simplest form. The editing style is much more straightforward than other editors, like <code>Vim</code>, making it an easy choice for Linux beginners (and me, who's been using Linux for a few years, and still only uses Nano). Since it's just a text editor, I can't really 'show' you how to use it, but I can tell you about some really helpful shortcuts included in <code>nano</code>:
	* <code>nano file.txt</code> - This command takes you into the text editor with the chosen file. You can use <code>nano</code> on most text files, including: .txt, .c, .py, .log, .config, etc.		* <code>nano file.txt</code> - This command takes you into the text editor with the chosen file. You can use <code>nano</code> on most text files, including: .txt, .c, .py, .log, .config, etc.

Tdjones22: Added more hotkeys to nano command

2025-10-04T16:01:40Z

Added more hotkeys to nano command

← Older revision		Revision as of 16:01, 4 October 2025
Line 732:		Line 732:
	* <code>Ctrl+O</code> - Saves the current file AND prompts you for the file name.		* <code>Ctrl+O</code> - Saves the current file AND prompts you for the file name.
	* <code>Ctrl+S</code> - Saves the current file without prompting for a file name; quick save, basically.		* <code>Ctrl+S</code> - Saves the current file without prompting for a file name; quick save, basically.
	* <code>Ctrl+X</code? - Exits the file; will prompt for saving if you haven't manually saved prior to exiting.		* <code>Ctrl+X</code> - Exits the file; will prompt for saving if you haven't manually saved prior to exiting.

	'''Navigation and Editing'''		'''Navigation and Editing'''
Line 738:		Line 738:
	* <code>Ctrl+A</code> - Move the cursor to the beginning of the line (like the 'home' button on a Windows laptop).		* <code>Ctrl+A</code> - Move the cursor to the beginning of the line (like the 'home' button on a Windows laptop).
	* <code>Ctrl+E</code> - Move the cursor to the end of the line (like the 'end' button on a Windows laptop).		* <code>Ctrl+E</code> - Move the cursor to the end of the line (like the 'end' button on a Windows laptop).
			* <code>Alt+3</code> - Comments or uncomments line where cursor is located.
			* <code>Ctrl+W</code> - Initiates a text search that finds the nearest match that appears ''after'' your cursor's current position.
			<blockquote>
			* <code>Alt+W</code> - Find the next forward occurrence of the searched word.
			* <code>Alt+Q</code> - Find the next backward occurrence of the searched word.
			</blockquote>
			* <code>Alt+_</code> - Go to line and column number (e.g., '4, 3').
			* <code>Ctrl+K</code> - Cut the line your cursor is currently positioned on.
			<blockquote>
			* <code>Ctrl+U</code> - When cutting lines with <code>Ctrl+K</code>, they're temporarily stored in a cut buffer, which you can then repaste. Almost like copy and pasting, with the addition of removing the content you're copying. The cut buffer can store multiple lines.
			</blockquote>
			* <code>Alt+U</code> - Undoes the last action.
			* <code>Alt+E</code> - Redoes the last undone action.
			* <code>Ctrl+C</code> - Display the cursor's current position (line, column, character).
			* <code>Ctrl+G</code> - Opens the help system within <code>nano</code>.

	== Searching and Text Processing (TBD) ==		== Searching and Text Processing (TBD) ==