Speech:Spring 2016 Jonathan Trimble Log


 * Home
 * Semesters
 * Spring 2016
 * Proposal
 * Report
 * Information - General Project Information
 * Experiments - List of speech experiments

Week Ending February 9, 2016

 * Task:
 * 2/3: Logged into Caesar as root. Read 2015 summer and spring logs. Skimmed many logs but focused on Zeb's (summer) and spring Tools Group's logs.
 * 2/4: Read more logs from 2014 and 2015.
 * 2/5: Install VirtualBox on my machine for testing new tools.
 * 2/6: Created a bridged connection between VB's network driver and my WAN connection so that I can SSH into my virtual server.


 * Results:
 * 2/3: Found Zeb's log interesting as was looking into TORQUE. Ken was looking into creating a Linux virtual machine.
 * 2/4: Discovered a wiki page on TORQUE here which mentions that it is only installed on Caesar which contradicts Forrest's log (2014) where he mentions that it is installed on all nodes/machines but is only utilizing 1/4 of the processors on each machine.
 * 2/5: Install was successful and the Ubuntu server install went smoothly however my host machine (Windows 10) is unable to ping my Ubuntu VM.
 * 2/6: The bridge was simple enough to create on my host machine, but my Ubuntu server is unable to connect to the Internet when bridged. This may not be an issue as I can share files between machines using a shared folder. I will need to do more research to be sure.
 * 2/7: Running SSH and FTP software on Host to VM (bridged) is now working: Filezilla on Windows host and proftpd on Linux guest. Determined that VirtualBox does not yet fully support Windows 10 OS resulting in guest machine not being able to connect to Internet when using a bridged connection.


 * Plan:
 * 2/3: Find more logs on TORQUE and get a better understanding of its purpose.
 * 2/4: Discuss TORQUE with the rest of the tools group and create a VM on my laptop for testing tools implementations and installations. Look into installing Sphinx and Switchboard corpus on my Ubuntu server.
 * 2/5: Create a bridged connection so that I can SSH into my VM from my windows host machine.
 * 2/6: Continue to look into my connection issue and installing Sphinx and Switchboard corpus on my Ubuntu server.


 * Concerns:
 * 2/3: TORQUE installation and configuration may be too complex to accomplish before end of semester.
 * 2/4: Same as 2/3.
 * 2/5: Complexities of setting up VM server similar to how Caesar is setup may be great.
 * 2/6: I am not sure how my server's connection issues will be resolved.

Week Ending February 16, 2016

 * Task:
 * 2/13: Read Logs from last semester.
 * 2/14: Read Logs from last semester.
 * 2/15: Researched Sphinx 3 vs Sphinx 4.
 * 2/16: Continued Research.


 * Results:
 * 2/15: Found a CMU comparison: From CMU website.
 * 2/16: Based on research and previous semester's research, Sphinx 4 has major differences from previous version Sphinx 3, but does not have performance improvements. An upgrade is likely not worth it, unless we plan on changing the project's architecture to SOA.


 * Plan:
 * 2/13: Continue reading logs. I will not continue building my sphinx virtual machine based on Jonas' feedback.
 * 2/14: Research Sphinx 3 vs Sphinx 4.
 * 2/15: Continue research.
 * 2/16: Continue research and learn more about Sphinx.


 * Concerns:
 * 2/13: None.
 * 2/14: None.
 * 2/15: Need to find more research.
 * 2/16: None.

Week Ending February 23, 2016

 * Task:
 * 2/20: Continued researching Sphinx Decoder version 3 vs version 4.
 * 2/21: Researched Sphinx Decoder and CMU Language Model Toolkit. Met with Tools team to discuss proposal and findings.
 * 2/22: Read logs from last year. Uploaded speech papers as PDFs to this website using this tool.
 * 2/23: Read logs from last year and added another link to the 'Speech Recognition Related Readings' page.


 * Results:
 * 2/20: After more research on the java decoder I am still not convinced that it would benefit the project.
 * 2/21: Same as yesterday.
 * 2/22: Updated the speech software page and proposal. Linked a couple papers in the 'Speech Recognition Related Readings' page.
 * 2/23: Added a speech reading link.


 * Plan:
 * 2/20: Update 'Speech Recognition Related Readings' page with some additional readings.
 * 2/21: Update proposal with findings.
 * 2/22: Read logs.
 * 2/23: I need to start working on emacs install once the machines are connected.


 * Concerns:
 * 2/21: None.
 * 2/21: None.
 * 2/22: Hoping that the Systems team is working on connecting the remaining machines to the network, which I believe is all of them but Caesar.
 * 2/23: None.

