Terminal Guide - Revision history

imported>Chris at 04:43, 23 July 2012

2012-07-23T04:43:24Z

← Older revision		Revision as of 04:43, 23 July 2012
Line 15:		Line 15:

	Some commands require extra information such as a time or path, these come after any options. For example, the <font class="code">shutdown</font> command requires a time indicated for when the shutdown should occur (ex. <font class="code">shutdown -r now</font>).		Some commands require extra information such as a time or path, these come after any options. For example, the <font class="code">shutdown</font> command requires a time indicated for when the shutdown should occur (ex. <font class="code">shutdown -r now</font>).


	=== Command History ===		=== Command History ===
	All commands entered are saved in a history that can be quickly accessed by using the '''[UP]''' and '''[DOWN]''' arrow keys on your keyboard. This is helpful when repeating similar commands in a sequence or save time on commands typed frequently. Each press of the '''[UP]''' arrow scrolls through past commands, starting with the most recent; each press of the '''[DOWN]''' arrow advances forward to the next command in your history until the most recent. Once you have reached the most recent entry, pressing the '''[DOWN]''' arrow key once more will exit searching the history, and return you to a blank line to enter a new command. You can execute any command in your history by first navigating with the '''[ARROW]''' keys and pressing '''[ENTER]''' when the command you want to execute is displayed.		All commands entered are saved in a history that can be quickly accessed by using the '''[UP]''' and '''[DOWN]''' arrow keys on your keyboard. This is helpful when repeating similar commands in a sequence or save time on commands typed frequently. Each press of the '''[UP]''' arrow scrolls through past commands, starting with the most recent; each press of the '''[DOWN]''' arrow advances forward to the next command in your history until the most recent. Once you have reached the most recent entry, pressing the '''[DOWN]''' arrow key once more will exit searching the history, and return you to a blank line to enter a new command. You can execute any command in your history by first navigating with the '''[ARROW]''' keys and pressing '''[ENTER]''' when the command you want to execute is displayed.


	=== Recursive History ===		=== Recursive History ===

imported>Chris at 04:43, 23 July 2012

2012-07-23T04:43:01Z

← Older revision		Revision as of 04:43, 23 July 2012
Line 15:		Line 15:

	Some commands require extra information such as a time or path, these come after any options. For example, the <font class="code">shutdown</font> command requires a time indicated for when the shutdown should occur (ex. <font class="code">shutdown -r now</font>).		Some commands require extra information such as a time or path, these come after any options. For example, the <font class="code">shutdown</font> command requires a time indicated for when the shutdown should occur (ex. <font class="code">shutdown -r now</font>).

			=== Command History ===
			All commands entered are saved in a history that can be quickly accessed by using the '''[UP]''' and '''[DOWN]''' arrow keys on your keyboard. This is helpful when repeating similar commands in a sequence or save time on commands typed frequently. Each press of the '''[UP]''' arrow scrolls through past commands, starting with the most recent; each press of the '''[DOWN]''' arrow advances forward to the next command in your history until the most recent. Once you have reached the most recent entry, pressing the '''[DOWN]''' arrow key once more will exit searching the history, and return you to a blank line to enter a new command. You can execute any command in your history by first navigating with the '''[ARROW]''' keys and pressing '''[ENTER]''' when the command you want to execute is displayed.

			=== Recursive History ===
			Having a command history is incredibly useful, but since it's displayed in a chronological order, can become difficult to search through after many commands have been entered. Recursive searching helps give you a result of a previous command you used based on the command itself, instead of the time it was entered. For example, using the arrow keys, navigating 50 entries deep to get to a command entered a few days ago would take quite a while. Using recursive search allows you to type the first few letters of the command and search though the entire history at once, bringing up commands that start with those characters until you find the command you are looking for.

			To use the recursive search, press the '''[CTRL]''' key and the '''[R]''' key at the same time, then start typing the command you are looking for. Press '''[ENTER]''' when you want to execute that particular command.

imported>Chris at 04:26, 1 April 2011

