<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SI 667 Labs (Winter 2026) on SI 667 - Winter 2026</title><link>https://morskyjezek.github.io/si667-2026-activities/labs/</link><description>Recent content in SI 667 Labs (Winter 2026) on SI 667 - Winter 2026</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 21 Feb 2026 11:25:36 -0500</lastBuildDate><atom:link href="https://morskyjezek.github.io/si667-2026-activities/labs/index.xml" rel="self" type="application/rss+xml"/><item><title>Lab 07 Key</title><link>https://morskyjezek.github.io/si667-2026-activities/labs/lab-07-key/</link><pubDate>Sat, 21 Feb 2026 11:25:36 -0500</pubDate><guid>https://morskyjezek.github.io/si667-2026-activities/labs/lab-07-key/</guid><description>&lt;h2 id="lab-guidance-and-solutions"&gt;Lab Guidance and Solutions&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Problem 1:&lt;/strong&gt; Create directories to use for the reports, which will be the basis of your PDI.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Use the &lt;code&gt;mkdir&lt;/code&gt; command to make two new directories in the course files folder, one titled &lt;code&gt;sf_out&lt;/code&gt; and the second &lt;code&gt;br_out&lt;/code&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Problem 2:&lt;/strong&gt; Running Siegfried. Siegfried is a useful tool to create an inventory and a bulk process for file characterization information. Run the command on the &lt;code&gt;PKG-web-files-small&lt;/code&gt; directory and output the reports to the &lt;code&gt;sf_out&lt;/code&gt; directory.&lt;/p&gt;</description></item><item><title>Lab 08: Information Packages with BagIt</title><link>https://morskyjezek.github.io/si667-2026-activities/labs/lab-08/</link><pubDate>Thu, 12 Feb 2026 15:30:59 -0500</pubDate><guid>https://morskyjezek.github.io/si667-2026-activities/labs/lab-08/</guid><description>&lt;p&gt;This lab asks you to explore the BagIt file packaging structure, which was discussed in class. BagIt is a specification for a file-level information package, which contains basic descriptive information as well as PDI. Because it relies on operating system level information, it can be readily created for local files, and various tools support its creation. In this week&amp;rsquo;s lab, the BagIt library in python was demonstrated. This can be run in a standalone &lt;code&gt;.py&lt;/code&gt; file. But, for this lab, you are welcome to use the Jupyter notebook from the samples at: &lt;a href="https://github.com/morskyjezek/bagit-walkthrough-lcwa"&gt;https://github.com/morskyjezek/bagit-walkthrough-lcwa&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Lab 06 Key</title><link>https://morskyjezek.github.io/si667-2026-activities/labs/lab-06-key/</link><pubDate>Thu, 12 Feb 2026 15:21:30 -0500</pubDate><guid>https://morskyjezek.github.io/si667-2026-activities/labs/lab-06-key/</guid><description>&lt;p&gt;Answers will vary. Your answers should discuss the nature of the various CoreTrustSeal certification elements and their relationships.&lt;/p&gt;
&lt;p&gt;Original lab questions: 

