Changes

:* Understand Define the term '''i-node''' as it relates to the purpose and why links are used in Unix / LinuxFile System

:* Define Issue the term '''inodels -i''' number as it relates command to a file on view '''i-node''' (index) numbers associated with Unix / Linuxfiles

:* Define the terms: '''Hard''' Link and '''Symbolic''' LinkLinks

:* Issue the '''<span style="font-family:courier">ln</span>''' command to create '''hard ''' and '''symbolic ''' links

:* Define and understand the purpose of a term '''process''' in as it relates to the Unix / Linuxoperating system

|colspan="2" |Course Notes'''Slides:'''<ul><li>Week 8 Lecture 1 Notes:<br>[https://ictwiki.cdot.senecacollege.ca/~murrayuli101/slides/ULI101-8.1.pdf PDF] | [https://wiki.saulcdot.senecacollege.ca/uli101/slides/ULI101-Week78.1.pptx PPTX]</li><li>Week 8 Lecture 2 Notes:<br> [https://wiki.cdot.senecacollege.ca/uli101/slides/ULI101-8.2.pdf PDF] | [https://ictwiki.cdot.senecacollege.ca/~murray.saululi101/uli101slides/ULI101-Week88.2.pptx PPTX]<br></li></ul>

| style="padding-left:15px;" |'''Links:'''* [http://www.linfo.org/hard_link.html#:~:text=A%20hard%20link%20is%20merely,created%20to%20other%20hard%20links. Hard Links]* [https://www.computerhope.com/jargon/s/symblink.htm#:~:text=Alternatively%20referred%20to%20as%20a,or%20directory%20using%20its%20path.&text=In%20Linux%20and%20Unix%20symbolic,created%20using%20the%20mklink%20command. Symbolic Links]<br>'''Managing Processes:'''* Process Information [https://en.wikipedia.org/wiki/Inode inode] * [https://opensource.com/article/18/9/linux-commands-process-management Manipulating Processes* Running commands / programs in background with &]

| style="padding-left:15px;"|'''Linux Commands:'''

|colspan="1" style="padding-left:15px;" width="30%"|'''Brauer Instructional Videos:'''<ul><li>[https://www.youtube.com/watch?v=tZ94-qH9unM&list=PLU1b1f-2Oe90TuYfifnWulINjMv_Wr16N&index=9 Inodes and Links]</li><li>[https://www.youtube.com/watch?v=q93POTgH-aQ&list=PLU1b1f-2Oe90TuYfifnWulINjMv_Wr16N&index=7 Processes and Jobs]</li></ul>

===Linking Files=== ''Links are powerful and add flexibility to Linux filesystems because everything is a file.<br><br>There are two types of Linux filesystem links: hard and soft. The difference between the two types of links is significant, but both types are used to solve similar problems. They both provide multiple directory entries (or references) to a single file, but they do it quite differently.'' <br><br>Reference: https://opensource.com/article/17/6/linking!-linux-filesystem  '''inode (index) Number of a File:'''

<table align="right"><tr valign="top"><td>[[Image:inode-number-1.png|thumb|right|300px|Each inode stores the attributes and disk block locations of the object's data.<br>(Image licensed under [https://creativecommons.org/licenses/by-sa/3.0/ cc])]]</td><td>[[Image:inode-number-2.png|thumb|right|360px|The '''inode number''' is like a '''finger-print''', and usually is considered to be '''unique''' for each file on the Unix / Linux file system.]]</td></tr></table>

The '''inode number''' is like a '''finger-print''', and usually is '''unique''' for each file on the Unix / Linux file system.<br>Referring to the diagram on the far right, issuing the '''ls''' command with the '''===i-i''' option<br>displays the inode number for each file. You can see that <u>each</u> file<br>node (whether it is index) ID Number of a directory or regular file) has its own unique inode number.File===

[[Image:hard-link-1.png|thumb|right|300px|A '''Hard Linkslink''' is a file which is created that shares the '''same i-node number''' with the <u>original</u> file<br>(Image licensed under [https://creativecommons.org/licenses/by-sa/3.0/ cc])<br>Image manipulated by author]]A '''Hard link''' is a '''reference''' to the physical data on a file system.<br>It does this by creating a file that shares the '''same i-node number'''with the <u>original</u> file.

'''Advantages:''' of hard links are that if If only one hard link remains (even if original file has been removed), the '''data in that hard linked file is NOT lost, a '''. The data in hard links will automatically change when a change to that original file or hard links occur since they share the same linked files are '''i-node numberautomatically updated'''<br>and the Unix/Linux OS treats them all as the same when original fileare updated.

'''Disadvantages:''' of hard Hard links are that they '''take-up extra space''',<br>you '''cannot hard link directory filesdirectories''', <br>and you '''cannot hard link files from other Unix/Linux servers<br>''' (since the inode number may already be used by the other Unix/Linux server).

<span style="font-family:courier">'''touch myfile.txt<br>ln myfile.txt myfile1.hard.lnk<br>ln myfile.txt myfile2.hard.lnk<br>ln myfile.txt ~/backups/myfile.hard.lnk<br>'''</span> 

[[Image:symbolic-link-1.png|thumb|right|300px|A '''Symbolic LinksLink''' is an indirect '''pointer''' to a file and are also known as '''soft''' link or '''symlink'''. The symbolic link file contains the pathname to the original file. (Image licensed under [https://creativecommons.org/licenses/by-sa/3.0/ cc])]]A '''Symbolic Link''' is an indirect '''pointer''' to a file and are also known as '''soft''' link or '''symlink'''. The symbolic link file contains the '''pathname'''to the original file.

'''Advantages:''' of symbolic links are that they are '''shortcuts ''' to other files, where the symbolic link only contains the pathname to the original file, you '''can create symbolic links'''<br>'''on different Unix/Linux servers''', and that you '''can create symbolic links for directories'''.

'''Disadvantages:''' of symbolic Symbolic links are that they are NOT good for backup purposes<br>since a symbolic link can point to a nonexistent file (referred to as a "broken link").

<span style="font-family:courier">'''touch otherfile.txt<br>ln -s otherfile.txt otherfile1.sym.lnk<br>ln -s otherfile.txt otherfile2.sym.lnk<br>ln -s otherfile.txt ~/backups/otherfile.sym.lnk<br>'''</span>

All programs that are executing on <br>'''Aliases:'''<br><br>An '''alias''' is a UNIX '''nickname''' to an existing command or group of commands.<br><br>An alias existing in '''system are referred to as memory''' and will be '''lost''' when your current Linux session ends,<br>unless the alias is set in a '''processesstart-up file'''(e.g. <span style="font-family:courier;font-weight:bold;">~/.bashrc</span>. You will learn about using start-up files <u>later</u> in this course.<br><br>

* Each process has an ''Examples:'owner'''* Each process has a unique ID (PID) Processes in UNIX can run in the '''foreground''' or '''background'''.

[[Image<span style="font-family:process-diagramcourier;font-1.png|thumb|right|300px|(Image licensed under [httpsweight://creativecommons.org/licenses/bybold;>alias dir=ls<br>alias ls='ls -saal'<br>alias clearfile='cat /3.0dev/ cc])]]]UNIX processes are null >'''hierarchical''':</span>

* The process structure has a '''root<span style="font-family:courier;font-weight:bold;>unalias alias-name</span>''', '''parents''', and '''children'''* Creation of a new process is called '''forking''' or '''spawning'''* Each process has its own '''PID''' (''process ID number'')* The Parent process can spawn a child and children can spawn their own children* Processes keep their '''PID''' for their entire life* Usually a parent sleeps when a child is executing (the exception is when the child process is executing in the backgroundremoves alias from memory)

Below are some common Linux '''Command History:'''<br><br>The filename <span style="font-family:courier;font-weight:bold;>~/.bash_history</span> stores recently executed command lines<br><br>''Examples of commands involving processesthat use command history:''

<table cellpaddingwidth="80%"><tr valign="5top" ><td width="6030%"><tr><th span style="borderfont-bottomfamily: 1px solid blackcourier;textfont-alignweight:leftbold;">Linux Commandup arrow</thspan>or <th span style="borderfont-bottomfamily: 1px solid blackcourier;textfont-alignweight:leftbold;">Purposedown arrow</thspan> </tr><tr valign="top"><td>'''ps'''</td><td>The ''move to 'ps''previous' (''process status'') command displays snapshot information about processes. By default, the ps command displays information only about the current terminal<br>(or '''ps -lnext''' provides a detailed listing, '''ps -U''' username shows allcommand within Bash shell prompt<br/td>''Examples:''<br/tr><brtr></td></tr><tr valignspan style="top"font-family:courier;font-weight:bold;>fc -l<td/span>'''top'''</td><td>The '' display last 'top''16' command provides a continuous update including resource usage<br>''Examples:''<br>commands</td></tr><tr><td>'''fg'''<span style="font-family:courier;font-weight:bold;>history | more</tdspan></td>The '''fg''' (foreground) command moves a background job from the current environment into the foreground.<brtd>''Examples:''display all stored commands</td></tr><tr valign><td><span style="top"font-family:courier;font-weight:bold;>!num<td/span>'''bg'''</td><td>the '''bgre-execute''' utility shall resume suspended jobs an issued command number by command number (determined from the current environment.<br>''Examples:history''command)</td></tr><tr valign><td><span style="top"font-family:courier;font-weight:bold;>!xxx<td/span>'''jobs'''</td><td>The '''jobsre-run''' utility shall display the status of jobs that were started in the current shell environment<br>''Examples:''a most recent previously-issued command beginning with string "xxx"</td></tr><tr><td>'''kill'''</tdtable><td>The command kill sends the specified signal to the specified processes or process groups.<br>If no signal is specified, the TERM signal is sent. The default action for this signal is to terminate the process.<br>''Examples:''</td></tr></table>

<brspan style="color:red;">In this section, you '''ATTENTION''': This online tutorial will learn how be required to ...be completed by '''Friday in week 9 by midnight''' to obtain a grade of '''2%''' towards this course</span><br><br>

# '''Perform Login''' to your matrix account.<br><br># Issue a Linux command to '''confirm''' you are located in your '''home''' directory.<br><br>'''NOTE:''' You will remain in your '''home''' directory to get practice using pathnames.<br><br># Issue the following Linux command to create a directory called '''~/links''':<br><span style="color:blue;font-weight:bold;font-family:courier;">mkdir ~/links</span><br><br># Issue the '''ls -ld''' command to confirm that the directory '''~/links''' exists.<br><br># Use a text editor to create a file called <span style="font-weight:bold;font-family:courier;">~/links/data-file.txt </span><br>(i.e. <u>without</u> changing to the links directory).<br><br># Enter the following text displayed below:<br><br><span style="font-family:courier;font-weight:bold;">This is line 1<br>This is line 2<br>This is line 3<br><br></span>[[Image:hard-link-inode1.png|thumb|right|450px|'''Hard links''' <u>share</u> the same '''i-node''' with regular files on a Unix / Linux filesystem.]]# Save your editing session and exit your text editor.<br><br># Issue the following Linux command:<br><span style="color:blue;font-weight:bold;font-family:courier;">ls -li ~/links/data-file.txt</span><br><br>View the '''i-node''' number for this file. What does this ''i-node'' number represent?<br><br>We will now create a '''hard link''' file to demonstrate how creating hard links are useful for '''back-ups'''.<br><br># Issue the following Linux command to create the following '''hard link''' in the same directory: <br><span style="color:blue;font-weight:bold;font-family:courier;">ln ~/links/data-file.txt ~/links/data-file.hard.lnk</span><br><br># Issue the following Linux command to display ''i-node'' ID numbers for <u>both</u> files:<br><span style="color:blue;font-weight:bold;font-family:courier;">ls -li ~/links/data-file.txt ~/links/data-file.hard.lnk</span><br><br>What do you notice about both of those file's ''i-node'' numbers?<br><br># Use a text editor to edit <span style="font-weight:bold;font-family:courier;">~/links/data-file.txt</span><br>and '''add some lines of text''' to the <u>bottom</u> of that file.<br><br># Save your editing session and exit your text editor.<br><br># Issue the following Linux command: <br><span style="color:blue;font-weight:bold;font-family:courier;">cat ~/links/data-file.hard.lnk</span><br><br>You should notice that the hard linked file also contains the additional line(s) that you added to the <u>original</u> file.<br>This is very useful for backing up your files <u>without</u> using the '''cp''' command!<br><br># Use a text editor to edit the hard-linked file <span style="font-weight:bold;font-family:courier;">~/links/data-file.hard.lnk</span><br>and add some lines to the bottom of this file.<br><br># Save your editing session and exit your text editor.<br><br># Issue the following Linux command: <br><span style="color:blue;font-weight:bold;font-family:courier;">cat ~/links/data-file.txt</span><br><br>What happened to this '''original''' file?</u> file?<br>What does this mean in terms of creating hard-linked files for back-ups?<br><br># Issue the following Linux command to create a hard-linked file in your '''home''' directory:<br><span style="color:blue;font-weight:bold;font-family:courier;">ln ~/links/data-file.txt ~/data-file.hard.lnk<br><br># Issue the following Linux command to compare all file's ''i-node'' numbers:<br><span style="color:blue;font-weight:bold;font-family:courier;">ls -li ~/links/data-file.txt ~/links/data-file.hard.lnk ~/data-file.hard.lnk</span><br><br>What do you notice about all of those file's ''i-node'' numbers?<br><br># Issue the following Linux command to check that you created those hard links: <br><span style="color:blue;font-weight:bold;font-family:courier;">~uli101/week8-check-1</span><br><br>If you encounter errors, then view the feedback to make corrections, and then re-run the checking script.<br>If you receive a congratulation message that there are no errors, then proceed with this tutorial.<br><br># Issue the following Linux command to remove the '''~/links''' directory and its contents: <br><span style="color:blue;font-weight:bold;font-family:courier;">rm -rf ~/links</span><br><br># Issue a Linux command to confirm that the '''~/links''' directory has been removed.<br><br># Issue the following Linux command to view the contents of your linked file in your '''home''' directory:<br><span style="color:blue;font-weight:bold;font-family:courier;">cat ~/data-file.hard.lnk</span><br><br>What do you notice? What does this tell you about hard links?<br><br>We will now learn how to create '''symbolic links'''.<br><br># Issue the following Linux command to create a directory called '''~/links2''':<br><span style="color:blue;font-weight:bold;font-family:courier;">mkdir ~/links2</span><br><br>'''NOTE:''' You will remain in your '''home''' directory to get practice using pathnames.<br><br># Issue the <span style="font-weight:bold;font-family:courier;">ls -ld</span> command to confirm that the directory called '''~/links2''' exists.<br><br># Use a text editor to create a file called <span style="font-weight:bold;font-family:courier;">~/links2/text-file.txt</span><br>(i.e. <u>without</u> changing to the '''links2''' directory). <br><br>[[Image:symbolic-link-inode1.png|thumb|right|500px|'''Symbolic links''' are '''pointers''' (i.e. pathnames) to '''regular files''' and '''directories'''.<br>They do '''NOT''' share the same '''i-node'''.]]# Enter the following text displayed below:<br><br><span style="font-family:courier;font-weight:bold;">This is line one<br>This is line two<br>This is line three<br><br></span># Save your editing session and exit your text editor.<br><br># Issue the following Linux command to create the following '''symbolic''' link in the same directory: <br><span style="color:blue;font-weight:bold;font-family:courier;">ln -s ~/links2/text-file.txt ~/links2/text-file.sym.lnk</span><br><br># Issue the following Linux command to display ''i-node'' numbers for <u>both</u> files:<br><span style="color:blue;font-weight:bold;font-family:courier;">ls -li ~/links2/text-file.txt ~/links2/text-file.sym.lnk</span><br><br>What do you notice about both of these file's ''i-node'' numbers?<br>What do you notice about the size of the file <span style="font-weight:bold;font-family:courier;">~/links2/text-file.sym.lnk''</span>?<br>What '''pathname''' do you think this ''symbolic-linked'' file represents?<br><br># Issue the following Linux command to create the following '''symbolic link''' in your '''home''' directory: <br><span style="color:blue;font-weight:bold;font-family:courier;">ln -s ~/links2/text-file.txt ~/text-file.sym.lnk</span><br><br># Issue the following Linux command to display ''i-node'' numbers for all of those files:<br><span style="color:blue;font-weight:bold;font-family:courier;">ls -li ~/links2/text-file.txt ~/links2/text-file.sym.lnk ~/text-file.sym.lnk</span><br><br>What do you notice about all of those file's i-node numbers?<br>What is the file size of <span style="font-weight:bold;font-family:courier;">~/text-file.sym.lnk</span>?<br>What '''pathname''' do you think this ''symbolic-linked'' file contains?<br><br># Use a text editor to edit the '''symbolic''' link file called <span style="font-weight:bold;font-family:courier;">~/links2/text-file.sym.lnk</span><br>and add some lines to the Following Stepsbottom of that file.<br><br># Save your editing session and exit your text editor.<br><br># Issue the following Linux command to view the contents of the '''original''' file:<br><span style="color:blue;font-weight:bold;font-family:courier;">cat ~/links2/text-file.txt</span><br><br>What did you notice? This happened because when you edited the symbolic-linked file,<br>you were redirected (via ''pathname'') to the <u>original</u> file.<br><br># Use a text editor to edit the '''original''' file called <span style="font-weight:bold;font-family:courier;">~/links2/text-file.txt</span><br>and add some lines to the bottom of that file.<br><br># Save your editing session and exit your text editor.<br><br># Issue the following Linux command to view the contents of the '''symbolic''' linked file:<br><span style="color:blue;font-weight:bold;font-family:courier;">cat ~/links2/text-file.sym.lnk</span><br><br>What did you notice? Again, when you view the contents of the symbolic-linked file,<br>you are redirected (via ''pathname'') to the <u>original</u> file.<br><br># Issue the following Linux command to check that you created those symbolic links: <br><span style="color:blue;font-weight:bold;font-family:courier;">~uli101/week8-check-2</span><br><br>If you encounter errors, then view the feedback to make corrections, and then re-run the checking script.<br>If you receive a congratulation message that there are no errors, then proceed with this tutorial.<br><br># Issue the following Linux command to remove the '''~/links2''' directory: <br><span style="color:blue;font-weight:bold;font-family:courier;">rm -rf ~/links2</span><br><br># Issue a Linux command to confirm that the '''~/links2''' directory has been removed.<br><br># Issue the following Linux command to view the contents of the<br>'''original''' file called <span style="font-weight:bold;font-family:courier;">~/links2/text-file.txt:</span><br><span style="color:blue;font-weight:bold;font-family:courier;">cat ~/text-file.sym.lnk</span><br><br>What happened? Why did does this happen?<br><br>[[Image:symbolic-link-inode3.png|thumb|right|500px|Example of a '''broken link''' when a symbolic link points to a '''non-existent file'''.]]# Issue the following Linux command: <br><span style="color:blue;font-weight:bold;font-family:courier;">ls -l ~/text-file.sym.lnk</span><br><br>This output indicates a "'''broken link'''" and indicates this is not an effective method of backing up files.<br><br># Issue a command to delete the <span style="font-weight:bold;font-family:courier;">~/text-file.sym.lnk</span> file which is a ''broken link''.<br><br># Issue the following Linux command:<br><span style="color:blue;font-weight:bold;font-family:courier;">ln -s ~jason.carman/example t8example</span><br><br>[[Image:symbolic-link-inode2.png|thumb|right|500px|'''Symbolic links''' can be used to point to '''directories''' as well as regular files. Symbolic links can also point to files on '''other''' Unix/Linux filesystems.]]# Issue the following Linux command:<br><span style="color:blue;font-weight:bold;font-family:courier;">ls -ld t8example</span><br><br>What do you notice? Symbolic links are good for creating "short-cuts" to <u>both</u> '''regular files''' and '''directories'''.

:In the next investigation, you will ..learn how to '''manage processes''' on your Matrix server.<br><br>

In this sectioninvestigation, you will learn how to '''manage processes''' on a Unix / Linux server.  '''Perform the Following Steps:''' # Make certain that you are logged into your Matrix account.<br><br># Issue a Linux command to confirm that you are located in your '''home''' directory.<br><br>The '''sleep''' command '''pauses for a specified number of seconds''' before returning to the shell prompt.<br>In this tutorial, we will be using this command to '''simulate''' the management of "long-running" processes.<br><br># Issue the following Linux command: <span style="color:blue;font-family:courier;font-weight:bold">sleep 700</span><br><br>Notice that this process will run for '''700 seconds''', and is forcing the user to '''wait''' until this process finishes.<br>A process that is '''running in the terminal''' is referred to as a '''foreground processes'''.<br><br>The Unix/Linux system is designed to allow users to send '''preemptive signals''' to manage those processes.<br><br># Press the following '''key combination''' to '''terminate''' the command running on the terminal: <span style="color:blue;font-family:courier;font-weight:bold">ctrl-c</span><br><br>You should notice that the process that was running in the foreground has been '''interrupted''' (i.e. terminated).<br>'''NOTE:''' The '''ctrl-c''' key combination sends '''SIGINT''' ('''Signal Interrupt''' - which is signal '''#2''')<br>to ''terminate'' a process that is running on the terminal (i.e. a '''foreground''' process).<br><br># Reissue the Linux command: <span style="color:blue;font-family:courier;font-weight:bold">sleep 700</span><br><br># Press the '''key combination''': <span style="color:blue;font-family:courier;font-weight:bold">ctrl-z</span><br><br>[[Image:process-jobs1.png|thumb|right|300px|Running a command in the terminal, pressing '''ctrl-z''' to place into the background, and issuing the '''jobs''' command to view processes in the background.]]# You should now see output similar to what is displayed below:<br><span style="font-family:courier;font-weight:bold">[1]+ Stopped sleep 700</span><br><br>'''NOTE:''' This indicates that this process has been placed into the '''background'''.<br>This is useful in order to "'''free-up'''" the terminal to run other Linux commands.<br><br># Issue the following Linux command: <span style="color:blue;font-family:courier;font-weight:bold">jobs</span><br><br>You should see the following output similar that was displayed above:<br><span style="font-family:courier;font-weight:bold">[1]+ Stopped sleep 700</span><br><br>This display indicates that this process (that is now in the background) has '''stopped'''.<br>In other words, the ''sleep'' command is NOT counting-down to zero to terminate.<br><br>'''NOTE:''' You need to use the '''bg''' command to '''run''' that process that was sent into the '''background'''.<br><br>[[Image:process-jobs2.png|thumb|right|300px|Using the '''bg''' command to '''run recent process''' that was placed into background from using '''ctrl-z''' keys.]]# Issue the following Linux command: <span style="color:blue;font-family:courier;font-weight:bold">bg</span><br><br>'''NOTE:''' You can use the bg command WITHOUT arguments to run recent in the background. From the '''jobs''' command, the process that has a plus sign "+" indicates the most recent process placed into the background.<br><br># Issue the following Linux command: <span style="color:blue;font-family:courier;font-weight:bold">jobs</span><br><br>You should see the following output similar that was displayed above:<br><span style="font-family:courier;font-weight:bold">[1]+ sleep 700 &</span><br><br>This display indicates that this process in the background is '''running in the background'''<br>(indicated by the ampersand character "'''&'''"). Now this command has resume pausing until '''700 seconds'''.<br><br>[[Image:process-jobs3.png|thumb|right|300px|Using the '''ampersand''' character '''&''' to run a '''series of processes''' in the background.]]# Issue the following Linux command: <span style="color:blue;font-family:courier;font-weight:bold">fg</span><br><br>You should notice that the ''sleep'' command is now running in the '''foreground'''.<br><br> # Press the '''key combination''' to '''terminate''' the process running in the '''foreground''':<br><span style="color:blue;font-family:courier;font-weight:bold">ctrl-c</span> <br><br>You can issue Linux commands with ampersand "'''&'''" in your terminal to '''run''' processes automatically in the '''background''' <u>without</u> having to issue ''ctrl-z'' and ''bg'' short-cut keys.<br><br> # Issue the following Linux commands:<br><span style="color:blue;font-family:courier;font-weight:bold">sleep 500 & sleep 600 & sleep 700 &</span><br><br># Issue the '''jobs''' command. What do you notice?<br><br>In the jobs command output, jobs that display a plus sign ('''+''') indicates the '''most recent''' process<br>placed in to the background, and a minus sign ('''-''') indicates the '''second most recent''' process<br>placed into the background.<br><br>The '''kill''' command issued to terminate processes that are running in the '''foreground''' or '''background'''.<br>Issuing the kill command <u>without</u> options would send the '''SIGTERM''' signal (eg. ''signal terminate'' - which is signal '''#15''').<br><br>[[Image:process-jobs4.png|thumb|right|300px|Using the '''kill %1''' command to '''terminate''' job #1.]]# Issue the following Linux command to '''terminate''' the '''first''' job running in the background:<br><span style="color:blue;font-family:courier;font-weight:bold">kill %1</span><br><br>'''NOTE:''' You can specify job number preceded by percent % with the<br>'''kill''', '''bg''', and '''fg''' commands to specify the processes' job number.<br><br># Issue the '''jobs''' command. What do you notice?<br><br># Issue the following Linux commands:<br><span style="color:blue;font-family:courier;font-weight:bold">kill %2</span><br><span style="color:blue;font-family:courier;font-weight:bold">kill %3</span><br><br># Issue the '''jobs''' command (you may have to issue the ''jobs'' command several times to get final result).<br> What do you notice?<br><br>[[Image:process-jobs5.png|thumb|right|300px|Using round brackets to '''group''' a series of commands to be run as '''one process'''.]]# Let's use '''grouping''' to run several commands in sequence within a single process.<br><br># Issue the following Linux command:<br><span style="color:blue;font-family:courier;font-weight:bold">(sleep 400; sleep 500; sleep 600) &</span><br><br># Issue the '''jobs''' command. What do you notice?<br>You should notice all commands are run in a group as just one process.<br><br># Issue the following Linux command to terminate the first job running in the '''background''':<br><span style="color:blue;font-family:courier;font-weight:bold">kill %1</span><br><br>NOTE: If issuing the kill command does not work, then you would need to send a STRONGER signal<br>to "'''kill'''" (not "''SIGTERM'' - which is signal ''#15''") the process. The '''SIGKILL''' signal (signal '''#9''')<br>would be required to do this by issuing the '''kill''' command with the option: '''-9'''.<br><br># Issue the '''jobs''' command and make certain there are no processes that are running in the '''background'''.<br><br>You can also manipulate processes by their '''PID''' ('''process ID'''). Let's terminate our Matrix Bash shell process<br>by using the '''kill''' command using that processes' '''PID'''.<br><br># Issue the following Linux command: <span style="color:blue;font-family:courier;font-weight:bold">ps</span><br><br>#Note in the '''ps''' command output the PID of the process called '''bash'''.<br><br>You will be using that PID when issuing the <u>next</u> Linux command.<br><br># Issue the following Linux command (using the bash processes' PID number instead of "PID"):<br><span style="color:blue;font-family:courier;font-weight:bold">kill PID</span><br><br>What did you notice?<br><br>'''FYI:''' If the command did NOT work, issue the following Linux command (using the bash processes' PID number instead of "PID"):<br><span style="color:blue;font-family:courier;font-weight:bold">kill -9 PID</span><br><br>

<br>In this investigation, you will learn how to '''Perform the Following Steps:manage aliases'''and '''Linux command history''' on your Matrix account.

In '''Perform the next investigation, you will ...Following Steps:'''

https://ictwiki.cdot.senecacollege.ca/~murray.saululi101/uli101files/uli101_week8_practice.docx

# Hard Links:<ol type="a"><li>What is the purpose of creating a hard-link?</li><li>What is a limitation of a hard link?<li>Write a single Linux command to create a hard link called '''~/backup/myfile.txt.lnk''' to for the <u>existing </u> file called '''~/myfile.txt'''<br/li><li>Write a single Linux command to display detailed information the '''i-node''' number for those both files above displaying their . Are the '''i-node ''' numbers.identical?</li></ol><br>In this case, will # Symbolic (Soft) Links:<ol type="a"><li>What is the inode numbers for those files above be the same or differentpurpose of creating a symbolic (soft) link?</li><li>What is a limitation of a symbolic (soft) link?<br/li><brli># Write a single Linux command to create a symbolic link called '''~/shortcuts/murray.saul.lnk''' <br>to the <u>existing </u> directory called '''~murray.saul'''<br/li><li>Write a single Linux command to display detailed information for those files above displaying their Are the i-node numbers.<br>In this case, will the inode numbers identical for both of those files above be the same or different?<br/li><brli>What data is contained in the file called '''~/shortcuts/murray.saul.lnk'''?<br/li>What would be the size of the file called '''~</shortcuts/murray.saul.lnk'''?<brol><br># Background / Foreground Processes:<ol type="a"><li>Write a single Linux command to run the program called '''~/clean.sh''' in the '''background'''.<br/li><li>What Write a single Linux command would you issue to place the previously issued program in the '''foreground?'''.</li><brli>What Write a single Linux command would you issue to '''confirm ''' that this program is running in the background?.</li><brli>What '''key-combination ''' would you issue to send that program again into the '''background'''?</li><li>Write a single Linux command to have that process sent into the background to '''continue running'''?</li></ol><br># Managing Background processes:<br><span style="text-indent:120px;">Use the following diagram to answer the accompanying questions.<br>Each of the following questions will use the diagram below and are treated as independent situations.<br><br><span style="font-family:courier;font-weight:bold;">[1]&nbsp; Stopped vim a<br>[2]- Stopped vim b<br>[3]+ Stopped vim c</span></span><ol type="a"><li>Write a single Linux command to bring the second-recently process placed in the background into the '''foreground'''.</li><li>Write a single Linux command to '''terminate job #3'''.</li></ol><br>

# Write a single Linux command to terminal terminate a process that has the following PID: '''22384'''# Use the following diagram to answer the accompanying questions.<br>Each of the following questions will use the diagram below and are treated as independent situations.<br># Aliases / History:<br><span styleol type="font-family:courier;font-weight:bold;a">[1] Stopped vim a<brli>[2]Write a linux command to create an '''alias''' called '''ld''' that issues the command: '''ls - Stopped vim b<br>[3]+ Stopped vim cld'''</span><brli><brli>Write a single Linux linux command to bring unset the second-recently process placed '''alias''' created in the background into the foregroundprevious question.<br/li><li>Write Issue a single Linux command to terminate list '''history''' of commands that match the pattern called '''job #3touch'''.<br/li></ol><br># Create a '''table''' listing each Linux command, useful options and command purpose for the following Linux commands: <br>'''ln''' , '''ps''' , '''top''' , '''fg''' , '''bg''' , '''jobs''' , '''kill''', '''alias''' , '''unalias''' , '''history'''  _________________________________________________________________________________ Author: Murray Saul License: LGPL version 3Link: https://www.gnu.org/licenses/lgpl.html _________________________________________________________________________________