2011-04-01T04:26:28Z

← Older revision		Revision as of 04:26, 1 April 2011
Line 7:		Line 7:

	When working with xterm, pay attention to the user; different user accounts have different privileges which can give unexpected results or deny commands. To identify which user is logged in, find the current line in the xterm window; it will be displayed as user name @ workstation name (ex. gvuser@inet-7). To change which user is logged in, type <font class="code">su [username]</font> where [username] is the user you want to log in as and press '''[ENTER]'''; log-in will be successful once the password for that user is entered.		When working with xterm, pay attention to the user; different user accounts have different privileges which can give unexpected results or deny commands. To identify which user is logged in, find the current line in the xterm window; it will be displayed as user name @ workstation name (ex. gvuser@inet-7). To change which user is logged in, type <font class="code">su [username]</font> where [username] is the user you want to log in as and press '''[ENTER]'''; log-in will be successful once the password for that user is entered.


	== Using Commands ==		== Using Commands ==
Line 14:		Line 15:

	Some commands require extra information such as a time or path, these come after any options. For example, the <font class="code">shutdown</font> command requires a time indicated for when the shutdown should occur (ex. <font class="code">shutdown -r now</font>).		Some commands require extra information such as a time or path, these come after any options. For example, the <font class="code">shutdown</font> command requires a time indicated for when the shutdown should occur (ex. <font class="code">shutdown -r now</font>).


	== Using Options ==		== Using Options ==
Line 19:		Line 21:

	''Note: options can be case-sensitive, -r and -R are not the same to xterm; this can give unexpected results.''		''Note: options can be case-sensitive, -r and -R are not the same to xterm; this can give unexpected results.''


	== Common Commands ==		== Common Commands ==
Line 35:		Line 38:
	su              switch user<br />		su              switch user<br />
	xkill            changes the mouse cursor to an x, click on a window to close that window/program<br />		xkill            changes the mouse cursor to an x, click on a window to close that window/program<br />


	== Copy and Paste ==		== Copy and Paste ==
Line 42:		Line 46:
	- the up and down arrows cycle through previously entered commands		- the up and down arrows cycle through previously entered commands
	- the tab key will auto complete a file or folder name based on the first few characters typed.		- the tab key will auto complete a file or folder name based on the first few characters typed.


	== Editing text files ==		== Editing text files ==
Line 49:		Line 54:

	The vi editor is an advanced text editor, it is recommended to use nano unless you are familiar with vi. To use vi, type <font class="code">vi [filename]</font> where [filename] is the file you would like to open and press '''[ENTER]'''. To quit the vi editor type <font class="code">:q</font> and press '''[ENTER]'''.		The vi editor is an advanced text editor, it is recommended to use nano unless you are familiar with vi. To use vi, type <font class="code">vi [filename]</font> where [filename] is the file you would like to open and press '''[ENTER]'''. To quit the vi editor type <font class="code">:q</font> and press '''[ENTER]'''.


	== Killing a program ==		== Killing a program ==

imported>Chris at 00:29, 30 September 2010

2010-09-30T00:29:42Z

← Older revision		Revision as of 00:29, 30 September 2010
Line 59:		Line 59:
	To kill just the inactivity timer, type <font class="code">kill xautolock</font>, type <font class="code">kill pacrez</font> to kill the session timer.		To kill just the inactivity timer, type <font class="code">kill xautolock</font>, type <font class="code">kill pacrez</font> to kill the session timer.

	=== Killing a program in the Groovix GUI ===		==== Killing a program in the Groovix GUI ====
	If you can’t find the PID or have the process you want to kill open in the desktop, open a new xterm window and type <font class="code">xkill</font>; this will change the mouse cursor to an X and will kill the first process window you click on with your mouse.		If you can’t find the PID or have the process you want to kill open in the desktop, open a new xterm window and type <font class="code">xkill</font>; this will change the mouse cursor to an X and will kill the first process window you click on with your mouse.

imported>Chris: /* Killing a program */

2010-09-30T00:28:50Z

Killing a program