Week Ending March 1, 2016

 * Task:
 * 2/24: Talk with group about backup system.
 * 2/26: Work on Proposal.
 * 2/27: Meet with team. Discuss Proposal with group and made changes.
 * 3/01: Review Tom's sox fix page and check rsyncBackups dir.


 * Results:
 * 2/24: Reviewed Hard Links.
 * 2/26: Work on Proposal.
 * 2/27: Discussed Proposal with group and made changes.
 * 3/01: Getting caught up with what other group members are working on.


 * Plan:
 * 2/24: Work on proposal.
 * 2/26: Edit proposal with group.
 * 2/27: Now that the proposal is done, I need to start working on the emacs install on Majestix and read logs.
 * 3/01: emacs install.


 * Concerns:
 * 2/24: None.
 * 2/26: None.
 * 2/27: None.
 * 3/01: None.

Week Ending March 8, 2016

 * Task:
 * 3/05: Research rsync issues with deleted files so that we can explain what happened to the sox lib files.
 * 3/06: Continue research on rsync. Generate SSH key for SSO connection to other machines.
 * 3/07: Search for specifics on deleted files from rsync use with a narrow focus of the parameters Tom used. Add recommendations for software upgrades to Tools group page.
 * 3/08: Read logs and emacs documentation from last years tools group.


 * Results:
 * 3/05: Did some general research on how rsync works and some of the parameters it takes. No direct results; building a foundation for more rsync research.
 * 3/06: Successfully generated an ssh key and connected to other networked machines using ssh. No new findings on rsync. Logged into Majestix (192.168.10.5) using root; no usr files on Majestix.
 * 3/07: I did not find any blogs or articles on rsync deleting files with the following commands (what Tom used, -n meaning dry-run):

rsync -anv --ignore-existing /usr/lib/libX* root@caesar:/usr/lib/ rsync -av --ignore-existing /usr/lib/libX* root@caesar:/usr/lib/


 * 3/08: Found Refic's logs on the emax install that he did. He is missing a detailed account of which files were added during the install. The emacs page is missing these details as well.


 * Plan:
 * 3/05: I need to do a more thorough investigation into what could go wrong with rsync, specifically when using the commands Tom was using.
 * 3/06: Continue research on rsync.
 * 3/07: Checkout details of what last year's tools group did with emacs.
 * 3/08: Discuss with group the need for another emacs install on Majestix. It would be nice to know emacs' dependencies.


 * Concerns:
 * 3/05: I was not able to find many detailed accounts of deleted files using rsync. The link Professor Jonas sent us about rsync deletion issues was good, but it was narrowly focused to the usage of the rsync --delete-after option which deletes extraneous files from dest dirs after transfer.
 * 3/06: None.
 * 3/07: None.
 * 3/08: We may have to redo what last year's Tool's group did if, after discussing with my group, we decide that we need more information on what files emacs uses.

Week Ending March 22, 2016

 * Task:
 * 3/12: Research how to install Emacs on the Internet and logs.
 * 3/19: Determine how to install a compiler on Majestix by reading other semesters logs and scanning the Internet.
 * 3/20: Read logs on running an experiment.


 * Results:
 * 3/12: Emacs requires a C compiler to install.
 * 3/19: Determined that Majestix does not have a subscription to Redhat setup using the command: $root subscription-manager version. This will limit our available options for installing the compiler unless we are able to fix it.
 * 3/20: I cannot find the createWikiExperiment.pl script using the find command. I will ask other team members where it is.


 * Plan:
 * 3/12: Research how to install a compiler.
 * 3/19:
 * 3/20:


 * Concerns:
 * 3/12:
 * 3/19:
 * 3/20:

