UMIACS - User contributions [en]

Main Page

2014-09-19T16:20:21Z

Jlent:

==Announcements==
<startFeed />

Please see our [https://intranet.umiacs.umd.edu intranet] page for announcements.

<endFeed />

==Technical Reference==

Welcome to UMIACS Wiki. This is the main place to find documentation and information about your account and the technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].

We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].

We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.

Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].

If you would like to open a support ticket, please contact the UMIACS [[HelpDesk]].

__NOTOC__

MonthlyMaintenanceWindow

2014-09-09T15:33:37Z

Jlent:

UMIACS takes a monthly maintenance window to patch and reboot our hosts. This provides a way to ensure security updates are installed and activated on the numerous different platforms and appliances that we maintain.

The window is calculated each month by adding 9 days to [http://en.wikipedia.org/wiki/Patch_Tuesday Microsoft's Patch Tuesday]. This allows us to marshal patches released that month from Microsoft, Red Hat, and our other vendors and have enough time to get our systems prepared to reboot for that month's window.

The window is always going to be on a '''Thursday''' from '''8pm-12am'''. A list of maintenance windows for 2014 is as follows with the upcoming window in bold.

* '''September 18th 2014'''
* October 23rd 2014
* November 20th 2014
* December 18th 2014

==Archives==
* January 17th 2013
* February 21st 2013
* March 21st 2013
* April 18th 2013
* May 23rd 2013
* June 20th 2013
* July 18th 2013
* August 22nd 2013
* September 19th 2013
* October 17th 2013
* December 19th 2013
* January 23rd 2014
* February 20th 2014
* March 20th 2014
* April 17th 2014
* May 22nd 2014
* June 19th 2014
* July 17th 2014
* August 21st 2014

Main Page

2014-09-09T15:33:10Z

Jlent:

==Announcements==
<startFeed />

=== 8/11 Phishing Attempts ===
Staff has received word that users are seeing mail claiming that their email quotas are nearly full and action is required to avoid loss of the account. '''THIS IS A PHISHING ATTEMPT'''; please delete the mail. Tell-tale indicators that this is a phishing email include the bogus to/from addresses, the generic (and poorly formatted) University of Maryland signature, as well as the hyperlinks which point to non-UMIACS systems. '''IF YOU HAVE RESPONDED TO THE MAIL''' by clicking the link and providing your credentials, please notify staff@umiacs.umd.edu immediately, and change your password at https://intranet.umiacs.umd.edu/password.

We recommend that you check out [[Phishing | this page]] on phishing for helpful tips in distinguishing between legitimate mail and phishing attempts in the future.

=== Condor Upgrade ===

Staff has upgraded the UMIACS [[Condor]] pool to HTCondor 8. For most users, this should be a smooth transition. However, if you have the Condor 7 paths in your environment (e.g. <tt>/opt/UMcondor</tt>), these should be removed. The Condor binaries now live in <tt>/usr/bin</tt>. Please contact [[HelpDesk | staff]] with any questions or concerns.

<endFeed />

==Technical Reference==

Welcome to UMIACS Wiki. This is the main place to find documentation and information about your account and the technical services that UMIACS offers. If this is your first time please start here [[GettingStarted| Getting Started]].

We provide many [[CoreServices|Core Services]] which include [[EMail]], [[Backups]] and [[VPN]].

We have lots of specific [[LabFacilities|Lab Facilities]] that you may be interested in.

Please check here if you are interested in [[OrderingEquipment|Ordering Equipment]].

If you would like to open a support ticket, please contact the UMIACS [[HelpDesk]].

__NOTOC__

LaTeX

2014-07-27T21:27:16Z

Jlent:

==Background==

From the main [http://www.latex-project.org Project Page]:

LaTeX is a high-quality typesetting system; it includes features designed for the production of technical and scientific documentation. LaTeX is the de facto standard for the communication and publication of scientific documents.

==LaTeX on Windows==

In Windows, it is highly recommended to use a full-featured suite such as [https://www.tug.org/texlive/ TeX Live] or [http://miktex.org/ MiKTeX]. Both of these suites include everything required for end-to-end LaTeX compilation and filetype conversation. Please contact the [[HelpDesk]] for assistance with installing or using these on a UMIACS-supported Windows machine.

==LaTeX on Linux/UNIX==

As with Windows, there are full-featured suites available to compile and convert filetypes. On our supported RHEL5 and RHEL6 systems, Kile is pre-installed and located at <tt>/usr/local/bin/kile</tt>. [https://www.tug.org/texlive/ TeX Live] is also available for Linux, with OSX support made available in [https://www.tug.org/mactex/ MacTeX]

Most of our supported Linux systems should already have the LaTeX command-line utilities, as well as TeX Live, installed. Here is a example of using these to receive output as a PDF:

* Create a working directory. Traverse into it, and create a file <tt>example.tex</tt> with the following contents:

<pre>
\documentclass[12pt]{article}
\usepackage{amsmath}
\title{\LaTeX}
\date{}
\begin{document}
\maketitle
\LaTeX{} is a document preparation system for the \TeX{}
typesetting program. It offers programmable desktop
publishing features and extensive facilities for
automating most aspects of typesetting and desktop
publishing, including numbering and cross-referencing,
tables and figures, page layout, bibliographies, and
much more. \LaTeX{} was originally written in 1984 by
Leslie Lamport and has become the dominant method for
using \TeX; few people write in plain \TeX{} anymore.
The current version is \LaTeXe.

% This is a comment, not shown in final output.
% The following shows typesetting power of LaTeX:
\begin{align}
E_0 &= mc^2 \\
E &= \frac{mc^2}{\sqrt{1-\frac{v^2}{c^2}}}
\end{align}
\end{document}
</pre>

* Compile the file using the <tt>latex</tt> command. Your output should be similar to the following:

<pre>
[jlent@opensub01 example]$ latex example.tex
This is pdfTeX, Version 3.1415926-2.3-1.40.12 (TeX Live 2011)
[...]
[1] (./example.aux) )
Output written on example.dvi (1 page, 1692 bytes).
Transcript written on example.log.
</pre>

* Assuming no errors, this should have created a file <tt>example.dvi</tt>. Depending your system, there are two ways to convert this file to PDF format:

* Option 1: Using <tt>dvips</tt> and then <tt>ps2pdf</tt>:
<pre>
[jlent@opensub01 example]$ dvips example.dvi
This is dvips(k) 5.991 Copyright 2011 Radical Eye Software (www.radicaleye.com)
' TeX output 2014.07.24:1013' -> example.ps
</opt/local/stow/texlive/2011/texmf/dvips/base/tex.pro>
</opt/local/stow/texlive/2011/texmf/dvips/base/texps.pro>.
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr6.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi8.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmsy10.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmex10.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi12.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr8.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr12.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr17.pfb>
[1]
[jlent@opensub01 example]$ ps2pdf example.ps
[jlent@opensub01 example]$
</pre>

* Option 2: Using <tt>dvipdf</tt>:
<pre>
[jlent@opensub01 example]$ dvipdf example.dvi
[jlent@opensub01 example]$
</pre>

* Assuming there are no errors, you should now have a file <tt>example.pdf</tt> in your working directory. If your output PDF does not look quite right, you may need to use different conversion tools. Your workflow may necessarily vary depending on the contents of your document and how they are formatted and rendered.

==Further Reading==

* [http://latex-project.org/guides LaTeX project documentation page]
* [http://mintaka.sdsu.edu/GF/bibliog/latex/LaTeXtoPDF.html More LaTex to PDF options]

LaTeX

2014-07-27T21:26:49Z

Jlent:

==Background==

From the main [http://www.latex-project.org Project Page]:

LaTeX is a high-quality typesetting system; it includes features designed for the production of technical and scientific documentation. LaTeX is the de facto standard for the communication and publication of scientific documents.

==LaTeX on Windows==

In Windows, it is highly recommended to use a full-featured suite such as [https://www.tug.org/texlive/ TeX Live] or [http://miktex.org/ MiKTeX]. Both of these suites include everything required for end-to-end LaTeX compilation and filetype conversation. Please contact the [[HelpDesk]] for assistance with installing or using these on a UMIACS-supported Windows machine.

==LaTeX on Linux/UNIX==

As with Windows, there are full-featured suites available to compile and convert filetypes. On our supported RHEL5 and RHEL6 systems, Kile is pre-installed and located at <tt>/usr/local/bin/kile</tt>. [https://www.tug.org/texlive/ TeX Live] is also available for Linux, with OSX support made available in [https://www.tug.org/mactex/ MacTeX]

Most of our supported Linux systems should already have the LaTeX command-line utilities, as well as TeX Live, installed. Here is a example of using these to receive output as a PDF:

* Create a working directory. Traverse into it, and create a file <tt>example.tex</tt> with the following contents:

<pre>
\documentclass[12pt]{article}
\usepackage{amsmath}
\title{\LaTeX}
\date{}
\begin{document}
\maketitle
\LaTeX{} is a document preparation system for the \TeX{}
typesetting program. It offers programmable desktop
publishing features and extensive facilities for
automating most aspects of typesetting and desktop
publishing, including numbering and cross-referencing,
tables and figures, page layout, bibliographies, and
much more. \LaTeX{} was originally written in 1984 by
Leslie Lamport and has become the dominant method for
using \TeX; few people write in plain \TeX{} anymore.
The current version is \LaTeXe.

% This is a comment, not shown in final output.
% The following shows typesetting power of LaTeX:
\begin{align}
E_0 &= mc^2 \\
E &= \frac{mc^2}{\sqrt{1-\frac{v^2}{c^2}}}
\end{align}
\end{document}
</pre>

* Compile the file using the <tt>latex</tt> command. Your output should be similar to the following:

<pre>
[jlent@opensub01 example]$ latex example.tex
This is pdfTeX, Version 3.1415926-2.3-1.40.12 (TeX Live 2011)
[...]
[1] (./example.aux) )
Output written on example.dvi (1 page, 1692 bytes).
Transcript written on example.log.
</pre>

* Assuming no errors, this should have created a file <tt>example.dvi</tt>. Depending your system, there are two ways to convert this file to PDF format:

* Option 1: Using <tt>dvips</tt> and then <tt>ps2pdf</tt>:
<pre>
[jlent@opensub01 example]$ dvips example.dvi
This is dvips(k) 5.991 Copyright 2011 Radical Eye Software (www.radicaleye.com)
' TeX output 2014.07.24:1013' -> example.ps
</opt/local/stow/texlive/2011/texmf/dvips/base/tex.pro>
</opt/local/stow/texlive/2011/texmf/dvips/base/texps.pro>.
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr6.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi8.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmsy10.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmex10.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi12.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr8.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr12.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr17.pfb>
[1]
[jlent@opensub01 example]$ ps2pdf example.ps
[jlent@opensub01 example]$
</pre>

* Option 2: Using <tt>dvipdf</tt>:
<pre>
[jlent@opensub01 example]$ dvipdf example.dvi
[jlent@opensub01 example]$
</pre>

* Assuming there are no errors, you should now have a file <tt>example.pdf</tt> in your working directory. If your output PDF does not look quite right, you may need to use different conversion tools. Your workflow may necessarily vary depending on the contents of your document and how they are rendered.

==Further Reading==

* [http://latex-project.org/guides LaTeX project documentation page]
* [http://mintaka.sdsu.edu/GF/bibliog/latex/LaTeXtoPDF.html More LaTex to PDF options]

LaTeX

2014-07-27T21:24:48Z

Jlent:

==Background==

From the main [http://www.latex-project.org Project Page]:

LaTeX is a high-quality typesetting system; it includes features designed for the production of technical and scientific documentation. LaTeX is the de facto standard for the communication and publication of scientific documents.

==LaTeX on Windows==

In Windows, it is highly recommended to use a full-featured suite such as [https://www.tug.org/texlive/ TeX Live] or [http://miktex.org/ MiKTeX]. Both of these suites include everything required for end-to-end LaTeX compilation and filetype conversation. Please contact the [[HelpDesk]] for assistance with installing or using these on a UMIACS-supported Windows machine.

==LaTeX on Linux/UNIX==

As with Windows, there are full-featured suites available to compile and convert filetypes. On our supported RHEL5 and RHEL6 systems, Kile is pre-installed and located at <tt>/usr/local/bin/kile</tt>. [https://www.tug.org/texlive/ TeX Live] is also available for Linux, with OSX support made available in [https://www.tug.org/mactex/ MacTeX]

Most of our supported Linux systems should already have the LaTeX command-line utilities, as well as TeX Live, installed. Here is a example of using these to receive output as a PDF:

* Create a working directory. Traverse into it, and create a file <tt>example.tex</tt> with the following contents:

<pre>
\documentclass[12pt]{article}
\usepackage{amsmath}
\title{\LaTeX}
\date{}
\begin{document}
\maketitle
\LaTeX{} is a document preparation system for the \TeX{}
typesetting program. It offers programmable desktop
publishing features and extensive facilities for
automating most aspects of typesetting and desktop
publishing, including numbering and cross-referencing,
tables and figures, page layout, bibliographies, and
much more. \LaTeX{} was originally written in 1984 by
Leslie Lamport and has become the dominant method for
using \TeX; few people write in plain \TeX{} anymore.
The current version is \LaTeXe.

% This is a comment, not shown in final output.
% The following shows typesetting power of LaTeX:
\begin{align}
E_0 &= mc^2 \\
E &= \frac{mc^2}{\sqrt{1-\frac{v^2}{c^2}}}
\end{align}
\end{document}
</pre>

* Compile the file using the <tt>latex</tt> command. Your output should be similar to the following:

<pre>
[jlent@opensub01 example]$ latex example.tex
This is pdfTeX, Version 3.1415926-2.3-1.40.12 (TeX Live 2011)
[...]
[1] (./example.aux) )
Output written on example.dvi (1 page, 1692 bytes).
Transcript written on example.log.
</pre>

* Assuming no errors, this should have created a file <tt>example.dvi</tt>. Depending your system, there are two ways to convert this file to PDF format:

* Option 1: Using <tt>dvips</tt> and then <tt>ps2pdf</tt>:
<pre>
[jlent@opensub01 example]$ dvips example.dvi
This is dvips(k) 5.991 Copyright 2011 Radical Eye Software (www.radicaleye.com)
' TeX output 2014.07.24:1013' -> example.ps
</opt/local/stow/texlive/2011/texmf/dvips/base/tex.pro>
</opt/local/stow/texlive/2011/texmf/dvips/base/texps.pro>.
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr6.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi8.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmsy10.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmex10.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi12.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr8.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr12.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr17.pfb>
[1]
[jlent@opensub01 example]$ ps2pdf example.ps
[jlent@opensub01 example]$
</pre>

* Option 2: Using <tt>dvipdf</tt>:
<pre>
[jlent@opensub01 example]$ dvipdf example.dvi
[jlent@opensub01 example]$
</pre>

* Assuming there are no errors, you should now have a file <tt>example.pdf</tt> in your working directory.

Note: Depending on the components of your document, your compilation workflow may be necessarily different and require different conversion tools.

==Further Reading==

* [http://latex-project.org/guides LaTeX project documentation page]
* [http://mintaka.sdsu.edu/GF/bibliog/latex/LaTeXtoPDF.html More LaTex to PDF options]

LaTeX

2014-07-24T16:40:43Z

Jlent:

==Background==

From the main [http://www.latex-project.org Project Page]:

LaTeX is a high-quality typesetting system; it includes features designed for the production of technical and scientific documentation. LaTeX is the de facto standard for the communication and publication of scientific documents.

==LaTeX on Windows==

In Windows, it is highly recommended to use a full-featured suite such as [https://www.tug.org/texlive/ TeX Live] or [http://miktex.org/ MiKTeX]. Both of these suites include everything required for end-to-end LaTeX compilation and filetype conversation. Please contact the [[HelpDesk]] for assistance with installing or using these on a UMIACS-supported Windows machine.

==LaTeX on Linux/UNIX==

As with Windows, there are full-featured suites available to compile and convert filetypes. On our supported RHEL5 and RHEL6 systems, Kile is pre-installed and located at <tt>/usr/local/bin/kile</tt>. [https://www.tug.org/texlive/ TeX Live] is also available for Linux, with OSX support made available in [https://www.tug.org/mactex/ MacTeX]

Most of our supported Linux systems should already have the LaTeX command-line utilities, as well as TeX Live, installed. Here is a example of using these to receive output as a PDF:

* Create a working directory. Traverse into it, and create a file <tt>example.tex</tt> with the following contents:

<pre>
\documentclass[12pt]{article}
\usepackage{amsmath}
\title{\LaTeX}
\date{}
\begin{document}
\maketitle
\LaTeX{} is a document preparation system for the \TeX{}
typesetting program. It offers programmable desktop
publishing features and extensive facilities for
automating most aspects of typesetting and desktop
publishing, including numbering and cross-referencing,
tables and figures, page layout, bibliographies, and
much more. \LaTeX{} was originally written in 1984 by
Leslie Lamport and has become the dominant method for
using \TeX; few people write in plain \TeX{} anymore.
The current version is \LaTeXe.

% This is a comment, not shown in final output.
% The following shows typesetting power of LaTeX:
\begin{align}
E_0 &= mc^2 \\
E &= \frac{mc^2}{\sqrt{1-\frac{v^2}{c^2}}}
\end{align}
\end{document}
</pre>

* Compile the file using the <tt>latex</tt> command. Your output should be similar to the following:

<pre>
[jlent@opensub01 example]$ latex example.tex
This is pdfTeX, Version 3.1415926-2.3-1.40.12 (TeX Live 2011)
[...]
[1] (./example.aux) )
Output written on example.dvi (1 page, 1692 bytes).
Transcript written on example.log.
</pre>

* Assuming no errors, this should have created a file <tt>example.dvi</tt>. Depending your system, there are two ways to convert this file to PDF format:

* Option 1: Using <tt>dvips</tt> and then <tt>ps2pdf</tt>:
<pre>
[jlent@opensub01 example]$ dvips example.dvi
This is dvips(k) 5.991 Copyright 2011 Radical Eye Software (www.radicaleye.com)
' TeX output 2014.07.24:1013' -> example.ps
</opt/local/stow/texlive/2011/texmf/dvips/base/tex.pro>
</opt/local/stow/texlive/2011/texmf/dvips/base/texps.pro>.
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr6.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi8.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmsy10.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmex10.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi12.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr8.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr12.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr17.pfb>
[1]
[jlent@opensub01 example]$ ps2pdf example.ps
[jlent@opensub01 example]$
</pre>

* Option 2: Using <tt>dvipdf</tt>:
<pre>
[jlent@opensub01 example]$ dvipdf example.dvi
[jlent@opensub01 example]$
</pre>

* Assuming there are no errors, you should now have a file <tt>example.pdf</tt> in your working directory. There are other options as well. Please see the second link below.

==Further Reading==

* [http://latex-project.org/guides LaTeX project documentation page]
* [http://mintaka.sdsu.edu/GF/bibliog/latex/LaTeXtoPDF.html More LaTex to PDF options]

LaTeX

2014-07-24T15:48:24Z

Jlent:

==Background==

From the main [http://www.latex-project.org Project Page]:

LaTeX is a high-quality typesetting system; it includes features designed for the production of technical and scientific documentation. LaTeX is the de facto standard for the communication and publication of scientific documents.

==LaTeX on Windows==

In Windows, it is highly recommended to use a full-featured suite such as [https://www.tug.org/texlive/ TeX Live] or [http://miktex.org/ MiKTeX]. Both of these suites include everything required for end-to-end LaTeX compilation and filetype conversation. Please contact the [[HelpDesk]] for assistance with installing or using these on a UMIACS-supported Windows machine.

==LaTeX on Linux/UNIX==

As with Windows, there are full-featured suites available to compile and convert filetypes. On our supported RHEL5 and RHEL6 systems, Kile is pre-installed and located at <tt>/usr/local/bin/kile</tt>. [https://www.tug.org/texlive/ TeX Live] is also available for Linux, with OSX support made available in [https://www.tug.org/mactex/ MacTeX]

Most of our supported Linux systems should already have the LaTeX command-line utilities, as well as TeX Live, installed. Here is a example of using these to receive output as a PDF:

* Create a working directory. Traverse into it, and create a file <tt>example.tex</tt> with the following contents:

<pre>
\documentclass[12pt]{article}
\usepackage{amsmath}
\title{\LaTeX}
\date{}
\begin{document}
\maketitle
\LaTeX{} is a document preparation system for the \TeX{}
typesetting program. It offers programmable desktop
publishing features and extensive facilities for
automating most aspects of typesetting and desktop
publishing, including numbering and cross-referencing,
tables and figures, page layout, bibliographies, and
much more. \LaTeX{} was originally written in 1984 by
Leslie Lamport and has become the dominant method for
using \TeX; few people write in plain \TeX{} anymore.
The current version is \LaTeXe.

% This is a comment, not shown in final output.
% The following shows typesetting power of LaTeX:
\begin{align}
E_0 &= mc^2 \\
E &= \frac{mc^2}{\sqrt{1-\frac{v^2}{c^2}}}
\end{align}
\end{document}
</pre>

* Compile the file using the <tt>latex</tt> command. Your output should be similar to the following:

<pre>
[jlent@opensub01 example]$ latex example.tex
This is pdfTeX, Version 3.1415926-2.3-1.40.12 (TeX Live 2011)
[...]
[1] (./example.aux) )
Output written on example.dvi (1 page, 1692 bytes).
Transcript written on example.log.
</pre>

* Assuming no errors, this should have created a file <tt>example.dvi</tt>. Depending your system, there are two ways to convert this file to PDF format:

* Using <tt>dvips</tt> and then <tt>ps2pdf</tt>:
<pre>
[jlent@opensub01 example]$ dvips example.dvi
This is dvips(k) 5.991 Copyright 2011 Radical Eye Software (www.radicaleye.com)
' TeX output 2014.07.24:1013' -> example.ps
</opt/local/stow/texlive/2011/texmf/dvips/base/tex.pro>
</opt/local/stow/texlive/2011/texmf/dvips/base/texps.pro>.
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr6.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi8.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmsy10.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmex10.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi12.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr8.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr12.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr17.pfb>
[1]
[jlent@opensub01 example]$ ps2pdf example.ps
[jlent@opensub01 example]$
</pre>

* Using <tt>dvipdf</tt>:
<pre>
[jlent@opensub01 example]$ dvipdf example.dvi
[jlent@opensub01 example]$
</pre>

* Assuming there are no errors, you should now have a file <tt>example.pdf</tt> in your working directory.

==Further Reading==

* [http://latex-project.org/guides LaTeX project documentation page]
* [http://mintaka.sdsu.edu/GF/bibliog/latex/LaTeXtoPDF.html More LaTex to PDF options]

LaTeX

2014-07-24T14:19:42Z

Jlent:

==Background==

From the main [http://www.latex-project.org Project Page]:

LaTeX is a high-quality typesetting system; it includes features designed for the production of technical and scientific documentation. LaTeX is the de facto standard for the communication and publication of scientific documents.

==LaTeX on Windows==

In Windows, it is highly recommended to use a full-featured suite such as [https://www.tug.org/texlive/ TeX Live] or [http://miktex.org/ MiKTeX]. Both of these suites include everything required for end-to-end LaTeX compilation and filetype conversation. Please contact the [[HelpDesk]] for assistance with installing or using these on a UMIACS-supported Windows machine.

==LaTeX on Linux/UNIX==

As with Windows, there are full-featured suites available to compile and convert filetypes. On our supported RHEL5 and RHEL6 systems, Kile is pre-installed and located at <tt>/usr/local/bin/kile</tt>. [https://www.tug.org/texlive/ TeX Live] is also available for Linux, with OSX support made available in [https://www.tug.org/mactex/ MacTeX]

Most of our supported Linux systems should already have the LaTeX command-line utilities, as well as TeX Live, installed. Here is a example of using these to receive output as a PDF:

* Create a working directory. Traverse into it, and create a file <tt>example.tex</tt> with the following contents:

<pre>
\documentclass[12pt]{article}
\usepackage{amsmath}
\title{\LaTeX}
\date{}
\begin{document}
\maketitle
\LaTeX{} is a document preparation system for the \TeX{}
typesetting program. It offers programmable desktop
publishing features and extensive facilities for
automating most aspects of typesetting and desktop
publishing, including numbering and cross-referencing,
tables and figures, page layout, bibliographies, and
much more. \LaTeX{} was originally written in 1984 by
Leslie Lamport and has become the dominant method for
using \TeX; few people write in plain \TeX{} anymore.
The current version is \LaTeXe.

% This is a comment, not shown in final output.
% The following shows typesetting power of LaTeX:
\begin{align}
E_0 &= mc^2 \\
E &= \frac{mc^2}{\sqrt{1-\frac{v^2}{c^2}}}
\end{align}
\end{document}
</pre>

* Compile the file using the <tt>latex</tt> command. Your output should be similar to the following:

<pre>
[jlent@opensub01 example]$ latex example.tex
This is pdfTeX, Version 3.1415926-2.3-1.40.12 (TeX Live 2011)
[...]
[1] (./example.aux) )
Output written on example.dvi (1 page, 1692 bytes).
Transcript written on example.log.
</pre>

* Assuming no errors, this should have created a file <tt>example.dvi</tt>. Depending your system, there are two ways to convert this file to PDF format:

* Using <tt>dvips</tt> and then <tt>ps2pdf</tt>:
<pre>
[jlent@opensub01 example]$ dvips example.dvi
This is dvips(k) 5.991 Copyright 2011 Radical Eye Software (www.radicaleye.com)
' TeX output 2014.07.24:1013' -> example.ps
</opt/local/stow/texlive/2011/texmf/dvips/base/tex.pro>
</opt/local/stow/texlive/2011/texmf/dvips/base/texps.pro>.
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr6.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi8.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmsy10.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmex10.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi12.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr8.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr12.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr17.pfb>
[1]
[jlent@opensub01 example]$ ps2pdf example.ps
[jlent@opensub01 example]$
</pre>

* Using <tt>dvipdf</tt>:
<pre>
[jlent@opensub01 example]$ dvipdf example.dvi
[jlent@opensub01 example]$
</pre>

* Assuming there are no errors, you should now have a file <tt>example.pdf</tt> in your working directory.

==Further Reading==

* [http://latex-project.org/guides LaTeX project documentation page]

LaTeX

2014-07-24T14:18:57Z

Jlent:

==Background==

From the main [http://www.latex-project.org Project Page]:

LaTeX is a high-quality typesetting system; it includes features designed for the production of technical and scientific documentation. LaTeX is the de facto standard for the communication and publication of scientific documents.

==LaTeX on Windows==

In Windows, it is highly recommended to use a full-featured suite such as [https://www.tug.org/texlive/ TeX Live] or [http://miktex.org/ MiKTeX]. Both of these suites include everything required for end-to-end LaTeX compilation and filetype conversation. Please contact the [[HelpDesk]] for assistance with installing or using these on a UMIACS-supported Windows machine.

==LaTeX on Linux/UNIX==

As with Windows, there are full-featured suites available to compile and convert filetypes. On our supported RHEL5 and RHEL6 systems, Kile is pre-installed and located at <tt>/usr/local/bin/kile</tt>. [https://www.tug.org/texlive/ TeX Live] is also available for Linux, with OSX support made available in [https://www.tug.org/mactex/ MacTeX]

That being said, most of our supported Linux systems should already have the LaTeX command-line utilities installed. Here is a example of using these to receive output as a PDF:

* Create a working directory. Traverse into it, and create a file <tt>example.tex</tt> with the following contents:

<pre>
\documentclass[12pt]{article}
\usepackage{amsmath}
\title{\LaTeX}
\date{}
\begin{document}
\maketitle
\LaTeX{} is a document preparation system for the \TeX{}
typesetting program. It offers programmable desktop
publishing features and extensive facilities for
automating most aspects of typesetting and desktop
publishing, including numbering and cross-referencing,
tables and figures, page layout, bibliographies, and
much more. \LaTeX{} was originally written in 1984 by
Leslie Lamport and has become the dominant method for
using \TeX; few people write in plain \TeX{} anymore.
The current version is \LaTeXe.

% This is a comment, not shown in final output.
% The following shows typesetting power of LaTeX:
\begin{align}
E_0 &= mc^2 \\
E &= \frac{mc^2}{\sqrt{1-\frac{v^2}{c^2}}}
\end{align}
\end{document}
</pre>

* Compile the file using the <tt>latex</tt> command. Your output should be similar to the following:

<pre>
[jlent@opensub01 example]$ latex example.tex
This is pdfTeX, Version 3.1415926-2.3-1.40.12 (TeX Live 2011)
[...]
[1] (./example.aux) )
Output written on example.dvi (1 page, 1692 bytes).
Transcript written on example.log.
</pre>

* Assuming no errors, this should have created a file <tt>example.dvi</tt>. Depending your system, there are two ways to convert this file to PDF format:

* Using <tt>dvips</tt> and then <tt>ps2pdf</tt>:
<pre>
[jlent@opensub01 example]$ dvips example.dvi
This is dvips(k) 5.991 Copyright 2011 Radical Eye Software (www.radicaleye.com)
' TeX output 2014.07.24:1013' -> example.ps
</opt/local/stow/texlive/2011/texmf/dvips/base/tex.pro>
</opt/local/stow/texlive/2011/texmf/dvips/base/texps.pro>.
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr6.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi8.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmsy10.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmex10.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi12.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr8.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr12.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr17.pfb>
[1]
[jlent@opensub01 example]$ ps2pdf example.ps
[jlent@opensub01 example]$
</pre>

* Using <tt>dvipdf</tt>:
<pre>
[jlent@opensub01 example]$ dvipdf example.dvi
[jlent@opensub01 example]$
</pre>

* Assuming there are no errors, you should now have a file <tt>example.pdf</tt> in your working directory.

==Further Reading==

* [http://latex-project.org/guides LaTeX project documentation page]

LaTeX

2014-07-24T14:18:00Z

Jlent:

==Background==

From the main [http://www.latex-project.org Project Page]:

LaTeX is a high-quality typesetting system; it includes features designed for the production of technical and scientific documentation. LaTeX is the de facto standard for the communication and publication of scientific documents.

==LaTeX on Windows==

In Windows, it is highly recommended to use a full-featured suite such as [https://www.tug.org/texlive/ TeX Live] or [http://miktex.org/ MiKTeX]. Both of these suites include everything required for end-to-end LaTeX compilation and filetype conversation. Please contact the [[HelpDesk]] for assistance with installing or using these on a UMIACS-supported Windows machine.

==LaTeX on Linux/UNIX==

As with Windows, there are full-featured suites available to compile and convert filetypes. On our supported RHEL5 and RHEL6 systems, Kile is pre-installed and located at <tt>/usr/local/bin/kile</tt>. [https://www.tug.org/texlive/ TeX Live] is also available for Linux, with OSX support made available in [https://www.tug.org/mactex/ MacTeX]

That being said, most of our supported Linux systems should already have the LaTeX command-line utilities installed. Here is a example of using these to receive output as a PDF:

* Create a working directory. Traverse into it, and create a file <tt>example.tex</tt> with the following contents:

<pre>
\documentclass[12pt]{article}
\usepackage{amsmath}
\title{\LaTeX}
\date{}
\begin{document}
\maketitle
\LaTeX{} is a document preparation system for the \TeX{}
typesetting program. It offers programmable desktop
publishing features and extensive facilities for
automating most aspects of typesetting and desktop
publishing, including numbering and cross-referencing,
tables and figures, page layout, bibliographies, and
much more. \LaTeX{} was originally written in 1984 by
Leslie Lamport and has become the dominant method for
using \TeX; few people write in plain \TeX{} anymore.
The current version is \LaTeXe.

% This is a comment, not shown in final output.
% The following shows typesetting power of LaTeX:
\begin{align}
E_0 &= mc^2 \\
E &= \frac{mc^2}{\sqrt{1-\frac{v^2}{c^2}}}
\end{align}
\end{document}
</pre>

* Compile the file using the <tt>latex</tt> command. Your output should be similar to the following:

<pre>
[jlent@opensub01 example]$ latex example.tex
This is pdfTeX, Version 3.1415926-2.3-1.40.12 (TeX Live 2011)
[...]
[1] (./example.aux) )
Output written on example.dvi (1 page, 1692 bytes).
Transcript written on example.log.
</pre>

* Assuming no errors, this should have created a file <tt>example.dvi</tt>. Depending your system, there are two ways to convert this file to PDF format:

** Using <tt>dvips</tt> and then <tt>ps2pdf</tt>:
<pre>
[jlent@opensub01 example]$ dvips example.dvi
This is dvips(k) 5.991 Copyright 2011 Radical Eye Software (www.radicaleye.com)
' TeX output 2014.07.24:1013' -> example.ps
</opt/local/stow/texlive/2011/texmf/dvips/base/tex.pro>
</opt/local/stow/texlive/2011/texmf/dvips/base/texps.pro>.
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr6.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi8.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmsy10.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmex10.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi12.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr8.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr12.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr17.pfb>
[1]
[jlent@opensub01 example]$ ps2pdf example.ps
[jlent@opensub01 example]$
</pre>

** Using <tt>dvipdf</tt>

==Further Reading==

* [http://latex-project.org/guides LaTeX project documentation page]

LaTeX

2014-07-24T14:17:23Z

Jlent:

==Background==

From the main [http://www.latex-project.org Project Page]:

LaTeX is a high-quality typesetting system; it includes features designed for the production of technical and scientific documentation. LaTeX is the de facto standard for the communication and publication of scientific documents.

==LaTeX on Windows==

In Windows, it is highly recommended to use a full-featured suite such as [https://www.tug.org/texlive/ TeX Live] or [http://miktex.org/ MiKTeX]. Both of these suites include everything required for end-to-end LaTeX compilation and filetype conversation. Please contact the [[HelpDesk]] for assistance with installing or using these on a UMIACS-supported Windows machine.

==LaTeX on Linux/UNIX==

As with Windows, there are full-featured suites available to compile and convert filetypes. On our supported RHEL5 and RHEL6 systems, Kile is pre-installed and located at <tt>/usr/local/bin/kile</tt>. [https://www.tug.org/texlive/ TeX Live] is also available for Linux, with OSX support made available in [https://www.tug.org/mactex/ MacTeX]

That being said, most of our supported Linux systems should already have the LaTeX command-line utilities installed. Here is a example of using these to receive output as a PDF:

* Create a working directory. Traverse into it, and create a file <tt>example.tex</tt> with the following contents:

<pre>
\documentclass[12pt]{article}
\usepackage{amsmath}
\title{\LaTeX}
\date{}
\begin{document}
\maketitle
\LaTeX{} is a document preparation system for the \TeX{}
typesetting program. It offers programmable desktop
publishing features and extensive facilities for
automating most aspects of typesetting and desktop
publishing, including numbering and cross-referencing,
tables and figures, page layout, bibliographies, and
much more. \LaTeX{} was originally written in 1984 by
Leslie Lamport and has become the dominant method for
using \TeX; few people write in plain \TeX{} anymore.
The current version is \LaTeXe.

% This is a comment, not shown in final output.
% The following shows typesetting power of LaTeX:
\begin{align}
E_0 &= mc^2 \\
E &= \frac{mc^2}{\sqrt{1-\frac{v^2}{c^2}}}
\end{align}
\end{document}
</pre>

* Compile the file using the <tt>latex</tt> command. Your output should be similar to the following:

<pre>
[jlent@opensub01 example]$ latex example.tex
This is pdfTeX, Version 3.1415926-2.3-1.40.12 (TeX Live 2011)
[...]
[1] (./example.aux) )
Output written on example.dvi (1 page, 1692 bytes).
Transcript written on example.log.
</pre>

* Assuming no errors, this should have created a file <tt>example.dvi</tt>. Depending your system, there are two ways to convert this file to PDF format:

** Using <tt>dvips</tt> and then <tt>ps2pdf</tt>:
*** <pre>
[jlent@opensub01 example]$ dvips example.dvi
This is dvips(k) 5.991 Copyright 2011 Radical Eye Software (www.radicaleye.com)
' TeX output 2014.07.24:1013' -> example.ps
</opt/local/stow/texlive/2011/texmf/dvips/base/tex.pro>
</opt/local/stow/texlive/2011/texmf/dvips/base/texps.pro>.
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr6.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi8.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmsy10.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmex10.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmmi12.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr8.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr12.pfb>
</opt/local/stow/texlive/2011/texmf-dist/fonts/type1/public/amsfonts/cm/cmr17.pfb>
[1]
[jlent@opensub01 example]$ ps2
ps2ascii ps2eps ps2epsi ps2frag ps2pdf ps2pdf12 ps2pdf13 ps2pdf14 ps2pdfwr ps2pk ps2ps ps2ps2
[jlent@opensub01 example]$ ps2p
ps2pdf ps2pdf12 ps2pdf13 ps2pdf14 ps2pdfwr ps2pk ps2ps ps2ps2
[jlent@opensub01 example]$ ps2pd
ps2pdf ps2pdf12 ps2pdf13 ps2pdf14 ps2pdfwr
[jlent@opensub01 example]$ ps2pdf ex
example.aux example.dvi example.log example.pdf example.ps example.tex
[jlent@opensub01 example]$ ps2pdf example.ps
[jlent@opensub01 example]$
</pre>
** Using <tt>dvipdf</tt>

==Further Reading==

* [http://latex-project.org/guides LaTeX project documentation page]

LaTeX

2014-07-24T14:16:26Z

Jlent:

LaTeX

2014-07-24T14:15:25Z

Jlent:

LaTeX

2014-07-24T14:12:41Z

Jlent:

LaTeX

2014-07-24T14:09:16Z

Jlent:

LaTeX

2014-07-24T14:05:42Z

Jlent:

LaTeX

2014-07-24T13:39:07Z

Jlent:

LaTeX

2014-07-24T13:36:17Z

Jlent:

LaTeX

2014-07-24T13:36:09Z

Jlent:

==Background==

From the main [[http://www.latex-project.org Project Page]]:

LaTeX is a high-quality typesetting system; it includes features designed for the production of technical and scientific documentation. LaTeX is the de facto standard for the communication and publication of scientific documents.

==LaTeX on Windows==

==LaTeX on Linux/UNIX==

LaTeX

2014-07-24T13:35:15Z

Jlent: Created page with "==Background== From the main Project Page: LaTeX is a high-quality typesetting system; it includes features designed for the production of technical and scientific docum..."

==Background==

From the main [[Project Page]]:

LaTeX is a high-quality typesetting system; it includes features designed for the production of technical and scientific documentation. LaTeX is the de facto standard for the communication and publication of scientific documents.

==LaTeX on Windows==

==LaTeX on Linux/UNIX==

MonthlyMaintenanceWindow

2014-07-18T14:58:00Z

Jlent:

UMIACS takes a monthly maintenance window to patch and reboot our hosts. This provides a way to ensure security updates are installed and activated on the numerous different platforms and appliances that we maintain.

The window is calculated each month by adding 9 days to [http://en.wikipedia.org/wiki/Patch_Tuesday Microsoft's Patch Tuesday]. This allows us to marshal patches released that month from Microsoft, Red Hat, and our other vendors and have enough time to get our systems prepared to reboot for that month's window.

The window is always going to be on a '''Thursday''' from '''8pm-12am'''. A list of maintenance windows for 2014 is as follows with the upcoming window in bold.

* '''August 21st 2014'''
* September 18th 2014
* October 23rd 2014
* November 20th 2014
* December 18th 2014

==Archives==
* January 17th 2013
* February 21st 2013
* March 21st 2013
* April 18th 2013
* May 23rd 2013
* June 20th 2013
* July 18th 2013
* August 22nd 2013
* September 19th 2013
* October 17th 2013
* December 19th 2013
* January 23rd 2014
* February 20th 2014
* March 20th 2014
* April 17th 2014
* May 22nd 2014
* June 19th 2014
* July 17th 2014

MonthlyMaintenanceWindow

2014-07-12T16:36:54Z

Jlent: /* Archives */

UMIACS takes a monthly maintenance window to patch and reboot our hosts. This provides a way to ensure security updates are installed and activated on the numerous different platforms and appliances that we maintain.

The window is calculated each month by adding 9 days to [http://en.wikipedia.org/wiki/Patch_Tuesday Microsoft's Patch Tuesday]. This allows us to marshal patches released that month from Microsoft, Red Hat, and our other vendors and have enough time to get our systems prepared to reboot for that month's window.

The window is always going to be on a '''Thursday''' from '''8pm-12am'''. A list of maintenance windows for 2014 is as follows with the upcoming window in bold.

* '''July 17th 2014'''
* August 21st 2014
* September 18th 2014
* October 23rd 2014
* November 20th 2014
* December 18th 2014

==Archives==
* January 17th 2013
* February 21st 2013
* March 21st 2013
* April 18th 2013
* May 23rd 2013
* June 20th 2013
* July 18th 2013
* August 22nd 2013
* September 19th 2013
* October 17th 2013
* December 19th 2013
* January 23rd 2014
* February 20th 2014
* March 20th 2014
* April 17th 2014
* May 22nd 2014
* June 19th 2014

MonthlyMaintenanceWindow

2014-07-12T16:36:41Z

Jlent:

UMIACS takes a monthly maintenance window to patch and reboot our hosts. This provides a way to ensure security updates are installed and activated on the numerous different platforms and appliances that we maintain.

The window is calculated each month by adding 9 days to [http://en.wikipedia.org/wiki/Patch_Tuesday Microsoft's Patch Tuesday]. This allows us to marshal patches released that month from Microsoft, Red Hat, and our other vendors and have enough time to get our systems prepared to reboot for that month's window.

The window is always going to be on a '''Thursday''' from '''8pm-12am'''. A list of maintenance windows for 2014 is as follows with the upcoming window in bold.

* '''July 17th 2014'''
* August 21st 2014
* September 18th 2014
* October 23rd 2014
* November 20th 2014
* December 18th 2014

==Archives==
* January 17th 2013
* February 21st 2013
* March 21st 2013
* April 18th 2013
* May 23rd 2013
* June 20th 2013
* July 18th 2013
* August 22nd 2013
* September 19th 2013
* October 17th 2013
* December 19th 2013
* January 23rd 2014
* February 20th 2014
* March 20th 2014
* April 17th 2014
* May 22nd 2014
*'June 19th 2014

Java

2014-06-27T14:24:52Z

Jlent:

Java can be obtained in one of two flavors: Java Runtime Environment (JRE) or Java Development Kit (JDK). Unless you do programming in Java, JRE is usually sufficient for running programs and applets written in Java. JRE is also included in JDK so there is no need to install both. There are two main flavors of Java that we have support for [http://www.oracle.com/us/technologies/java/overview/index.html Oracle Java] and [http://openjdk.java.net/ OpenJDK]. For the Java6 spec OpenJDK was not the same codebase and had some issues with some code that would run in the normal Oracle Java6 JVM. The Java7 versions of OpenJDK is much closer if not the same codebase for Oracle Java and OpenJDK.

'''Note''': Support for Sun JDK 1.6.0 has ended and we will be purged from UMIACS supported systems in March 2013 due to many security vulnerabilities. This does not impact the OpenJDK 1.6.0 versions as they are still maintained at this point.

=RHEL=
The default Java on these systems currently is Oracle Java 1.7.0. We additionally have support for OpenJDK 1.6.0. The alternative JDK and JRE options can be found in <tt>/usr/lib/jvm</tt>.

=Ubuntu=
The default Java on Ubuntu systems is OpenJDK 1.6.0 and 1.7.0 is available in the default repositories.

=Windows=
For PCs, you may send a request to [mailto:staff@umiacs.umd.edu staff] to have JRE or JDK installed on your machine.

NAGWareCompiler

2014-06-22T15:47:46Z

Jlent: /* Example use of the compiler */

__NOTOC__

The NAGWare Fortran compiler is available under <tt>/opt/common/NAGWare_f95</tt>* on our supported RHEL6/RHEL7/Ubuntu hosts, and <tt>/opt/NAGWare_f95</tt>* on our supported RHEL5 hosts. You can either load the binaries into your environment using [[Modules | GNU Modules]], reference the paths directly, else add them to your [[PATH | PATH]].

==Example use of the compiler==

Here is a very basic compilation and execution example of [http://en.wikipedia.org/wiki/Hello_world_program Hello World] using the NAGWare fortran compiler. This example will utilize a GNU Module available on all supported Linux hosts to quickly load the binaries and libraries into your environment.

First, in a working directory, create a file <tt>hello.f95</tt> with the following contents:

PRINT *, "Hello World!"
END

Then, load the NAGWare modules into your environment and verify that the compiler is in your path (libraries, MANpages, and license server information will be loaded as well):

[jlent@opensub00 jlent]$ module load nagware
[jlent@opensub00 jlent]$ which f95
/opt/common/NAGWare_f95-5.1/bin/f95

Compile and then run the program:

[jlent@opensub00 jlent]$ f95 -o hello hello.f95
[jlent@opensub00 jlent]$ ./hello
Hello World!

==See Also==
* [http://www.nag.com/nagware/np/doc_index.asp NAG Compiler Documentation Index]
* [http://www.nag.com/nagware/np.asp NAG Compiler Product Page]

NAGWareCompiler

2014-06-22T15:47:31Z

Jlent: /* Example use of the compiler */

__NOTOC__

The NAGWare Fortran compiler is available under <tt>/opt/common/NAGWare_f95</tt>* on our supported RHEL6/RHEL7/Ubuntu hosts, and <tt>/opt/NAGWare_f95</tt>* on our supported RHEL5 hosts. You can either load the binaries into your environment using [[Modules | GNU Modules]], reference the paths directly, else add them to your [[PATH | PATH]].

==Example use of the compiler==

Here is a very basic compilation and execution example of [http://en.wikipedia.org/wiki/Hello_world_program Hello World] using the NAGWare fortran compiler. This example will GNU Module available on all supported Linux hosts to quickly load the binaries and libraries into your environment.

First, in a working directory, create a file <tt>hello.f95</tt> with the following contents:

PRINT *, "Hello World!"
END

Then, load the NAGWare modules into your environment and verify that the compiler is in your path (libraries, MANpages, and license server information will be loaded as well):

[jlent@opensub00 jlent]$ module load nagware
[jlent@opensub00 jlent]$ which f95
/opt/common/NAGWare_f95-5.1/bin/f95

Compile and then run the program:

[jlent@opensub00 jlent]$ f95 -o hello hello.f95
[jlent@opensub00 jlent]$ ./hello
Hello World!

==See Also==
* [http://www.nag.com/nagware/np/doc_index.asp NAG Compiler Documentation Index]
* [http://www.nag.com/nagware/np.asp NAG Compiler Product Page]

NAGWareCompiler

2014-06-21T17:13:42Z

Jlent:

__NOTOC__

The NAGWare Fortran compiler is available under <tt>/opt/common/NAGWare_f95</tt>* on our supported RHEL6/RHEL7/Ubuntu hosts, and <tt>/opt/NAGWare_f95</tt>* on our supported RHEL5 hosts. You can either load the binaries into your environment using [[Modules | GNU Modules]], reference the paths directly, else add them to your [[PATH | PATH]].

==Example use of the compiler==

Here is a very basic compilation and execution example of [http://en.wikipedia.org/wiki/Hello_world_program Hello World] using the NAGWare fortran compiler. This example will use the GNU Module we setup to quickly load the binaries into your environment.

First, in a working directory, create a file <tt>hello.f95</tt> with the following contents:

PRINT *, "Hello World!"
END

Then, load the NAGWare modules into your environment and verify that the compiler is in your path (libraries, MANpages, and license server information will be loaded as well):

[jlent@opensub00 jlent]$ module load nagware
[jlent@opensub00 jlent]$ which f95
/opt/common/NAGWare_f95-5.1/bin/f95

Compile and then run the program:

[jlent@opensub00 jlent]$ f95 -o hello hello.f95
[jlent@opensub00 jlent]$ ./hello
Hello World!

==See Also==
* [http://www.nag.com/nagware/np/doc_index.asp NAG Compiler Documentation Index]
* [http://www.nag.com/nagware/np.asp NAG Compiler Product Page]

NAGWareCompiler

2014-06-20T14:46:38Z

Jlent:

__NOTOC__

The NAGWare Fortran compiler is available under <tt>/opt/common/NAGWare_f95</tt>* on our supported RHEL6/RHEL7/Ubuntu hosts, and <tt>/opt/NAGWare_f95</tt>* on our supported RHEL5 hosts. You can either load the binaries into your environment with the [[Modules | GNU Modules]] we created, reference the paths directly, else add them to your [[PATH | PATH]].

==Example use of the compiler==

Here is a very basic compilation and execution example of [http://en.wikipedia.org/wiki/Hello_world_program Hello World] using the NAGWare fortran compiler. This example will use the GNU Module we setup to quickly load the binaries into your environment.

First, in a working directory, create a file <tt>hello.f95</tt> with the following contents:

PRINT *, "Hello World!"
END

Then, load the NAGWare modules into your environment and verify that the compiler is in your path (libraries, MANpages, and license server information will be loaded as well):

[jlent@opensub00 jlent]$ module load nagware
[jlent@opensub00 jlent]$ which f95
/opt/common/NAGWare_f95-5.1/bin/f95

Compile and then run the program:

[jlent@opensub00 jlent]$ f95 -o hello hello.f95
[jlent@opensub00 jlent]$ ./hello
Hello World!

==See Also==
* [http://www.nag.com/nagware/np/doc_index.asp NAG Compiler Documentation Index]
* [http://www.nag.com/nagware/np.asp NAG Compiler Product Page]

NAGWareCompiler

2014-06-20T14:46:14Z

Jlent:

__NOTOC__

The NAGWare Fortran compiler is available under <tt>/opt/common/NAGWare_f95</tt>* on our supported RHEL6/RHEL7/Ubuntu hosts, and <tt>/opt/NAGWare_f95</tt>* on our supported RHEL5 hosts. You can either load the binaries into your environment with the [[Modules | GNU Modules]] we created, reference the paths directly, else add them to your [[PATH | PATH]].

==Example use of the compiler==

Here is a very basic compilation and execution example of Hello World using the NAGWare fortran compiler. This example will use the GNU Module we setup to quickly load the binaries into your environment.

First, in a working directory, create a file <tt>hello.f95</tt> with the following contents:

PRINT *, "Hello World!"
END

Then, load the NAGWare modules into your environment and verify that the compiler is in your path (libraries, MANpages, and license server information will be loaded as well):

[jlent@opensub00 jlent]$ module load nagware
[jlent@opensub00 jlent]$ which f95
/opt/common/NAGWare_f95-5.1/bin/f95

Compile and then run the program:

[jlent@opensub00 jlent]$ f95 -o hello hello.f95
[jlent@opensub00 jlent]$ ./hello
Hello World!

==See Also==
* [http://www.nag.com/nagware/np/doc_index.asp NAG Compiler Documentation Index]
* [http://www.nag.com/nagware/np.asp NAG Compiler Product Page]

NAGWareCompiler

2014-06-20T14:43:38Z

Jlent:

__NOTOC__

The NAGWare Fortran compiler is available under <tt>/opt/common/NAGWare_f95</tt>* on our supported RHEL6/RHEL7/Ubuntu hosts, and <tt>/opt/NAGWare_f95</tt>* on our supported RHEL5 hosts. You can either load the binaries into your environment with the [[Modules | GNU Modules]] we created, reference the paths directly, else add them to your [[PATH | PATH]].

==Example use of the compiler==

Here is a very basic example compilation and execution of Hello World using the NAGWare fortran compiler. This example will use the GNU Module we setup to quickly load the binaries into your environment.

First, in a working directory, create a file <tt>hello.f95</tt> with the following contents:

PRINT *, "Hello World!"
END

Then, load the NAGWare modules into your environment and verify that the compiler is in your path (libraries, MANpages, and license server information will be loaded as well):

[jlent@opensub00 jlent]$ module load nagware
[jlent@opensub00 jlent]$ which f95
/opt/common/NAGWare_f95-5.1/bin/f95

Compile and then run the program:

[jlent@opensub00 jlent]$ f95 -o hello hello.f95
[jlent@opensub00 jlent]$ ./hello
Hello World!

==See Also==
* [http://www.nag.com/nagware/np/doc_index.asp NAG Compiler Documentation Index]
* [http://www.nag.com/nagware/np.asp NAG Compiler Product Page]

NAGWareCompiler

2014-06-20T14:41:45Z

Jlent:

__NOTOC__

The NAGWare Fortran compiler is available under <tt>/opt/common/NAGWare_f95</tt>* on our supported RHEL6/RHEL7/Ubuntu hosts, and <tt>/opt/NAGWare_f95</tt>* on our supported RHEL5 hosts. You can either load the binaries into your environment with the [[Modules | GNU Modules]] we created, reference the paths directly, else add them to your [[PATH | PATH]].

==Example use of the compiler==

Here is a very basic example compilation and execution of Hello World using the NAGWare fortran compiler. This example will use the GNU Module we setup to quickly load the binaries into your environment.

First, in a working directory, create a file <tt>hello.f95</tt> with the following contents:

PRINT *, "Hello World!"
END

Then, load the NAGWare modules into your environment and verify that the compiler is in your path (libraries, MANpages, and license server information will be loaded as well):

[jlent@opensub00 jlent]$ module load nagware
[jlent@opensub00 jlent]$ which f95
/opt/common/NAGWare_f95-5.1/bin/f95

Compile and then run the program:

[jlent@opensub00 jlent]$ f95 -o hello hello.f95
[jlent@opensub00 jlent]$ ./hello
Hello World!

NAGWareCompiler

2014-06-20T14:40:43Z

Jlent:

__NOTOC__

The NAGWare Fortran compiler is available under <tt>/opt/common/NAGWare_f95</tt>* on our supported RHEL6/RHEL7/Ubuntu hosts, and <tt>/opt/NAGWare_f95</tt>* on our supported RHEL5 hosts. You can either load the binaries into your environment with the [[Modules | GNU Modules]] we created, reference the paths directly, else add them to your [[PATH | PATH]].

==Example use of the compiler==

Here is a very basic example compilation and execution of Hello World using the NAGWare fortran compiler. This example will use the GNU Module we setup to quickly load the binaries into your environment.

First, in a working directory, create a file <tt>hello.f95</tt> with the following contents:

PRINT *, "Hello World!"
END

Then, load the NAGWare modules into your environment and verify that the binaries are in your path:

[jlent@opensub00 jlent]$ module load nagware
[jlent@opensub00 jlent]$ which f95
/opt/common/NAGWare_f95-5.1/bin/f95

Compile and then run the program:

[jlent@opensub00 jlent]$ f95 -o hello hello.f95
[jlent@opensub00 jlent]$ ./hello
Hello World!

NAGWareCompiler

2014-06-20T14:40:14Z

Jlent:

__NOTOC__

The NAGWare Fortran compiler is available under <tt>/opt/common/NAGWare_f95</tt>* on our supported RHEL6/RHEL7/Ubuntu hosts, and <tt>/opt/NAGWare_f95</tt>* on our supported RHEL5 hosts. You can either load the binaries into your environment with the [[Modules | GNU Modules]] we created, reference the paths directly, else add them to your [[PATH | PATH]].

==Example use of the compiler==

Here is a basic compilation an execution of Hello World using the NAGWare fortran compiler. This example will use the GNU Module we setup to quickly load the binaries into your environment.

First, in a working directory, create a file <tt>hello.f95</tt> with the following contents:

PRINT *, "Hello World!"
END

Then, load the NAGWare modules into your environment and verify that the binaries are in your path:

[jlent@opensub00 jlent]$ module load nagware
[jlent@opensub00 jlent]$ which f95
/opt/common/NAGWare_f95-5.1/bin/f95

Compile and then run the program:

[jlent@opensub00 jlent]$ f95 -o hello hello.f95
[jlent@opensub00 jlent]$ ./hello
Hello World!

NAGWareCompiler

2014-06-20T14:39:57Z

Jlent:

__NOTOC__

The NAGWare Fortran compiler is available under <tt>/opt/common/NAGWare_f95</tt>* on our supported RHEL6/RHEL7/Ubuntu hosts, and <tt>/opt/NAGWare_f95</tt>* on our supported RHEL5 hosts. You can either load the binaries into your environment with the [[Modules | GNU Modules]] we created, reference the paths directly, else add them to your [[PATH | PATH]].

==Example use of the compiler==

Here is a basic compilation an execution of Hello World using the NAGWare fortran compiler. This example will use the GNU Module we setup to quickly load the binaries into your environment.

First, in a working directory, create a file <tt>hello.f95</tt> with the following contents:

PRINT *, "Hello World!"
END

Then, load the NAGWare modules into your environment and verify that the binaries are in your path:

[jlent@opensub00 jlent]$ module load nagware
[jlent@opensub00 jlent]$ which f95
/opt/common/NAGWare_f95-5.1/bin/f95

Compile and then run your <tt>hello.f95</tt> source:

[jlent@opensub00 jlent]$ f95 -o hello hello.f95
[jlent@opensub00 jlent]$ ./hello
Hello World!

NAGWareCompiler

2014-06-20T14:31:16Z

Jlent:

NAGWareCompiler

2014-06-20T14:30:56Z

Jlent:

NAGWareCompiler

2014-06-20T14:26:30Z

Jlent:

NAGWareCompiler

2014-06-20T14:26:06Z

Jlent:

NAGWareCompiler

2014-06-20T14:24:55Z

Jlent:

NAGWareCompiler

2014-06-20T14:24:36Z

Jlent:

NAGWareCompiler

2014-06-20T14:24:23Z

Jlent: /* Example use of the compiler */

__NOTOC__

The NAGWare Fortran compiler is available under <tt>/opt/common/NAGWare_f95</tt>* on our supported RHEL6/RHEL7/Ubuntu hosts, and <tt>/opt/NAGWare_f95</tt>* on our supported RHEL5 hosts.

==Example use of the compiler==

Here is a basic compilation an execution of Hello World using the NAGWare fortran compiler. This example will use the GNU Module we setup to quickly load the binaries into your environment.

First, create a file <tt>hello.f95</tt> with the following contents:

PRINT *, "Hello World!"
END

NAGWareCompiler

2014-06-20T14:21:28Z

Jlent:

__NOTOC__

The NAGWare Fortran compiler is available under <tt>/opt/common/NAGWare_f95</tt>* on our supported RHEL6/RHEL7/Ubuntu hosts, and <tt>/opt/NAGWare_f95</tt>* on our supported RHEL5 hosts.

==Example use of the compiler==

Here is a basic compilation an execution of Hello World using the NAGWare fortran compiler. This example will use the GNU Module we setup to quickly load the binaries into your environment.

First, create a file <tt>hello.f90</tt> with the following contents:

PRINT *, "Hello World!"
END

NAGWareCompiler

2014-06-20T14:19:28Z

Jlent:

__NOTOC__

The NAGWare Fortran compiler is available under <tt>/opt/common/NAGWare_f95</tt>* on our supported RHEL6/RHEL7/Ubuntu hosts, and <tt>/opt/NAGWare_f95</tt>* on our supported RHEL5 hosts.

==LM_LICENSE_FILE [[EnvironmentalVariables | Environmental Variable]]==
Please make sure to set the LM_LICENSE_FILE environment variable to ''/etc/license.pgi''.

In <tt>tcsh</tt>, you can do this as follows:
setenv LM_LICENSE_FILE $LM_LICENSE_FILE:/etc/license.dat:/etc/license.pgi
In <tt>bash</tt>:
export LM_LICENSE_FILE="$LM_LICENSE_FILE:/etc/license.dat:/etc/license.pgi"

NAGWareCompiler

2014-06-20T14:18:10Z

Jlent: Created page with "__NOTOC__ The Portland Group C and Fortran compilers are available under <tt>/opt/common/pgi</tt>* on our supported RHEL6/RHEL7/Ubuntu hosts, and <tt>/opt/pgi</tt>* on our su..."

__NOTOC__

The Portland Group C and Fortran compilers are available under <tt>/opt/common/pgi</tt>* on our supported RHEL6/RHEL7/Ubuntu hosts, and <tt>/opt/pgi</tt>* on our supported RHEL5 hosts.

==LM_LICENSE_FILE [[EnvironmentalVariables | Environmental Variable]]==
Please make sure to set the LM_LICENSE_FILE environment variable to ''/etc/license.pgi''.

In <tt>tcsh</tt>, you can do this as follows:
setenv LM_LICENSE_FILE $LM_LICENSE_FILE:/etc/license.dat:/etc/license.pgi
In <tt>bash</tt>:
export LM_LICENSE_FILE="$LM_LICENSE_FILE:/etc/license.dat:/etc/license.pgi"

CCompilers

2014-06-19T18:30:47Z

Jlent:

We currently have the following C/C++ compilers on the following platforms:

===RHEL4===

* gcc 3.4.6 - /usr/bin/gcc
* gcc 3.3.6 - /usr/local/stow/gcc-3.3.6
* gcc 4.0.3 - /usr/local/stow/gcc-4.0.3

===RHEL5===

* gcc 4.1.2 - /usr/bin/gcc
* gcc 3.4.6 - /usr/bin/gcc34
* gcc 3.3.6 - /usr/local/stow/gcc-3.3.6
* gcc 4.0.4 - /usr/local/stow/gcc-4.0.4
* gcc 4.2.4 - /usr/local/stow/gcc-4.2.4
* gcc 4.5.1 - /usr/local/stow/gcc-4.5.1
* [[IntelCompilers|Intel Compilers]]
* [[PGICompilers|Portland Group Compilers]]

===RHEL6===

* gcc 4.4.4 - /usr/bin/gcc
* [[IntelCompilers|Intel Compilers]]
* [[PGICompilers|Portland Group Compilers]]

===Ubuntu 12.04===
* gcc 4.6.3 - /usr/bin/gcc
* [[IntelCompilers|Intel Compilers]]
* [[PGICompilers|Portland Group Compilers]]

Also see: [[CDebuggers]]

CCompilers

2014-06-19T18:30:35Z

Jlent:

We currently have the following C/C++ compilers on the following platforms:

===RHEL4===

* gcc 3.4.6 - /usr/bin/gcc
* gcc 3.3.6 - /usr/local/stow/gcc-3.3.6
* gcc 4.0.3 - /usr/local/stow/gcc-4.0.3

===RHEL5===

* gcc 4.1.2 - /usr/bin/gcc
* gcc 3.4.6 - /usr/bin/gcc34
* gcc 3.3.6 - /usr/local/stow/gcc-3.3.6
* gcc 4.0.4 - /usr/local/stow/gcc-4.0.4
* gcc 4.2.4 - /usr/local/stow/gcc-4.2.4
* gcc 4.5.1 - /usr/local/stow/gcc-4.5.1
* [[IntelCompilers|Intel Compilers]]
* [[PGICompiler|Portland Group Compilers]]

===RHEL6===

* gcc 4.4.4 - /usr/bin/gcc
* [[IntelCompilers|Intel Compilers]]
* [[PGICompilers|Portland Group Compilers]]

===Ubuntu 12.04===
* gcc 4.6.3 - /usr/bin/gcc
* [[IntelCompilers|Intel Compilers]]
* [[PGICompilers|Portland Group Compilers]]

Also see: [[CDebuggers]]

UMIACS Account

2014-06-19T18:25:02Z

Jlent:

== Types of Accounts ==
A UMIACS Account is a collection of distinct account credentials, associated with a unique user, that provide access to various UMIACS systems and related resources.

When a UMIACS Account is first created, three sets of credentials (Windows, UNIX, and Jira) are configured based on the username and password requested via the [https://intranet.umiacs.umd.edu/requests/accounts/new/ UMIACS Account Request] (new users: see [[GettingStarted]].) With the exception of Jira, which requires a full email address, the username is identical for all credentials tied to a UMIACS account.

==== [[OSSupport | Windows]] ====
:Your Windows (aka "PC") account authenticates against our [[ActiveDirectory]] domain and is set when you first create your UMIACS account.
:It controls access for the following resources:
::*Windows computers
::*[[exchange]] e-mail
::*[[VPN]] Authentication

==== [[OSSupport | UNIX]] ====
:Your UNIX (aka "[[Kerberos]]") account authenticates against our Kerberos realm and is set when you first create your UMIACS account.
:It controls access for the following resources:
::*UNIX/Linux computers
::*[[UNIXEmail|IMAP]] e-mail
::*[[ApplicationResource|AR]]-controlled resources (wikis, [[SourceCodeManagement|repositories]], webapps)

==== [[Jira]] ====
:Your Jira username is your full email address. By default, the [[Jira]] account associated with your @umiacs email address authenticates against the kerberos realm. However it is possible to set a separate password for this account. If you change your password through the Jira web interface it will create a '''new''', '''separate''' password, and no longer authenticate against the kerberos realm. Changing your Jira password DOES NOT change any other UMIACS passwords.

:Please note that Jira creates a new account for each new email address it sees (including non-UMIACS addresses like @gmail or @umd.edu addresses.) This occasionally causes some confusion for new users. Please see the [[Jira]] page for further details.

== Changing your password ==
==== Approved Methods ====
There are currently two ways to change your UMIACS passwords:
*Via the web interface tool on the UMIACS Intranet at:
:https://intranet.umiacs.umd.edu/password
*Stop by the [[HelpDesk|UMIACS Helpdesk]], in room 3142 AVW
::If you plan on stopping by the UMIACS Helpdesk, please make sure to bring photo ID
==== Password Requirements ====
#Must be atleast 8 characters in length
#Must have alteast 3 of the following character classes: lower-case letters, upper-case letters, numbers, punctuation, special characters
#Cannot be the same as any of your previous 5 passwords
#Cannot contain a string that is part of your username
==== Off-site or out-of-state users ====
UMIACS Staff requires positive identification before we'll honor a request to change a password. In the event that you are unable to change your password via the methods above, send an email to staff@umiacs.umd.edu detailing your situation. Typically, we'll ask you to get in touch with your PI/advisor, as they should be able to identify you. They will work with staff to reset your password on your behalf, and then communicate it to you in a secure manner.
==== Forgotten Passwords ====
If you have forgotten your Windows or Unix password(s), you will need to stop by the UMIACS Help Desk or follow the Off-site instructions above.

MonthlyMaintenanceWindow

2014-06-13T14:47:44Z

Jlent:

UMIACS takes a monthly maintenance window to patch and reboot our hosts. This provides a way to ensure security updates are installed and activated on the numerous different platforms and appliances that we maintain.

The window is calculated each month by adding 9 days to [http://en.wikipedia.org/wiki/Patch_Tuesday Microsoft's Patch Tuesday]. This allows us to marshal patches released that month from Microsoft, Red Hat, and our other vendors and have enough time to get our systems prepared to reboot for that month's window.

The window is always going to be on a '''Thursday''' from '''8pm-12am'''. A list of maintenance windows for 2014 is as follows with the upcoming window in bold.

* '''June 19th 2014'''
* July 17th 2014
* August 21st 2014
* September 18th 2014
* October 23rd 2014
* November 20th 2014
* December 18th 2014

==Archives==
* January 17th 2013
* February 21st 2013
* March 21st 2013
* April 18th 2013
* May 23rd 2013
* June 20th 2013
* July 18th 2013
* August 22nd 2013
* September 19th 2013
* October 17th 2013
* December 19th 2013
* January 23rd 2014
* February 20th 2014
* March 20th 2014
* April 17th 2014
* May 22nd 2014

UpdatingMozillaSoftware

2014-06-05T19:25:36Z

Jlent: /* Troubleshooting */

__FORCETOC__
Like most applications, it is important to keep your browser and email clients up-to-date to combat security flaws and gain new functionality. The instructions on this page should help you update Mozilla Firefox and Thunderbird.

You can also find installers and documentation for the latest versions of Firefox and Thunderbird here:
*Firefox: http://www.getfirefox.com
*Thunderbird: http://www.getthunderbird.com

== Determining the Installed Version ==

You can find out what version of Firefox or Thunderbird you have installed on you computer by opening up the application and choosing:
*"Help > About Mozilla [application]" from the menu bar on Windows
*"Firefox > About [application]" from the menu bar on Mac OS X
where [application] is either "Firefox" or "Thunderbird".

== Updating Mozilla Firefox (Windows & Mac) ==

#To manually check for a Firefox update, click the "Help" menu on the menu bar, and select "Check for Updates..." 
#*On occasion, you may see "Apply Downloaded Update now...", rather than "Check for Updates..." -- the same process applies.
#If there are updates available, click the "Get the New Version" or "Update Firefox" button
#*If no updates are available, click "OK" or "Done" to close the window.
#When the install process is complete, you must restart Firefox. To close Firefox and re-open it, click "Restart Firefox".
#Finally, verify that there are no more updates to be installed by performing Step #1 again. Depending on what version you start with, Firefox may need to run through this process multiple times.

 
[[Image:winfoxstp1.png|thumb|left|300px|Step 1: Check for Updates (Windows)]]
[[Image:FFcheckUpdatesMac.png|thumb|300px|Step 1: Check for Updates (Mac)]]
 
[[Image:winfoxstp3.png|thumb|left|300px|Step 2: Get New Version (Windows)]]
[[Image:FFgetNewVersionMac.png|thumb|300px|Step 2: Get New Version (Mac)]]
 
[[Image:winfoxstp2.png|thumb|left|300px|Step 3: Restart Firefox (Windows)]]
[[Image:RestartFirefoxMac.png|thumb|300px|Step 3: Restart Firefox (Mac)]]
 

== Updating Mozilla Thunderbird (Windows & Mac) ==

#To manually check for a Thunderbird update, click the "Help" menu on the menu bar, and select "Check for Updates..." 
#*On occasion, you may see "Apply Downloaded Update now...", rather than "Check for Updates..." -- the same process applies.
#If there are updates available, click the "Get the New Version" or "Update Thunderbird" button
#*If no updates are available, click "OK" or "Done" to close the window.
#When the install process is complete, you must restart Thunderbird. To close Thunderbird and re-open it, click "Restart Thunderbird".
#Finally, verify that there are no more updates to be installed by performing Step #1 again. Depending on what version you start with, Thunderbird may need to run through this process multiple times.

 
[[Image:Winstp1.png|thumb|left|300px|Step 1: Check for Updates (Windows)]]
[[Image:CheckForThunderbirdUpdatesMac.png|thumb|300px|Step 1: Check for Updates (Mac)]]
 
[[Image:Windstp2.png|thumb|left|300px|Step 2: Get New Version (Windows)]]
[[Image:ThunderbirdGetNewVersion.png|thumb|300px|Step 2: Get New Version (Mac)]]
 
[[Image:Winthunstp2.png|thumb|left|300px|Step 3: Restart Thunderbird (Windows)]]
[[Image:RestartThunderbird.png|thumb|300px|Step 3: Restart Thunderbird (Mac)]]
 

== Troubleshooting ==
If for some reason Firefox or Thunderbird refuses to update using the methods described above, please stop by the [[HelpDesk]] and have a technician assist you.