Upcoming Changes to Default Permissions for New Linux Files

Over the semester break (the exact date is to be determined) we will make changes to the default permissions for new files on the Linux system. This will not affect files stored on the Windows system, but it will affect Linux files accessed from Windows like the Z: drive and Linux project directories.

The net effect of the changes will be to make new files in private directories private and new files in project directories (and other shared directories) readable and writable by the people associated with that project. We will not change the permissions of existing files in project directories, but we will change the permissions of files in home directories to make them private. Owners of project directories are welcome to request that we change the permissions of files in their directories to match the new standard.

For a more detailed description of the changes we will make, see Changes to Default Linux Permissions. Owners of project directories will be receiving a couple of messages with further details, including the opportunity to opt out of the changes. Individuals can also change their own default Linux permissions if they desire, and can of course change the permissions on any given file at will.

Linux Project Directories to be Available as V: Drive

The changes described above will also allow us to create a new Windows network drive, V:, which gives access to all the Linux project directories--similar to how X: gives access to all the Windows project directories. It will no longer be necessary for users to map a drive to a Linux project directory before they can use it, but existing mappings will continue to work. There is one exception: if you currently have a drive mapped to V:, you will need to change it to use a different drive letter. Instructions for mapping a network drive can be found in our publication Mapping a Drive to a Network Share.

X-Win32 License

The annual campus site license for X-Win32 expired at the end of November and was renewed. To renew your license, download the software from the SSCC web server. You'll need to give your SSCC user name and password, as X-Win32 is only licensed for UW faculty, staff, and students. Save the file in a convenient location, and then double-click on it. Xwin32 will install itself and connections to HAL and KITE will be set up automatically. Note: If you already have X-Win32 installed, it's best to uninstall it before installing the new copy. For more information on X-Win32, see the SSCC Publication, Connecting to SSCC Linux Computers using X-Win32.

Reserving Computer Classroom for Spring Semester Courses

Now is the time to get a jump on reserving the 3218 classroom or mobile lab for your spring semester class before your spot gets taken by someone else. Reservations are filling very quickly. Contact Ann Lewis (atlewis@wisc.edu) to reserve. Ann's office is in the 4226 office suite and her phone number is 2-0862.  Visit www.ssc.wisc.edu/sscc/instruction/ for more information about the 3218 classroom and the mobile lab.

Even if you do not need to reserve the classroom or lab, you can arrange for your students to have access to SSCC's drop in labs (3218 and 4218 Social Science) for doing their homework. Ann can help you with this as well.

Doug Hemken (dehemken@wisc.edu), statistical computing specialist for SSCC, is available to help students with homework and class projects. You can also arrange for Doug to come to your class and provide instruction on statistical software. Doug's office is in the 4226 office suite and his phone number is 2-4327.

Tip: Making the Most of Your Visit to the SSCC Consultant

The SSCC's statistical software consulting service is very busy this time of year as deadlines approach, so we'd like to offer a few suggestions to make your visit as helpful as possible.

• Plan to come to the consultant's office in 4226 rather than discussing things in the labs if at all possible. That way we can talk freely without disturbing other lab users.
• You can be logged in in more than one place at a time.
• Put your data and program files on the network so we can access them from the consultant's office. Of course storing things on the network is generally a good idea, because that way they get backed up.
• If you're using Winstat, you can disconnect from your session rather than logging off and then we can reconnect to it in the consulting office. That way we'll have everything you've been working on immediately available.
• Taking a few moments ahead of time to think about how to describe what you're doing and to frame your specific question can be very helpful. Sometimes you'll find that describing the problem to someone else--or even thinking about doing so--will be enough for you to see the solution.
• Don't forget about the SSCC's publication collection. Something like An Introduction to Stata may have all the answers you need.