haas/fall2026/unix/projects/pbx0.md
... ...
@@ -206,33 +206,8 @@ To successfully complete this project, you must follow the directions
206 206
located in a readable file at the conclusion of this project. Until you
207 207
encounter it, you are not yet finished (hint).
208 208
209
-You should get some sort of confirmation indicating successful submission
210
-(actually, two) if all went according to plan. If not, check for typos
211
-and or locational mismatches.
212
-
213
-### SUBMIT TOOL USAGE
214
-
215
-Let's say you have completed work on the project, and are ready to
216
-submit, you would do the following:
217
-
218
-```
219
-lab46:~/src/SEMESTER/unix/pbx0$ submit unix pbx0 file1 file2 file3 ... fileN
220
-```
221
-
222
-A less abstract instantiation of the above (to help you transition):
223
-
224
-```
225
-lab46:~/src/SEMESTER/unix/pbx0$ submit unix pbx0 results pbx0steps
226
-Submitting unix project "pbx0":
227
- -> results(OK)
228
- -> pbx0steps(OK)
229
-
230
-SUCCESSFULLY SUBMITTED
231
-```
232
-
233
-You should get some sort of confirmation indicating successful submission
234
-if all went according to plan. If not, check for typos and or locational
235
-mismatches.
209
+Be sure to track the produced file in your private semester repository,
210
+under the `unix/pbx0/` directory.
236 211
237 212
I'll be looking for the following:
238 213
... ...
@@ -240,8 +215,8 @@ I'll be looking for the following:
240 215
241 216
```
242 217
104:pbx0:final tally of results (104/104)
243
-*:pbx0:submitted results file via submit tool [13/13]
244
-*:pbx0:submitted pbx0steps file via submit tool [13/13]
218
+*:pbx0:results file in private semester repo [13/13]
219
+*:pbx0:pbx0steps file in private semester repo [13/13]
245 220
*:pbx0:results md5sum matches project MANIFEST [13/13]
246 221
*:pbx0:results is correctly unscrambled and assembled [13/13]
247 222
*:pbx0:pbx0steps contains valid set of instructions [13/13]
haas/fall2026/unix/projects/pbx1.md
... ...
@@ -104,6 +104,7 @@ tasks related to this project, do keep in mind that for the actual
104 104
solving of the puzzlebox:
105 105
106 106
* you do NOT need to call upon sudo / root access in any way (solutions containing such steps will be considered to not be following the spirit of the project)
107
+
107 108
* all actionable steps taken are to be done using **non-interactive** tools. There is zero need to make use of an interactive tool like **nano**. Solutions that make central use of interactive tools will be considered to not be following the spirit of the project.
108 109
109 110
While you as a user investigating things may end up using various tools
... ...
@@ -152,36 +153,10 @@ In addition to the files produced during the completion of this project,
152 153
I would also like for you to create a detailed step-by-step text file
153 154
called **pbx1steps** which includes the valid command-lines that will
154 155
document for me the steps you took from project commencement through
155
-completion. You will submit this file at the end in accordance with the
156
-instructions.
157
-
158
-You should get some sort of confirmation indicating successful submission
159
-(actually, two) if all went according to plan. If not, check for typos
160
-and or locational mismatches.
161
-
162
-### SUBMIT TOOL USAGE
163
-
164
-Let's say you have completed work on the project, and are ready to
165
-submit, you would do the following:
166
-
167
-```
168
-lab46:~/src/SEMESTER/unix/pbx1$ submit unix pbx1 file1 file2 file3 ... fileN
169
-```
170
-
171
-A less abstract instantiation of the above (to help you transition):
172
-
173
-```
174
-lab46:~/src/SEMESTER/unix/pbx1$ submit unix pbx1 pbx1.results pbx1steps
175
-Submitting unix project "pbx1":
176
- -> pbx1.results(OK)
177
- -> pbx1steps(OK)
178
-
179
-SUCCESSFULLY SUBMITTED
180
-```
156
+completion.
181 157
182
-You should get some sort of confirmation indicating successful submission
183
-if all went according to plan. If not, check for typos and or locational
184
-mismatches.
158
+Be sure to track the produced file in your private semester repository,
159
+under the `unix/pbx1/` directory.
185 160
186 161
I'll be looking for the following:
187 162
... ...
@@ -189,11 +164,10 @@ I'll be looking for the following:
189 164
190 165
```
191 166
130:pbx1:final tally of results (130/130)
192
-*:pbx1:submitted pbx1.results file via submit tool [13/13]
193
-*:pbx1:submitted pbx1steps file via submit tool [13/13]
194
-*:pbx1:both files pushed to private semester repository [13/13]
167
+*:pbx1:pbx1.results file in private semester repo [13/13]
168
+*:pbx1:pbx1steps file in private semester repo [13/13]
195 169
*:pbx1:pbx1.results is correctly unscrambled and assembled [13/13]
196
-*:pbx1:pbx1.results md5sum matches project MANIFEST [13/13]
170
+*:pbx1:pbx1.results md5sum matches project MANIFEST [26/26]
197 171
*:pbx1:pbx1steps has valid list of non-interactive instructions [13/13]
198 172
*:pbx1:pbx1steps uses shell features like wildcards, IO redir [13/13]
199 173
*:pbx1:pbx1steps contains comments explaining process [13/13]
haas/fall2026/unix/projects/pbx2.md
... ...
@@ -145,40 +145,7 @@ In addition to the files produced during the completion of this project,
145 145
I would also like for you to create a detailed step-by-step text file
146 146
called **pbx2steps** which includes the valid command-lines that will
147 147
document for me the steps you took from project commencement through
148
-completion. You will submit this file at the end in accordance with the
149
-instructions.
150
-
151
-To successfully complete this project, you must follow the directions
152
-located in a readable file at the conclusion of this project. Until you
153
-encounter it, you are not yet finished (hint).
154
-
155
-You should get some sort of confirmation indicating successful submission
156
-(actually, two) if all went according to plan. If not, check for typos
157
-and or locational mismatches.
158
-
159
-### SUBMIT TOOL USAGE
160
-
161
-Let's say you have completed work on the project, and are ready to
162
-submit, you would do the following:
163
-
164
-```
165
-lab46:~/src/SEMESTER/unix/pbx2$ submit unix pbx2 file1 file2 file3 ... fileN
166
-```
167
-
168
-A less abstract instantiation of the above (to help you transition):
169
-
170
-```
171
-lab46:~/src/SEMESTER/unix/pbx2$ submit unix pbx2 pbx2.results pbx1steps
172
-Submitting unix project "pbx2":
173
- -> pbx2.results(OK)
174
- -> pbx2steps(OK)
175
-
176
-SUCCESSFULLY SUBMITTED
177
-```
178
-
179
-You should get some sort of confirmation indicating successful submission
180
-if all went according to plan. If not, check for typos and or locational
181
-mismatches.
148
+completion.
182 149
183 150
I'll be looking for the following:
184 151
... ...
@@ -187,10 +154,9 @@ I'll be looking for the following:
187 154
```
188 155
156:pbx2:final tally of results (156/156)
189 156
*:pbx2:post screenshot of results to DISCORD channel [13/13]
190
-*:pbx2:submitted pbx2.results file via submit tool [13/13]
191
-*:pbx2:submitted pbx2steps file via submit tool [13/13]
192
-*:pbx2:both files pushed to private semester repository [13/13]
193
-*:pbx2:pbx2.results is correctly unscrambled and assembled [13/13]
157
+*:pbx2:pbx2.results file in private semester repo [13/13]
158
+*:pbx2:pbx2steps file in private semester repo [13/13]
159
+*:pbx2:pbx2.results is correctly unscrambled and assembled [26/26]
194 160
*:pbx2:pbx2.results md5sum matches project MANIFEST [13/13]
195 161
*:pbx2:pbx2steps has valid list of non-interactive instructions [13/13]
196 162
*:pbx2:pbx2steps uses shell features like wildcards, IO redir [13/13]