Week Ending March 29, 2016

 * Task:
 * 3/26: Install a compiler on Majestix, then Install Emacs.
 * 3/27: Determine a solution to get the GCC compiler on Majestix and learn how to run an experiment.
 * 3/28: Work with Systems group to get an Internet connection on Majestix.
 * 3/29: Work on SSH issue on Caesar - currently Caesar asks for a password (this is ok for root) whenever SSHing into it.


 * Results:
 * 3/26: Spent the day working on getting the GCC compiler on Majestix with its dependencies. Here is what I did:

Determine cpu architecture $ lscpu Result: i686 (32-bit) on Majestix GCC version 4.4.X is what is offered for RHEL 6.6 (Red Hat Enterprise). Opted to go with newest version of 4.4 which was 4.4.7, and because I couldn't find the exact version that RHEL offers in 6.6.

Download files to caesar (I downloaded on my pc and used Filezilla to transfer to caesar tmp folder)

While in dir that FTPed files are in use cmd (Edit on 5/3/16: rsync may be an easier route than tar piped ssh cmd): $ tar zcf - gcc-4.4.7.tar.gz | ssh root@majestix 'tar zxf -' Copy dependency files: $ tar zcf - gmp-4.3.2.tar.bz2 | ssh root@majestix 'tar zxf -' $ tar zcf - mpfr-2.4.2.tar.bz2 | ssh root@majestix 'tar zxf -' $ tar zcf - mpc-0.8.1.tar.gz | ssh root@majestix 'tar zxf -' $ tar zcf - libelf-0.8.13.tar.gz | ssh root@majestix 'tar zxf -'

Also copy app tars: $ tar zcf - emacs-24.5.tar.gz | ssh root@majestix 'tar zxf -' Result: Copies files to majestix root home directory (/root).

Moving to folder where it will be installed (could have done this in previous cmd somehow, may need to do $ mkdir gcc): $ mv gcc-4.4.7.tar.gz /etc/gcc

Also, move dependencies: $ mv gmp-4.3.2.tar.bz2 mpfr-2.4.2.tar.bz2 mpc-0.8.1.tar.gz libelf-0.8.13.tar.gz /etc/gcc/lib_4.4.7/

Now unpack tar files (while in the correct dir):

$ tar xzf gcc-4.4.7.tar.gz $ tar xjf gmp-4.3.2.tar.bz2 $ tar xjf mpfr-2.4.2.tar.bz2 $ tar xzf mpc-0.8.1.tar.gz $ tar xvzf libelf-0.8.13.tar.gz --->throws error

Include GCC in PATH variable $ export PATH="$PATH:/etc/gcc/gcc-4.4.7"

$ $PWD/../gcc-4.4.7/configure --prefix=$HOME/gcc-4.4.7 --enable-languages=c,c++,fortran --->throws error

In regards to the errors:

I am still not sure why libelf failed, but due to the other error it doesn't matter now.

