Skip to content

Commit

Permalink
adds final edits
Browse files Browse the repository at this point in the history
  • Loading branch information
oceansize committed Mar 10, 2016
1 parent 23d311e commit 40e358d
Show file tree
Hide file tree
Showing 4 changed files with 35 additions and 19 deletions.
15 changes: 10 additions & 5 deletions step6
Original file line number Diff line number Diff line change
@@ -1,16 +1,21 @@
Reference: ./detective_handbook/step6.md

Now you have more information to identify the perpetrator. Peek into 'mystery/vehicles' file. What information does it contain? Look into your 'clues.txt' again - is there anything else you can search for in the vehicles record?
Now you have more information to identify the perpetrator. Peek into the './mystery/vehicles' file. What information does it contain? Cross-reference it with your 'clues.txt' again - is there anything else you could search for in the vehicles record?

############ Challenge ###############

Now you need to search for multiple keywords in one file. How can you combine `grep` with flags and pipe operator to filter vehicles record for car model, color, license plate number and suspect's height?
Now you need to search for multiple keywords in one file. How can you combine `grep` with flags and the pipe operator ('|') to filter the vehicle records for:

* car model
* car color
* license plate number
* suspect's height

######################################


Save the list of suspect into 'suspects.txt', commit and push to Github.
Save the list of suspects into a new file called 'suspects.txt', commit and push to Github.

Looks like you've got quite far now. Make a pull request to the original 'clmystery' repository to let us know about your progress.
You're very happy with the progress of your investigation - you feel like you are close to identifying the culprit. Make a pull request to the original 'clmystery' repository to report your progress to The Chief.

Move on to step 7.
Move on to step 7.
8 changes: 5 additions & 3 deletions step7
Original file line number Diff line number Diff line change
@@ -1,13 +1,15 @@
Reference: ./detective_handbook/step7.md

Now you're down to 4 suspects. First, remove all files you've created but 'clues' and 'suspects', you don't need them anymore.
Now you're down to 4 suspects. First, destroy all the files you've created except for 'clues.txt' and 'suspects.txt', you don't need them anymore.


############ Challenge ###############

How can you tell what files you've added? Can you use git to see the changes between one commit and another?
The phone rings unexpectedly and you lose your train of thought. How can you remind yourself which files you have changed or added? Maybe git can help.

Can you use git to see the changes between one commit and another?

######################################


Move on to step 8.
Move on to step 8.
13 changes: 5 additions & 8 deletions step8
Original file line number Diff line number Diff line change
@@ -1,22 +1,19 @@
Reference: ./detective_handbook/step8.md

The last clue that you have left is the list of memberships in the wallet found at the crimescene. All you need to do now is to see if one of the suspects has all these memberships.
The final outstanding clue is the list of memberships in the wallet found at the crime scene. All that's required now is to verify your suspect holds all of the relevant memberships.

What files does the 'mystery/memberships' subdirectory contain? What is inside these files?
What files does the './mystery/memberships' subdirectory contain? What's inside these files?


############ Challenge ###############

Remember that the `cat` command was originally intended for concatenating files. Using this how can you tell if one suspect has all of the memberships?

How many membership cards were in the wallet? Can you automatically count if the suspect has all of them using `grep`, `wc` and the pipe operator?
How many membership cards were in the wallet? Can you automatically count if the suspect has all of them using `grep`, `wc` commands and the pipe operator?

######################################


If you managed to narrow your investigation down to one suspect, read the `solution` file to verify that you have found the killer. Move on to 'step9'

If you got it down to one suspect check if he's the one by following the instructions in the 'solution' file.

Congratulations! You caught the murderer! Move on to step 9 to submit your answer.

Save his name in the 'jail.txt' file, commit and push to Github.
If not, retrace your steps until there is only one suspect.
18 changes: 15 additions & 3 deletions step9
Original file line number Diff line number Diff line change
@@ -1,5 +1,17 @@
Reference: sudo, chown, chmod
Reference: ./detective_handbook/step9.md

Save the murderer's name to the file 'jail.txt'. Change permissions on the file so that everyone else but you are only allowed to read this file. We don't want anyone to swap this guy for someone innocent on his way to jail!
Congratulations! You caught the murderer!

Commit 'jail.txt' and push to Github.
To close the investigation and let the courts do their work, save his name in a file called 'jail.txt'.

Change permissions on the file so that you are the only one able to edit it (everyone else can read the contents). There was a case last summer where a convict was switched out for an innocent man on the way to jail - and we don't want that happening again!

Add & commit 'jail.txt' and push to Github. You can now relax and wait for that promotion, Detective!


_______ _ _ ______ ______ _ _ _____
|__ __| | | | | | ____| | ____| | \ | | | __ \
| | | |__| | | |__ | |__ | \| | | | | |
| | | __ | | __| | __| | . ` | | | | |
| | | | | | | |____ | |____ | |\ | | |__| |
|_| |_| |_| |______| |______| |_| \_| |_____/

0 comments on commit 40e358d

Please sign in to comment.