← Older revision		Revision as of 00:28, 30 September 2010
Line 53:		Line 53:
	The ‘kill’ command is used to forcefully end a process that is not responding. Technicians can kill the inactivity or session timer(s) when working on a particular workstation and don’t want to be bothered with timers or pop-ups.		The ‘kill’ command is used to forcefully end a process that is not responding. Technicians can kill the inactivity or session timer(s) when working on a particular workstation and don’t want to be bothered with timers or pop-ups.

	To kill a program you must first find the process id (PID), type the following command~~(s)~~ to receive a list of processes and their PIDs ~~use the command~~ <font class="code">~~‘ps~~ aux ~~\| grep cmon_’</font> , <font class="code">‘ps aux \| grep pacrez_’~~</font>. The first column is the user running the process, the second column is the PID. To kill a particular process type <font class="code">kill [pid]</font>, if the process refuses, type <font class="code">kill -9 [pid]</font> for a more forceful attempt.		To kill a program you must first find the process ID (PID); type the following command to receive a list of processes and their PIDs <font class="code">ps aux</font>. The first column is the user running the process, the second column is the PID. To kill a particular process type <font class="code">kill [pid]</font>, if the process refuses, type <font class="code">kill -9 [pid]</font> for a more forceful attempt.

			If you know the name of the application you want to kill, you can add the grep command followed by the program name to only display that program. For example, to search for the PID for Firefox, type <font class="code">ps aux \| grep firefox</font>; this will display results for any application named firefox.

	To kill just the inactivity timer, type <font class="code">kill xautolock</font>, type <font class="code">kill pacrez</font> to kill the session timer.		To kill just the inactivity timer, type <font class="code">kill xautolock</font>, type <font class="code">kill pacrez</font> to kill the session timer.

imported>Chris at 05:01, 29 September 2010

2010-09-29T05:01:59Z

← Older revision		Revision as of 05:01, 29 September 2010
Line 20:		Line 20:
	''Note: options can be case-sensitive, -r and -R are not the same to xterm; this can give unexpected results.''		''Note: options can be case-sensitive, -r and -R are not the same to xterm; this can give unexpected results.''

	== Common ~~xterm~~ Commands ==		== Common Commands ==
	cd              command alone will navigate to the root directory, add a path to navigate to a specific folder (ex. cd /etc/Groovix/)<br />		cd              command alone will navigate to the root directory, add a path to navigate to a specific folder (ex. cd /etc/Groovix/)<br />
	clear           clears the screen of previous information<br />		clear           clears the screen of previous information<br />

imported>Chris at 04:56, 29 September 2010

2010-09-29T04:56:48Z

← Older revision		Revision as of 04:56, 29 September 2010
Line 32:		Line 32:
	ping            pings a system ''Note: filtered webs will not respond'' <br />		ping            pings a system ''Note: filtered webs will not respond'' <br />
	rm              delete a file<br />		rm              delete a file<br />
	shutdown    shuts down the computer (requires a time) (-r option ~~will~~ reboot)<br />		shutdown    shuts down the computer (requires a time) (-r option to reboot, -h option to halt)<br />
	su              switch user<br />		su              switch user<br />
	xkill            changes the mouse cursor to an x, click on a window to close that window/program<br />		xkill            changes the mouse cursor to an x, click on a window to close that window/program<br />

imported>Chris at 04:55, 29 September 2010

2010-09-29T04:55:17Z