The issue with the ./configure cmd above is that there is no compiler (obviously) to build it. I should have foreseen this. There is no simple solution from here. I am getting the same result on Caesar (even though it wouldn't work to copy the compiled binary over to Caesar as Caesar is x64 and Majestix is x32) as there is no compiler in Caesar's PATH. I am going to email professor Jonas to see what he suggests. I will question why there was no compiler installed on, at the very least, Majestix during the OS install as it should have been an option.


 * 3/27: Professor Jonas suggested that we take Zach and Erol's machine offline so that we can use their Ethernet connection as a temporary Internet connection for Majestix. This will allow us to register Red Hat which will allow for us to be able to use the yum repos to install GCC on Majestix.
 * 3/28: We were able to get a hold of Zach and Erol, who owned the other server connected to the Internet besides Caesar, but even though we had the Ethernet connection we were not able to get the connection working.
 * 3/29: No progress was made here, but we have eliminated possibilities of what it could be such as file permissions, authorized_keys values, and a couple other possibilities that we hammered out by just searching google of ssh issues that people have. For instance, I read somewhere that encrypted home directories will give ssh an issue so I made sure that our home directories weren't encrypted by again searching online for how to do this. I think I used ls -A and search for a hidden encryption folder.


 * Plan:
 * 3/26: I need to run an experiment. I also need to install Emacs. What I do tomorrow will depend on if I hear back from the professor or not.
 * 3/27: Follow up with Neil from the Systems group.
 * 3/28: Wait to hear back from Systems group while working on SSH.
 * 3/29: We need the Internet connection on Majestix.


 * Concerns:
 * 3/26: Getting a compiler on Majestix, seems like we will need an Internet connection in order to get a compiler.
 * 3/27: None at this moment, waiting to hear back from Systems/Tools group members on how we can coordinate the temp Internet connection on Majestix.
 * 3/28: We need to get the Internet connection on Majestix working.
 * 3/29:

Week Ending April 5, 2016

 * Task:
 * 3/31: Install Emacs on Majestix and take logs of all the lib & bin dirs so that I can do a diff on the log files in order to see what files the Emacs installation added.


 * 4/02: Learn training and decoding by doing a practice run.
 * 4/04: Finish training and decoding. Also finish Emacs install log by doing diffs on the before-emacs and after-emacs ls -al txt files.
 * 4/05: Determine how to view WER and the decode log. I tried to view hyp.trans or scoring.log, but only saw text rather than WER or any numerical data.


 * Results:
 * 3/31: I made a mistake during the installation when prompted with y/n by the yum installer on Majestix - it was displaying the dependency packages that were installed and I wanted to have a general idea of what was installed so that when I ran the diff commands I could compare those results with a screenshot of the install. I pressed fn+alt+printscreen for a screenshot. Alt only takes a snapshot of the current window and I pressed fn because my laptop at work has printscreen as a fn rather than a key and I had just worked a 10hr day so it was habit. On my laptop keyboard at home fn+prntscrn is airplane mode so I dropped my connection from PuTTY and right clicked to reconnect after switching airplane mode back off which brought me to Caesar. I quickly hit up arrow because it was the last cmd I had entered and took a screenshot and entered y when prompted and as soon as I saw the jmq85@caesar pop-up I froze up because I realized what I had done and soon after I sent an email to professor Jonas. I did not undo my install because I could have completely removed Emacs dependencies.

Here are the commands that I executed during the install: ls -al /bin > snapshot/before-emacs/bin.txt ls -al /usr/bin > snapshot/before-emacs/usr-bin.txt etc...

yum install emacs

ls -al /bin > snapshot/after-emacs/bin.txt ls -al /usr/bin > snapshot/after-emacs/usr-bin.txt etc...


 * 4/02: Both of our servers are down, but Caesar is running however someone is running a long decode on it. I probably won't be able to run a train/decode until Monday as the building is locked.
 * 4/04: Started running a train. hoping it will be done soon so I can run a decode on it. Finished up logging the Majestix install by doing the following cmd on all 9 or 10 files:

diff before-emacs/bin.txt after-emacs/bin.txt > diff-emacs/bin.txt diff before-emacs/var-lib.txt after-emacs/var-lib.txt > diff-emacs/var-lib.txt
 * 4/05: I communicated with Ryan on how to view the log for the decode because I wasn't seeing the WER or the table that everyone else is posting on the Experiment Wiki.


 * Plan:
 * 3/31: When Majestix is back up, log diffs of before_install and after_install directories. This will help to determine what Emacs dependencies/files may have been overwritten on Caesar.
 * 4/02: Resume my practice run on Monday or Tuesday when resources aren't so tight.
 * 4/04: Work on getting a decode running on the train.
 * 4/05: Reinstall Emacs using tar file rather than yum so that we can keep any GUI files out of the install.


 * Concerns:
 * 3/31: Looks like training and decoding is still working after the Emacs mishap on Caesar. I am hoping that we can get the same results that we were before.
 * 4/02: The other servers being down.
 * 4/04: I am hoping to hear back from Professor Jonas on the mistaken Emacs install on Caesar and am hoping that the lib that got overwritten did not affect the train/decode process.
 * 4/05:

Week Ending April 12, 2016

 * Task:
 * 4/09: Research all of the bin, lib, and other directories that could change when doing an application install on a Linux machine.
 * 4/10: Emacs tar install.
 * 4/11: Continue Emacs install so that the emacs-nox version launches when typing emacs in the shell on Majestix.
 * 4/12: Continue Emacs-nox install.


 * Results:
 * 4/9: Added some more directories to our existing list that Professor Jonas gave us. Here is what I have so far:

Given by Jonas: 1) /bin 2) /lib 2) /sbin 3) /sys 4) /sys/bin 5) /usr/sbin 6) /usr/bin 7) /usr/lib 8) /usr/local 9) /sys/lib 10) /var/lib 11) /var/local 12) /usr/share/lib*

