Our Shared Infastructure Services group offers web hosting. This service exists on redundant Red Hat Linux front-end servers running Apache and PHP, with a backend database server running MySQL (we also offer a Windows / IIS hosting option).
<CTRL>d -- Scroll down (half a screen)
<CTRL> -- Scroll up (half a screen)
<CTRL>f -- Page forward
<CTRL>b -- Page backward
/string -- Search forward
?string -- Search backward
n -- Repeat search
N -- Repeat search reverse
G -- Go to last line
nG -- Go to line n :n -- Go to line n
<CTRL>l -- Redraw screen
<CTRL>g -- File information
Three screen editors are available on OIT Unix systems. They are pico, vi, and emacs.
Pico is the editor that pine uses by default to compose messages. If you use pine, you will find pico very easy to use. Even if you do not use pine, pico is a very simple screen editor to learn. The commands are always listed at the bottom of the screen. If you lack experience with editors, this is probably the one for you.
To view the online manual pages for this edtor, type man pico at the prompt:
The first thing to know is the lpr command. The basic syntax to print any file on any printing resource is
spot> lpr -P resource-name file-name
where resource-name is the name of the printing resource (ie, printer) and file-name is the name of the file to be printed. Unix print jobs are "spooled," which means the file specified by the lpr command is copied into a "spooling directory," where it is actually printed.
spot> man printing
This is an overview of how to compile programs on Unix machines. The examples are specific to the C compiler but can be applied to all Unix compilers. Note that compilers are available only on rintintin, rastro, and eddie--not on the information-only machines like spot. To find out which compilers are on a particular machine, type:
man -k compile
This command will produce a list of all the compilers that have manual pages and will indicate which sections address compilers. For example, on spot the output looks like this:
This document is designed to introduce Boulder Campus users to local Unix conventions that they may have not seen on Unix systems at other sites. The directory
contains several files that explain OIT procedures, user responsibilities, and some third-party software documentation. In particular, Accounts, Disk Allocation, and User Responsibilities should be consulted.
The path to a user's home directory uses the following convention:
To use the online Unix manual, enter the command man, followed by the subject you want to read about. For example, to find out nearly everything there is to know about the Unix command ls, which displays the contents of a directory, type man ls in response to the system prompt.
spot> man ls
For more information on the man command itself, type
To log in to your Unix account, enter your login name at the login: prompt and press RETURN
Or, on Macintosh's Terminal application you will enter:
You will now see the Password: prompt
Enter your password exactly and press RETURN. Your password will not be displayed on the screen as you type it. Your login and password are case-sensitive.
Below is a brief explanation of how to set up password protection of web pages hosted on our WWW basic content management service.
First you can only protect directories. You cannot specify individual pages. But this is easily worked around by making subdirectories.
These notes only explain how to set up passwords for individual users. You can give each user on a page their own username and password, or you can give the same username and password to everyone who needs access to the pages. The latter is much easier to maintain, and works well for almost all pages that require passwords, such as a course, department, committee, etc.
Create a directory in your web space. Inside of it, create a file called .htaccess (notice that the file name begins with a period). The .htaccess file should contain these lines, modified to match your web site (explanations of each line are just below):
Every Web page has permissions set behind the scenes, which allow the creator of the page and other individuals to read that page on the Web and/or to make changes to that page.
There are three categories of users:
There are three types of permissions (usually called modes):
If your web site has more than one person making updates to the web pages, it is important to set the proper write permissions. Setting the group write permission will allow all of the people who are in your web site group to make and publish updates.