← Older revision		Revision as of 04:55, 29 September 2010
Line 6:		Line 6:
	The terminal command line interface (or terminal) is non-graphical and used by typing individual commands for each task. Tasks such as navigating directories or folders, editing text files, moving/copying files are all done with typed commands. This might seem slow or obsolete compared to a modern graphical interface, but the terminal interface is capable of incredibly complex commands that can automate many tasks with one line of commands. ''The terminal interface used in Groovix is known as xterm, both terminal and xterm can be used interchangeably. From now on, this wiki will only be using xterm when referencing the terminal interface.''		The terminal command line interface (or terminal) is non-graphical and used by typing individual commands for each task. Tasks such as navigating directories or folders, editing text files, moving/copying files are all done with typed commands. This might seem slow or obsolete compared to a modern graphical interface, but the terminal interface is capable of incredibly complex commands that can automate many tasks with one line of commands. ''The terminal interface used in Groovix is known as xterm, both terminal and xterm can be used interchangeably. From now on, this wiki will only be using xterm when referencing the terminal interface.''

	When working with xterm, ~~log~~ in as the ~~root~~ user. To identify which user is logged in, find the current line in the xterm window; it will be displayed as user name @ workstation name (ex. gvuser@inet-7). To change which user is logged in, type <font class="code">su ~~root~~</font> and press '''[ENTER]'''; ~~login~~ will be successful once the password for that user is entered.		When working with xterm, pay attention to the user; different user accounts have different privileges which can give unexpected results or deny commands. To identify which user is logged in, find the current line in the xterm window; it will be displayed as user name @ workstation name (ex. gvuser@inet-7). To change which user is logged in, type <font class="code">su [username]</font> where [username] is the user you want to log in as and press '''[ENTER]'''; log-in will be successful once the password for that user is entered.

	== Using Commands ==		== Using Commands ==

imported>Chris at 04:48, 29 September 2010

2010-09-29T04:48:58Z

← Older revision		Revision as of 04:48, 29 September 2010
Line 1:		Line 1:
			__TOC__

	<div class="dashed-box">Note: The terminal interface can be a very powerful tool, it is recommended for advanced technicians that are comfortable working with a 'Command Line Interface'.</div>		<div class="dashed-box">Note: The terminal interface can be a very powerful tool, it is recommended for advanced technicians that are comfortable working with a 'Command Line Interface'.</div>

Line 42:		Line 44:

	== Editing text files ==		== Editing text files ==
	There are two types of text editors to use in xterm; vi and nano. To use nano, type <font class="code">nano</font> ~~followed~~ by the file you would like to open and press ~~enter~~.		There are two types of text editors to use in xterm; vi and nano. To use nano, type <font class="code">nano [filename]</font> where [filename] is the file you would like to open and press '''[ENTER]'''.

	The terminal screen will be replaced by the contents of the file, at the bottom (in red) are the commands available. Each command is represented by a ‘^’ and a letter (^ = CTRL); press both ~~the~~ CTRL ~~key~~ and the letter to perform that command. To quit the nano editor, press CTRL+X; if prompted to save changes press ~~‘y’~~ for yes, ~~‘n’~~ for no. If yes is selected a path to the document is displayed, to save to another location type the path, otherwise, press enter to overwrite the file you are editing.		The terminal screen will be replaced by the contents of the file, at the bottom (in red) are the commands available. Each command is represented by a ‘^’ and a letter (^ = CTRL); press both '''[CTRL]''' and the letter to perform that command. To quit the nano editor, press '''[CTRL+X]'''; if prompted to save changes press '''[Y]''' for yes, '''[N]''' for no. If yes is selected a path to the document is displayed, to save to another location type the path, otherwise, press enter to overwrite the file you are editing.

	The vi editor is an advanced text editor, it is recommended to use nano unless you are familiar with vi. To use vi, type ~~‘vi’~~ ~~followed~~ by the file you would like to open and press ~~enter~~. To quit the vi editor type <font class="code">:q</font> and press ~~enter~~.		The vi editor is an advanced text editor, it is recommended to use nano unless you are familiar with vi. To use vi, type <font class="code">vi [filename]</font> where [filename] is the file you would like to open and press '''[ENTER]'''. To quit the vi editor type <font class="code">:q</font> and press '''[ENTER]'''.

	== Killing a program ==		== Killing a program ==
	The ‘kill’ command is used to forcefully end a process that is not responding. Technicians can kill the inactivity or session timer(s) when working on a particular workstation and don’t want to be bothered with timers or pop-ups.		The ‘kill’ command is used to forcefully end a process that is not responding. Technicians can kill the inactivity or session timer(s) when working on a particular workstation and don’t want to be bothered with timers or pop-ups.

	To kill a program you must first find the process id (PID), type the following command(s) to receive a list of processes and their PIDs use the command <font class="code">‘ps aux \| grep cmon_’ , <font class="code">‘ps aux \| grep pacrez_’</font>. The first column is the user running the process, the second column is the PID. To kill a particular process type <font class="code">kill [pid]</font>, if the process refuses, type <font class="code">kill -9 [pid]</font> for a more forceful attempt.		To kill a program you must first find the process id (PID), type the following command(s) to receive a list of processes and their PIDs use the command <font class="code">‘ps aux \| grep cmon_’</font> , <font class="code">‘ps aux \| grep pacrez_’</font>. The first column is the user running the process, the second column is the PID. To kill a particular process type <font class="code">kill [pid]</font>, if the process refuses, type <font class="code">kill -9 [pid]</font> for a more forceful attempt.

	To kill just the inactivity timer, type <font class="code">kill xautolock</font>, type <font class="code">kill pacrez</font> to kill the session timer.		To kill just the inactivity timer, type <font class="code">kill xautolock</font>, type <font class="code">kill pacrez</font> to kill the session timer.