From research: 13) /usr/share 14) /usr/local/bin 15) /usr/local/sbin 16) /usr/local/lib 17) /usr/libexec 18) /var/lib/alternatives ??? 19) /etc/alternatives ???


 * 4/10: I found that the Emacs package without the GUI is called Emacs-nox, where X is the gui meaning no gui. Downloaded it onto my computer and FTPed it to Caesar (/root/tmp) using Filezilla. Then I did the following steps:

Copy .tar file from Caesar to Majestix root folder (while root in the same directory as the .tar file) tar zcf - emacs-nox-24.5-3-i686.pkg.tar.xz | ssh root@majestix 'tar zxf -'

Then do snapshots of all the install directories (I know of 19). ls -al /bin > ~/snapshot/before-emacsnox/bin.txt ls -al /lib> ~/snapshot/before-emacsnox/lib.txt ls -al /sbin > ~/snapshot/before-emacsnox/sbin.txt ls -al /sys > ~/snapshot/before-emacsnox/sys.txt ls -al /sys/bin > ~/snapshot/before-emacsnox/sys-bin.txt etc... (for all 19 listed above)

I unzipped the tar file to /usr/local/emacs-nox-24.5 using this command (while in roots home directory, where the tar file is): tar Jxf emacs-nox-24.5-3-i686.pkg.tar.xz -C /usr/local/emacs-nox-24.5

I tried searching for a configure file or a make file and realized that the tar file contained the binaries already.

Tried to run Emacs using: /usr/local/emacs-nox-24.5/usr/bin/emacs

I encountered this error: error while loading shared libraries: libncursesw.so.6: cannot open shared object file: No such file or directory

I installed ncursesw6.0 as a tar by SSHing its tar from Caesar to Majestix then unzipping it to /usr/local/emacs-nox-24.5-depends and running ./configure, make, and make install in its directory but I am still getting the same error message.


 * 4/11: Emacs is still not working, I tried a few things:

Tried to find libncursesw.so.6 on Caesar so that I could copy it over, but it wasn't there. This may not have worked anyways because Caesar is 32 bit.

Tried creating a soft link to a couple different libs in ncurses6 which did not work because it threw a different error: Command to try to trick emacs into thinking it had the right lib: ln -s /usr/local/emacs-nox-24.5-depends/ncurses-6.0/lib/libncurses_g.a /usr/lib/libncursesw.so.6 Error msg: /usr/local/emacs-nox-24.5/usr/bin/emacs: error while loading shared libraries: /usr/lib/libncursesw.so.6: invalid ELF header

Created a 32bit Ubuntu virtual machine to try to use the package manager installer for emacs-nox to see what dependencies it has so that I don't mess up the emacs install logs any further by trying the wrong libs. This is the command I found online: (tried a number of repos, none of which had the package) sudo apt-get install emacs-nox
 * 4/12: Tom helped me find a couple of the lib files including libncursesw.so.6. I tar/ssh piped gnutls to Majestix and unzipped it using:

rpm2cpio gnutls-3.4.10-1.fc25.src.rpm | cpio -idmv

Tom was able to find the lib file in gnutls that Emacs was looking for. Emacs-nox is still asking for more dependencies.


 * Plan:
 * 4/9: Do Emacs install tomorrow using tar install method.
 * 4/10: Try to finish Emacs install tomorrow.
 * 4/11: Work on an in-depth search online for libncursesw.so.6. I only spent an hour looking last time. It has to be out there somewhere.
 * 4/12: Talk with Tom in class to figure out where & how he found the lib files so that I can continue the install this coming week.


 * Concerns:
 * 4/9: Finding a version of Emacs without the UI piece attached could be challenging.
 * 4/10: I alerted my group that I am not done with the Emacs install, so hopefully no one logs on and changes anything so that it doesn't mess up my diffs. It is also concerning that installing ncurses 6.0 did not fix my error message. This might mess up the diffs.
 * 4/11: Finding the right libs. Hopefully I only need this one, but its likely I will need at least a few. Hopefully the others are not so difficult to find.
 * 4/12: I am hoping that there are not too many more dependency files.

