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 Linux storage space.

What is the “Linux storage space”?

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

While some of you may have specific Linux accounts, with which you access Linux systems in CS or ECE, you may not be aware that ALL users on CAT supported systems have a Linux account.  This account can be used for additional storage.

The S: drive mapping provides you with access to certain universal folders that are shared between platforms in our Linux environment (Ubuntu and CentOS Linux). 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 Linux machines on our network. The U: drive is an older reference that points to the “Solaris” home folder in your Linux storage. We recommend everyone use the S: drive as we will be phasing out the U: drive entirely.

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

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

The 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 a sub directory in your existing Linux storage called “solaris/smb_files”.  You may chose to make your Linux home directory available through this drive mapping by creating a appropriate symbolic link on from the Linux side.

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

Most users will find the S: drive space indistinguishable from the N: 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 Linux home directory natively from Linux side.