The progress report and compliance with specs are updated at one second past every minute. They were last updated 2019-11-19 17:45:03. Logs for bash and sftp history are updated every ten minutes. The above paragraph was taken from the very top of the "HOL Progress Report" page. Due to my lack of creativeness, this is the result. From this, I have resigned myself to this fact. Because I did not read the prompt properly, this project is now "late". Sometimes, I wonder why I was given the gift of sight when there are so many others that can make use of it better. Alas, these types of feelings are always fleeting.
A good looking progress report will have no red marks for components on their due date. Due dates and other specs are posted on the class' web page. The lack of redmarks does not necessarily mean that all specs for the project have been met. This paragraph was taken much like the first paragraph from "File1". Like "File1", this paragraph was also borne of my own lack of creativity. This weakness will not go unnoticed, but will also, most likely, never be fixed. And much like "File1", this was also done late. Done on the same day as well, it should also be no surprise that "File3" was also finished "late". Nevertheless, I will now proceed to finish "File3".
This is an exercise for working at the command line on a Linux server and using the vi editor. Do not edit these files on a Windows or Mac desktop and copy them to the server. "File3" was done late much like "File1" and "File2". There was something involving "something" in which the solution was shown in class about "swapping". Not entirely sure of how to go about resolving this, but this assignment is late anyway. In the end, a late assignment is a late assignment. I'm not entirely sure how many points were deducted, or if it ends up being a "0", but what's done is done. I am sad.
No lines are longer than 80 characters, TYVM. Other specified properties aren't being scored automatically at this time so this is not necessarily good news...