...

1.4  If for whatever reason the patch does not apply please apply it based on the text above (screenshots shown below as a visual aid:  L = original, R= modified, red = deletions, green = additions, purple = changes):  

...

Appendix F: Misc.

Installation Logging

1. To keep a record of the installation process, we recommend you enable input & output logging before starting.  This will greatly help if for some reason you need to review or submit logs for troubleshooting later.  You can do this in one of two ways: 
   1. Terminal Logging:  Exact steps depend on the terminal client you are using but there should be settings in your terminal's console to configure this (usually setting it to the max # of lines of scrollback is best).  OR if you don't want to use that or it has terrible logging facilities you can generate a replay-able log file with timings by using
   2. script:  To use, simply run:  script (on *NIX, do this from the shell, ie:  bash; in Windows, do this from the Cygwin Terminal- which runs bash).  Then proceed to do the steps you wish to record, then end it by hitting ^D (CTRL-D) or type exit to stop recording.  You can then rename the file called typescript from the location where script was invoked and review/share that if necessary (for more information see man script).
       WARNING, be aware that using any interactive tool that allows arbitrary cursor placement, ex: vi or vim , etc. will record very erratic-looking output in the log so you may wish to stop logging (temporarily) if you need to use one, and use script -a to resume appending after completing the use of the interactive tool.