&lt;a href="https://morskyjezek.github.io/si667-2026-activities/labs/lab-06/"&gt;Lab 06: CoreTrustSeal Hexagonal Thinking Diagram&lt;/a&gt;
&lt;/p&gt;</description></item><item><title>Lab 07: File Characterization with Siegfried and Brunnhilde</title><link>https://morskyjezek.github.io/si667-2026-activities/labs/lab-07/</link><pubDate>Thu, 12 Feb 2026 15:14:13 -0500</pubDate><guid>https://morskyjezek.github.io/si667-2026-activities/labs/lab-07/</guid><description>&lt;p&gt;This week&amp;rsquo;s lab questions are prompts that aim to guide you in the file inspection process and to reflect on the information that you can glean in this process. The problems below are designed to run on the course files, which you have previously downloaded, and that the directory is named &lt;code&gt;si667-2026-main&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Note: &lt;a href="https://morskyjezek.github.io/si667-2026-activities/guides/guide-running-sf-br/"&gt;this guide page on the course activities site demonstrates using Siegfried and Brunnhilde for file reporting and characterization&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Lab 05 Key</title><link>https://morskyjezek.github.io/si667-2026-activities/labs/lab-05-key/</link><pubDate>Thu, 12 Feb 2026 12:47:18 -0500</pubDate><guid>https://morskyjezek.github.io/si667-2026-activities/labs/lab-05-key/</guid><description>&lt;p&gt;This lab will allow you to explore concepts and tools related to various digital &amp;ldquo;materialities&amp;rdquo; and initial tools to create basic file fixity information, another step toward creating preservation metadata. The files you should use for the assignment are from the course file collection you downloaded previously; if you don&amp;rsquo;t have the files, download an unzip them again from &lt;a href="https://github.com/morskyjezek/si667-2026"&gt;https://github.com/morskyjezek/si667-2026&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id="lab-questions-using-the-shell-for-file-identification-and-characterization"&gt;Lab Questions: Using the Shell for File Identification and Characterization&lt;/h2&gt;
&lt;h3 id="q1"&gt;Q1.&lt;/h3&gt;
&lt;p&gt;Use the &lt;code&gt;file&lt;/code&gt; command to inspect files and create a MIME Type registry. For this question, use files in the &lt;code&gt;PKG-text-data&lt;/code&gt; directory.&lt;/p&gt;</description></item><item><title>Lab 06: CoreTrustSeal Hexagonal Thinking Diagram</title><link>https://morskyjezek.github.io/si667-2026-activities/labs/lab-06/</link><pubDate>Mon, 09 Feb 2026 17:07:47 -0500</pubDate><guid>https://morskyjezek.github.io/si667-2026-activities/labs/lab-06/</guid><description>&lt;h2 id="in-this-lab-you-will"&gt;In this lab you will&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Engage with the CoreTrustSeal requirements.&lt;/li&gt;
&lt;li&gt;Create a hexagonal diagram from a list of concepts.&lt;/li&gt;
&lt;li&gt;Explain your choices.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="what-to-submit"&gt;What to submit&lt;/h2&gt;
&lt;p&gt;Upload 1 PDF to Canvas.&lt;/p&gt;
&lt;h2 id="instructions"&gt;Instructions&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;&lt;strong&gt;Note:&lt;/strong&gt; you may work on the diagrams in small groups in class, but must each submit your own reflection in Canvas.&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;First, review the provided information about the CoreTrustSeal and its checklist. Make sure to understand what the CoreTrustSeal is, why it&amp;rsquo;s important, and what each item on the checklist means.&lt;/li&gt;
&lt;li&gt;Prepare Your Hexagons: On each hexagonal card or sticky note (or digital equivalent), write a different criterion from the CoreTrustSeal checklist. You should end up with a hexagon for each item on the checklist.
&lt;ul&gt;
&lt;li&gt;You may use the following template if you like, or you can create your own diagram using pen &amp;amp; paper, or any tool of your choice: &lt;a href="https://docs.google.com/drawings/d/1IZRojEJeeyK50xKYaaTWsUkfKjpzUlYRcXyImBJV00U/edit?usp=sharing"&gt;Lab 6: CTS Hexagons Template&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Analyze the Criteria: Consider each criterion and think about its meaning, importance, and implications. How does each criterion contribute to the trustworthiness of digital repositories?&lt;/li&gt;
&lt;li&gt;Creating Connections: Start to arrange your hexagons to visually represent the connections you see between the different criteria. You can place connecting sides together to show direct relationships. Don&amp;rsquo;t forget to consider indirect relationships and how different criteria may impact one another.&lt;/li&gt;
&lt;li&gt;Write About Your Connections: Choose three connections between criteria that you find particularly interesting or surprising. Write a brief explanation about each connection. Make sure to explain what each criterion is, how they are connected, and why you find this connection significant.&lt;/li&gt;
&lt;li&gt;Once you have completed your hexagonal connections and written your explanations, submit your work as a single PDF that includes your hexagonal diagram AND your written work.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Tips:&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;This assignment isn&amp;rsquo;t about finding &amp;ldquo;right&amp;rdquo; or &amp;ldquo;wrong&amp;rdquo; connections. Rather, it&amp;rsquo;s an exploration of the interrelatedness of the different aspects of the CoreTrustSeal checklist. So, be creative and thoughtful in your approach.&lt;/li&gt;
&lt;li&gt;Your written explanations are a chance to demonstrate your understanding of the CoreTrustSeal and its checklist. Be thorough and detailed in explaining your chosen connections.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Additional information about Hexagonal Thinking exercises can be found here: &lt;a href="https://www.cultofpedagogy.com/hexagonal-thinking/"&gt;https://www.cultofpedagogy.com/hexagonal-thinking/&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Lab 05: File Information in the Shell</title><link>https://morskyjezek.github.io/si667-2026-activities/labs/lab-05/</link><pubDate>Mon, 09 Feb 2026 17:01:06 -0500</pubDate><guid>https://morskyjezek.github.io/si667-2026-activities/labs/lab-05/</guid><description>&lt;p&gt;This lab will allow you to explore concepts and tools related to various digital &amp;ldquo;materialities&amp;rdquo; and initial tools to create basic file fixity information, another step toward creating preservation metadata. The files you should use for the assignment are from the course file collection you downloaded previously; if you don&amp;rsquo;t have the files, download an unzip them again from &lt;a href="https://github.com/morskyjezek/si667-2026"&gt;https://github.com/morskyjezek/si667-2026&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id="lab-questions-using-the-shell-for-file-identification-and-characterization"&gt;Lab Questions: Using the Shell for File Identification and Characterization&lt;/h2&gt;
&lt;h3 id="q1"&gt;Q1.&lt;/h3&gt;
&lt;p&gt;Use the &lt;code&gt;file&lt;/code&gt; command to inspect files and create a MIME Type registry. For this question, use files in the &lt;code&gt;PKG-text-data&lt;/code&gt; directory.&lt;/p&gt;</description></item><item><title>Lab 04 Key</title><link>https://morskyjezek.github.io/si667-2026-activities/labs/lab-04-key/</link><pubDate>Mon, 09 Feb 2026 14:27:00 -0500</pubDate><guid>https://morskyjezek.github.io/si667-2026-activities/labs/lab-04-key/</guid><description>&lt;h2 id="question-solutiuons-and-commentary-for-lab-04"&gt;Question Solutiuons and Commentary for Lab 04&lt;/h2&gt;
&lt;h3 id="q1"&gt;Q1.&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Pipelines.&lt;/strong&gt; Create a string of commands that can identify the shortest (by line numbers) TSV file in the &lt;code&gt;PKG-text-data&lt;/code&gt; directory. Provide the commands you would use. What is the name of the shortest TSV file and how many lines does it have?&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;$ &lt;span class="nb"&gt;pwd&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;~/si667-2026-main/PKG-text-data/
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;$ wc -l *.tsv &lt;span class="p"&gt;|&lt;/span&gt; sort -n &lt;span class="p"&gt;|&lt;/span&gt; head -n &lt;span class="m"&gt;1&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;&lt;em&gt;In the commands above, the first prompt (running &lt;code&gt;pwd&lt;/code&gt;) demonstrates that the shell is located in the user&amp;rsquo;s directory corresponding to &lt;code&gt;PKG-text-data&lt;/code&gt;. The second &amp;ldquo;pipes&amp;rdquo; together a series of commands: first, &lt;code&gt;wc&lt;/code&gt; with the flag &lt;code&gt;-l&lt;/code&gt; indicating a line count, and using a filter to sort all &lt;code&gt;.tsv&lt;/code&gt; files (the asterisk); second, the &lt;code&gt;sort&lt;/code&gt; command sorting by number (&lt;code&gt;-n&lt;/code&gt;) in descending order; and finally, third, the &lt;code&gt;head&lt;/code&gt; command to show the beginning of the response with the line number set to show only one line (&lt;code&gt;-n 1&lt;/code&gt;).&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Lab 04: Shell Materialities and File Information</title><link>https://morskyjezek.github.io/si667-2026-activities/labs/lab-04/</link><pubDate>Mon, 09 Feb 2026 14:15:15 -0500</pubDate><guid>https://morskyjezek.github.io/si667-2026-activities/labs/lab-04/</guid><description>&lt;p&gt;This lab will allow you to explore concepts and tools related that help to understand various digital &amp;ldquo;materialities&amp;rdquo; and locate or search within files. The files you should use for the assignment are from the course file collection you downloaded previously; if you don&amp;rsquo;t have the files, download an unzip them again from &lt;a href="https://github.com/morskyjezek/si667-2026"&gt;https://github.com/morskyjezek/si667-2026&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id="lab-questions-using-the-shell-for-advanced-finding-and-file-searching"&gt;Lab Questions: Using the Shell for Advanced Finding and File Searching&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Pipelines.&lt;/strong&gt; Create a string of commands that can identify the shortest (by line numbers) TSV file in the &lt;code&gt;PKG-text-data&lt;/code&gt; directory. Provide the commands you would use. What is the name of the shortest TSV file and how many lines does it have?&lt;/li&gt;
&lt;li&gt;Using the &lt;code&gt;find&lt;/code&gt; command (for this question you should be located in the main directory of the course files that you downloaded). What is the &lt;code&gt;find&lt;/code&gt; command you could use to look (in the current directory and all subdirectories), for all the files?&lt;/li&gt;
&lt;li&gt;Choose one of the sample datasets for &lt;a href="https://umich.instructure.com/courses/812017/assignments/2929731"&gt;Assignment 1 (links to Canvas)&lt;/a&gt;. Use these questions to make a preliminary analysis using the sorts of tools and questions we&amp;rsquo;ve been asking so far.
a. What dataset did you choose? What drew you to this dataset?
b. For this dataset, identify at least one file type that appears to hold data. What is the filetype? How can you find out more about the file type?
c. Try downloading the file you identified above.
d. Is it easy or difficult to identify the file, to download the file? Is there any information that you might use to demonstrate provenance or authenticity about the file in the access interface? (For example, how big is the file, a hash value, creator, filename, creation/modification date, etc?)
e. Using command line tools, can you get detailed technical information about the file? Can you identify the file? Can you get basic information like who created the file and when? If you were able to identify any file information in the previous step from the data interface, does the way that you can interact with or &amp;ldquo;see&amp;rdquo; the file in the shell agree with the information you found from the broader context?&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;em&gt;&lt;strong&gt;Bonus Question (&lt;code&gt;find&lt;/code&gt; + &lt;code&gt;regex&lt;/code&gt;):&lt;/strong&gt;&lt;/em&gt; How would you use find with regular expressions to create a list of all image files at the current location (and subdirectories), that is, with extensions &lt;code&gt;tif&lt;/code&gt;, &lt;code&gt;tiff&lt;/code&gt;, &lt;code&gt;jpg&lt;/code&gt;, &lt;code&gt;jpeg&lt;/code&gt;, &lt;code&gt;png&lt;/code&gt;, &lt;code&gt;bmp&lt;/code&gt;, &lt;code&gt;gif&lt;/code&gt;; then, send that output to a file named &lt;code&gt;image_file_list.txt&lt;/code&gt;. Put the command and the output list of files in your submission. How would you count how many files you found? How many files did you find?&lt;/p&gt;</description></item><item><title>Lab 03 Key</title><link>https://morskyjezek.github.io/si667-2026-activities/labs/lab-03-key/</link><pubDate>Mon, 09 Feb 2026 14:08:06 -0500</pubDate><guid>https://morskyjezek.github.io/si667-2026-activities/labs/lab-03-key/</guid><description>&lt;h2 id="glitched-files"&gt;Glitched Files&lt;/h2&gt;
&lt;p&gt;The responses and changes that you make to your files when creating &amp;ldquo;bit rot art&amp;rdquo;
will vary widely. In general, the process involves opening the file in a hex editor,
then changing or deleting some of the bytes to see what will happen.
You can &amp;ldquo;see&amp;rdquo; the results by reopening the file in an image viewer.&lt;/p&gt;
&lt;h2 id="lab-activitiesquestions"&gt;Lab Activities/Questions&lt;/h2&gt;
&lt;p&gt;Record answers for the following questions:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Modify at least one jpg and one tif file. Note the original name of the files that you modified, and the name of the file that you uploaded to the online gallery/folder.&lt;/li&gt;
&lt;li&gt;Describe what changed and how this affected the rendering of the files. What was most interesting or challenging about this process?&lt;/li&gt;
&lt;/ol&gt;
&lt;ul&gt;
&lt;li&gt;&lt;em&gt;Results will vary, but generally, there may be some color changes, skewing, shift of the image, or visual artifacts and changes introduced in parts of the image.&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Original lab questions: 