imported>Chris at 04:44, 29 September 2010

2010-09-29T04:44:08Z

← Older revision		Revision as of 04:44, 29 September 2010
Line 11:		Line 11:
	''Note: adding ‘--help’ after a command will display the command description and options available for that command.''		''Note: adding ‘--help’ after a command will display the command description and options available for that command.''

	* Some commands require extra information such as a time or path, these come after any options. For example, the <font class="code">shutdown</font> command requires a time indicated for when the shutdown should occur (ex. <font class="code">shutdown -r now</font>).		Some commands require extra information such as a time or path, these come after any options. For example, the <font class="code">shutdown</font> command requires a time indicated for when the shutdown should occur (ex. <font class="code">shutdown -r now</font>).

	== Using Options ==		== Using Options ==
Line 23:		Line 23:
	cp              make a copy of a file<br />		cp              make a copy of a file<br />
	eject           ejects a CD-ROM or removable device<br />		eject           ejects a CD-ROM or removable device<br />
	exit            closes an xterm window (also used to log out of an SSH session)<br />		exit             closes an xterm window (also used to log out of an SSH session)<br />
	ifconfig        displays network adapters and their properties<br />		ifconfig        displays network adapters and their properties<br />
	ls              lists files and folders in the current directory<br />		ls                lists files and folders in the current directory<br />
	more~~ ~~           outputs large file contents one page at a time, spacebar will advance one page until finished<br />		more           outputs large file contents one page at a time, spacebar will advance one page until finished<br />
	mv              move a file<br />		mv              move a file<br />
	ping            pings a system ''Note: filtered webs will not respond'' <br />		ping            pings a system ''Note: filtered webs will not respond'' <br />
	rm              delete a file<br />		rm              delete a file<br />
	shutdown~~    ~~    shuts down the computer (requires a time) (-r option will reboot)<br />		shutdown    shuts down the computer (requires a time) (-r option will reboot)<br />
	su              switch user<br />		su              switch user<br />
	xkill           changes the mouse cursor to an x, click on a window to close that window/program<br />		xkill            changes the mouse cursor to an x, click on a window to close that window/program<br />

	Copy and Paste ~~in xterm:~~		== Copy and Paste ==
	To copy text in an xterm window, highlight the information to be copied and click the middle mouse button at the end of the highlighted text. To paste text in an xterm window, click the middle mouse button, the text will be pasted wherever the cursor is.		To copy text in an xterm window, highlight the information to be copied and click the middle mouse button at the end of the highlighted text. To paste text in an xterm window, click the middle mouse button, the text will be pasted wherever the cursor is.

	Note: while copying in PuTTY works just like xterm, pasting does not. To paste in PuTTY, right click the mouse.

	xterm Tips:		xterm Tips:
