S: and U: Drives

S: and U: Drives2019-08-09T09:24:31+00:00

Understanding the S: and U: Drives

Observant users of CAT supported Tier 1 or 2 Windows systems may notice that two of their drive mappings is mapped to their UNIX storage space.

What is the “UNIX storage space”?

The UNIX Storage Space is the contents of your UNIX and Linux home directory.

While some of you may have specific UNIX accounts, with which you access UNIX (ie: Solaris) systems in CS or ECE, you may not be aware that ALL users on CAT supported systems have a UNIX account.  This account can be used as additional storage.

The S: drive mapping provides you with access to that storage location (ie: home directory).  Windows users can use the S: drive the same way they use their N: drive.  The S: drive points to the “common” parts of your home folder that are synced across all the unix/linux machines on our network. While the old U: drive points to the Solaris home folder. You can navigate inside the U: Drive to access the same files as the S: drive. Eventually the S: drive will replace the U: drive entirely.

For Setup instructions, see Mapping a Drive to a UNIX Account

Disk Quota on the S: (and U:) drive

The UNIX/Linux disk quota is 15GB.  This is on top of your Windows quota of 10GB.

Accessing Your Public Webpages via the S: Drive

Windows Users can access their public webpages via S:\public_html

Does the U: drive also give you access to your Linux storage space? 

As delivered, the U: drive simply maps to your existing UNIX (Solaris) storage.  You may chose to make your Linux home directory available through this drive mapping by creating a appropriate symbolic link on UNIX.

Is the S: drive completely compatible with the U: drive?

Most users will find the S: drive space indistinguishable from the U: drive.

However, some of the more sophisticated use of restricting user rights to files and directories on a selective basis are not applied transparently through the S: drive.  If you want to do file and directory rights across the U: drive, you will need to manipulate the UNIX home directory natively from UNIX.