&lt;a href="https://morskyjezek.github.io/si667-2026-activities/labs/lab-03/"&gt;Lab 03: Bit Rot Experimental Art&lt;/a&gt;
.&lt;/p&gt;</description></item><item><title>Lab 01: Pre-Course Questionnaire</title><link>https://morskyjezek.github.io/si667-2026-activities/labs/lab-01/</link><pubDate>Sun, 08 Feb 2026 22:54:47 -0500</pubDate><guid>https://morskyjezek.github.io/si667-2026-activities/labs/lab-01/</guid><description>&lt;p&gt;For the first lab, complete a short questionnaire to let the instructors know about your preparation coming into the course. You will find the survey at &lt;a href="https://docs.google.com/forms/d/e/1FAIpQLSeb0Av40eBTCeR8bcC1QmeK0lOgWaybbTugIfF-Yn-nUkV0Yg/viewform?usp=publish-editorLinks"&gt;https://docs.google.com/forms/d/e/1FAIpQLSeb0Av40eBTCeR8bcC1QmeK0lOgWaybbTugIfF-Yn-nUkV0Yg/viewform?usp=publish-editorLinks&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Note that the form will collect your umich email address in order to track participation.&lt;/p&gt;
&lt;h2 id="key"&gt;Key&lt;/h2&gt;
&lt;p&gt;See the answer key: 

