Resources

Changing Your Faculty of Engineering Account Password

To change your password, use Autopass the account management interface.

Note that this will not affect your UOAccess account, but only your Faculty of Engineering account, which is deprecated for most users.

Connect Remotely

You can connect remotely to the Faculty of Engineering using SSH for textual session or SFTP for file transfer. SSH for Windows is made available for download:
http://www.ccs.uottawa.ca/software/licensed/ssh/download.html
The host used for those connections is ugate.site.uottawa.ca

Lost Files

Windows

On the local hard drive, you can recover the file from the Windows Recycling Bin, as long as you are logged into the same session as when you deleted the files and you haven't emptied the Recycling Bin. Once you log off the workstation, all personal files you may have left on the local hard drive will be deleted permanently.

If the file was deleted from your network drive (H drive) the deleted file will not go to the recycle bin. It is permanently deleted. You may be able to get the file recovered from the previous day's backup if the file existed then. Send an email to support@genie.uOttawa.ca indicating the date of the last known good copy/version, of the document, its name and the directory where the file resides.

You should be aware that the chances of recovering files is inversely proportional to the amount of time that has elapsed since you erased your files, and to how much activity there has been on the system.

Unix

Erased files are totally unrecoverable. Hence, be very careful with the 'rm' command. You may be able to get the file recovered from the previous day's backup.
The recovery procedure is the same for Unix as for Windows: send an email to support@genie.site.uottawa.ca indicating the date of the last known good copy/version, of the document, its name and the directory where the file resides.

Create web pages

Any user with a Faculty of Engineering account can create web pages. To do so, ssh to your Unix account to linux.site.uottawa.ca and verify that you have a public_html directory; the directory should have been created already. If not, create the directory 'public_html' and make it readable and executable to everyone:

   mkdir public_html
   chmod 755 public_html

You may want to investigate the 'chmod' command manual page, using 'man chmod'.

Make sure that your root directory has executable access set for everyone. To do this, go to your root directory (directory you are in when you login) and type the following command:

   chmod 711 ~

Note that the ~ character is part of the syntax.

You can then create files and sub-directories in the 'public_html' directory. Ensure that any file you create is set to be world readable; any directory must be set to world executable.

You might want a default Web page. You simply need to create an html file named index.html in your 'public_html' directory. The content of your index.html file could be:

<html>
    <body>
         <h1>Welcome to my Web site</h1>
    </body>
</html>

Your personal Web page will be accessible via this URL:

       http://www.site.uottawa.ca/~login

where login is your Faculty of Engineering login.

SITE email disambiguation

Since 2008, SITE no longer provides email services to undergrad students; this service is provided by IT.

Versioning with subversion

Subversion is an open source version control system. It was designed to replace (improve upon) CVS.. There is a Subversion Book available on-line (in various formats).

 - Modes of Operation
Subversion offers different modes of operation; usage dictates which one to chose. Those modes and their typical usages are summarizes as follows:

  public server : accessible on- and off-campus
    svnserver: universal (Internet) read access; write access limited to owners/collaborators;
    semi-public server : accessible on- and off-campus
    httpd+WebDAV: authorisation based on (and limited to) Faculty of Engineering users/groups authentication;
  private server : within user space and under user control
    svnclient on top of filesystem, not much different from an editor or compiler
    svnserver over SSH, permitting off-campus capability

 - Public SVN Server
This is the common version of a centralized service. It is meant to be accessed mostly in read-only mode. Initially, the system administrator creates an empty repository and grants write privileges to a small number of individuals. After a while, existence of the repository is publicized. Off-campus (non-faculty) users may become active participants.

Researchers with on-going or long term projects would probably want to have the repository of their work reside here. Copies of the latest version of their documents become available immediately. Colleagues from other institutions can become active members.

You should contact the Faculty of Engineering Support Team if you want to have a centralized Subversion repository setup.

 - Semi-Public HTTP+WebDAV Server
HTTP+WebDAV provides repositories centralized and public as the regular centralized SVN server described previously, but with a few variations, resulting mostly from being a WEB server component.

 Pros:
   access to files is possible through a web browser
   integrated authentication (Faculty of Engineering accounts and groups)
   possibility of encryption (SSL)
   Cons:
   noticeably slower over HTTP, even more so when encrypted
   write privileges are limited to authenticated (Faculty of Engineering) users

This kind of server is best suited for short term projects, like a software engineering course requiring groups of users to manage and use repositories as part of some exercises or projects. For example, a repository could be attributed to a group of students, maybe even one per student.

You should contact the Faculty of Engineering Support Team if you want to have a centralized HTTP+WebDAV repository setup.

- Private SVN Repository
A private SVN repository is meant as a sandbox for users who want to experiment with Subversion. This would be for academic purposes, and on an individual basis.

Since the access is performed via the file-system, the user maintains full control over the resource. All operations that can be performed by a centralized SVN server are possible here too, with the exception of sharing write privileges with other users (making one's repository public - or readable - is possible).

Users have the possibility to remotely accessing it, either on-campus or off-campus. This mode of operation is identified as SVN+SSH.

Users can create (and destroy) private SVN repositories at will (within the limits of the existing system, and under constraints such as quota imposed on disk space).

Back to top