Week Ending April 19, 2016

 * Task:
 * 4/14: Find remaining lib files for Emacs-nox install.
 * 4/17: Group work & finish Emacs install.
 * 4/18: Secret group work.
 * 4/19: Secret group work.


 * Results:
 * 4/14: I found the possible remaining dependencies for emacs here: https://www.archlinux.org/packages/community/i686/emacs-nox/. I downloaded libtasn because that is the lib that Emacs is now asking for. This is the error that I am getting: "./emacs: error while loading shared libraries: libtasn1.so.6: cannot open shared object file: No such file or directory".

I am not able to hold a connection to Caesar with Filezilla so I asked my group if they were having connection issues as well. A few people responded that they have had slow connections and Aaron offered to check out Caesar in the server room after his class gets out. He later responded that Caesar was throwing 3+ errors and that the VGA ports were not working. I was unable to get the dependency file to Caesar in order to transfer it to Majestix.


 * 4/17: Secret group work.
 * 4/18: Secret group work.
 * 4/19: Secret group work.


 * Plan:
 * 4/14: I will keep trying to connect to Caesar everyday after work so that I can hopefully finish off this long overdue Emacs install. On 4/15 & 4/16 I am still seeing the same issue and have been unable to connect to Caesar using Filezilla.
 * 4/17: I could not connect to Caesar using Filezilla, kept getting a dropped connection, so I emailed the group to see if they were able to get in using an FTP app and Daisuke responded. He put the libtasn1 install file into the /tmp folder for me.
 * 4/18: Secret group work.
 * 4/19: Secret group work.


 * Concerns:
 * 4/14: I will reach out to my Tools group team members tomorrow if I cannot connect so that I can get this install completed. Daisuke and Nigel are waiting for me to finish so that they can install screen and tree on Majestix.
 * 4/17: None
 * 4/18: None
 * 4/19: None

Week Ending April 26, 2016

 * Task:
 * 4/22: Secret Group Work.
 * 4/23: Emacs-nox install.
 * 4/24: Emacs install, trying an older version.
 * 4/25:


 * Results:
 * 4/22: Secret Group Work.
 * 4/23: Had trouble finding the lib files required by Emacs in the glibc-2.15.tar.gz, glibc-2.16.tar.gz, glibc-2.17.tar.gz extracts. Seems like picking the newest version of emacs may not be the best idea given that I am having to update nearly every dependency.
 * 4/24: The older version worked and I did not have any missing dependencies. I redid all the snapshots. Emacs-nox is now working.

These are the diff results (###this indicates a new diff .txt file###): 3c3 < drwxr-xr-x. 13 root root 4096 Apr 10 20:22 .. --- > drwxr-xr-x. 14 root root 4096 Apr 24 12:07 ..
 * 1) /usr/local/bin###

3c3 < drwxr-xr-x. 13 root root 4096 Apr 10 20:22 .. --- > drwxr-xr-x. 14 root root 4096 Apr 24 12:07 ..
 * 1) /usr/local/lib###

3c3 < drwxr-xr-x. 13 root root 4096 Apr 10 20:22 .. --- > drwxr-xr-x. 14 root root 4096 Apr 24 12:07 ..
 * 1) /usr/local/sbin###

1,2c1,2 < total 52 < drwxr-xr-x. 13 root root 4096 Apr 10 20:22. --- > total 56 > drwxr-xr-x. 14 root root 4096 Apr 24 12:07. 4a5 > drwxr-xr-x. 3 root root 4096 Apr 24 12:08 emacs-nox-23.1
 * 1) /usr/local###


 * 4/25:


 * Plan:
 * 4/22: Work with Daisuke over the weekend on Emacs and maybe train/decode.
 * 4/23: Try a fresh install of an older Emacs and redoing the snapshots. Tom recommended the same version as the yum installed Emacs (with a GUI) and gave a link to the emacs-nox version 23.1.
 * 4/24: See what I need to do for group work.
 * 4/25:


 * Concerns:
 * 4/22: None
 * 4/23: None
 * 4/24: None
 * 4/25: None