&lt;a href="https://morskyjezek.github.io/si667-2026-activities/labs/lab-01-key/"&gt;Lab 01 Key&lt;/a&gt;
&lt;/p&gt;</description></item><item><title>Lab 02: Navigating in the Shell</title><link>https://morskyjezek.github.io/si667-2026-activities/labs/lab-02/</link><pubDate>Sun, 08 Feb 2026 22:54:47 -0500</pubDate><guid>https://morskyjezek.github.io/si667-2026-activities/labs/lab-02/</guid><description>&lt;p&gt;For reference, see the &lt;a href="https://docs.google.com/presentation/d/1OZyh3pcNeZ2NIyGptQuR_idpbW9SbMe0ZLuAtsr8Q14/edit?usp=drive_link"&gt;shell slide deck&lt;/a&gt; and &lt;a href="https://github.com/morskyjezek/si667-2026/blob/main/shell/exercise-shell-unix-basics.md"&gt;this reference document in the course GitHub repo&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id="questions-to-answer"&gt;Questions to Answer&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Q1.&lt;/strong&gt; Imagine that you have opened a window that gives access to the command line. What command would you use to determine your current location (current path)?&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Q2.&lt;/strong&gt; What command would you use to move to another directory or folder?&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Q3.&lt;/strong&gt; What command would you use to list the contents of the directory or folder?&lt;/p&gt;</description></item><item><title>Lab 03: Bit Rot Experimental Art</title><link>https://morskyjezek.github.io/si667-2026-activities/labs/lab-03/</link><pubDate>Sun, 08 Feb 2026 22:54:47 -0500</pubDate><guid>https://morskyjezek.github.io/si667-2026-activities/labs/lab-03/</guid><description>&lt;p&gt;You will find the lab description at &lt;a href="https://umich.instructure.com/courses/812017/assignments/3065280"&gt;the lab assignment on Canvas&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id="learning-goals"&gt;Learning Goals&lt;/h2&gt;
&lt;p&gt;This lab asks you to go beyond &amp;ldquo;screen essentialism&amp;rdquo; and experience different ways of looking at and modifying files. You will work on:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;How to view files at the raw bitstream level (focus on the &amp;ldquo;informational&amp;rdquo; view of digital information)&lt;/li&gt;
&lt;li&gt;Use tools that help to view digital encodings, through examples of text and images
How to alter the raw bitstream and an exploratory approach to what those alterations produce&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="useful-tools"&gt;Useful Tools&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;You should have a hex editor extension for VS Code. You can use the Hex EditorLinks to an external site. or Hex Inspector. (To install an extension, you can search in VS Code, then click the green install button.)&lt;/li&gt;
&lt;li&gt;If your VS Code extensions aren&amp;rsquo;t working well, try an online hex viewer, like &lt;a href="https://hexed.it/"&gt;https://hexed.it/&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Find the files in the &lt;code&gt;bit-rot-lab&lt;/code&gt; folder of the course shared files, &lt;a href="https://github.com/morskyjezek/si667-2026/tree/main/bit-rot-lab"&gt;linked here&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="what-to-submit"&gt;What to submit&lt;/h2&gt;
&lt;p&gt;You should submit one file that answers the lab questions below here on Canvas, and also &lt;a href="https://github.com/morskyjezek/si667-2026/tree/main/bit-rot-lab"&gt;upload a glitched jpg and a glitched tiff file to the shared folder&lt;/a&gt;. (Remember that it may take a few tries to get something that renders a visually noticeable or interesting new file.) Other files will be generated during your activities, but only share two of the most interesting glitched files. We will view the files next week and during next class!&lt;/p&gt;</description></item><item><title>Lab 02 Key</title><link>https://morskyjezek.github.io/si667-2026-activities/labs/lab-02-key/</link><pubDate>Sun, 08 Feb 2026 15:26:08 -0500</pubDate><guid>https://morskyjezek.github.io/si667-2026-activities/labs/lab-02-key/</guid><description>&lt;p&gt;For reference, see the &lt;a href="https://docs.google.com/presentation/d/1OZyh3pcNeZ2NIyGptQuR_idpbW9SbMe0ZLuAtsr8Q14/edit?usp=drive_link"&gt;shell slide deck&lt;/a&gt; and &lt;a href="https://github.com/morskyjezek/si667-2026/blob/main/shell/exercise-shell-unix-basics.md"&gt;this reference document in the course GitHub repo&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id="questions-to-answer"&gt;Questions to Answer&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Q1.&lt;/strong&gt; Imagine that you have opened a window that gives access to the command line. What command would you use to determine your current location (current path)?&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;$ &lt;span class="nb"&gt;pwd&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;&lt;strong&gt;Q2.&lt;/strong&gt; What command would you use to move to another directory or folder?&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;$ &lt;span class="nb"&gt;cd&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;&lt;strong&gt;Q3.&lt;/strong&gt; What command would you use to list the contents of the directory or folder?&lt;/p&gt;</description></item><item><title>Lab 01 Key</title><link>https://morskyjezek.github.io/si667-2026-activities/labs/lab-01-key/</link><pubDate>Sun, 08 Feb 2026 15:10:11 -0500</pubDate><guid>https://morskyjezek.github.io/si667-2026-activities/labs/lab-01-key/</guid><description>&lt;p&gt;Responses will vary.&lt;/p&gt;
&lt;p&gt;Original lab questions: 

&lt;a href="https://morskyjezek.github.io/si667-2026-activities/labs/lab-01/"&gt;Lab 01: Pre-Course Questionnaire&lt;/a&gt;
.&lt;/p&gt;</description></item></channel></rss>