Problem 1: Preventing users from downloading/saving items to the computers. This would “junk up” the computer, possibly creating privacy issues and potentially introducing malware to the system.

Walker, the TA for the 451 course, wrote a script to be created in the root user’s cron file which would automatically reset desktop for the “Genuser” account each evening. If the computer was not powered up at the time that the script was scheduled to run, then the ancron function of the operating system would automatically run the script the next time the computer was powered up. For the text of the script, see: Linux Clean Desktop Script

Problem 2: Automating the download and installation of Mint OS updates to improve network security. Mint notifies a user that there are updates available, but an administrator needs to log in and approve the installation manually. The project team isn’t sure that there will be someone at Second Chance who will remember to regularly complete this task.

Again, Walker helped by writing a script to be created in the root user’s cron file which would use the “apt get” command to weekly go to the repositories, search for and install updates to the OS and other applications. While on-site for the third visit, we debated whether it would be more risky to install a potentially unsafe update or to not update the system at all. In the end, we (Martin, Adam [from the Morning Star group] and Fiona decided to use the script to update with one modification. The original script Walker created included a command to also upgrade the software. This was removed from the script before it was copied into the cron.weekly folder. For the script as it was added to the computers, see: Linux Auto-Update Script

Problem 3: Preventing users from accessing Websites deemed “inappropriate” by the shelter’s administrators.

A no-cost online solution, OpenDNS.com, was used to provide the site administrators with the option of blocking certain types of Web content. By directing the Internet browser to the OpenDNS servers, the site administrators, using a secure account, can determine what types of sites (e.g., adult content, drug-related, gambling) or even which specific sites (by entering a URL) they wish to have blocked. This type of solution can be troublesome at times, blocking some sites that probably should be allowed and allowing users to view others that may not be desirable, but with some time, the administrators should be able to fine tune the settings to achieve the level of security that they want.

Problem 4: Ensuring that Open DNS will continue running despite the variable IP address.

Because the IP address that the shelter’s broadband router assigned by their Internet Service Provider is variable, we needed to have a means of ensuring that the Open DNS settings selected by the site administrators would persist. The Open DNS site had links to software/solutions produced by others that would solve this problem. On the fly, Martin developed a script to run using the cron command in Linux that would periodically go to a Website that would tell us the current IP address and would then update it through Open DNS. More information about the script can be found here:Open DNS solution for variable IP

Problem 5: Finding a way for residents to store files (like their resume) without resorting to the expense of a flash drive or allowing storage on the hard drive or desktop.

Permanent file storage for the users was an important matter to consider at both sites.  One of the primary intended purposes of these computers was to provide a means for adult residents to find employment and/or job training.  Adult residents, therefore, would be using the computers to work on resumes, download job applications, and save contact information for potential employers, etc.  In order to ensure for them the best chance of success, they had to have a way to access their files after leaving the shelter.  The cost of purchasing a flash drive for every resident would be too expensive. Therefore, it was decided that Google Docs was the best solution and Sharon Jackson, the shelter Director at the time was in agreement with this solution. Tutorials on creating a Google account and using Google Docs was created and saved in the Tutorials folder on the Genuser desktop of each computer. In addition, help documents created by Google on how to use Google Docs were bookmarked in tutorials folder on Firefox.

Problem 6: Lack of functional Internet connection to the basement lab location.

During the initial site visit in September, the group believed that there was a functional Internet connection to the basement lab, but, because the lab was no longer functional, it wasn’t in use. Therefore, we had anticipated that once we brought in the new machines, it would just be a matter of setting up the workstations and making the network connections. When we returned in November to set up the lab, we discovered that the Internet connection was not functional and upon further investigation, realized that the cable running into the lab came from an antenna on the roof of the shelter that was installed in the early 2000s to pick up a wireless Internet signal from a transmitter that had been set up on a radio tower. The wireless transmitter proved to be unsustainable (lightning kept knocking it out, requiring costly and time-consuming repairs). Therefore, there hadn’t been an Internet connection for the lab for at least three or four years. The shelter’s office on the main floor, however, did have Internet access via a DSL connection. Therefore, the solution was to run a cable from the router in the office on the first floor to the switch in the lab in the basement. Accomplishing this, however, was no easy task since the two areas were on different floors and on opposite sides of the building. Fortunately, we had brought two boxes of cable, cable-making equipment, and had an extra switch that could be used to make the connections (since the all the router’s jacks were already in use). With Martin’s assistance, Fiona surveyed the building for pre-existing holes or openings through which the cable might be able to pass. In the end, Martin was able to map out a route that would take the cable through the basement wall into the lab along a hot-water pipe, up through a hole next to the staircase (through which another pipe was running), then (hopefully) through another pre-existing hole in the wall into the office and above the drop ceilings and down into the Director’s office where the router was located. Mary Ann, Paula and Fiona tried to start the cable running through the wall of the lab using two straightened coat hangers, but were having little success. Fortunately, the shelter supervisor on duty that day, Ricky Perkins, had construction experience and took on the task himself. He was able to devise a better way to run the cable and soon had it going from the computer lab up to the first floor hallway. We ran into a second roadblock when we couldn’t find a way through the wall of the office and tried to run it at the top of the doorjam. This, however, wouldn’t work as the cable would be pinched by the door and so it was decided that we would run it under the door (well taped) where there was clearance. Our visit ended before the cable could be run and finished and so we left the cable with Ricky to finish some time before one or more of us would return in early December.

When Fiona and Martin arrived at the shelter on December 5 for the final visit, they discovered that the cabling hadn’t progressed past the point at which it was left in November. Ricky was on duty, though, and worked with Fiona and Martin to finish running the cable with minimal difficulty. The cable was then finished off at each end, a second shorter cable was made to connect the new switch to the router, and everything was connected and the six lab computers had Internet access at last!