Week Ending May 3, 2016

 * Task:
 * 4/30: Complete Emacs Hotfix install on all servers.
 * 5/01: Talk with Daisuke about the Screen install.
 * 5/02: Same as yesterday.
 * 5/03: Edit Emacs wiki page.


 * Results:
 * 4/30: All of the servers, except Caesar, are able to run Emacs. I am waiting to hear back from Tom on whether or not I should attempt to create the links to the hotfix dir on Caesar although it seemed like he wanted to wait for Jonas to do the wipe on Caesar first since I had mistakenly installed Emacs using Yum resulting in the directories already existing. Basically, it is safer to not delete anything on Caesar our selves and let Jonas do it.

I worked with Tom during class on Wednesday to figure out where Emacs-nox dependencies were located. The snapshots that I took were not helpful so he suggested copying the Emacs executable, emacs/usr/bin/emacs-23.1-nox, to Miraculix and running it to see where it was looking for files. I found that it was looking in two places, /usr/libexec/emacs and /usr/share/emacs. We then moved the directories over from Majestix to Miraculix to verify that Emacs would run. It ran so we then moved the executable and 2 directories over to the hotfix dir at /mnt/main/local/lib/hotfix/emacs after creating the emacs dir.

Today on Obelix, Miraculix, Idefix, and Asterix this is what I did to create an Emacs-nox hotfix (as root):

First I deleted the Emacs test dir on Miraculix and removed the links pointing to it in /usr/libexec and /usr/share.

*Create a link to emacs executable in /usr/bin (while in /usr/bin): ln -s /mnt/main/local/lib/hotfix/emacs/usr/bin/emacs-23.1-nox emacs

*Link emacs hotfix libexec dir to current server's /usr/libexec dir named emacs (while in /usr/libexec): ln -s /mnt/main/local/lib/hotfix/emacs/libexec/emacs emacs

*Link emacs hotfix usr/share dir to current server's /usr/share dir named emacs (while in /usr/share): ln -s /mnt/main/local/lib/hotfix/emacs/usr/share/emacs emacs


 * 5/01: We made some progress, I had to leave while he was creating before-screen snapshot txt files.
 * 5/02: I added Linux-PAM-0.8.0 tar file to Majestix and unzipped it. I was not able to find the lib that screen was looking for. I also could not find the executable for screen.
 * 5/03: Edited the Emacs and Emacs Status sections. I kept about half of the Emacs section and completely redid the Emacs Status section.


 * Plan:
 * 4/30: Contact Daisuke about the screen install because I had mentioned in class that I would help him if he still wanted to try it. If there are more than 2 dependencies we will likely not go through with it. Also possibly group work. I am waiting to hear back from Tom as well about hot fixing Emacs on Caesar.
 * 5/01: Edit the Emacs install page with my findings.
 * 5/02: Edit the Emacs wiki page with my install steps and findings.
 * 5/03: Finish the hotfix links on Caesar once Professor Jonas wipes Caesar when the semester is over. This will complete the Emacs Install.


 * Concerns:
 * 4/30: None
 * 5/01: None
 * 5/02: None
 * 5/03: Wondering how long I will need to wait after the semester is over to finish the hotfix links on Caesar.

Week Ending May 10, 2016

 * Task:
 * 5/06: Create links to hotix on Caesar now rather than waiting for Caesar to be wiped. Requested by Professor Jonas.
 * 5/07: Add more detail to Emacs wiki page and create a hotfix link to the Emacs page on the Speech Software Functionality page.
 * 5/10: Add to the report for the tools group.


 * Results:
 * 5/06: Emacs is now running on Caesar.
 * 5/07: Created a link to GNU's Emacs manual and added a couple sentences to the page. Also created a link from the Software Functionality page to the Emacs hotfix page.
 * 5/10: Created links and content in the report.


 * Plan:
 * 5/06: Add more detail to the Emacs wiki page such as guides on how to use Emacs for next semester. I also need to add my research findings to the final report.
 * 5/07: Add to the report.
 * 5/10: I may need to add more documentation, there is never enough.


 * Concerns:
 * 5/06: None
 * 5/07: None
 * 5/08: None
 * 5/10: None