Line 43:		Line 41:
	- the tab key will auto complete a file or folder name based on the first few characters typed.		- the tab key will auto complete a file or folder name based on the first few characters typed.

		⚫	== Editing text files ==
		⚫	There are two types of text editors to use in xterm; vi and nano. To use nano, type <font class="code">nano</font> followed by the file you would like to open and press enter.

		⚫	The terminal screen will be replaced by the contents of the file, at the bottom (in red) are the commands available. Each command is represented by a ‘^’ and a letter (^ = CTRL); press both the CTRL key and the letter to perform that command. To quit the nano editor, press CTRL+X; if prompted to save changes press ‘y’ for yes, ‘n’ for no. If yes is selected a path to the document is displayed, to save to another location type the path, otherwise, press enter to overwrite the file you are editing.
⚫	~~Section 6.2:~~ Editing text files ~~in xterm~~
	There are two types of text editors to use in xterm; vi and nano.

⚫	To use nano, type ~~‘nano’~~ followed by the file you would like to open and press enter.



⚫	The terminal screen will be replaced by the contents of the file, at the bottom (in red) are the commands available. Each command is represented by a ‘^’ and a letter (^ = CTRL); press both the CTRL key and the letter to perform that command. To quit the nano editor, press CTRL+X; if prompted to save changes press ‘y’ for yes, ‘n’ for no. If yes is selected a path to the document is displayed, to save to another location type the path, otherwise, press enter.

⚫	The vi editor is an advanced text editor, it is recommended to use nano unless you are familiar with vi. To use vi, type ‘vi’ followed by the file you would like to open and press enter. To quit the vi editor type ‘:~~’ followed by~~ q and press enter.

		⚫	The vi editor is an advanced text editor, it is recommended to use nano unless you are familiar with vi. To use vi, type ‘vi’ followed by the file you would like to open and press enter. To quit the vi editor type <font class="code">:q</font> and press enter.
	Section 6.3: Killing a program
⚫	The ‘kill’ command is used to forcefully end a process that is not responding. ~~Systems technicians~~ can kill the inactivity or session timer(s) when working on a particular workstation and don’t want to be bothered with timers or pop-ups.

	Killing a ~~process in~~ ~~xterm:~~		== Killing a program ==
		⚫	The ‘kill’ command is used to forcefully end a process that is not responding. Technicians can kill the inactivity or session timer(s) when working on a particular workstation and don’t want to be bothered with timers or pop-ups.
	To kill a program you must first find the process id (PID), type the following command(s) to receive a list of processes and their PIDs: ‘ps aux \| grep cmon_’ , ‘ps aux \| grep pacrez_’

	The first column is the user running the process, the second column is the PID. To kill a particular process type ~~‘kill~~ [pid]’, if the process refuses, type ~~‘kill~~ -9 [pid]’ for a more forceful attempt.		To kill a program you must first find the process id (PID), type the following command(s) to receive a list of processes and their PIDs use the command <font class="code">‘ps aux \| grep cmon_’ , <font class="code">‘ps aux \| grep pacrez_’</font>. The first column is the user running the process, the second column is the PID. To kill a particular process type <font class="code">kill [pid]</font>, if the process refuses, type <font class="code">kill -9 [pid]</font> for a more forceful attempt.

	To kill just the inactivity timer, type ~~‘kill~~ ~~xautolock’~~, type ~~‘kill~~ ~~pacrez’~~ to kill the session timer.		To kill just the inactivity timer, type <font class="code">kill xautolock</font>, type <font class="code">kill pacrez</font> to kill the session timer.

	Killing a program in the Groovix GUI:		=== Killing a program in the Groovix GUI ===
	If you can’t find the PID or have the process you want to kill open in the desktop, open a new xterm window and type ~~‘xkill’~~; this will change the mouse cursor to an X and will kill the first process window you click on with your mouse.		If you can’t find the PID or have the process you want to kill open in the desktop, open a new xterm window and type <font class="code">xkill</font>; this will change the mouse cursor to an X and will kill the first process window you click on with your mouse.