INFO300 Hands On Linux Project • ???? Section:

The progress report and compliance with specs are updated at one second past every minute. They were last updated 2020-06-07 02:20:02.
Logs for bash and sftp history are updated every ten minutes.

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 red marks does not
necessariy mean that all specs for the project have been met.

Outlines/Brief1

~web

Outline

Permissions and other Specs

Part 1 -- Learn vi and Post your Topic

Before making Outlines and web directories, find a vim tutorial you like and get comfortable
using it.

Then, use vi to edit files in your home directory named File1, File2, and File3, each with at least
three well-formatted paragraphs from a text, novel, article or your own poetry, prose, or blog.
Make each line of text a max of 75 characters wide.
Set the permissions for each of these files to 600, readable by only yourself
and root.

Make a directory named Outlines in your home directory and
edit the topic for your brief on the 1st line of a file named Brief1 in the Outlines directory.
Nothing else is required in the file for Part 1 but line 2 should be left empty if there is.
The file should be 'plain text', with no HTML.

Set the permissions on the Outlines directory to 700 and the file Brief1 to 600.
Check the progress page to make sure Outlines and Brief1 are in the right place with the right permissions.
The progress page is updated one second past every minute. Enter 'date' at the command line
to check the time.

Part 2 -- Posting Your Outline and References

Part 2 of the project is to find references for your brief,
organize them, make an outline for the brief, and use vi to key the outline and references into the file Brief1.

Brief1 should be a plain-text file, should not have any html, will only be read
by you and the instructor. It should be organized by indenting to show the 'levels of the outline'.

When you've completed the research, edit the file Brief1 and add
a nicely indented outline for your tech market brief, starting in line 3, leaving the 2nd line empty.
Single-space between each entry in the outline, leaving no 'blank line' between the lines of your outline.
Use spaces to make indentations to structure the outline.
After the single-spaced outline, double-space to leave an empty line and list your references.
If you have done this properly, your feedback below will show your topic,
the first entry in your outline, and the first reference in your list.

Part 3 -- Making the 3-page website:

Please find and comply with all the specs posted on the class' page and mentioned in class for the HOL/Tech Brief project.
Make a valid skeleton of your website first, then pitch your brief in standards-compliant html and css.

Please complete these little tasks at the linux command line without desktop editors!
Steps, without FileZilla or WinSCP, at the command line:

Make a directory named 'web', all lower case, with no apostrophes, in your home directory
if you haven't already done it.
Set it's permissions to rwx-----x so you have full access to it and httpd can include it in a path.

Use vi to create and edit index.html in your web directory. Verify that it shows up
as index.html in your progress report below.

Use vi to edit a file named Brief1.html in your web directory.
Your Brief1.html will hold the web version of your technical market brief.

Set the permissions of any web pages, css, graphics,
or other files in the web directory to 604 rw----r--.
If there are subdirectories, set them to rwx---r-x.

Grading:

Get any questions answered in class, not in email.
Snapshots of this page, the contents of your home directory, and your history at the command line will be
taken after the deadline and used to score the timeliness and quality of each component at the time it was due.