Computer Science at Indiana State University - User contributions [en]

FAQ

2026-06-05T02:03:39Z

Jkinne: /* Recommended Computer */

==Recommended Computer==
Much of what we do in CS courses can work in Windows, Mac OS, Linux, or Chrome. There will be an odd thing or two still that may not work in Chrome.

All other things being equal, getting a computer that is not "bottom of the barrel" would be good. Chromebooks in the $400+ range should generally work reasonably well. For Windows/Linux/Mac OS laptops, you should be looking for 8GB RAM bare minimum, preferred 16GB if possible, and avoid getting a laptop with an i3 or Celeron processor; this roughly corresponds to the $500+ price range. You can potentially get anything to work, but will have an easier time with a medium-range computer than a low-end system.

For laptops, we recommend getting at least a 3 year warranty (since they tend to break if you actually do transport them around). Also, we recommend getting an option that has a long battery life (rule of thumb - battery life will be half of its original rating after 1-2 years of regular daily use).

You should also have the ability to install programs on the system and have a normally reliable internet connection at home if possible.

If you have a particular system in mind for purchase that you would like an opinion on, please feel free to contact one of the CS faculty members.

University recommendations are listed [https://indstate.teamdynamix.com/TDClient/1851/Portal/KB/Article/71665/Student-Laptop-Minimum-Specifications here] and are similar to that described above.

== CS 151 ==
New students majoring in computer science should take ECT 130 and CS 151 their first term. ECT 130 is an overview of CS, IT, and CEET majors. It is required for all of those majors. There is a ''small'' amount of programming. CS 151 is the first programming course in the CS major, is a full semester of programming (in Python, as of 2026), and helps to decide whether you prefer CS or IT.

If you are a new student and have a really full first semester, you might just take ECT 130 your first term, and wait to take CS 151 your second term. But we recommend taking CS 151 your first term if you can fit it in; it helps you decide if you want to stick with computer science, and it gets you further into the major sooner (which is good for applying for internships).

== Should you buy your textbooks? ==
Find a copy for a reasoanble price, and yes, purchase it. You will be more likely to actually read it if you have a copy (rather than trying to borrow a copy or something). Whatever your major is, you should want to learn the course content. Also, not everything you need to know is covered in lecture (there just isn't enough time), and it's up to you to fill in the gaps.

== Positions in the department ==
We consider all CS students whenever we have an opening. The most important qualities we consider are how well you do in your courses (are you one of the top few students?), how responsible and hard-working you are, and how well you communicate and interact with others.

== Finding information at ISU ==
Think of what the department might be called, and try going to the [https://indianastate.edu/search/offices A-Z Department/Office Directory] and searching using the browser's search option (ctrl-f). You can also try doing a regular internet search (google, bing, etc.) with Indiana State University and whatever you are looking for (directory, schedule of classes, etc.). That sometimes gets you to the right page faster than using ISU's search page.

== How to contact your professors ==
Check your professor's class schedule (see the schedule of classes linked off the [http://cs.indstate.edu CS homepage]). You can normally catch a professor just before or just after one of their classes, and then ask them when you could come to their office or how they prefer to be contacted. Once the semester starts office hours should be in the syllabus for each course.

== Why are you Here? ==
Ask yourself why you are paying ISU thousands of dollars for a degree? Hopefully because you are ''interested'' in CS and also want to get a job in CS after graduating. This is much more likely to happen (getting a job in CS) if you take your courses seriously and put your full effort in. Students who do not do their best, or try to get others to to their work, have much less success in securing good jobs after graduating.

== Programming and Linux ==
Many professors (e.g., Kinne) require students to turn in assignments on the CS server. For these courses you will do most (or all) of your programming assignments for the course on the CS server. To be counted as correct, in these courses your program must compile and run on the CS server. See [[Programming and CS - Getting Started]] for help in getting started on the CS machines.

== Planning Ahead ==
You should begin to think about applying for jobs at least one year before you will do so. If you wait until you graduate to think about how to get a job after graduation, you will not be as successful. Some of our graduates have decided to complete an industry certification program (e.g., from Microsoft, Oracle, or Cisco) to increase their chances of getting a job after graduation; we have been told this can take about one year from when you begin.

For both on campus jobs and jobs after graduation, you wil benefit by doing well in your classes - (i) doing well better prepares you, (ii) having a higher GPA looks better to prospective employers, and (iii) your professors can give you good recommendation letters if you have done well in their classes. It really does pay off to do your best in your classes (and participate fully - pay attention, answer/ask questions, etc.).

== On Campus Jobs ==
You can view available on-campus jobs by visiting [http://jobs.indstate.edu/] and clicking on the appropriate category for you. Make sure to check back regularly because jobs might not all be posted by the beginning of the semester. To apply for a position, you need to apply online; it will normally not do you any good to contact the department in person as well. Make sure to submit all documents that are asked for (e.g., resume, transcripts, cover letter). A cover letter should briefly explain your background and interests, and indicate enthusiasm for the position you are applying for. For the resume, see [[Careers]] for advice and you can find examples online to get ideas for the appropriate format and contents; as a general philosophy, you should be very positive about yourself, but do not ever lie (e.g., do not say you know Java if you do not). For additional help in writing your resume and cover letter, you can contact the Career Center or more senior CS students (e.g., lab assistants who are currently on duty in the lab).

Note for new students. The application system asks you to list some number of references. You can list professors who you will have in class or your advisor, but they will not be able to say much about you other than what they might know from your transcript. It is better to list a reference that knows you (possibly someone you had in previous studies or work). Once you have been in class long enough to have had some assignments or exams graded, the professors you have in class might able to give more support in a recommendation for you. And always check with someone before listing them as a reference.

FAQ

2026-06-05T02:03:11Z

Jkinne: /* CS 151 */

=Recommended Computer=
Much of what we do in CS courses can work in Windows, Mac OS, Linux, or Chrome. There will be an odd thing or two still that may not work in Chrome.

All other things being equal, getting a computer that is not "bottom of the barrel" would be good. Chromebooks in the $400+ range should generally work reasonably well. For Windows/Linux/Mac OS laptops, you should be looking for 8GB RAM bare minimum, preferred 16GB if possible, and avoid getting a laptop with an i3 or Celeron processor; this roughly corresponds to the $500+ price range. You can potentially get anything to work, but will have an easier time with a medium-range computer than a low-end system.

For laptops, we recommend getting at least a 3 year warranty (since they tend to break if you actually do transport them around). Also, we recommend getting an option that has a long battery life (rule of thumb - battery life will be half of its original rating after 1-2 years of regular daily use).

You should also have the ability to install programs on the system and have a normally reliable internet connection at home if possible.

If you have a particular system in mind for purchase that you would like an opinion on, please feel free to contact one of the CS faculty members.

University recommendations are listed [https://indstate.teamdynamix.com/TDClient/1851/Portal/KB/Article/71665/Student-Laptop-Minimum-Specifications here] and are similar to that described above.

== CS 151 ==
New students majoring in computer science should take ECT 130 and CS 151 their first term. ECT 130 is an overview of CS, IT, and CEET majors. It is required for all of those majors. There is a ''small'' amount of programming. CS 151 is the first programming course in the CS major, is a full semester of programming (in Python, as of 2026), and helps to decide whether you prefer CS or IT.

If you are a new student and have a really full first semester, you might just take ECT 130 your first term, and wait to take CS 151 your second term. But we recommend taking CS 151 your first term if you can fit it in; it helps you decide if you want to stick with computer science, and it gets you further into the major sooner (which is good for applying for internships).

== Should you buy your textbooks? ==
Find a copy for a reasoanble price, and yes, purchase it. You will be more likely to actually read it if you have a copy (rather than trying to borrow a copy or something). Whatever your major is, you should want to learn the course content. Also, not everything you need to know is covered in lecture (there just isn't enough time), and it's up to you to fill in the gaps.

== Positions in the department ==
We consider all CS students whenever we have an opening. The most important qualities we consider are how well you do in your courses (are you one of the top few students?), how responsible and hard-working you are, and how well you communicate and interact with others.

== Finding information at ISU ==
Think of what the department might be called, and try going to the [https://indianastate.edu/search/offices A-Z Department/Office Directory] and searching using the browser's search option (ctrl-f). You can also try doing a regular internet search (google, bing, etc.) with Indiana State University and whatever you are looking for (directory, schedule of classes, etc.). That sometimes gets you to the right page faster than using ISU's search page.

== How to contact your professors ==
Check your professor's class schedule (see the schedule of classes linked off the [http://cs.indstate.edu CS homepage]). You can normally catch a professor just before or just after one of their classes, and then ask them when you could come to their office or how they prefer to be contacted. Once the semester starts office hours should be in the syllabus for each course.

== Why are you Here? ==
Ask yourself why you are paying ISU thousands of dollars for a degree? Hopefully because you are ''interested'' in CS and also want to get a job in CS after graduating. This is much more likely to happen (getting a job in CS) if you take your courses seriously and put your full effort in. Students who do not do their best, or try to get others to to their work, have much less success in securing good jobs after graduating.

== Programming and Linux ==
Many professors (e.g., Kinne) require students to turn in assignments on the CS server. For these courses you will do most (or all) of your programming assignments for the course on the CS server. To be counted as correct, in these courses your program must compile and run on the CS server. See [[Programming and CS - Getting Started]] for help in getting started on the CS machines.

== Planning Ahead ==
You should begin to think about applying for jobs at least one year before you will do so. If you wait until you graduate to think about how to get a job after graduation, you will not be as successful. Some of our graduates have decided to complete an industry certification program (e.g., from Microsoft, Oracle, or Cisco) to increase their chances of getting a job after graduation; we have been told this can take about one year from when you begin.

For both on campus jobs and jobs after graduation, you wil benefit by doing well in your classes - (i) doing well better prepares you, (ii) having a higher GPA looks better to prospective employers, and (iii) your professors can give you good recommendation letters if you have done well in their classes. It really does pay off to do your best in your classes (and participate fully - pay attention, answer/ask questions, etc.).

== On Campus Jobs ==
You can view available on-campus jobs by visiting [http://jobs.indstate.edu/] and clicking on the appropriate category for you. Make sure to check back regularly because jobs might not all be posted by the beginning of the semester. To apply for a position, you need to apply online; it will normally not do you any good to contact the department in person as well. Make sure to submit all documents that are asked for (e.g., resume, transcripts, cover letter). A cover letter should briefly explain your background and interests, and indicate enthusiasm for the position you are applying for. For the resume, see [[Careers]] for advice and you can find examples online to get ideas for the appropriate format and contents; as a general philosophy, you should be very positive about yourself, but do not ever lie (e.g., do not say you know Java if you do not). For additional help in writing your resume and cover letter, you can contact the Career Center or more senior CS students (e.g., lab assistants who are currently on duty in the lab).

Note for new students. The application system asks you to list some number of references. You can list professors who you will have in class or your advisor, but they will not be able to say much about you other than what they might know from your transcript. It is better to list a reference that knows you (possibly someone you had in previous studies or work). Once you have been in class long enough to have had some assignments or exams graded, the professors you have in class might able to give more support in a recommendation for you. And always check with someone before listing them as a reference.

Programming and CS - Getting Started

2026-06-05T02:02:38Z

Jkinne:

=Getting Started Pages=
* [[CS accounts]]
* [[Linux and CS Systems - Getting Started]]
* [[Python Programming - Getting Started]]
* [[C Programming - Getting Started]]
* [[R Programming - Getting Started]]
* [[Algorithms and Data Structures - Getting Started]]
* [[Gitlab - Getting Started]]

=Practice Programming Contest Problems=
See [[Programming Practice]].

= Source Control =
It is a good idea to use source control when developing software, and is necessary when you are developing in a group or professionally. When working on assignments or course projects it is the best practice to use a private repository so other students cannot copy your work. Git is the industry standard for source control. Here are some resources to use to learn Git.

* https://try.github.io/
* https://learngitbranching.js.org/
* https://www.atlassian.com/git

Programming and CS - Getting Started

2026-06-05T02:02:21Z

Jkinne: /* Recommended Computer */

CS accounts

2026-06-04T22:29:11Z

Jkinne:

This page gives information about logging into and using the CS server (cs.indstate.edu). For help about getting started with using the terminal once you can login, see [[Linux and CS Systems - Getting Started]]. For more about getting started with programming in general for CS courses, see [[Programming and CS - Getting Started]].

=Logging In=
The CS server is a Linux server. The primary ways you will login to the server is either (a) with a terminal (aka shell) that allows you to type text commands, or (b) with an sftp program to transfer files between your computer and the server. In either case, you need a username (aka login) and password. There are two types of accounts on the system - ISU portal accounts, and local accounts.

==ISU Portal Accounts==
Any student/faculty/staff who is involved in CS courses or programs (enrolled in a course, teaching a course, etc.) can login to cs.indstate.edu using their full ISU email address and portal password. The first time you login to the system, an account is created on the system that you can use. It will set your home directory on the system to <code>/home/SID@isuad.indstate.edu/</code> where <code>SID</code> is your portal id (aka sycamore id - for students it is the part before the @sycamores in your email address). After logging in, you can run the <code>pwd</code> command to see this.

For those familiar with Linux already... Note that there is not currently "finger information" about ISU portal account users. In fact, trying to run something like "finger jkinne@isuad.indstate.edu" will fail. Note that instructors of current courses can get a class list (aka roster) of accounts for their course; see below.

==Local Accounts==
Some users will have accounts on the CS server that are not tied to their ISU portal accounts. For example, CS faculty have local accounts, and a number of users of the server prior to 2025 have local accounts. These are accounts with username and password that were created just on the server (the ability to login to the server with ISU portal credentials was added in 2025). Any new instructor teaching a CS course can ask for a local account if you do not have one already - write to root@cs.indstate.edu.

==SSH Key==
You can setup an SSH key to login to the system. You will first need to login to the system normally. Once you are logged in, you can run the following commands.
<pre>
mkdir ~/.ssh # in case it does not exist yet
chmod 700 ~/.ssh # make sure this directory is not accessible to other users
ssh-keygen # create keys for logging in
</pre>
You will then transfer the private key file (the one that does not end in .pub) to your local computer in the location for ssh keys. This varies depending on your operating system. On Linux and Mac OS, it will be in <code>~/.ssh</code>.

= CS Server Policies =
== Prohibitions ==
For any accounts that you have on the CS server, you should follow all ISU policies. In particular the following are prohibited -
* using your account to store or distribute anything that is against its terms/copyright/etc. (e.g., no movies, textbooks, answers to HW problems)
* using your account to do anything that is illegal
* using a password that is too easy to guess (i.e., a password cracker that we run finds your password)
* overloading the CPU or GPU of the system, or filling up any of the system drives
* anything that is along these lines that we have not thought to state explicitly
A violation of any of these will result in your account being locked and no longer being allowed to have an account on the systems.

== Inactivity ==
Accounts that are not used for a period of 6 months will likely be locked as a security precaution. You can write to root@cs.indstate.edu to ask to have your account unlocked again.

=Student Use and Course Account=
For courses that are currently being offered, if the course uses the server, a class account is created that the instructor of the course can use if they like. This is explained in this section with two examples: CS 151 Intro to Computer Science, and CS 473/573 Computer Networks.

==Course Account==
An account on the system is created where files for the class can be kept that are to be shared with the students. For CS 151, the account created has username <code>cs151</code>. For CS 473/573, a single account, <code>cs473</code>, is created that is to be used for both courses.

==Student Use==
For students who are currently enrolled in a CS course that uses the server, the first time you login to the system with your ISU portal account, a directory should be created within your account for the course. For example, students in CS 151 will have a directory <code>cs151</code>, and students in CS 473/573 will have a directory <code>cs473</code>.

Permissions are set on the system so that instructors of the course have read access to the files within student's course directories for their courses. The instructor for CS 151 will have read access to the <code>cs151</code> directories of the students enrolled in CS 151; the instructor for CS 473/573 will have read access to the <code>cs473</code> directories of the students enrolled in CS 473/573; etc. The instructor of the course might have the students submit their work on the server within these directories. Each instructor can choose how they would like to do this.

The course account for each course also has read access to the directories for that course. For example, the <code>cs151</code> account will have read access to the <code>cs151</code> directories within any student enrolled in CS 151.

==Course Account - Instructor Private Files==
The course account is created with a <code>~/private</code> directory that is not accessible to other users (i.e., not accessible to students). The class list (aka roster) of students and their accounts is put into this directory (<code>classlist_brief.csv</code> with the most important information for each student, and <code>classlist_full.csv</code> with more information). The instructor could keep other files in this <code>private</code> directory that is meant to be private (e.g., model solutions or grading information).

Inside the <code>~/private/</code> directory of the course account, there is also a <code>students</code> directory that has symbolic links to each of the student's course directories in the course. For example, if the course is cs151, and if the user jdoe12345@isuad.indstate.edu is a student in the course, then there will be a link <code>/home/cs151/private/students/jdoe12345@isuad.indstate.edu</code> that is a link to the cs151 directory for this student (<code>/home/jdoe12345@isuad.indstate.edu/cs151/</code>). The instructor for the course can quickly get into the students' directories for the course (but not their home directory) by going to the private/students/ directory and going from there.

The accounts for the instructors of the course are set so they can sudo as the course account. If the instructor of CS 151 uses the local account <code>jkinne</code> then this user can run the following command to get a shell running as the CS 151 course account: <code>sudo -u cs151 -i</code>.
Note that this only works for local accounts, and does not work for ISU Portal accounts (it might work for the jkinne local account but not for the jkinne@isuad.indstate.edu account).

====Change of Semester and Backups====
Before the next semester, a backup copy of each course account will be created that will be in the course's <code>~/private/backup/</code> directory. A directory will be created for the term, and it will have all of the course account's files from that term within it.

Once the backup has been created for the previous term, the instructor for the current semester can remove files and directories that are no longer needed for the new term. For example, you can clear out the assignment directories in the course account's home directory, and also the student submissions that are in <code>~/private/submissions/</code>. Those files will still be in the backup directory in case you need them later.

When the new semester starts (if the course is running in the new semester), the following in the <code>~/private</code> directory will be updated to be for the new term: classlist_brief.csv, classlist_full.csv, students directory (symbolic links to new semester's students).

==Assignments==
Any directory within the course account can be used as an assignment. For example, suppose the account <code>cs151</code> contains a directory <code>h7</code>. This directory might have files for the students to use on the assignment; they can view these files by going to the directory <code>/home/cs151/h7/</code>.

A student can "checkout" or "get" an assignment by running
<pre>hw_get.py cs151 h7</pre>
This will copy the <code>h7</code> directory that is in the <code>cs151</code> account into the <code>cs151</code> directory of the user that executes the command.

An instructor can collect an assignment by running the script <code>hw_collect.py</code>. For the above example, the instructor would run: <code>hw_collect.py cs151 h7</code>. This will go into each student in the course's <code>cs151</code> directory and copy their h7 directory into <code>/home/cs151/private/submissions/h7/</code>. There will be a new directory in that submissions directory for the date and time the submissions were collected. For example, if the user jdoe12345@isuad.indstate.edu is in the cs151 course, then the contents of <code>/home/jdoe12345@isuad.indstate.edu/h7/</code> will be copied into the submission directory (inside of <code>/home/cs151/private/submissions/h7/</code>). The directory <code>/home/cs151/private/submissions/h7/</code> will have a symbolic link <code>latest</code> that is a pointer to the latest submission.

There is a system in place that can be used for auto-checking the output of student programs. The instructor creates a file <code>.tests.json</code> inside of the assignment directory that has the test cases. The instructor will also need to create a correct working version of each program that can be run to get the "correct" results. The students will use the <code>hw_check.py</code> command to check their output. The instructor can also use the same command to check student submissions. You can get more details about how this works by logging into the system and running: <code>hw_check.py --help</code>.

=Websites / Webservers=
==Apache==
The main cs.indstate.edu website uses the Apache web server. This is configured so that any user can put html and php files in the right directory in their account to be on the web server. Jeff Kinne, who has portal id <code>jkinne</code> and therefore account on the server with home directory <code>jkinne@isuad.indstate.edu</code>, would do the following to create the right directories.
<pre>
cd ~jkinne@isuad.indstate.edu # jkinne's home directory
mkdir public_html # directory apache looks in for website files
setfacl -m group:www-data:x . # give apache execute access to home directory
setfacl -R -m group:www-data:rX public_html # give apache rX access to public_html
setfacl -R -m default:group:www-data:rX public_html # and new files will also have access
cd public_html # go into that directory
echo "Hello world" > index.html # write a hello world file
</pre>
Then the file index.html will be accessible on the web at https://cs.indstate.edu/~jkinne@isuad.indstate.edu. Since the web server is Apache, you can look for help on the Apache web server about configuration options (in particular .htaccess files that you can put in your public_html directory to change some settings). By default, the Apache web server understands html and php files. There may be other types of files you would want it to be able to understand; if so you can write to root@cs.indstate.edu.

==Node, Django, etc.==
Node, Django, and many other web server frameworks can also be run off of the CS server. These generally will pick a port that they will run off of, and you run the main file for your server. Note that the Apache web server uses the "standard" ports (80 for http and 443 for https), so you cannot use those. If you want to run a Node, Django, or similar web server off of the CS server, you need to pick a port that isn't used for anything else. You should never pick a port number that is below 1024 and really should avoid port numbers below 10000. If you want to make sure to pick a port that will not interfere with anything, write to root@cs.indstate.edu. If you were to run your node web server with port 60000, then you would browse to it on the web at https://cs.indstate.edu:60000. Note that there is indeed normally a node server running on that particular port.

=Spring 2026=
The following is the list of courses that are supported on the server for the 2026 spring, along with the instructor accounts (aka admin accounts) for each course.
<pre>
course,admin_accounts
cs151,"jkinne,jeff,jkinne@isuad.indstate.edu"
cs170,"hrafieipour@isuad.indstate.edu"
cs201,"majid,mafsharnoghon@isuad.indstate.edu"
cs203,"namoako,namoako@isuad.indstate.edu"
cs211,"mjenkins1@isuad.indstate.edu"
cs351,"rabhyankar@isuad.indstate.edu"
cs331,"namoako,namoako@isuad.indstate.edu"
"cs401,cs501","majid,mafsharnoghon@isuad.indstate.edu"
cs401L,"majid,mafsharnoghon@isuad.indstate.edu"
"cs456,cs556","jcompton5,jcompton5@isuad.indstate.edu"
cs456L,"jcompton5,jcompton5@isuad.indstate.edu"
"cs457,cs557","kwexoo,kexoo@isuad.indstate.edu"
cs457L,"kwexoo,kexoo@isuad.indstate.edu"
"cs458,cs558","namoako,namoako@isuad.indstate.edu"
cs458L,"namoako,namoako@isuad.indstate.edu"
"cs469,cs569","katterson1,katterson1@isuad.indstate.edu"
"cs475,cs575","rabhyankar@isuad.indstate.edu"
cs500,"jkinne,jeff,jkinne@isuad.indstate.edu"
cs600,"arash,arafiey@isuad.indstate.edu"
"cs601,cs417","majid,mafsharnoghon@isuad.indstate.edu"
cs609,"katterson1,katterson1@isuad.indstate.edu"
cs611,"rabhyankar@isuad.indstate.edu"
cs618,"shosseini@isuad.indstate.edu"
cs685,"arash,arafiey@isuad.indstate.edu"
cs695,"arash,arafiey@isuad.indstate.edu"
ect438,"jkinne,jeff,jkinne@isuad.indstate.edu"
</pre>
If any course instructors would like any additions, subtractions, or changes to these, let the sys-admin know.

Gitlab - Getting Started

2026-06-04T22:28:39Z

Jkinne:

''This page is part of [[Programming and CS - Getting Started]]''

=Git=
[https://en.wikipedia.org/wiki/Git Git] is a version control system that can be used to keep track of your files (programming code, but also other files as well).

Two of the most popular installations of git (as of 2020) are [https://github.com/ github] and [https://gitlab.com/ gitlab]. When Microsoft purchased github, it became fashionable to prefer gitlab. Github allows for projects to be hosted on their servers. Gitlab allows for hosting either on their servers or to run a local installation of gitlab on ones own servers.

Of late, we have hosted projects using gitlab either on gitlab's servers or on ISU's local installation of gitlab.

=Account Setup=
'''On gitlab.com''' - Account setup on [https://gitlab.com/ gitlab.com] is just like any other website. You create a free account, choose your username/password, etc. The account is yours and is not tied in any particular way to ISU. You can give access to your projects in much the same way as you give access to files on google drive, onedrive, dropbox, etc.

'''On gitlab.indstate.edu''' - ISU's local installation of gitlab is at https://gitlab.indstate.edu/. For this system you use your ISU portal id and password. You do not need to create an account. The first time you login into the system, it initializes an account for you. CS courses and ISU CS projects in general tend to use ISU's local installation because we can tie access based on course rosters, etc.

=Getting Around=
Whether you are using gitlab.com or gitlab.indstate.edu, the functionality and "how to get around" is about the same. You have two main methods for using either.

==Web browser interface==
You can view projects within your web browser. How to get around is fairly intuitive - as is the case with any web page, you look around and click around to see what different things do. When you have something specific you want to do but don't see how to do, you ask the internet or ask your instructor (and we may update this wiki to give instructions on how to do it).

==Terminal interface==
Git allows for downloading/uploading/etc. files in your projects from the terminal. In order to do this, you need to (a) have a git client installed on your system, (b) understand the terminology that git uses for keeping track of files and the steps in using git to download/update/upload files, (c) make it so.

Some reading material about using git - https://www.tutorialspoint.com/git/index.htm

===Vocab / Cheat Sheet===

===Workflow===
A common use case is that you will need to download someone else's (e.g., instructor's) gitlab project, create your own version of some part of the project, test/debug your version of the project, eventually put in a request to update the main project with your code. The steps involved in that workflow.

'''Clone''' - To download the current version of the project you (a) browse in your terminal to the directory where you want to have the project code, (b) run <code>git clone url_to_project</code>

'''Branch''' - If a branch has already been created for you, then you can set that as your active branch by running <code>git checkout branch_name</code>. If a branch has not yet been created for you, you run <code>git branch branch_name</code> to create a new branch. In either case, you have a branch of the project to work within.

'''Do your work''' - You work on your files locally - test, debug, etc.

'''Stage/Commit/Push''' - To save your work to the remote server, you need to stage, commit, and push. You can stage/commit batches of changes, or do a stage/commit for each discreet task accomplished. If you are working in some_file.txt, you would run the following sequence of commands.
<pre>
git add some_file.txt # this "stages" the file to be part of the next commit
git commit -m "Some updates to the file" # This commits, will be a permanent record of this version of the file
git push # sends all committed changes to the remote server
</pre>
Note that the push will likely ask for login information to the remote server. Note that if you want there to be a record of a particular version of a file, you need to stage/commit the file. It is the commit'ed versions of files that are stored permanently.

'''Pull''' - To pull/download updates that have happened (by others), you use <code>git pull</code>.

'''Merge''' - When you ready to have your changes merged in to the main branch of the project, ask the owner of the project to check your branch. When the owner is ready for it, the owner can run the following commands.
<pre>
git branch main # owner is working in the main branch
git merge branch_name # merge your branch into the main branch
</pre>

Linux and CS Systems - Getting Started

2026-06-04T22:27:42Z

Jkinne:

''This page is part of [[Programming and CS - Getting Started]]''

This page is meant to help a new student in a CS course at ISU to get familiar with using Linux (in particular using the text-based terminal to interact with the system).

=Getting Started=
# '''Read''' - [https://ubuntu.com/tutorials/command-line-for-beginners#1-overview Ubuntu Linux Command Line Tutorial] or [http://www.ee.surrey.ac.uk/Teaching/Unix/ Linux Tutorial] - this gives you some background and introduces you to some of the terms that we use. After reading through the tutorial you have a better chance of being able to follow along the rest of the steps in this Getting Started.
# '''System Setup''' - [[Linux - System Setup]] - to get your computer setup (programs installed, etc.).
# '''Using the Terminal'''
## [[Linux Terminal - Files and Directories and Getting Around]]
## [[Linux Terminal - System Information]]
## [[Linux Terminal - Text Editors]]
## [[Using Linux - Large Text Files]]
## [[Linux Terminal - More Commands to Know]]

=Common Mistakes=
* When logging in remotely to the CS server, when you are typing your password you might not see anything printed on your screen while you type. That is a security feature so that someone watching your screen would not know how many characters are in your password. Just finish typing your password and type enter when finished.
* Note that all commands and file names in Linux are '''case sensitive'''. hello.txt is different than Hello.txt. The copy command is cp, Cp would not work, and neither would cP or CP.
* The characters _ and - are different, and having a space in a file name is different than not having one ("hello world.txt" is different than "helloworld.txt").
* For Linux directories and filenames, the "/" character is used to separate directories. On Windows, the "\" character is used instead. If you typed <pre>cd /home/cs151</pre> then this changes the directory to the cs151 user's home directory. If you instead typed <pre>cd \home\cs151</pre> you would get an error.
* The "top" or "highest level" of the Linux file system is the directory / and this is comparable to the "C:\" that was traditionally the top of the file system in Windows. In Windows there can be multiple drives (so D:\, E:\, etc.), but in Linux '''everything''' is underneath / (including additional drives, they will show up at a certain location under /).
* On Linux, ~ is a shortcut for your home directory. User jkinne@isuad.indstate.edu's home directory is in /home/jkinne@isuad.indstate.edu, so if this user is logged in and types <pre>cd ~</pre> then this means to change directories to /home/jkinne@isuad.indstate.edu/. If user jeff types <pre>cd ~</pre> then this means to change directories to jeff's home directory (which happens to be /home/jeff/).
* Not all sequences of commands are ''idempotent'' - this is a technical term that means that the sequence of commands gives the same results if executed more than once. For example, executing <code>echo "hello world!" >> hello.txt</code> once creates a file hello.txt that has one line in it, but executing again makes the file have two lines. When you see a sequence of commands to run to complete some task (e.g., from an online tutorial) be careful to execute one command after the other, all the way through, stopping after each to make sure you know what that step was supposed to do.
* Sometimes the precise syntax of commands might depend on which shell program you are using. bash is the default shell program on the CS server, but zsh is commonly used instead. You can see which shell you are running by executing the <code>ps</code> command and seeing which one is in the printed output from that command. For example, the command for displaying your resource limits is <code>ulimit -a</code> in bash and zsh, but is <code>limit</code> in tcsh. When looking up how to do things online, it is good to include your shell in the search terms (e.g., search for - bash get resource limits - rather than just - get resource limits).

=More Reading=
Read through another tutorial about Linux. Some options include the follow.
* [http://www.linuxcommand.org/ Linux Console Tutorial]
* [http://www.reallylinux.com/ Information for Beginning Linux Users]
* [http://cs.indstate.edu/~sbaker/faq/QuickRefCard.pdf Unix/Linux Quick Reference Card]

=Self Test=
Note: a practice quiz over linux commands and the terminal is here - https://indstate.instructure.com/courses/12565/quizzes/244584

Here we give small tasks for you to complete. These are numbered so that we can refer to them. For each you would need to be logged into one of the CS systems (remotely logged into the CS server or using one of the CS lab computers).

''Linux.1'' Log in to the CS server, create a directory named aboutMe in your home directory, and create a text file name.txt. In the name.txt file, give your full name.

''Linux.2'' In your aboutMe directory, create a file courses.txt and list which CS courses you are currently taking or plan to take in the upcoming term.

''Linux.3'' Log in to the CS server, create a directory named notes in your home directory, and create a text file named linux.txt and put in some links to linux tutorials or information that you have found helpful.

''Linux.4'' Log in to the CS server, create a directory named linux-bootcamp in your home directory.

''Linux.5'' In your linux-bootcamp directory, create a text file shake.txt. In shake.txt, put how many lines are in the shakespeare.txt file mentioned in the information above.

''Linux.6'' In your shake.txt file, add information about how many times "the" appears in shakespeare.txt. Use the command grep,
add to what you had how many lines "the" appears in shakespeare.txt. Hint - use the -c option for grep, also use the -i option so your count will also include "The", "THE", etc. In your shake.txt, you should have the number of lines that contain "the" (including "The", etc.), and also the percentage of the lines that contain the.

''Linux.7'' In your linux-bootcamp directory, create a text file weather.txt. Copy the Indianapolis weather csv file from /var/junk/weather/ into your linux-bootcamp directory. In your weather.txt file, put how many rows of data are in the csv file (use wc, head, and tail). Assuming 365 days per year, put in your weather.txt file how many years of data are in the csv file.

''Linux.8'' In your weather.txt file, put the maximum PRCP, SNOW, SNWD, TMAX, TMIN, MEAN from the csv file. Hint - use the sort command, and use the options -t, -k, -n, -o.

=Account Configuration=
Bash reads configuration information from a file <code>~/.bashrc</code>. A file with good defaults for the CS server are at [https://cs.indstate.edu/~jkinne/training_files/.bashrc .bashrc]. More help on bash - [https://www.gnu.org/software/bash/manual/ bash manual].

If you want to see what commands you have run in the current login session you can run the command <code>history</code>. Bash also keeps history from previous sessions in the file <code>~/.bash_history</code>.

You should create the following directories and use (a) your <code>bin</code> directory to put programs or scripts that you have downloaded or created that you want to be able to use, (b) your <code>programs</code> directory to put installation files for programs that you might need, (c) your <code>private</code> directory to keep files you want to make sure to keep private from other users, and (d) your <code>public_html</code> directory to store files that you want to be accessible on the web (at https://cs.indstate.edu/~YOUR_LOGIN).
<pre>
mkdir ~/bin/
echo "export PATH=$PATH:~/bin/" >> .bashrc # add the ~/bin/ directory to where shell looks for programs
mkdir ~/programs/
mkdir ~/private/
chmod go-rwx ~/private/ # makes that directory not accessible to other users
mkdir ~/public_html/
chmod go+rx ~/public_html/ # so the web server can access this directory
chmod go+x ~ # so the web server can access your public_html
</pre>
Note that the web server is Apache, so if you want to configure how it processes files in your account, you should look for help on the Apache web server. It is also possible to run a web server using node.js; you can look up tutorials for how to do that.

=Copying/Creating/Editing Files=
Create a file in your <code>public_html</code> directory, and practice copying a file from somewhere else on the system.
<pre>
cd ~/public_html
nano hello.txt # or use your preferred editor - vim, emacs, jove, ...
# type something in your hello.txt file, save it, and
# check that you can view it at https://cs.indstate.edu/~YOUR_LOGIN/hello.txt
cp /usr/dict/words . # copies that file into current directory, which should still be your public_html
# now check https://cs.indstate.edu/~YOUR_LOGIN/words
</pre>
Create a sub-directory within your <code>public_html</code> directory, put some file there, edit the Apache configuration file (<code>.htaccess</code>) to allow directory listing of this directory (turned off by default for security reasons).
<pre>
cd ~/public_html
mkdir files_public
cd files_public
echo "Options +Indexes" >> .htaccess
ls -a # verify that the .htaccess file exists now
cat .htaccess # see what is in the file now
cp /var/junk/kinne/text-samples/shakespeare.txt .
cp /var/junk/kinne/text-samples/austen.txt .
# Now browse to https://cs.indstate.edu/~YOUR_LOGIN/files_public
</pre>

=Long Running Jobs=
If you have a process that needs to run for more than a few minutes, you should run it like this:
<pre>time nice -n 19 whatever_command</pre>
Starting the command with <code>time</code> will give you a printout afterwards of how much time the job took (<code>man time</code> for more details). Having <code>nice -n 19</code> makes your long running job run at a lower priority. Your job will finish just as fast, but it will interfere less with more important processes (other users on the system).

If the job is going to take an hour or more, you probably want to run it like this:
<pre>time nice -n 19 whatever_command > output.txt 2>stderr.txt &</pre>
The <code> > output.txt</code> will have output go to the output.txt file, and <code> 2>stderr.txt</code> (no spaces is important) redirects error output to stderr.txt. The <code>&</code> will detach the process from your terminal so that it can continue running even if your terminal disconnects. You can login again and check on it by running <code>ps a</code> to see all your running processes (not just the ones started on the current login).

Alternatively to redirecting the output and detaching, you could use the <code>screen</code> command to run the command in a terminal that you can detach. You can lookup help on the screen command for how to do that (for example, [https://www.geeksforgeeks.org/screen-command-in-linux-with-examples/ here]).

Python Programming - Getting Started

2026-06-04T22:26:30Z

Jkinne: /* Installing Python on Your Personal Computer */

''This page is part of [[Programming and CS - Getting Started]]''

For a video explaining how to get started here, see https://www.youtube.com/watch?v=uLnhcCZS4-Y&t=424s

==Getting Started==
# '''Reading''' - start reading through at least one of the following before you start working on the programming problems.
## [https://www.w3schools.com/python/python_intro.asp w3schools Python] - interactive tutorial where you can try out code in the browser
## [https://www.learnpython.org/ Learn Python] - interactive tutorial where you can try out code in the browser
## [https://automatetheboringstuff.com/ Automate the Boring Stuff with Python] - suitable for people with very limited programming experience, this is the text that is being followed for our CS 151 course (as of 2019)
## [http://greenteapress.com/thinkpython2/html/index.html Think Python] - suitable for people with very limited programming experience, not very deep
## [https://learnxinyminutes.com/docs/python3/ LearnXinYminutes] - quick review once you are familiar with the basics
## [https://docs.python.org/3/tutorial/ Python.org tutorial] - good for those with programming experience already
# '''Get Python installed on your computer''' - download the latest Python3 version at https://www.python.org/downloads/. Having python3 installed on your computer allows you to debug much quicker.
# '''Work on solving problems''' that are listed below.
# If you are a current or incoming ISU student, or an ISU alumni, get help on what you are working on using the online unix lab. When asking about the hackerrank problems make sure to refer to them using the title hackerrank gives them, or give a link to the problem statement on hackerrank.
# '''Cheat sheets''' - keep a cheat sheet for yourself of python syntax, built-in functions, etc. See below on this page for our model cheat sheets.

==Running Python==
''See [https://youtu.be/ABmQ2QyYCLg this video] for a video demo of getting started running Python on the CS server and in IDLE.''

Once you have a computer with Python installed you are ready to try it out! You can use the CS systems (computers in our classrooms and labs, or connect to the CS server - see [[Linux - System Setup]]), or install Python on your personal computer. ''We recommend doing both.''

===Run in the Terminal===
On the CS server, other Linux systems, and macOS, you can run python using your terminal. If you run the command <code>python3</code> then you will see the python console. Here you can type one python line at a time to run, and the results are displayed. You can try these -
<pre>
2 + 3
3 * 4
10 ** 3
</pre>

We normally store our python code in text files and want to run the entire file. If you have a file with python code (let's say it is named myProgram.py) then you change directories to the directory that has your file, and then type <code>python3 myProgram.py</code>. You can have one terminal open where you are running your program with this command, and you can have another terminal open to edit the file (or use some other text editor).

===Run in IDLE===
Python comes with a graphical front-end called IDLE. You can run this program if you are in the CS labs by opening your terminal and then typing <code>idle3</code>. If you have python installed on your personal computer, then you can find IDLE in your list of programs (Start button on Windows, Finder then click Applications on macOS) or run idle3 from the terminal (if you are using Linux). If you are connecting to the CS server with a terminal program from home, you cannot run idle3 in the terminal because it is a graphical program - you will need to install it on your home computer to use it from home.

When you start IDLE, it shows you the Python3 console, where you can type your Python3 commands. Try typing in arithmetic expressions to make sure it is working. For example -
<pre>
2 + 3
3 * 4
10 ** 3
</pre>

===First Python Program===
We store python programs in text files. You can use the following as your first python program.
<pre>
print('Hello world.')
print('Hello again.')
print('Goodbye now.')
</pre>
If you are using IDLE you create and run a file by -
# Click on File and then New File.
# Copy/paste or type your code in the file window that comes up.
# Click File and Save As. Name the file myProgram.py and save it in whichever directory you want to keep your python programs.
# Click Run and then Run Module. In the python console window you should see that your program ran.
If you are connecting to the CS server with your terminal from your home computer, you can choose one of the following options.
* Create and edit the myProgram.py file with a text editor that works in the terminal - see [[Linux Terminal - Text Editors]]. Save the program and run the program with <code>python3 myProgram.py</code>. If you make changes, edit the program, and then run it again.
* Edit the program using a text editor on your home computer (for example, Kate or Atom, see [[Linux Terminal - Text Editors]]), transfer to the CS server using a file transfer program (see [[Linux - System Setup]]), change directories in your terminal to the directory that has the program, and then run the program in the terminal with <code>python3 myProgram.py</code>

===Python2 versus Python3===
If you want to use Python version 2 instead, you would use commands <code>python</code> and <code>idle</code> rather than <code>python3</code> and <code>idle3</code>. You should normally use Python3; the only reason to use Python2 is if you are using a package that is only available on Python2 (Python2 is not officially supported anymore, so this should be fairly rare).

==Installing Python on Your Personal Computer==
'''Windows and macOS''' Download and install from https://www.python.org/downloads/.

'''Linux''' On Linux python is probably already installed. If not do an internet search for your Linux distribution and "install python3" (i.e., search for - ubuntu install python).

'''Chromebook''' You should first get the Linux development environment enabled and then you can follow instructions for installing python3 for ubuntu. If python3 is not already installed, then running <code>sudo apt-get install python3</code> should install it.

==Lists of Problems==
===Programming Assignments 1===
[[Programming Assignments - Beginning 1]] - start with trying to solve these problems. Each requires a different feature of the Python programming language, so solve these problems as you read through one of the tutorials or links above. Note that the page includes a link to repl.it that contains solutions to most of the problems. If you do not have Python installed on your computer, you can try it out at [https://repl.it/ repl.it] - click the logo at the top, then click "+ new repl", select Python and Create Repl.

[[Programming Assignments - Beginning 2]] - another set of classic beginning programming exercises. Some of these will be more involved.

===HackerRank Problems===
Once you can do some basic Python programming it is time to have some of your work checked. Hackerrank is a site where you can create an account and work on problems that will be checked if they are correct. Note that hackerrank has very strict rules for accepting correct solutions. Start with the basic problems to get a feel for what hackerrank expects.

[[Python programming - hackerrank problems]]

===More Practice===
If you are able to do most of the problems on the pages linked above, then you don't need us to give you lists of problems any more. You can pick problems to work through on your own. Some suggested places with problems are as follows.
* [https://www.hackerrank.com/domains/algorithms Hackerrank - algorithms]
* [https://www.hackerrank.com/domains/data-structures Hackerrank - data structures]
* [http://cs.indstate.edu/acm/contests.html ACM Contest Problems]

==Cheat Sheets and Quizzes==
These cheat sheets have the highlights of some of the basic information to memorize when you are in your first year of Python programming. Note - each cheat sheet contains a sample quiz that might be used by your instructor.
* [[Cheat sheet - Python Operators, Expressions]]
* [[Cheat sheet - Python Keywords, Concepts, Functions]]

==Programming Errors and How to Fix Them==
* '''Syntax error''' - program is not a valid program, and normally python gives you an error message giving some indication of what the problem was.
** ''Debugging'' - read the error message! Normally you are given a line number where python got "confused" - sometimes that is where the problem is, but you may need to look just before that line (or just after). Common syntax errors in python...
** ''Mismatched'' () or [] or "" or '', for example <code>x = 2 * (3 + 4</code>
** ''Mis-capitalization or mis-spelling'', for example <code>Print('hello')</code>
** ''Improper indenting'', for example
** ''Data type'' problems - mixing up strings and numbers, for example <code>x = '3' + 4</code>
<pre>
for i in range(0, 10):
print(i)
</pre>
* '''Runtime error''' - program is a valid program but when you run it something goes wrong. Debugging is similar as for syntax errors and logical errors. For example...
<pre>
x = 1
print(x)
x = y + z
</pre>
* '''Logical error''' - program runs but does not do the right thing.
** ''Print debugging'' - One debugging method is to start printing things (values of variables) in your program starting at the beginning, run the program, make sure it is printing the values you expect, at some point you see a value you don't expect, and that tells you where to look in your code. You often are 100% sure what you have is right, but in the end there is some problem. So you have to ''check everything'', start at the very beginning of the program.
** ''Disable all'' - Another strategy is to disable almost all parts of your program (e.g., put it all in comments) until you get behavior that makes sense, and then start adding things back in (uncommenting), and eventually you'll add something in that doesn't behave the way you thought, and now you know where the problem is. Examples...
<pre>
x = 1
y = 2
z = 3
avg = x + y + z / 3
print(avg)
</pre>

Programming and CS - Getting Started

2026-06-04T22:25:07Z

Jkinne: /* Getting Started Pages */

We are developing Getting Started pages on the most important topics and skills that are used throughout our courses. These can be used by incoming undergraduate students to get a head start, incoming graduate students to review, or current students to refresh/remediate.

=Recommended Computer=
Much of what we do in CS courses can work in Windows, Mac OS, Linux, or Chrome. There will be an odd thing or two still that may not work in Chrome.

All other things being equal, getting a computer that is not "bottom of the barrel" would be good. Chromebooks in the $400+ range should generally work reasonably well. For Windows/Linux/Mac OS laptops, you should be looking for 8GB RAM bare minimum, preferred 16GB if possible, and avoid getting a laptop with an i3 or Celeron processor; this roughly corresponds to the $500+ price range. You can potentially get anything to work, but will have an easier time with a medium-range computer than a low-end system.

For laptops, we recommend getting at least a 3 year warranty (since they tend to break if you actually do transport them around). Also, we recommend getting an option that has a long battery life (rule of thumb - battery life will be half of its original rating after 1-2 years of regular daily use).

You should also have the ability to install programs on the system and have a normally reliable internet connection at home if possible.

If you have a particular system in mind for purchase that you would like an opinion on, please feel free to contact one of the CS faculty members.

University recommendations are listed [https://indstate.teamdynamix.com/TDClient/1851/Portal/KB/Article/71665/Student-Laptop-Minimum-Specifications here] and are similar to that described above.

=Getting Started Pages=
* [[CS accounts]]
* [[Linux and CS Systems - Getting Started]]
* [[Python Programming - Getting Started]]
* [[C Programming - Getting Started]]
* [[R Programming - Getting Started]]
* [[Algorithms and Data Structures - Getting Started]]
* [[Gitlab - Getting Started]]

=Practice Programming Contest Problems=
See [[Programming Practice]].

= Source Control =
It is a good idea to use source control when developing software, and is necessary when you are developing in a group or professionally. When working on assignments or course projects it is the best practice to use a private repository so other students cannot copy your work. Git is the industry standard for source control. Here are some resources to use to learn Git.

* https://try.github.io/
* https://learngitbranching.js.org/
* https://www.atlassian.com/git

Linux - System Setup

2026-06-04T22:24:38Z

Jkinne:

This page is meant to help you get your computer ready to connect to the CS server. This page is in a series on [[Programming and CS - Getting Started]].

=CS User Accounts=
Below we guide you through getting software setup on your computer. In order to connect to the CS server you will also need your CS user account; see [[CS accounts]].

=Your Personal Computer=

==Terminal Program==
A terminal program allows you to type commands to run programs and view files and folders on your computer, and allows you to do the same on a remote computer (i.e., the CS server) after you have connected to it.

Any current computer (Windows, Mac, Linux, Chrome) has a terminal program builtin. You just need to know how to start it. For each OS, here is what you need to do...

''Note - the first time you connect to the CS server with a terminal or file transfer program, you will be notified that the identity of cs.indstate.edu cannot be verified, an ECDSA key will be displayed, and you will be asked if you still want to connect. Type or click yes.''

* '''Windows''' - use the command prompt or powershell. To use the command prompt, click the Start button (at the bottom of your screen, in the middle or the left normally), start typing either "command" or "cmd" and you should see the option to run "Cmd.exe" or "Command Prompt". To use the PowerShell, do the same (click the Start button) but start typing "Power Shell".
* '''Mac OS''' - use the Terminal program. To use the built-in Terminal program, use Spotlight (hold down the command key and press spacebar) and type in "Terminal". You should see the Terminal program to click on. You can also start Terminal by clicking on the Apps icon in the Dock, and start typing "Terminal".
* '''Linux''' - this depends on the distribution you are using. Some use the name "terminal" for this program, and some use the name "shell". For Ubuntu Linux with the default user interface (Gnome), you can click on the button in the bottom left (or press the Start key on your keyboard) and then start typing "Terminal" or "Shell". You can also directly open the terminal by holding down the control-alt-t keys.
* '''Chrome''' - you need to first need to enable the "Linux development environment". Click on the G or Chrome button (in the bottom left), click on Settings, in the settings click on "About ChromeOS" on the bottom, and find the "Developers" section, then click on "Set up" for the Linux development environment, then click through the setup process (you can leave default values for everything). Once you have this complete, you can start the terminal by clicking on the G or Chrome button (in the bottom left), start typing "Terminal" and click on it. You will see a Linux section and click on the first entry to start the terminal.

==File Transfer Program==
You will eventually need to transfer files between your personal computer and the CS server.
* All current OSes include a text-based file transfer program as part of the terminal (see above for starting a terminal). Once you have a terminal open, you use the command "sftp" to start the secure ftp program.
* [https://filezilla-project.org/download.php?type=client FileZilla] is a graphical file transfer program that can be installed on any current OS.

''Note - the first time you connect to the CS server with a terminal or file transfer program, you may be notified that the identity of cs.indstate.edu cannot be verified, an ECDSA key will be displayed, and you will be asked if you still want to connect. Type or click yes.''

''Note - make sure to choose "sftp" as opposed to "ftp" when connecting. ftp is not encrypted and is disabled on the CS server (it will not work). sftp is encrypted and is what we use.''

==Text Editor==
Note that while you are using a terminal that is connected to the CS server you can use text-based editors - nano, emacs, vim, jove (see [[Linux Terminal - Text Editors]] for more on how to get started with these). You will eventually want to have a good text editor on your personal computer.

The following are four good options that are cross-platform - can be installed on Mac, Windows, Linux, and Chromebook. If you already use some other option (e.g., Visual Studio Code, Eclipse, Notepad++, or anything else that is used by programmers) feel free to keep using what you are already using. Note that Word is ''not'' a text editor - it does not store files in plain text, which is what is needed for programming.
* [https://code.visualstudio.com/ VS Code] - one of the most popular (as of 2026) with a lot of available add-ons.
* [https://www.vim.org/download.php Vim] - is normally already installed by default on Linux. Follow the instructions if on a different OS.
* [https://www.gnu.org/software/emacs/ Emacs] - used by Jeff Kinne, click your OS and follow the instructions. The graphical version uses all the same keyboard shortcuts as the text-based version that you can also use in the terminal. Note that for Chrome OS, you will first start a Terminal (see above) and then run the command <code>sudo apt-get install emacs</code> and answer Y when it asks if you want to install it.
* Other cross-platform editors that students and faculty have used - [https://kate-editor.org/get-it/ Kate],[https://www.sublimetext.com/ Submlime]
* You might also choose to use an Integrated Development Environment (IDE). Those have a bit of a learning curve, but if you have used one before you can use it for CS coursework as well.

When starting to learn a new text editor do an internet search for a tutorial to get you started; once you are comfortable with the basics do an internet search for a cheat sheet of keyboard shortcuts to help you remember them.

Linux - System Setup

2026-06-04T22:23:03Z

Jkinne: /* Text Editor */

Linux - System Setup

2026-06-04T22:15:42Z

Jkinne: /* Sample HW */

Linux - System Setup

2026-06-04T22:15:21Z

Jkinne: /* GUI Programs X-Windows */

This page is meant to help you get your computer ready to connect to the CS server.

=CS User Accounts=
Below we guide you through getting software setup on your computer. In order to connect to the CS server you will also need your CS user account; see [[CS accounts]].

=Your Personal Computer=

==Terminal Program==
A terminal program allows you to type commands to run programs and view files and folders on your computer, and allows you to do the same on a remote computer (i.e., the CS server) after you have connected to it.

Any current computer (Windows, Mac, Linux, Chrome) has a terminal program builtin. You just need to know how to start it. For each OS, here is what you need to do...

''Note - the first time you connect to the CS server with a terminal or file transfer program, you will be notified that the identity of cs.indstate.edu cannot be verified, an ECDSA key will be displayed, and you will be asked if you still want to connect. Type or click yes.''

* '''Windows''' - use the command prompt or powershell. To use the command prompt, click the Start button (at the bottom of your screen, in the middle or the left normally), start typing either "command" or "cmd" and you should see the option to run "Cmd.exe" or "Command Prompt". To use the PowerShell, do the same (click the Start button) but start typing "Power Shell".
* '''Mac OS''' - use the Terminal program. To use the built-in Terminal program, use Spotlight (hold down the command key and press spacebar) and type in "Terminal". You should see the Terminal program to click on. You can also start Terminal by clicking on the Apps icon in the Dock, and start typing "Terminal".
* '''Linux''' - this depends on the distribution you are using. Some use the name "terminal" for this program, and some use the name "shell". For Ubuntu Linux with the default user interface (Gnome), you can click on the button in the bottom left (or press the Start key on your keyboard) and then start typing "Terminal" or "Shell". You can also directly open the terminal by holding down the control-alt-t keys.
* '''Chrome''' - you need to first need to enable the "Linux development environment". Click on the G or Chrome button (in the bottom left), click on Settings, in the settings click on "About ChromeOS" on the bottom, and find the "Developers" section, then click on "Set up" for the Linux development environment, then click through the setup process (you can leave default values for everything). Once you have this complete, you can start the terminal by clicking on the G or Chrome button (in the bottom left), start typing "Terminal" and click on it. You will see a Linux section and click on the first entry to start the terminal.

==File Transfer Program==
You will eventually need to transfer files between your personal computer and the CS server.
* All current OSes include a text-based file transfer program as part of the terminal (see above for starting a terminal). Once you have a terminal open, you use the command "sftp" to start the secure ftp program.
* [https://filezilla-project.org/download.php?type=client FileZilla] is a graphical file transfer program that can be installed on any current OS.

''Note - the first time you connect to the CS server with a terminal or file transfer program, you may be notified that the identity of cs.indstate.edu cannot be verified, an ECDSA key will be displayed, and you will be asked if you still want to connect. Type or click yes.''

''Note - make sure to choose "sftp" as opposed to "ftp" when connecting. ftp is not encrypted and is disabled on the CS server (it will not work). sftp is encrypted and is what we use.''

==Text Editor==
Note that while you are using a terminal that is connected to the CS server you can use text-based editors - nano, emacs, vim, jove (see [[Linux Terminal - Text Editors]] for more on how to get started with these). You will eventually want to have a good text editor on your personal computer.

The following are four good options that are cross-platform - can be installed on Mac, Windows, Linux, and Chromebook. If you already use some other option (e.g., Visual Studio Code, Eclipse, Notepad++, or anything else that is used by programmers) feel free to keep using what you are already using. Note that Word is ''not'' a text editor - it does not store files in plain text, which is what is needed for programming.
* [https://code.visualstudio.com/ VS Code] - one of the most popular (as of 2026) with a lot of available add-ons.
* [https://www.vim.org/download.php Vim] - is normally already installed by default on Linux. Follow the instructions if on a different OS.
* [https://www.gnu.org/software/emacs/ Emacs] - used by Jeff Kinne, click your OS and follow the instructions. The graphical version uses all the same keyboard shortcuts as the text-based version that you can also use in the terminal. Note that for Chrome OS, you will first start a Terminal (see above) and then run the command <code>sudo apt-get install emacs</code> and answer Y when it asks if you want to install it.
* Other cross-platform editors that students and faculty have used - [https://kate-editor.org/get-it/ Kate],[https://www.sublimetext.com/ Submlime]
* You might also choose to use an Integrated Development Environment (IDE). Those have a bit of a learning curve, but if you have used one before you can use it for CS coursework as well.

When starting a new text editor do an internet search for a tutorial to get you started; once you are comfortable with the basics do an internet search for a cheat sheet of keyboard shortcuts to help you remember them.

=Sample HW=
The following might be used by your instructor as part of a HW assignment to verify you have your computer setup properly.

# Follow the steps above to setup your computer with a file transfer program, text editor, and terminal program. Make sure you are able to use the file transfer program and terminal programs to connect to your CS class account on the CS server.
# Make sure you can open the text editor. Create a text file aboutMySystem.txt and put the following information.
## Your name:
## Your CS class account:
## Operating System:
## Text editor you are using:
## File transfer program:
## Did you have any difficulties in getting the programs setup? If yes, explain.
# Create the following screen shots demonstrating that you have the programs installed on your system properly. Note - you can ask the internet how to take a screenshot (e.g., type in - how to screenshot on chromebook). For each screenshot, make the screenshot of your whole screen (so I can see which OS you are running on and the program open and connected).
## textEditor.jpg - a screenshot that shows you editing the aboutMySystem.txt file with your text editor.
## fileTransfer.jpg - a screenshot that shows you using the file transfer program to connect to the CS server with your CS class account.
## terminal.jpg - a screenshot that shows you with the terminal program open and connected to the CS server with your CS class account.
# Use the file transfer program to connect to the CS server with your CS class account.
## While connected, create a new directory in your CS class account on the CS server. Name the new directory SystemSetup.
## Transfer the files you just created (aboutMySystem.txt, textEditor.jpg, fileTransfer.jpg, terminal.jpg) into the SystemSetup directory in your CS class account on the server.

Linux - System Setup

2026-06-04T22:14:32Z

Jkinne:

This page is meant to help you get your computer ready to connect to the CS server.

=CS User Accounts=
Below we guide you through getting software setup on your computer. In order to connect to the CS server you will also need your CS user account; see [[CS accounts]].

=Your Personal Computer=

==Terminal Program==
A terminal program allows you to type commands to run programs and view files and folders on your computer, and allows you to do the same on a remote computer (i.e., the CS server) after you have connected to it.

Any current computer (Windows, Mac, Linux, Chrome) has a terminal program builtin. You just need to know how to start it. For each OS, here is what you need to do...

''Note - the first time you connect to the CS server with a terminal or file transfer program, you will be notified that the identity of cs.indstate.edu cannot be verified, an ECDSA key will be displayed, and you will be asked if you still want to connect. Type or click yes.''

* '''Windows''' - use the command prompt or powershell. To use the command prompt, click the Start button (at the bottom of your screen, in the middle or the left normally), start typing either "command" or "cmd" and you should see the option to run "Cmd.exe" or "Command Prompt". To use the PowerShell, do the same (click the Start button) but start typing "Power Shell".
* '''Mac OS''' - use the Terminal program. To use the built-in Terminal program, use Spotlight (hold down the command key and press spacebar) and type in "Terminal". You should see the Terminal program to click on. You can also start Terminal by clicking on the Apps icon in the Dock, and start typing "Terminal".
* '''Linux''' - this depends on the distribution you are using. Some use the name "terminal" for this program, and some use the name "shell". For Ubuntu Linux with the default user interface (Gnome), you can click on the button in the bottom left (or press the Start key on your keyboard) and then start typing "Terminal" or "Shell". You can also directly open the terminal by holding down the control-alt-t keys.
* '''Chrome''' - you need to first need to enable the "Linux development environment". Click on the G or Chrome button (in the bottom left), click on Settings, in the settings click on "About ChromeOS" on the bottom, and find the "Developers" section, then click on "Set up" for the Linux development environment, then click through the setup process (you can leave default values for everything). Once you have this complete, you can start the terminal by clicking on the G or Chrome button (in the bottom left), start typing "Terminal" and click on it. You will see a Linux section and click on the first entry to start the terminal.

==File Transfer Program==
You will eventually need to transfer files between your personal computer and the CS server.
* All current OSes include a text-based file transfer program as part of the terminal (see above for starting a terminal). Once you have a terminal open, you use the command "sftp" to start the secure ftp program.
* [https://filezilla-project.org/download.php?type=client FileZilla] is a graphical file transfer program that can be installed on any current OS.

''Note - the first time you connect to the CS server with a terminal or file transfer program, you may be notified that the identity of cs.indstate.edu cannot be verified, an ECDSA key will be displayed, and you will be asked if you still want to connect. Type or click yes.''

''Note - make sure to choose "sftp" as opposed to "ftp" when connecting. ftp is not encrypted and is disabled on the CS server (it will not work). sftp is encrypted and is what we use.''

==Text Editor==
Note that while you are using a terminal that is connected to the CS server you can use text-based editors - nano, emacs, vim, jove (see [[Linux Terminal - Text Editors]] for more on how to get started with these). You will eventually want to have a good text editor on your personal computer.

The following are four good options that are cross-platform - can be installed on Mac, Windows, Linux, and Chromebook. If you already use some other option (e.g., Visual Studio Code, Eclipse, Notepad++, or anything else that is used by programmers) feel free to keep using what you are already using. Note that Word is ''not'' a text editor - it does not store files in plain text, which is what is needed for programming.
* [https://code.visualstudio.com/ VS Code] - one of the most popular (as of 2026) with a lot of available add-ons.
* [https://www.vim.org/download.php Vim] - is normally already installed by default on Linux. Follow the instructions if on a different OS.
* [https://www.gnu.org/software/emacs/ Emacs] - used by Jeff Kinne, click your OS and follow the instructions. The graphical version uses all the same keyboard shortcuts as the text-based version that you can also use in the terminal. Note that for Chrome OS, you will first start a Terminal (see above) and then run the command <code>sudo apt-get install emacs</code> and answer Y when it asks if you want to install it.
* Other cross-platform editors that students and faculty have used - [https://kate-editor.org/get-it/ Kate],[https://www.sublimetext.com/ Submlime]
* You might also choose to use an Integrated Development Environment (IDE). Those have a bit of a learning curve, but if you have used one before you can use it for CS coursework as well.

When starting a new text editor do an internet search for a tutorial to get you started; once you are comfortable with the basics do an internet search for a cheat sheet of keyboard shortcuts to help you remember them.

==GUI Programs X-Windows==
To run a GUI program while connected to the server, you will need to be running an X11 client on your local computer and have it running when connect to the server. Some further details depending on your operating system.
* MacOS - install [https://www.xquartz.org/ XQuartz] and run it.
* Windows - install [https://x.cygwin.com/ Cygwin/X] ([https://x.cygwin.com/docs/ug/setup.html#setup-cygwin-x-installing installation]) and run it. Or, euse the [https://learn.microsoft.com/en-us/windows/wsl/install Windows Subsystem for Linux] (WSL).
* Linux - do not need to install anything extra.

Once you have your X11 client installed, open it, and then connect to the CS server using the -Y switch in your ssh command: <pre>ssh -Y username@cs.indstate.edu</pre>

To verify everything is working try running in your terminal xcalc: <pre>xcalc</pre>

=Sample HW=
The following might be used by your instructor as part of a HW assignment to verify you have your computer setup properly.

# Follow the steps above to setup your computer with a file transfer program, text editor, and terminal program. Make sure you are able to use the file transfer program and terminal programs to connect to your CS class account on the CS server.
# Make sure you can open the text editor. Create a text file aboutMySystem.txt and put the following information.
## Your name:
## Your CS class account:
## Operating System:
## Text editor you are using:
## File transfer program:
## Did you have any difficulties in getting the programs setup? If yes, explain.
# Create the following screen shots demonstrating that you have the programs installed on your system properly. Note - you can ask the internet how to take a screenshot (e.g., type in - how to screenshot on chromebook). For each screenshot, make the screenshot of your whole screen (so I can see which OS you are running on and the program open and connected).
## textEditor.jpg - a screenshot that shows you editing the aboutMySystem.txt file with your text editor.
## fileTransfer.jpg - a screenshot that shows you using the file transfer program to connect to the CS server with your CS class account.
## terminal.jpg - a screenshot that shows you with the terminal program open and connected to the CS server with your CS class account.
# Use the file transfer program to connect to the CS server with your CS class account.
## While connected, create a new directory in your CS class account on the CS server. Name the new directory SystemSetup.
## Transfer the files you just created (aboutMySystem.txt, textEditor.jpg, fileTransfer.jpg, terminal.jpg) into the SystemSetup directory in your CS class account on the server.

Linux - System Setup

2026-06-04T22:14:22Z

Jkinne: /* Backing up Files - Rsync */

Linux - System Setup

2026-06-04T22:14:14Z

Jkinne: /* Compilers/Interpreters */

Linux - System Setup

2026-06-04T22:14:01Z

Jkinne: /* Other OS-Specific Notes */

Linux - System Setup

2026-06-04T22:13:42Z

Jkinne: /* Chromebook */

Linux - System Setup

2026-06-04T22:13:27Z

Jkinne: /* Installing for Linux */

This page is meant to help you get your computer ready to connect to the CS server.

''Note - this page needs updating, was last updated in 2020.''

=CS User Accounts=
Below we guide you through getting software setup on your computer. In order to connect to the CS server you will also need your CS user account; see [[CS accounts]].

=Your Personal Computer=

==Terminal Program==
A terminal program allows you to type commands to run programs and view files and folders on your computer, and allows you to do the same on a remote computer (i.e., the CS server) after you have connected to it.

Any current computer (Windows, Mac, Linux, Chrome) has a terminal program builtin. You just need to know how to start it. For each OS, here is what you need to do...

''Note - the first time you connect to the CS server with a terminal or file transfer program, you will be notified that the identity of cs.indstate.edu cannot be verified, an ECDSA key will be displayed, and you will be asked if you still want to connect. Type or click yes.''

* '''Windows''' - use the command prompt or powershell. To use the command prompt, click the Start button (at the bottom of your screen, in the middle or the left normally), start typing either "command" or "cmd" and you should see the option to run "Cmd.exe" or "Command Prompt". To use the PowerShell, do the same (click the Start button) but start typing "Power Shell".
* '''Mac OS''' - use the Terminal program. To use the built-in Terminal program, use Spotlight (hold down the command key and press spacebar) and type in "Terminal". You should see the Terminal program to click on. You can also start Terminal by clicking on the Apps icon in the Dock, and start typing "Terminal".
* '''Linux''' - this depends on the distribution you are using. Some use the name "terminal" for this program, and some use the name "shell". For Ubuntu Linux with the default user interface (Gnome), you can click on the button in the bottom left (or press the Start key on your keyboard) and then start typing "Terminal" or "Shell". You can also directly open the terminal by holding down the control-alt-t keys.
* '''Chrome''' - you need to first need to enable the "Linux development environment". Click on the G or Chrome button (in the bottom left), click on Settings, in the settings click on "About ChromeOS" on the bottom, and find the "Developers" section, then click on "Set up" for the Linux development environment, then click through the setup process (you can leave default values for everything). Once you have this complete, you can start the terminal by clicking on the G or Chrome button (in the bottom left), start typing "Terminal" and click on it. You will see a Linux section and click on the first entry to start the terminal.

==File Transfer Program==
You will eventually need to transfer files between your personal computer and the CS server.
* All current OSes include a text-based file transfer program as part of the terminal (see above for starting a terminal). Once you have a terminal open, you use the command "sftp" to start the secure ftp program.
* [https://filezilla-project.org/download.php?type=client FileZilla] is a graphical file transfer program that can be installed on any current OS.

''Note - the first time you connect to the CS server with a terminal or file transfer program, you may be notified that the identity of cs.indstate.edu cannot be verified, an ECDSA key will be displayed, and you will be asked if you still want to connect. Type or click yes.''

''Note - make sure to choose "sftp" as opposed to "ftp" when connecting. ftp is not encrypted and is disabled on the CS server (it will not work). sftp is encrypted and is what we use.''

==Text Editor==
Note that while you are using a terminal that is connected to the CS server you can use text-based editors - nano, emacs, vim, jove (see [[Linux Terminal - Text Editors]] for more on how to get started with these). You will eventually want to have a good text editor on your personal computer.

The following are four good options that are cross-platform - can be installed on Mac, Windows, Linux, and Chromebook. If you already use some other option (e.g., Visual Studio Code, Eclipse, Notepad++, or anything else that is used by programmers) feel free to keep using what you are already using. Note that Word is ''not'' a text editor - it does not store files in plain text, which is what is needed for programming.
* [https://code.visualstudio.com/ VS Code] - one of the most popular (as of 2026) with a lot of available add-ons.
* [https://www.vim.org/download.php Vim] - is normally already installed by default on Linux. Follow the instructions if on a different OS.
* [https://www.gnu.org/software/emacs/ Emacs] - used by Jeff Kinne, click your OS and follow the instructions. The graphical version uses all the same keyboard shortcuts as the text-based version that you can also use in the terminal. Note that for Chrome OS, you will first start a Terminal (see above) and then run the command <code>sudo apt-get install emacs</code> and answer Y when it asks if you want to install it.
* Other cross-platform editors that students and faculty have used - [https://kate-editor.org/get-it/ Kate],[https://www.sublimetext.com/ Submlime]
* You might also choose to use an Integrated Development Environment (IDE). Those have a bit of a learning curve, but if you have used one before you can use it for CS coursework as well.

When starting a new text editor do an internet search for a tutorial to get you started; once you are comfortable with the basics do an internet search for a cheat sheet of keyboard shortcuts to help you remember them.

==Chromebook==
On Chromebook you can choose whether to install apps and do all of your work connected to the CS server, or install Linux on your Chromebook and then use the instructions above on installing the programs.

'''Using apps''' - Install the following apps.
* ''Text Editor'' - [https://chrome.google.com/webstore/detail/text/mmfbcljfglbokpmkimbfghdkjmjhdgbg?hl=en Text]
* ''Terminal Program'' - [https://chrome.google.com/webstore/detail/secure-shell-app/pnhechapfaindjhompbnflcldabbghjo Secure Shell]
* ''File Transfer Program'' - use the builtin Files app along with the Secure Shell app, configure as follows.
** Open the Files app.
** Click on the triple-dots in the upper right of the Files app, click Add new service, click Secure Shell App.
** On the Secure Shell App screen that comes up, enter your login information with cs.indstate.edu as the server and 22 as the port. Then click SFTP Mount.
** Go back to the Files app and you will see LOGIN@cs.indstate.edu:22 as an option on the left.

'''Linux (Beta) on Chromebook'''
* Not all chromebooks allow installation of Linux (Beta). If this works then you will have Linux installed on your Chromebook and will be able to use any of the commands that you use on the CS server.
* Follow [https://support.google.com/chromebook/answer/9145439?hl=en instructions from google].
* Note - installation could take a very long time (e.g., an hour or more). If installation fails you may need to select Remove Linux Beta and try again.
* Once installation is complete you open a terminal using the Terminal app. To install the programs mentioned on this page follow the instructions above for Linux (using the APT package manager commands).
* After the programs are installed you can open them by typing the command in the Terminal or by opening them as apps.

'''Copy/paste''' - in either the Secure Shell app or the Terminal app, copy/paste as follows. To copy, simply select text with the mouse and it will be copied to the clipboard. To paste, do a triple-click (three finger click).

==Other OS-Specific Notes==
If you are using Windows and have Putty installed as your terminal program, it installs a text-based file transfer program as well - psftp - which you should be able to find in your list of programs.

If you are using MacOS or Linux, a text-based file transfer program - sftp - is normally installed by default.

In either case, new users often prefer to use graphical file transfer programs (those mentioned above).

For the text-based sftp programs, the basic commands you will need.
* ls, cd, pwd - show you the files on the server and change directories on the server.
* lls, lcd, lpwd - show you the files on your computer and change directories on your computer.
* put - send a file from your computer to the server (from your current directory on your computer, to the current directory on the server).
* get - download a file from the server to your computer
* quit

==Compilers/Interpreters==

===Python===

===C/C++===

==Backing up Files - Rsync==

==GUI Programs X-Windows==
To run a GUI program while connected to the server, you will need to be running an X11 client on your local computer and have it running when connect to the server. Some further details depending on your operating system.
* MacOS - install [https://www.xquartz.org/ XQuartz] and run it.
* Windows - install [https://x.cygwin.com/ Cygwin/X] ([https://x.cygwin.com/docs/ug/setup.html#setup-cygwin-x-installing installation]) and run it. Or, euse the [https://learn.microsoft.com/en-us/windows/wsl/install Windows Subsystem for Linux] (WSL).
* Linux - do not need to install anything extra.

Once you have your X11 client installed, open it, and then connect to the CS server using the -Y switch in your ssh command: <pre>ssh -Y username@cs.indstate.edu</pre>

To verify everything is working try running in your terminal xcalc: <pre>xcalc</pre>

=Sample HW=
The following might be used by your instructor as part of a HW assignment to verify you have your computer setup properly.

# Follow the steps above to setup your computer with a file transfer program, text editor, and terminal program. Make sure you are able to use the file transfer program and terminal programs to connect to your CS class account on the CS server.
# Make sure you can open the text editor. Create a text file aboutMySystem.txt and put the following information.
## Your name:
## Your CS class account:
## Operating System:
## Text editor you are using:
## File transfer program:
## Did you have any difficulties in getting the programs setup? If yes, explain.
# Create the following screen shots demonstrating that you have the programs installed on your system properly. Note - you can ask the internet how to take a screenshot (e.g., type in - how to screenshot on chromebook). For each screenshot, make the screenshot of your whole screen (so I can see which OS you are running on and the program open and connected).
## textEditor.jpg - a screenshot that shows you editing the aboutMySystem.txt file with your text editor.
## fileTransfer.jpg - a screenshot that shows you using the file transfer program to connect to the CS server with your CS class account.
## terminal.jpg - a screenshot that shows you with the terminal program open and connected to the CS server with your CS class account.
# Use the file transfer program to connect to the CS server with your CS class account.
## While connected, create a new directory in your CS class account on the CS server. Name the new directory SystemSetup.
## Transfer the files you just created (aboutMySystem.txt, textEditor.jpg, fileTransfer.jpg, terminal.jpg) into the SystemSetup directory in your CS class account on the server.

Linux - System Setup

2026-06-04T21:50:00Z

Jkinne: /* Text Editor */

This page is meant to help you get your computer ready to connect to the CS server.

''Note - this page needs updating, was last updated in 2020.''

=CS User Accounts=
Below we guide you through getting software setup on your computer. In order to connect to the CS server you will also need your CS user account; see [[CS accounts]].

=Your Personal Computer=

==Terminal Program==
A terminal program allows you to type commands to run programs and view files and folders on your computer, and allows you to do the same on a remote computer (i.e., the CS server) after you have connected to it.

Any current computer (Windows, Mac, Linux, Chrome) has a terminal program builtin. You just need to know how to start it. For each OS, here is what you need to do...

''Note - the first time you connect to the CS server with a terminal or file transfer program, you will be notified that the identity of cs.indstate.edu cannot be verified, an ECDSA key will be displayed, and you will be asked if you still want to connect. Type or click yes.''

* '''Windows''' - use the command prompt or powershell. To use the command prompt, click the Start button (at the bottom of your screen, in the middle or the left normally), start typing either "command" or "cmd" and you should see the option to run "Cmd.exe" or "Command Prompt". To use the PowerShell, do the same (click the Start button) but start typing "Power Shell".
* '''Mac OS''' - use the Terminal program. To use the built-in Terminal program, use Spotlight (hold down the command key and press spacebar) and type in "Terminal". You should see the Terminal program to click on. You can also start Terminal by clicking on the Apps icon in the Dock, and start typing "Terminal".
* '''Linux''' - this depends on the distribution you are using. Some use the name "terminal" for this program, and some use the name "shell". For Ubuntu Linux with the default user interface (Gnome), you can click on the button in the bottom left (or press the Start key on your keyboard) and then start typing "Terminal" or "Shell". You can also directly open the terminal by holding down the control-alt-t keys.
* '''Chrome''' - you need to first need to enable the "Linux development environment". Click on the G or Chrome button (in the bottom left), click on Settings, in the settings click on "About ChromeOS" on the bottom, and find the "Developers" section, then click on "Set up" for the Linux development environment, then click through the setup process (you can leave default values for everything). Once you have this complete, you can start the terminal by clicking on the G or Chrome button (in the bottom left), start typing "Terminal" and click on it. You will see a Linux section and click on the first entry to start the terminal.

==File Transfer Program==
You will eventually need to transfer files between your personal computer and the CS server.
* All current OSes include a text-based file transfer program as part of the terminal (see above for starting a terminal). Once you have a terminal open, you use the command "sftp" to start the secure ftp program.
* [https://filezilla-project.org/download.php?type=client FileZilla] is a graphical file transfer program that can be installed on any current OS.

''Note - the first time you connect to the CS server with a terminal or file transfer program, you may be notified that the identity of cs.indstate.edu cannot be verified, an ECDSA key will be displayed, and you will be asked if you still want to connect. Type or click yes.''

''Note - make sure to choose "sftp" as opposed to "ftp" when connecting. ftp is not encrypted and is disabled on the CS server (it will not work). sftp is encrypted and is what we use.''

==Text Editor==
Note that while you are using a terminal that is connected to the CS server you can use text-based editors - nano, emacs, vim, jove (see [[Linux Terminal - Text Editors]] for more on how to get started with these). You will eventually want to have a good text editor on your personal computer.

The following are four good options that are cross-platform - can be installed on Mac, Windows, Linux, and Chromebook. If you already use some other option (e.g., Visual Studio Code, Eclipse, Notepad++, or anything else that is used by programmers) feel free to keep using what you are already using. Note that Word is ''not'' a text editor - it does not store files in plain text, which is what is needed for programming.
* [https://code.visualstudio.com/ VS Code] - one of the most popular (as of 2026) with a lot of available add-ons.
* [https://www.vim.org/download.php Vim] - is normally already installed by default on Linux. Follow the instructions if on a different OS.
* [https://www.gnu.org/software/emacs/ Emacs] - used by Jeff Kinne, click your OS and follow the instructions. The graphical version uses all the same keyboard shortcuts as the text-based version that you can also use in the terminal. Note that for Chrome OS, you will first start a Terminal (see above) and then run the command <code>sudo apt-get install emacs</code> and answer Y when it asks if you want to install it.
* Other cross-platform editors that students and faculty have used - [https://kate-editor.org/get-it/ Kate],[https://www.sublimetext.com/ Submlime]
* You might also choose to use an Integrated Development Environment (IDE). Those have a bit of a learning curve, but if you have used one before you can use it for CS coursework as well.

When starting a new text editor do an internet search for a tutorial to get you started; once you are comfortable with the basics do an internet search for a cheat sheet of keyboard shortcuts to help you remember them.

==Installing for Linux==
Most Linux distributions have their own package management systems, with the programs mentioned on this page being installable via the package management system. There often is a graphical interface to the package management system, and there is normally a text-based interface - you type commands on the terminal to install packages.

''Debian'', ''Ubuntu'', and related Linux distributions use the APT package manager, and you can install the programs mentioned on this page by entering the following commands in the terminal. Note that you will likely be asked in the terminal whether you want to install the package, you need to type Y and press enter.
<pre>
sudo apt update # makes sure APT has the latest information about packages available
sudo apt install emacs
sudo apt install kate
sudo apt install gftp
sudo apt install vim
# Note - installing atom requires adding the repository where atom is kept
wget -qO - https://packagecloud.io/AtomEditor/atom/gpgkey | sudo apt-key add -
sudo sh -c 'echo "deb [arch=amd64] https://packagecloud.io/AtomEditor/atom/any/ any main" > /etc/apt/sources.list.d/atom.list'
sudo apt update
sudo apt install atom
</pre>
''Other Linux distributions'' use different package managers. If you use a different Linux distribution and are unable to figure out how to install packages you can ask your instructor, your advisor, or the CS system administrator.

After installing the above programs you can open them from the terminal (i.e., to open filezilla you type the command, filezilla). The programs may also appear in the graphical menu of programs.

==Chromebook==
On Chromebook you can choose whether to install apps and do all of your work connected to the CS server, or install Linux on your Chromebook and then use the instructions above on installing the programs.

'''Using apps''' - Install the following apps.
* ''Text Editor'' - [https://chrome.google.com/webstore/detail/text/mmfbcljfglbokpmkimbfghdkjmjhdgbg?hl=en Text]
* ''Terminal Program'' - [https://chrome.google.com/webstore/detail/secure-shell-app/pnhechapfaindjhompbnflcldabbghjo Secure Shell]
* ''File Transfer Program'' - use the builtin Files app along with the Secure Shell app, configure as follows.
** Open the Files app.
** Click on the triple-dots in the upper right of the Files app, click Add new service, click Secure Shell App.
** On the Secure Shell App screen that comes up, enter your login information with cs.indstate.edu as the server and 22 as the port. Then click SFTP Mount.
** Go back to the Files app and you will see LOGIN@cs.indstate.edu:22 as an option on the left.

'''Linux (Beta) on Chromebook'''
* Not all chromebooks allow installation of Linux (Beta). If this works then you will have Linux installed on your Chromebook and will be able to use any of the commands that you use on the CS server.
* Follow [https://support.google.com/chromebook/answer/9145439?hl=en instructions from google].
* Note - installation could take a very long time (e.g., an hour or more). If installation fails you may need to select Remove Linux Beta and try again.
* Once installation is complete you open a terminal using the Terminal app. To install the programs mentioned on this page follow the instructions above for Linux (using the APT package manager commands).
* After the programs are installed you can open them by typing the command in the Terminal or by opening them as apps.

'''Copy/paste''' - in either the Secure Shell app or the Terminal app, copy/paste as follows. To copy, simply select text with the mouse and it will be copied to the clipboard. To paste, do a triple-click (three finger click).

==Other OS-Specific Notes==
If you are using Windows and have Putty installed as your terminal program, it installs a text-based file transfer program as well - psftp - which you should be able to find in your list of programs.

If you are using MacOS or Linux, a text-based file transfer program - sftp - is normally installed by default.

In either case, new users often prefer to use graphical file transfer programs (those mentioned above).

For the text-based sftp programs, the basic commands you will need.
* ls, cd, pwd - show you the files on the server and change directories on the server.
* lls, lcd, lpwd - show you the files on your computer and change directories on your computer.
* put - send a file from your computer to the server (from your current directory on your computer, to the current directory on the server).
* get - download a file from the server to your computer
* quit

==Compilers/Interpreters==

===Python===

===C/C++===

==Backing up Files - Rsync==

==GUI Programs X-Windows==
To run a GUI program while connected to the server, you will need to be running an X11 client on your local computer and have it running when connect to the server. Some further details depending on your operating system.
* MacOS - install [https://www.xquartz.org/ XQuartz] and run it.
* Windows - install [https://x.cygwin.com/ Cygwin/X] ([https://x.cygwin.com/docs/ug/setup.html#setup-cygwin-x-installing installation]) and run it. Or, euse the [https://learn.microsoft.com/en-us/windows/wsl/install Windows Subsystem for Linux] (WSL).
* Linux - do not need to install anything extra.

Once you have your X11 client installed, open it, and then connect to the CS server using the -Y switch in your ssh command: <pre>ssh -Y username@cs.indstate.edu</pre>

To verify everything is working try running in your terminal xcalc: <pre>xcalc</pre>

=Sample HW=
The following might be used by your instructor as part of a HW assignment to verify you have your computer setup properly.

# Follow the steps above to setup your computer with a file transfer program, text editor, and terminal program. Make sure you are able to use the file transfer program and terminal programs to connect to your CS class account on the CS server.
# Make sure you can open the text editor. Create a text file aboutMySystem.txt and put the following information.
## Your name:
## Your CS class account:
## Operating System:
## Text editor you are using:
## File transfer program:
## Did you have any difficulties in getting the programs setup? If yes, explain.
# Create the following screen shots demonstrating that you have the programs installed on your system properly. Note - you can ask the internet how to take a screenshot (e.g., type in - how to screenshot on chromebook). For each screenshot, make the screenshot of your whole screen (so I can see which OS you are running on and the program open and connected).
## textEditor.jpg - a screenshot that shows you editing the aboutMySystem.txt file with your text editor.
## fileTransfer.jpg - a screenshot that shows you using the file transfer program to connect to the CS server with your CS class account.
## terminal.jpg - a screenshot that shows you with the terminal program open and connected to the CS server with your CS class account.
# Use the file transfer program to connect to the CS server with your CS class account.
## While connected, create a new directory in your CS class account on the CS server. Name the new directory SystemSetup.
## Transfer the files you just created (aboutMySystem.txt, textEditor.jpg, fileTransfer.jpg, terminal.jpg) into the SystemSetup directory in your CS class account on the server.

Linux - System Setup

2026-06-04T21:40:06Z

Jkinne: /* Text Editor */

This page is meant to help you get your computer ready to connect to the CS server.

''Note - this page needs updating, was last updated in 2020.''

=CS User Accounts=
Below we guide you through getting software setup on your computer. In order to connect to the CS server you will also need your CS user account; see [[CS accounts]].

=Your Personal Computer=

==Terminal Program==
A terminal program allows you to type commands to run programs and view files and folders on your computer, and allows you to do the same on a remote computer (i.e., the CS server) after you have connected to it.

Any current computer (Windows, Mac, Linux, Chrome) has a terminal program builtin. You just need to know how to start it. For each OS, here is what you need to do...

''Note - the first time you connect to the CS server with a terminal or file transfer program, you will be notified that the identity of cs.indstate.edu cannot be verified, an ECDSA key will be displayed, and you will be asked if you still want to connect. Type or click yes.''

* '''Windows''' - use the command prompt or powershell. To use the command prompt, click the Start button (at the bottom of your screen, in the middle or the left normally), start typing either "command" or "cmd" and you should see the option to run "Cmd.exe" or "Command Prompt". To use the PowerShell, do the same (click the Start button) but start typing "Power Shell".
* '''Mac OS''' - use the Terminal program. To use the built-in Terminal program, use Spotlight (hold down the command key and press spacebar) and type in "Terminal". You should see the Terminal program to click on. You can also start Terminal by clicking on the Apps icon in the Dock, and start typing "Terminal".
* '''Linux''' - this depends on the distribution you are using. Some use the name "terminal" for this program, and some use the name "shell". For Ubuntu Linux with the default user interface (Gnome), you can click on the button in the bottom left (or press the Start key on your keyboard) and then start typing "Terminal" or "Shell". You can also directly open the terminal by holding down the control-alt-t keys.
* '''Chrome''' - you need to first need to enable the "Linux development environment". Click on the G or Chrome button (in the bottom left), click on Settings, in the settings click on "About ChromeOS" on the bottom, and find the "Developers" section, then click on "Set up" for the Linux development environment, then click through the setup process (you can leave default values for everything). Once you have this complete, you can start the terminal by clicking on the G or Chrome button (in the bottom left), start typing "Terminal" and click on it. You will see a Linux section and click on the first entry to start the terminal.

==File Transfer Program==
You will eventually need to transfer files between your personal computer and the CS server.
* All current OSes include a text-based file transfer program as part of the terminal (see above for starting a terminal). Once you have a terminal open, you use the command "sftp" to start the secure ftp program.
* [https://filezilla-project.org/download.php?type=client FileZilla] is a graphical file transfer program that can be installed on any current OS.

''Note - the first time you connect to the CS server with a terminal or file transfer program, you may be notified that the identity of cs.indstate.edu cannot be verified, an ECDSA key will be displayed, and you will be asked if you still want to connect. Type or click yes.''

''Note - make sure to choose "sftp" as opposed to "ftp" when connecting. ftp is not encrypted and is disabled on the CS server (it will not work). sftp is encrypted and is what we use.''

==Text Editor==
Note that while you are using a terminal that is connected to the CS server you can use text-based editors - nano, emacs, vim, jove (see [[Linux Terminal - Text Editors]] for more on how to get started with these). You will eventually want to have a good text editor on your personal computer.

The following are four good options that are cross-platform - can be installed on Mac, Windows, Linux, and Chromebook. If you already use some other option (e.g., Visual Studio Code, Eclipse, Notepad++, or anything else that is used by programmers) feel free to keep using what you are already using. Note that Word is ''not'' a text editor - it does not store files in plain text, which is what is needed for programming.
* [https://kate-editor.org/get-it/ Kate] - make sure to download the "release" installer.
* [https://www.sublimetext.com/ Submlime] - used by Luke May.
* [https://www.gnu.org/software/emacs/ Emacs] - used by Jeff Kinne, click "GNU/Linux", "Windows", or "MacOS" depending on your OS and follow the instructions.
** For Windows, download is from https://ftp.gnu.org/gnu/emacs/windows/, choose the latest emacs-## folder to click on, then download the zip file at the bottom that ends in "-x86_64.zip", extract the zip to somewhere to keep the program (e.g., C:\Program Files\), then run the file runemacs.exe in the bin directory.
** For macOS, the easiest install is from https://emacsformacosx.com/
* [https://www.vim.org/download.php Vim] - used by Geoff Exoo. For Windows, download and run the "self-installing executable". For macOS download and run MacVim.dmg from https://github.com/macvim-dev/macvim/releases/latest
* [https://code.visualstudio.com/ VS Code]
* ne (nice editor)

When starting a new text editor do an internet search for a tutorial to get you started; once you are comfortable with the basics do an internet search for a cheat sheet of keyboard shortcuts to help you remember them.

==Installing for Linux==
Most Linux distributions have their own package management systems, with the programs mentioned on this page being installable via the package management system. There often is a graphical interface to the package management system, and there is normally a text-based interface - you type commands on the terminal to install packages.

''Debian'', ''Ubuntu'', and related Linux distributions use the APT package manager, and you can install the programs mentioned on this page by entering the following commands in the terminal. Note that you will likely be asked in the terminal whether you want to install the package, you need to type Y and press enter.
<pre>
sudo apt update # makes sure APT has the latest information about packages available
sudo apt install emacs
sudo apt install kate
sudo apt install gftp
sudo apt install vim
# Note - installing atom requires adding the repository where atom is kept
wget -qO - https://packagecloud.io/AtomEditor/atom/gpgkey | sudo apt-key add -
sudo sh -c 'echo "deb [arch=amd64] https://packagecloud.io/AtomEditor/atom/any/ any main" > /etc/apt/sources.list.d/atom.list'
sudo apt update
sudo apt install atom
</pre>
''Other Linux distributions'' use different package managers. If you use a different Linux distribution and are unable to figure out how to install packages you can ask your instructor, your advisor, or the CS system administrator.

After installing the above programs you can open them from the terminal (i.e., to open filezilla you type the command, filezilla). The programs may also appear in the graphical menu of programs.

==Chromebook==
On Chromebook you can choose whether to install apps and do all of your work connected to the CS server, or install Linux on your Chromebook and then use the instructions above on installing the programs.

'''Using apps''' - Install the following apps.
* ''Text Editor'' - [https://chrome.google.com/webstore/detail/text/mmfbcljfglbokpmkimbfghdkjmjhdgbg?hl=en Text]
* ''Terminal Program'' - [https://chrome.google.com/webstore/detail/secure-shell-app/pnhechapfaindjhompbnflcldabbghjo Secure Shell]
* ''File Transfer Program'' - use the builtin Files app along with the Secure Shell app, configure as follows.
** Open the Files app.
** Click on the triple-dots in the upper right of the Files app, click Add new service, click Secure Shell App.
** On the Secure Shell App screen that comes up, enter your login information with cs.indstate.edu as the server and 22 as the port. Then click SFTP Mount.
** Go back to the Files app and you will see LOGIN@cs.indstate.edu:22 as an option on the left.

'''Linux (Beta) on Chromebook'''
* Not all chromebooks allow installation of Linux (Beta). If this works then you will have Linux installed on your Chromebook and will be able to use any of the commands that you use on the CS server.
* Follow [https://support.google.com/chromebook/answer/9145439?hl=en instructions from google].
* Note - installation could take a very long time (e.g., an hour or more). If installation fails you may need to select Remove Linux Beta and try again.
* Once installation is complete you open a terminal using the Terminal app. To install the programs mentioned on this page follow the instructions above for Linux (using the APT package manager commands).
* After the programs are installed you can open them by typing the command in the Terminal or by opening them as apps.

'''Copy/paste''' - in either the Secure Shell app or the Terminal app, copy/paste as follows. To copy, simply select text with the mouse and it will be copied to the clipboard. To paste, do a triple-click (three finger click).

==Other OS-Specific Notes==
If you are using Windows and have Putty installed as your terminal program, it installs a text-based file transfer program as well - psftp - which you should be able to find in your list of programs.

If you are using MacOS or Linux, a text-based file transfer program - sftp - is normally installed by default.

In either case, new users often prefer to use graphical file transfer programs (those mentioned above).

For the text-based sftp programs, the basic commands you will need.
* ls, cd, pwd - show you the files on the server and change directories on the server.
* lls, lcd, lpwd - show you the files on your computer and change directories on your computer.
* put - send a file from your computer to the server (from your current directory on your computer, to the current directory on the server).
* get - download a file from the server to your computer
* quit

==Compilers/Interpreters==

===Python===

===C/C++===

==Backing up Files - Rsync==

==GUI Programs X-Windows==
To run a GUI program while connected to the server, you will need to be running an X11 client on your local computer and have it running when connect to the server. Some further details depending on your operating system.
* MacOS - install [https://www.xquartz.org/ XQuartz] and run it.
* Windows - install [https://x.cygwin.com/ Cygwin/X] ([https://x.cygwin.com/docs/ug/setup.html#setup-cygwin-x-installing installation]) and run it. Or, euse the [https://learn.microsoft.com/en-us/windows/wsl/install Windows Subsystem for Linux] (WSL).
* Linux - do not need to install anything extra.

Once you have your X11 client installed, open it, and then connect to the CS server using the -Y switch in your ssh command: <pre>ssh -Y username@cs.indstate.edu</pre>

To verify everything is working try running in your terminal xcalc: <pre>xcalc</pre>

=Sample HW=
The following might be used by your instructor as part of a HW assignment to verify you have your computer setup properly.

# Follow the steps above to setup your computer with a file transfer program, text editor, and terminal program. Make sure you are able to use the file transfer program and terminal programs to connect to your CS class account on the CS server.
# Make sure you can open the text editor. Create a text file aboutMySystem.txt and put the following information.
## Your name:
## Your CS class account:
## Operating System:
## Text editor you are using:
## File transfer program:
## Did you have any difficulties in getting the programs setup? If yes, explain.
# Create the following screen shots demonstrating that you have the programs installed on your system properly. Note - you can ask the internet how to take a screenshot (e.g., type in - how to screenshot on chromebook). For each screenshot, make the screenshot of your whole screen (so I can see which OS you are running on and the program open and connected).
## textEditor.jpg - a screenshot that shows you editing the aboutMySystem.txt file with your text editor.
## fileTransfer.jpg - a screenshot that shows you using the file transfer program to connect to the CS server with your CS class account.
## terminal.jpg - a screenshot that shows you with the terminal program open and connected to the CS server with your CS class account.
# Use the file transfer program to connect to the CS server with your CS class account.
## While connected, create a new directory in your CS class account on the CS server. Name the new directory SystemSetup.
## Transfer the files you just created (aboutMySystem.txt, textEditor.jpg, fileTransfer.jpg, terminal.jpg) into the SystemSetup directory in your CS class account on the server.

Linux - System Setup

2026-06-04T21:36:26Z

Jkinne: /* File Transfer Program */

This page is meant to help you get your computer ready to connect to the CS server.

''Note - this page needs updating, was last updated in 2020.''

=CS User Accounts=
Below we guide you through getting software setup on your computer. In order to connect to the CS server you will also need your CS user account; see [[CS accounts]].

=Your Personal Computer=

==Terminal Program==
A terminal program allows you to type commands to run programs and view files and folders on your computer, and allows you to do the same on a remote computer (i.e., the CS server) after you have connected to it.

Any current computer (Windows, Mac, Linux, Chrome) has a terminal program builtin. You just need to know how to start it. For each OS, here is what you need to do...

''Note - the first time you connect to the CS server with a terminal or file transfer program, you will be notified that the identity of cs.indstate.edu cannot be verified, an ECDSA key will be displayed, and you will be asked if you still want to connect. Type or click yes.''

* '''Windows''' - use the command prompt or powershell. To use the command prompt, click the Start button (at the bottom of your screen, in the middle or the left normally), start typing either "command" or "cmd" and you should see the option to run "Cmd.exe" or "Command Prompt". To use the PowerShell, do the same (click the Start button) but start typing "Power Shell".
* '''Mac OS''' - use the Terminal program. To use the built-in Terminal program, use Spotlight (hold down the command key and press spacebar) and type in "Terminal". You should see the Terminal program to click on. You can also start Terminal by clicking on the Apps icon in the Dock, and start typing "Terminal".
* '''Linux''' - this depends on the distribution you are using. Some use the name "terminal" for this program, and some use the name "shell". For Ubuntu Linux with the default user interface (Gnome), you can click on the button in the bottom left (or press the Start key on your keyboard) and then start typing "Terminal" or "Shell". You can also directly open the terminal by holding down the control-alt-t keys.
* '''Chrome''' - you need to first need to enable the "Linux development environment". Click on the G or Chrome button (in the bottom left), click on Settings, in the settings click on "About ChromeOS" on the bottom, and find the "Developers" section, then click on "Set up" for the Linux development environment, then click through the setup process (you can leave default values for everything). Once you have this complete, you can start the terminal by clicking on the G or Chrome button (in the bottom left), start typing "Terminal" and click on it. You will see a Linux section and click on the first entry to start the terminal.

==File Transfer Program==
You will eventually need to transfer files between your personal computer and the CS server.
* All current OSes include a text-based file transfer program as part of the terminal (see above for starting a terminal). Once you have a terminal open, you use the command "sftp" to start the secure ftp program.
* [https://filezilla-project.org/download.php?type=client FileZilla] is a graphical file transfer program that can be installed on any current OS.

''Note - the first time you connect to the CS server with a terminal or file transfer program, you may be notified that the identity of cs.indstate.edu cannot be verified, an ECDSA key will be displayed, and you will be asked if you still want to connect. Type or click yes.''

''Note - make sure to choose "sftp" as opposed to "ftp" when connecting. ftp is not encrypted and is disabled on the CS server (it will not work). sftp is encrypted and is what we use.''

==Text Editor==
Note that while you are using a terminal that is connected to the CS server you can use text-based editors - nano, emacs, vim, jove (see [[Linux Terminal - Text Editors]] for more on how to get started with these). You will eventually want to have a good text editor on your personal computer.

The following are four good options that are cross-platform - can be installed on Mac, Windows, Linux, and Chromebook. If you already use some other option (e.g., Visual Studio Code, Eclipse, Notepad++, or anything else that is used by programmers) feel free to keep using what you are already using. Note that Word is ''not'' a text editor - it does not store files in plain text, which is what is needed for programming.
* [https://kate-editor.org/get-it/ Kate] - make sure to download the "release" installer.
* [https://www.sublimetext.com/ Submlime] - used by Luke May.
* [https://www.gnu.org/software/emacs/ Emacs] - used by Jeff Kinne, click "GNU/Linux", "Windows", or "MacOS" depending on your OS and follow the instructions.
** For Windows, download is from https://ftp.gnu.org/gnu/emacs/windows/, choose the latest emacs-## folder to click on, then download the zip file at the bottom that ends in "-x86_64.zip", extract the zip to somewhere to keep the program (e.g., C:\Program Files\), then run the file runemacs.exe in the bin directory.
** For macOS, the easiest install is from https://emacsformacosx.com/
* [https://www.vim.org/download.php Vim] - used by Geoff Exoo. For Windows, download and run the "self-installing executable". For macOS download and run MacVim.dmg from https://github.com/macvim-dev/macvim/releases/latest
* VS Code
* ne (nice editor)

When starting a new text editor do an internet search for a tutorial to get you started; once you are comfortable with the basics do an internet search for a cheat sheet of keyboard shortcuts to help you remember them.

==Installing for Linux==
Most Linux distributions have their own package management systems, with the programs mentioned on this page being installable via the package management system. There often is a graphical interface to the package management system, and there is normally a text-based interface - you type commands on the terminal to install packages.

''Debian'', ''Ubuntu'', and related Linux distributions use the APT package manager, and you can install the programs mentioned on this page by entering the following commands in the terminal. Note that you will likely be asked in the terminal whether you want to install the package, you need to type Y and press enter.
<pre>
sudo apt update # makes sure APT has the latest information about packages available
sudo apt install emacs
sudo apt install kate
sudo apt install gftp
sudo apt install vim
# Note - installing atom requires adding the repository where atom is kept
wget -qO - https://packagecloud.io/AtomEditor/atom/gpgkey | sudo apt-key add -
sudo sh -c 'echo "deb [arch=amd64] https://packagecloud.io/AtomEditor/atom/any/ any main" > /etc/apt/sources.list.d/atom.list'
sudo apt update
sudo apt install atom
</pre>
''Other Linux distributions'' use different package managers. If you use a different Linux distribution and are unable to figure out how to install packages you can ask your instructor, your advisor, or the CS system administrator.

After installing the above programs you can open them from the terminal (i.e., to open filezilla you type the command, filezilla). The programs may also appear in the graphical menu of programs.

==Chromebook==
On Chromebook you can choose whether to install apps and do all of your work connected to the CS server, or install Linux on your Chromebook and then use the instructions above on installing the programs.

'''Using apps''' - Install the following apps.
* ''Text Editor'' - [https://chrome.google.com/webstore/detail/text/mmfbcljfglbokpmkimbfghdkjmjhdgbg?hl=en Text]
* ''Terminal Program'' - [https://chrome.google.com/webstore/detail/secure-shell-app/pnhechapfaindjhompbnflcldabbghjo Secure Shell]
* ''File Transfer Program'' - use the builtin Files app along with the Secure Shell app, configure as follows.
** Open the Files app.
** Click on the triple-dots in the upper right of the Files app, click Add new service, click Secure Shell App.
** On the Secure Shell App screen that comes up, enter your login information with cs.indstate.edu as the server and 22 as the port. Then click SFTP Mount.
** Go back to the Files app and you will see LOGIN@cs.indstate.edu:22 as an option on the left.

'''Linux (Beta) on Chromebook'''
* Not all chromebooks allow installation of Linux (Beta). If this works then you will have Linux installed on your Chromebook and will be able to use any of the commands that you use on the CS server.
* Follow [https://support.google.com/chromebook/answer/9145439?hl=en instructions from google].
* Note - installation could take a very long time (e.g., an hour or more). If installation fails you may need to select Remove Linux Beta and try again.
* Once installation is complete you open a terminal using the Terminal app. To install the programs mentioned on this page follow the instructions above for Linux (using the APT package manager commands).
* After the programs are installed you can open them by typing the command in the Terminal or by opening them as apps.

'''Copy/paste''' - in either the Secure Shell app or the Terminal app, copy/paste as follows. To copy, simply select text with the mouse and it will be copied to the clipboard. To paste, do a triple-click (three finger click).

==Other OS-Specific Notes==
If you are using Windows and have Putty installed as your terminal program, it installs a text-based file transfer program as well - psftp - which you should be able to find in your list of programs.

If you are using MacOS or Linux, a text-based file transfer program - sftp - is normally installed by default.

In either case, new users often prefer to use graphical file transfer programs (those mentioned above).

For the text-based sftp programs, the basic commands you will need.
* ls, cd, pwd - show you the files on the server and change directories on the server.
* lls, lcd, lpwd - show you the files on your computer and change directories on your computer.
* put - send a file from your computer to the server (from your current directory on your computer, to the current directory on the server).
* get - download a file from the server to your computer
* quit

==Compilers/Interpreters==

===Python===

===C/C++===

==Backing up Files - Rsync==

==GUI Programs X-Windows==
To run a GUI program while connected to the server, you will need to be running an X11 client on your local computer and have it running when connect to the server. Some further details depending on your operating system.
* MacOS - install [https://www.xquartz.org/ XQuartz] and run it.
* Windows - install [https://x.cygwin.com/ Cygwin/X] ([https://x.cygwin.com/docs/ug/setup.html#setup-cygwin-x-installing installation]) and run it. Or, euse the [https://learn.microsoft.com/en-us/windows/wsl/install Windows Subsystem for Linux] (WSL).
* Linux - do not need to install anything extra.

Once you have your X11 client installed, open it, and then connect to the CS server using the -Y switch in your ssh command: <pre>ssh -Y username@cs.indstate.edu</pre>

To verify everything is working try running in your terminal xcalc: <pre>xcalc</pre>

=Sample HW=
The following might be used by your instructor as part of a HW assignment to verify you have your computer setup properly.

# Follow the steps above to setup your computer with a file transfer program, text editor, and terminal program. Make sure you are able to use the file transfer program and terminal programs to connect to your CS class account on the CS server.
# Make sure you can open the text editor. Create a text file aboutMySystem.txt and put the following information.
## Your name:
## Your CS class account:
## Operating System:
## Text editor you are using:
## File transfer program:
## Did you have any difficulties in getting the programs setup? If yes, explain.
# Create the following screen shots demonstrating that you have the programs installed on your system properly. Note - you can ask the internet how to take a screenshot (e.g., type in - how to screenshot on chromebook). For each screenshot, make the screenshot of your whole screen (so I can see which OS you are running on and the program open and connected).
## textEditor.jpg - a screenshot that shows you editing the aboutMySystem.txt file with your text editor.
## fileTransfer.jpg - a screenshot that shows you using the file transfer program to connect to the CS server with your CS class account.
## terminal.jpg - a screenshot that shows you with the terminal program open and connected to the CS server with your CS class account.
# Use the file transfer program to connect to the CS server with your CS class account.
## While connected, create a new directory in your CS class account on the CS server. Name the new directory SystemSetup.
## Transfer the files you just created (aboutMySystem.txt, textEditor.jpg, fileTransfer.jpg, terminal.jpg) into the SystemSetup directory in your CS class account on the server.

Linux - System Setup

2026-06-04T21:34:11Z

Jkinne: /* Terminal Program */

This page is meant to help you get your computer ready to connect to the CS server.

''Note - this page needs updating, was last updated in 2020.''

=CS User Accounts=
Below we guide you through getting software setup on your computer. In order to connect to the CS server you will also need your CS user account; see [[CS accounts]].

=Your Personal Computer=

==Terminal Program==
A terminal program allows you to type commands to run programs and view files and folders on your computer, and allows you to do the same on a remote computer (i.e., the CS server) after you have connected to it.

Any current computer (Windows, Mac, Linux, Chrome) has a terminal program builtin. You just need to know how to start it. For each OS, here is what you need to do...

''Note - the first time you connect to the CS server with a terminal or file transfer program, you will be notified that the identity of cs.indstate.edu cannot be verified, an ECDSA key will be displayed, and you will be asked if you still want to connect. Type or click yes.''

* '''Windows''' - use the command prompt or powershell. To use the command prompt, click the Start button (at the bottom of your screen, in the middle or the left normally), start typing either "command" or "cmd" and you should see the option to run "Cmd.exe" or "Command Prompt". To use the PowerShell, do the same (click the Start button) but start typing "Power Shell".
* '''Mac OS''' - use the Terminal program. To use the built-in Terminal program, use Spotlight (hold down the command key and press spacebar) and type in "Terminal". You should see the Terminal program to click on. You can also start Terminal by clicking on the Apps icon in the Dock, and start typing "Terminal".
* '''Linux''' - this depends on the distribution you are using. Some use the name "terminal" for this program, and some use the name "shell". For Ubuntu Linux with the default user interface (Gnome), you can click on the button in the bottom left (or press the Start key on your keyboard) and then start typing "Terminal" or "Shell". You can also directly open the terminal by holding down the control-alt-t keys.
* '''Chrome''' - you need to first need to enable the "Linux development environment". Click on the G or Chrome button (in the bottom left), click on Settings, in the settings click on "About ChromeOS" on the bottom, and find the "Developers" section, then click on "Set up" for the Linux development environment, then click through the setup process (you can leave default values for everything). Once you have this complete, you can start the terminal by clicking on the G or Chrome button (in the bottom left), start typing "Terminal" and click on it. You will see a Linux section and click on the first entry to start the terminal.

==File Transfer Program==
You will eventually need to transfer files between your personal computer and the CS server. Most OSes have built-in support to do this, but there are other options that are easier to use. We recommend choosing a file transfer program to install. For Windows or Mac you will download the installer to install the program. If you are using Linux or Chromebook, see the sections below about these environments.
* [https://cyberduck.io/download/ CyberDuck] - works for MacOS or Windows, is freeware, click the large "Download for Windows" or "Download for macOS" in the middle of the page.
* [https://winscp.net/eng/download.php WinSCP] - works for Windows, scroll past ads and click the "Download WINSCP" button.
* [https://www.gftp.org/ gFTP] - good option for Linux, see below about Linux for how to install.

''Note - the first time you connect to the CS server with a terminal or file transfer program, you will be notified that the identity of cs.indstate.edu cannot be verified, an ECDSA key will be displayed, and you will be asked if you still want to connect. Type or click yes.''

''Note - make sure to choose "sftp" as opposed to "ftp" when connecting. ftp is not encrypted and is disabled on the CS server (it will not work). sftp is encrypted and is what we use.''

''Text-based sftp program that is already installed on many systems - see OS Specific Notes below''

==Text Editor==
Note that while you are using a terminal that is connected to the CS server you can use text-based editors - nano, emacs, vim, jove (see [[Linux Terminal - Text Editors]] for more on how to get started with these). You will eventually want to have a good text editor on your personal computer.

The following are four good options that are cross-platform - can be installed on Mac, Windows, Linux, and Chromebook. If you already use some other option (e.g., Visual Studio Code, Eclipse, Notepad++, or anything else that is used by programmers) feel free to keep using what you are already using. Note that Word is ''not'' a text editor - it does not store files in plain text, which is what is needed for programming.
* [https://kate-editor.org/get-it/ Kate] - make sure to download the "release" installer.
* [https://www.sublimetext.com/ Submlime] - used by Luke May.
* [https://www.gnu.org/software/emacs/ Emacs] - used by Jeff Kinne, click "GNU/Linux", "Windows", or "MacOS" depending on your OS and follow the instructions.
** For Windows, download is from https://ftp.gnu.org/gnu/emacs/windows/, choose the latest emacs-## folder to click on, then download the zip file at the bottom that ends in "-x86_64.zip", extract the zip to somewhere to keep the program (e.g., C:\Program Files\), then run the file runemacs.exe in the bin directory.
** For macOS, the easiest install is from https://emacsformacosx.com/
* [https://www.vim.org/download.php Vim] - used by Geoff Exoo. For Windows, download and run the "self-installing executable". For macOS download and run MacVim.dmg from https://github.com/macvim-dev/macvim/releases/latest
* VS Code
* ne (nice editor)

When starting a new text editor do an internet search for a tutorial to get you started; once you are comfortable with the basics do an internet search for a cheat sheet of keyboard shortcuts to help you remember them.

==Installing for Linux==
Most Linux distributions have their own package management systems, with the programs mentioned on this page being installable via the package management system. There often is a graphical interface to the package management system, and there is normally a text-based interface - you type commands on the terminal to install packages.

''Debian'', ''Ubuntu'', and related Linux distributions use the APT package manager, and you can install the programs mentioned on this page by entering the following commands in the terminal. Note that you will likely be asked in the terminal whether you want to install the package, you need to type Y and press enter.
<pre>
sudo apt update # makes sure APT has the latest information about packages available
sudo apt install emacs
sudo apt install kate
sudo apt install gftp
sudo apt install vim
# Note - installing atom requires adding the repository where atom is kept
wget -qO - https://packagecloud.io/AtomEditor/atom/gpgkey | sudo apt-key add -
sudo sh -c 'echo "deb [arch=amd64] https://packagecloud.io/AtomEditor/atom/any/ any main" > /etc/apt/sources.list.d/atom.list'
sudo apt update
sudo apt install atom
</pre>
''Other Linux distributions'' use different package managers. If you use a different Linux distribution and are unable to figure out how to install packages you can ask your instructor, your advisor, or the CS system administrator.

After installing the above programs you can open them from the terminal (i.e., to open filezilla you type the command, filezilla). The programs may also appear in the graphical menu of programs.

==Chromebook==
On Chromebook you can choose whether to install apps and do all of your work connected to the CS server, or install Linux on your Chromebook and then use the instructions above on installing the programs.

'''Using apps''' - Install the following apps.
* ''Text Editor'' - [https://chrome.google.com/webstore/detail/text/mmfbcljfglbokpmkimbfghdkjmjhdgbg?hl=en Text]
* ''Terminal Program'' - [https://chrome.google.com/webstore/detail/secure-shell-app/pnhechapfaindjhompbnflcldabbghjo Secure Shell]
* ''File Transfer Program'' - use the builtin Files app along with the Secure Shell app, configure as follows.
** Open the Files app.
** Click on the triple-dots in the upper right of the Files app, click Add new service, click Secure Shell App.
** On the Secure Shell App screen that comes up, enter your login information with cs.indstate.edu as the server and 22 as the port. Then click SFTP Mount.
** Go back to the Files app and you will see LOGIN@cs.indstate.edu:22 as an option on the left.

'''Linux (Beta) on Chromebook'''
* Not all chromebooks allow installation of Linux (Beta). If this works then you will have Linux installed on your Chromebook and will be able to use any of the commands that you use on the CS server.
* Follow [https://support.google.com/chromebook/answer/9145439?hl=en instructions from google].
* Note - installation could take a very long time (e.g., an hour or more). If installation fails you may need to select Remove Linux Beta and try again.
* Once installation is complete you open a terminal using the Terminal app. To install the programs mentioned on this page follow the instructions above for Linux (using the APT package manager commands).
* After the programs are installed you can open them by typing the command in the Terminal or by opening them as apps.

'''Copy/paste''' - in either the Secure Shell app or the Terminal app, copy/paste as follows. To copy, simply select text with the mouse and it will be copied to the clipboard. To paste, do a triple-click (three finger click).

==Other OS-Specific Notes==
If you are using Windows and have Putty installed as your terminal program, it installs a text-based file transfer program as well - psftp - which you should be able to find in your list of programs.

If you are using MacOS or Linux, a text-based file transfer program - sftp - is normally installed by default.

In either case, new users often prefer to use graphical file transfer programs (those mentioned above).

For the text-based sftp programs, the basic commands you will need.
* ls, cd, pwd - show you the files on the server and change directories on the server.
* lls, lcd, lpwd - show you the files on your computer and change directories on your computer.
* put - send a file from your computer to the server (from your current directory on your computer, to the current directory on the server).
* get - download a file from the server to your computer
* quit

==Compilers/Interpreters==

===Python===

===C/C++===

==Backing up Files - Rsync==

==GUI Programs X-Windows==
To run a GUI program while connected to the server, you will need to be running an X11 client on your local computer and have it running when connect to the server. Some further details depending on your operating system.
* MacOS - install [https://www.xquartz.org/ XQuartz] and run it.
* Windows - install [https://x.cygwin.com/ Cygwin/X] ([https://x.cygwin.com/docs/ug/setup.html#setup-cygwin-x-installing installation]) and run it. Or, euse the [https://learn.microsoft.com/en-us/windows/wsl/install Windows Subsystem for Linux] (WSL).
* Linux - do not need to install anything extra.

Once you have your X11 client installed, open it, and then connect to the CS server using the -Y switch in your ssh command: <pre>ssh -Y username@cs.indstate.edu</pre>

To verify everything is working try running in your terminal xcalc: <pre>xcalc</pre>

=Sample HW=
The following might be used by your instructor as part of a HW assignment to verify you have your computer setup properly.

# Follow the steps above to setup your computer with a file transfer program, text editor, and terminal program. Make sure you are able to use the file transfer program and terminal programs to connect to your CS class account on the CS server.
# Make sure you can open the text editor. Create a text file aboutMySystem.txt and put the following information.
## Your name:
## Your CS class account:
## Operating System:
## Text editor you are using:
## File transfer program:
## Did you have any difficulties in getting the programs setup? If yes, explain.
# Create the following screen shots demonstrating that you have the programs installed on your system properly. Note - you can ask the internet how to take a screenshot (e.g., type in - how to screenshot on chromebook). For each screenshot, make the screenshot of your whole screen (so I can see which OS you are running on and the program open and connected).
## textEditor.jpg - a screenshot that shows you editing the aboutMySystem.txt file with your text editor.
## fileTransfer.jpg - a screenshot that shows you using the file transfer program to connect to the CS server with your CS class account.
## terminal.jpg - a screenshot that shows you with the terminal program open and connected to the CS server with your CS class account.
# Use the file transfer program to connect to the CS server with your CS class account.
## While connected, create a new directory in your CS class account on the CS server. Name the new directory SystemSetup.
## Transfer the files you just created (aboutMySystem.txt, textEditor.jpg, fileTransfer.jpg, terminal.jpg) into the SystemSetup directory in your CS class account on the server.

Linux - System Setup

2026-06-04T21:07:00Z

Jkinne: /* Your Personal Computer */

This page is meant to help you get your computer ready to connect to the CS server.

''Note - this page needs updating, was last updated in 2020.''

=CS User Accounts=
Below we guide you through getting software setup on your computer. In order to connect to the CS server you will also need your CS user account; see [[CS accounts]].

=Your Personal Computer=

==Terminal Program==
A terminal program allows you to type commands to run programs and view files and folders on your computer, and allows you to do the same on a remote computer (i.e., the CS server) after you have connected to it.

Any current computer (Windows, Mac, Linux, Chrome) has a terminal program builtin. You just need to know how to start it. For each OS, here is what you need to do...

''Note - the first time you connect to the CS server with a terminal or file transfer program, you will be notified that the identity of cs.indstate.edu cannot be verified, an ECDSA key will be displayed, and you will be asked if you still want to connect. Type or click yes.''

* '''Windows''' - use the command prompt or powershell. To use the command prompt, click the Start button (at the bottom of your screen, in the middle or the left normally), start typing either "command" or "cmd" and you should see the option to run "Cmd.exe" or "Command Prompt". To use the PowerShell, do the same (click the Start button) but start typing "Power Shell".
* '''Mac OS''' - use the Terminal program. To use the built-in Terminal program, use Spotlight (hold down the command key and press spacebar) and type in "Terminal". You should see the Terminal program to click on. You can also start Terminal by clicking on the Apps icon in the Dock, and start typing "Terminal".
* '''Linux''' - this depends on the distribution you are using. Some use the name "terminal" for this program, and some use the name "shell". For Ubuntu Linux with the default user interface (Gnome), you can click on the button in the bottom left (or press the Start key on your keyboard) and then start typing "Terminal" or "Shell". You can also directly open the terminal by holding down the control-alt-t keys.
* '''Chrome''' -

==File Transfer Program==
You will eventually need to transfer files between your personal computer and the CS server. Most OSes have built-in support to do this, but there are other options that are easier to use. We recommend choosing a file transfer program to install. For Windows or Mac you will download the installer to install the program. If you are using Linux or Chromebook, see the sections below about these environments.
* [https://cyberduck.io/download/ CyberDuck] - works for MacOS or Windows, is freeware, click the large "Download for Windows" or "Download for macOS" in the middle of the page.
* [https://winscp.net/eng/download.php WinSCP] - works for Windows, scroll past ads and click the "Download WINSCP" button.
* [https://www.gftp.org/ gFTP] - good option for Linux, see below about Linux for how to install.

''Note - the first time you connect to the CS server with a terminal or file transfer program, you will be notified that the identity of cs.indstate.edu cannot be verified, an ECDSA key will be displayed, and you will be asked if you still want to connect. Type or click yes.''

''Note - make sure to choose "sftp" as opposed to "ftp" when connecting. ftp is not encrypted and is disabled on the CS server (it will not work). sftp is encrypted and is what we use.''

''Text-based sftp program that is already installed on many systems - see OS Specific Notes below''

==Text Editor==
Note that while you are using a terminal that is connected to the CS server you can use text-based editors - nano, emacs, vim, jove (see [[Linux Terminal - Text Editors]] for more on how to get started with these). You will eventually want to have a good text editor on your personal computer.

The following are four good options that are cross-platform - can be installed on Mac, Windows, Linux, and Chromebook. If you already use some other option (e.g., Visual Studio Code, Eclipse, Notepad++, or anything else that is used by programmers) feel free to keep using what you are already using. Note that Word is ''not'' a text editor - it does not store files in plain text, which is what is needed for programming.
* [https://kate-editor.org/get-it/ Kate] - make sure to download the "release" installer.
* [https://www.sublimetext.com/ Submlime] - used by Luke May.
* [https://www.gnu.org/software/emacs/ Emacs] - used by Jeff Kinne, click "GNU/Linux", "Windows", or "MacOS" depending on your OS and follow the instructions.
** For Windows, download is from https://ftp.gnu.org/gnu/emacs/windows/, choose the latest emacs-## folder to click on, then download the zip file at the bottom that ends in "-x86_64.zip", extract the zip to somewhere to keep the program (e.g., C:\Program Files\), then run the file runemacs.exe in the bin directory.
** For macOS, the easiest install is from https://emacsformacosx.com/
* [https://www.vim.org/download.php Vim] - used by Geoff Exoo. For Windows, download and run the "self-installing executable". For macOS download and run MacVim.dmg from https://github.com/macvim-dev/macvim/releases/latest
* VS Code
* ne (nice editor)

When starting a new text editor do an internet search for a tutorial to get you started; once you are comfortable with the basics do an internet search for a cheat sheet of keyboard shortcuts to help you remember them.

==Installing for Linux==
Most Linux distributions have their own package management systems, with the programs mentioned on this page being installable via the package management system. There often is a graphical interface to the package management system, and there is normally a text-based interface - you type commands on the terminal to install packages.

''Debian'', ''Ubuntu'', and related Linux distributions use the APT package manager, and you can install the programs mentioned on this page by entering the following commands in the terminal. Note that you will likely be asked in the terminal whether you want to install the package, you need to type Y and press enter.
<pre>
sudo apt update # makes sure APT has the latest information about packages available
sudo apt install emacs
sudo apt install kate
sudo apt install gftp
sudo apt install vim
# Note - installing atom requires adding the repository where atom is kept
wget -qO - https://packagecloud.io/AtomEditor/atom/gpgkey | sudo apt-key add -
sudo sh -c 'echo "deb [arch=amd64] https://packagecloud.io/AtomEditor/atom/any/ any main" > /etc/apt/sources.list.d/atom.list'
sudo apt update
sudo apt install atom
</pre>
''Other Linux distributions'' use different package managers. If you use a different Linux distribution and are unable to figure out how to install packages you can ask your instructor, your advisor, or the CS system administrator.

After installing the above programs you can open them from the terminal (i.e., to open filezilla you type the command, filezilla). The programs may also appear in the graphical menu of programs.

==Chromebook==
On Chromebook you can choose whether to install apps and do all of your work connected to the CS server, or install Linux on your Chromebook and then use the instructions above on installing the programs.

'''Using apps''' - Install the following apps.
* ''Text Editor'' - [https://chrome.google.com/webstore/detail/text/mmfbcljfglbokpmkimbfghdkjmjhdgbg?hl=en Text]
* ''Terminal Program'' - [https://chrome.google.com/webstore/detail/secure-shell-app/pnhechapfaindjhompbnflcldabbghjo Secure Shell]
* ''File Transfer Program'' - use the builtin Files app along with the Secure Shell app, configure as follows.
** Open the Files app.
** Click on the triple-dots in the upper right of the Files app, click Add new service, click Secure Shell App.
** On the Secure Shell App screen that comes up, enter your login information with cs.indstate.edu as the server and 22 as the port. Then click SFTP Mount.
** Go back to the Files app and you will see LOGIN@cs.indstate.edu:22 as an option on the left.

'''Linux (Beta) on Chromebook'''
* Not all chromebooks allow installation of Linux (Beta). If this works then you will have Linux installed on your Chromebook and will be able to use any of the commands that you use on the CS server.
* Follow [https://support.google.com/chromebook/answer/9145439?hl=en instructions from google].
* Note - installation could take a very long time (e.g., an hour or more). If installation fails you may need to select Remove Linux Beta and try again.
* Once installation is complete you open a terminal using the Terminal app. To install the programs mentioned on this page follow the instructions above for Linux (using the APT package manager commands).
* After the programs are installed you can open them by typing the command in the Terminal or by opening them as apps.

'''Copy/paste''' - in either the Secure Shell app or the Terminal app, copy/paste as follows. To copy, simply select text with the mouse and it will be copied to the clipboard. To paste, do a triple-click (three finger click).

==Other OS-Specific Notes==
If you are using Windows and have Putty installed as your terminal program, it installs a text-based file transfer program as well - psftp - which you should be able to find in your list of programs.

If you are using MacOS or Linux, a text-based file transfer program - sftp - is normally installed by default.

In either case, new users often prefer to use graphical file transfer programs (those mentioned above).

For the text-based sftp programs, the basic commands you will need.
* ls, cd, pwd - show you the files on the server and change directories on the server.
* lls, lcd, lpwd - show you the files on your computer and change directories on your computer.
* put - send a file from your computer to the server (from your current directory on your computer, to the current directory on the server).
* get - download a file from the server to your computer
* quit

==Compilers/Interpreters==

===Python===

===C/C++===

==Backing up Files - Rsync==

==GUI Programs X-Windows==
To run a GUI program while connected to the server, you will need to be running an X11 client on your local computer and have it running when connect to the server. Some further details depending on your operating system.
* MacOS - install [https://www.xquartz.org/ XQuartz] and run it.
* Windows - install [https://x.cygwin.com/ Cygwin/X] ([https://x.cygwin.com/docs/ug/setup.html#setup-cygwin-x-installing installation]) and run it. Or, euse the [https://learn.microsoft.com/en-us/windows/wsl/install Windows Subsystem for Linux] (WSL).
* Linux - do not need to install anything extra.

Once you have your X11 client installed, open it, and then connect to the CS server using the -Y switch in your ssh command: <pre>ssh -Y username@cs.indstate.edu</pre>

To verify everything is working try running in your terminal xcalc: <pre>xcalc</pre>

=Sample HW=
The following might be used by your instructor as part of a HW assignment to verify you have your computer setup properly.

# Follow the steps above to setup your computer with a file transfer program, text editor, and terminal program. Make sure you are able to use the file transfer program and terminal programs to connect to your CS class account on the CS server.
# Make sure you can open the text editor. Create a text file aboutMySystem.txt and put the following information.
## Your name:
## Your CS class account:
## Operating System:
## Text editor you are using:
## File transfer program:
## Did you have any difficulties in getting the programs setup? If yes, explain.
# Create the following screen shots demonstrating that you have the programs installed on your system properly. Note - you can ask the internet how to take a screenshot (e.g., type in - how to screenshot on chromebook). For each screenshot, make the screenshot of your whole screen (so I can see which OS you are running on and the program open and connected).
## textEditor.jpg - a screenshot that shows you editing the aboutMySystem.txt file with your text editor.
## fileTransfer.jpg - a screenshot that shows you using the file transfer program to connect to the CS server with your CS class account.
## terminal.jpg - a screenshot that shows you with the terminal program open and connected to the CS server with your CS class account.
# Use the file transfer program to connect to the CS server with your CS class account.
## While connected, create a new directory in your CS class account on the CS server. Name the new directory SystemSetup.
## Transfer the files you just created (aboutMySystem.txt, textEditor.jpg, fileTransfer.jpg, terminal.jpg) into the SystemSetup directory in your CS class account on the server.

Beginning Programming

2026-06-04T19:45:17Z

Jkinne: /* Getting Ready */

== Computing majors ==
If you are interested in computing, at ISU your options are Computer Science, Information Technology, Cyber & Security Studies, Computer and Electrical Engineering Technology. There is a fair amount of overlap, but roughly - (a) CS is mostly about making software and making it efficient, (b) IT is about managing computer systems and networks, (c) CSS at ISU is in the School of Criminology and has a large focus in criminology / social science, (d) CEET more involves the hardware / circuits. The most common job titles for those graduating from CS are - programmer/developer/software engineer of various kinds (web, database, network, systems, ...). If you do not want to be a programmer, consider whether CS, IT, CSS, or CEET would best suit you.

== CS at ISU ==
Most programs that are called "Computer Science" have a common core in common so that you should get a similar experience at most universities that offer CS. After finishing any CS program (including at ISU), you should be a decent programmer in a few different programming languages, can use the right data structures and algorithms for different problems, understand precisely how modern software systems (e.g., operating systems, web servers, 3d graphics) work and are programmed, and have completed a few nicely sized software projects.

But each CS department has its own personality. CS at ISU is more unix-oriented than Windows-oriented, and gets you experience with both low-level and high-level programming. After finishing at ISU you should be very familiar with unix/linux, and be a decent programmer in Python, C, javascript, php, and sql. You should be familiar with a number of other programming languages (Java, a few others).

== Getting Ready ==
If you have done some work in computing before and want to do something extra to get ready for CS at ISU, here are a few things you can do.

* [[Programming Practice]]
* http://code.org - go do some of their tutorials. These are mostly aimed at middle-school aged students, but is great experience and fun.
* Get a copy of Introduction to Algorithms (any edition) and start perusing it.
* http://appinventor.mit.edu/explore/ - make apps for Android.
* See our [[Help and Getting Started]] page.
* Install linux on one of your home computers (Ubuntu and Mint are pretty easy to use). Note - do it on a computer that doesn't have any important data on it... You can also do this by first installing VirtualBox or VMWare in your current operating system and then install linux inside of that.
* Some key ideas in CS and examples -
** Algorithm - linear search vs. binary search, selection sort vs. merge sort, Euclid's algorithm vs. trial division
** Proof - there are infinitely many primes, the halting problem is uncomputable, the square root of 2 is irrational, formula for the sum of an arithmetic series [1 + 2 + ... + n = n*(n+1)/2]
** Data speeds - tape vs. hard disk drive vs. RAM vs. CPU cache vs. CPU registers
** Abstraction - operating system virtual memory, RAID, object-oriented programming, file system, any API, any programming language
** Assembly language - [https://en.wikipedia.org/wiki/Little_man_computer little man computer] ([http://robowriter.info/little-man-computer/ simulator])
* Some classic beginning programming projects -
** Encryption - Caesar cipher, substitution cipher, Vigenere, RSA, and others
** Letter and word frequency - used in breaking substitution cipher, used in AI
** Chatbot - responds in a reasonable way to many text, see Eliza ("the doctor")
** Choose your adventure game
** 2d maze/dungeon crawler
** Arithmetic quiz and tables - for kids learning their math facts
** Paint
** Drawing shapes - regular polygons, stars, fractals
** Board game - tic tac toe, connect 4, chess, you name it
** Calculator - with usual operations but also with your own custom ones

== Other Helpful Resources ==
* [https://developer.android.com/ Make Android applications]
* [https://developer.apple.com/ Make iOS applications]
* [https://www.jetbrains.com/student Development tools for students]

Beginning Programming

2026-06-04T19:45:07Z

Jkinne: /* Getting Ready */

== Computing majors ==
If you are interested in computing, at ISU your options are Computer Science, Information Technology, Cyber & Security Studies, Computer and Electrical Engineering Technology. There is a fair amount of overlap, but roughly - (a) CS is mostly about making software and making it efficient, (b) IT is about managing computer systems and networks, (c) CSS at ISU is in the School of Criminology and has a large focus in criminology / social science, (d) CEET more involves the hardware / circuits. The most common job titles for those graduating from CS are - programmer/developer/software engineer of various kinds (web, database, network, systems, ...). If you do not want to be a programmer, consider whether CS, IT, CSS, or CEET would best suit you.

== CS at ISU ==
Most programs that are called "Computer Science" have a common core in common so that you should get a similar experience at most universities that offer CS. After finishing any CS program (including at ISU), you should be a decent programmer in a few different programming languages, can use the right data structures and algorithms for different problems, understand precisely how modern software systems (e.g., operating systems, web servers, 3d graphics) work and are programmed, and have completed a few nicely sized software projects.

But each CS department has its own personality. CS at ISU is more unix-oriented than Windows-oriented, and gets you experience with both low-level and high-level programming. After finishing at ISU you should be very familiar with unix/linux, and be a decent programmer in Python, C, javascript, php, and sql. You should be familiar with a number of other programming languages (Java, a few others).

== Getting Ready ==
If you have done some work in computing before and want to do something extra to get ready for CS at ISU, here are a few things you can do.

* [[Programming Practice]]
* http://code.org - go do some of their tutorials. These are mostly aimed at middle-school aged students, but is great experience and fun.
* Get a copy of Introduction to Algorithms (any edition) and start perusing it.
* http://appinventor.mit.edu/explore/ - make apps for Android.
* See our [[Help and Getting Started]] page.
* Install linux on one of your home computers (Ubuntu and Mint are pretty easy to use). Note - do it on a computer that doesn't have any important data on it... You can also do this by first installing VirtualBox or VMWare in your current operating system and then install linux inside of that.
* Some key ideas in CS and examples -
** Algorithm - linear search vs. binary search, selection sort vs. merge sort, Euclid's algorithm vs. trial division
** Proof - there are infinitely many primes, the halting problem is uncomputable, the square root of 2 is irrational, formula for the sum of an arithmetic series [1 + 2 + ... + n = n*(n+1)/2]
** Data speeds - tape vs. hard disk drive vs. RAM vs. CPU cache vs. CPU registers
** Abstraction - operating system virtual memory, RAID, object-oriented programming, file system, any API, any programming language
** Assembly language - [https://en.wikipedia.org/wiki/Little_man_computer little man computer] ([http://robowriter.info/little-man-computer/ simulator])
* Some classic beginning programming projects -
** Encryption - Caesar cipher, substitution cipher, Vigenere, RSA, and others
** Letter and word frequency - used in breaking substitution cipher, used in AI
** Chatbot - responds in a reasonable way to many text, see Eliza ("the doctor")
** Choose your adventure game
** 2d maze/dungeon crawler
** Arithmetic quiz and tables - for kids learning their math facts
** Paint
** Drawing shapes - regular polygons, stars, fractals
** Board game - tic tac toe, connect 4, chess, you name it
** Calculator - with usual operations but also with your own cutsom ones

== Other Helpful Resources ==
* [https://developer.android.com/ Make Android applications]
* [https://developer.apple.com/ Make iOS applications]
* [https://www.jetbrains.com/student Development tools for students]

Beginning Programming

2026-06-04T19:43:10Z

Jkinne: /* Getting Ready */

== Computing majors ==
If you are interested in computing, at ISU your options are Computer Science, Information Technology, Cyber & Security Studies, Computer and Electrical Engineering Technology. There is a fair amount of overlap, but roughly - (a) CS is mostly about making software and making it efficient, (b) IT is about managing computer systems and networks, (c) CSS at ISU is in the School of Criminology and has a large focus in criminology / social science, (d) CEET more involves the hardware / circuits. The most common job titles for those graduating from CS are - programmer/developer/software engineer of various kinds (web, database, network, systems, ...). If you do not want to be a programmer, consider whether CS, IT, CSS, or CEET would best suit you.

== CS at ISU ==
Most programs that are called "Computer Science" have a common core in common so that you should get a similar experience at most universities that offer CS. After finishing any CS program (including at ISU), you should be a decent programmer in a few different programming languages, can use the right data structures and algorithms for different problems, understand precisely how modern software systems (e.g., operating systems, web servers, 3d graphics) work and are programmed, and have completed a few nicely sized software projects.

But each CS department has its own personality. CS at ISU is more unix-oriented than Windows-oriented, and gets you experience with both low-level and high-level programming. After finishing at ISU you should be very familiar with unix/linux, and be a decent programmer in Python, C, javascript, php, and sql. You should be familiar with a number of other programming languages (Java, a few others).

== Getting Ready ==
If you have done some work in computing before and want to do something extra to get ready for CS at ISU, here are a few things you can do.

* [[Programming Practice]]
* http://code.org - go do some of their tutorials. These are mostly aimed at middle-school aged students, but is great experience and fun.
* Get a copy of Introduction to Algorithms (any edition) and start perusing it.
* http://appinventor.mit.edu/explore/ - make apps for Android.
* See our [[Help and Getting Started]] page and [http://cs.indstate.edu/info/learn.html Learn].
* Install linux on one of your home computers (Ubuntu and Mint are pretty easy to use). Note - do it on a computer that doesn't have any important data on it... You can also do this by first installing VirtualBox in your current operating system and then install linux inside of that.
* Some key ideas in CS and examples -
** Algorithm - linear search vs. binary search, selection sort vs. merge sort, euclid's algorithm vs. trial division
** Proof - there are infinitely many primes, the halting problem is uncomputable, the square root of 2 is irrational, the sum of an arithmetic series [1 + 2 + ... + n = n*(n+1)/2]
** Data speeds - tape vs. hard disk drive vs. RAM vs. CPU cache vs. CPU registers
** Abstraction - operating system virtual memory, RAID, object-oriented programming, file system, any API, any programming language
** Assembly language - [https://en.wikipedia.org/wiki/Little_man_computer little man computer] ([http://robowriter.info/little-man-computer/ simulator])
* Some classic beginning programming projects -
** Encryption - Caesar cipher, substitution cipher, Vigenere, RSA, and others
** Letter and word frequency - used in breaking substitution cipher, used in AI
** Chatbot - responds in a reasonable way to many text, see Eliza ("the doctor")
** Choose your adventure game
** 2d maze/dungeon crawler
** Arithmetic quiz and tables - for kids learning their math facts
** Paint
** Drawing shapes - regular polygons, stars, fractals
** Board game - tic tac toe, connect 4, chess, you name it
** Calculator - with usual operations but also with your own cutsom ones

== Other Helpful Resources ==
* [https://developer.android.com/ Make Android applications]
* [https://developer.apple.com/ Make iOS applications]
* [https://www.jetbrains.com/student Development tools for students]

Beginning Programming

2026-06-04T19:42:39Z

Jkinne: /* Getting Ready */

== Computing majors ==
If you are interested in computing, at ISU your options are Computer Science, Information Technology, Cyber & Security Studies, Computer and Electrical Engineering Technology. There is a fair amount of overlap, but roughly - (a) CS is mostly about making software and making it efficient, (b) IT is about managing computer systems and networks, (c) CSS at ISU is in the School of Criminology and has a large focus in criminology / social science, (d) CEET more involves the hardware / circuits. The most common job titles for those graduating from CS are - programmer/developer/software engineer of various kinds (web, database, network, systems, ...). If you do not want to be a programmer, consider whether CS, IT, CSS, or CEET would best suit you.

== CS at ISU ==
Most programs that are called "Computer Science" have a common core in common so that you should get a similar experience at most universities that offer CS. After finishing any CS program (including at ISU), you should be a decent programmer in a few different programming languages, can use the right data structures and algorithms for different problems, understand precisely how modern software systems (e.g., operating systems, web servers, 3d graphics) work and are programmed, and have completed a few nicely sized software projects.

But each CS department has its own personality. CS at ISU is more unix-oriented than Windows-oriented, and gets you experience with both low-level and high-level programming. After finishing at ISU you should be very familiar with unix/linux, and be a decent programmer in Python, C, javascript, php, and sql. You should be familiar with a number of other programming languages (Java, a few others).

== Getting Ready ==
If you have done some work in computing before and want to do something extra to get ready for CS at ISU, here are a few things you can do.

* [[Programming Practice]]

* http://code.org - go do some of their tutorials. These are mostly aimed at middle-school aged students, but is great experience and fun.
* http://hackerrank.com - create an account and start doing basic programming problems. This site is great because your answer won't be accepted until it is 100% correct.
* [https://www.youtube.com/playlist?list=PLCFNfZsc2MIByWxTX2Zjg0wJpk1YXbcQ8 CS 151] - check out Jeff Kinne's video lectures from CS 151, the first course in our major.
* [https://www.youtube.com/playlist?list=PLXFP6J47Bp0fxKk5q6V_K2_3DkPIdGmMf AI] - video playlist from high school summer honors course at ISU from 2017.
* Get a copy of Introduction to Algorithms (any edition) and start perusing it.
* http://appinventor.mit.edu/explore/ - make apps for Android.
* See our [[Help and Getting Started]] page and [http://cs.indstate.edu/info/learn.html Learn].
* Install linux on one of your home computers (Ubuntu and Mint are pretty easy to use). Note - do it on a computer that doesn't have any important data on it... You can also do this by first installing VirtualBox in your current operating system and then install linux inside of that.
* Some key ideas in CS and examples -
** Algorithm - linear search vs. binary search, selection sort vs. merge sort, euclid's algorithm vs. trial division
** Proof - there are infinitely many primes, the halting problem is uncomputable, the square root of 2 is irrational, the sum of an arithmetic series [1 + 2 + ... + n = n*(n+1)/2]
** Data speeds - tape vs. hard disk drive vs. RAM vs. CPU cache vs. CPU registers
** Abstraction - operating system virtual memory, RAID, object-oriented programming, file system, any API, any programming language
** Assembly language - [https://en.wikipedia.org/wiki/Little_man_computer little man computer] ([http://robowriter.info/little-man-computer/ simulator])
* Some classic beginning programming projects -
** Encryption - Caesar cipher, substitution cipher, Vigenere, RSA, and others
** Letter and word frequency - used in breaking substitution cipher, used in AI
** Chatbot - responds in a reasonable way to many text, see Eliza ("the doctor")
** Choose your adventure game
** 2d maze/dungeon crawler
** Arithmetic quiz and tables - for kids learning their math facts
** Paint
** Drawing shapes - regular polygons, stars, fractals
** Board game - tic tac toe, connect 4, chess, you name it
** Calculator - with usual operations but also with your own cutsom ones

== Other Helpful Resources ==
* [https://developer.android.com/ Make Android applications]
* [https://developer.apple.com/ Make iOS applications]
* [https://www.jetbrains.com/student Development tools for students]

Beginning Programming

2026-06-04T19:41:16Z

Jkinne: /* Computing majors */

== Computing majors ==
If you are interested in computing, at ISU your options are Computer Science, Information Technology, Cyber & Security Studies, Computer and Electrical Engineering Technology. There is a fair amount of overlap, but roughly - (a) CS is mostly about making software and making it efficient, (b) IT is about managing computer systems and networks, (c) CSS at ISU is in the School of Criminology and has a large focus in criminology / social science, (d) CEET more involves the hardware / circuits. The most common job titles for those graduating from CS are - programmer/developer/software engineer of various kinds (web, database, network, systems, ...). If you do not want to be a programmer, consider whether CS, IT, CSS, or CEET would best suit you.

== CS at ISU ==
Most programs that are called "Computer Science" have a common core in common so that you should get a similar experience at most universities that offer CS. After finishing any CS program (including at ISU), you should be a decent programmer in a few different programming languages, can use the right data structures and algorithms for different problems, understand precisely how modern software systems (e.g., operating systems, web servers, 3d graphics) work and are programmed, and have completed a few nicely sized software projects.

But each CS department has its own personality. CS at ISU is more unix-oriented than Windows-oriented, and gets you experience with both low-level and high-level programming. After finishing at ISU you should be very familiar with unix/linux, and be a decent programmer in Python, C, javascript, php, and sql. You should be familiar with a number of other programming languages (Java, a few others).

== Getting Ready ==
If you have done some work in computing before and want to do something extra to get ready for CS at ISU, here are a few things you can do.

* http://code.org - go do some of their tutorials. These are mostly aimed at middle-school aged students, but is great experience and fun.
* http://hackerrank.com - create an account and start doing basic programming problems. This site is great because your answer won't be accepted until it is 100% correct.
* [https://www.youtube.com/playlist?list=PLCFNfZsc2MIByWxTX2Zjg0wJpk1YXbcQ8 CS 151] - check out Jeff Kinne's video lectures from CS 151, the first course in our major.
* [https://www.youtube.com/playlist?list=PLXFP6J47Bp0fxKk5q6V_K2_3DkPIdGmMf AI] - video playlist from high school summer honors course at ISU from 2017.
* Get a copy of Introduction to Algorithms (any edition) and start perusing it.
* http://appinventor.mit.edu/explore/ - make apps for Android.
* See our [[Help and Getting Started]] page and [http://cs.indstate.edu/info/learn.html Learn].
* Install linux on one of your home computers (Ubuntu and Mint are pretty easy to use). Note - do it on a computer that doesn't have any important data on it... You can also do this by first installing VirtualBox in your current operating system and then install linux inside of that.
* Some key ideas in CS and examples -
** Algorithm - linear search vs. binary search, selection sort vs. merge sort, euclid's algorithm vs. trial division
** Proof - there are infinitely many primes, the halting problem is uncomputable, the square root of 2 is irrational, the sum of an arithmetic series [1 + 2 + ... + n = n*(n+1)/2]
** Data speeds - tape vs. hard disk drive vs. RAM vs. CPU cache vs. CPU registers
** Abstraction - operating system virtual memory, RAID, object-oriented programming, file system, any API, any programming language
** Assembly language - [https://en.wikipedia.org/wiki/Little_man_computer little man computer] ([http://robowriter.info/little-man-computer/ simulator])
* Some classic beginning programming projects -
** Encryption - Caesar cipher, substitution cipher, Vigenere, RSA, and others
** Letter and word frequency - used in breaking substitution cipher, used in AI
** Chatbot - responds in a reasonable way to many text, see Eliza ("the doctor")
** Choose your adventure game
** 2d maze/dungeon crawler
** Arithmetic quiz and tables - for kids learning their math facts
** Paint
** Drawing shapes - regular polygons, stars, fractals
** Board game - tic tac toe, connect 4, chess, you name it
** Calculator - with usual operations but also with your own cutsom ones

== Other Helpful Resources ==
* [https://developer.android.com/ Make Android applications]
* [https://developer.apple.com/ Make iOS applications]
* [https://www.jetbrains.com/student Development tools for students]

ISU Computer Science

2026-06-04T19:39:07Z

Jkinne: /* More information */

This wiki is used to keep detailed information related to the CS programs at ISU. If you want to see marketing information about CS at ISU, you can go to the [https://indianastate.edu/ ISU home page] and do a search for computer science.

==Main links/information==

'''Contact/people''' - [[ISU CS People]], [https://cs.indstate.edu/web/index.php/ISU_CS_People#CS_Departmental_Graduate_Assistants GA Office Hours]

'''Admissions''' - [[Undergraduate Admissions]], [[Graduate Admissions]], [[For New Graduate Students]]

'''CS Programs''' - [[CS Programs]] ([https://catalog.indstate.edu/preview_program.php?catoid=67&poid=12305&returnto=4228 BS], [https://catalog.indstate.edu/preview_program.php?catoid=67&poid=12306&returnto=4228 minor], [https://catalog.indstate.edu/preview_program.php?catoid=67&poid=12279&returnto=4228 certificate], [https://catalog.indstate.edu/preview_program.php?catoid=67&poid=12561&returnto=4228 teaching minor]), ([https://catalog.indstate.edu/preview_program.php?catoid=65&poid=11704&returnto=3879 MS], [https://catalog.indstate.edu/preview_program.php?catoid=67&poid=12632&returnto=4228 4+1 MS])

'''Advising''' - [[Undergraduate Advising]], [[Graduate Advising]], [[Courses]] ( [https://cs.indstate.edu/info/course_schedule.php class schedule], [https://catalog.indstate.edu/content.php?filter%5B27%5D=CS&filter%5B29%5D=&filter%5Bcourse_type%5D=-1&filter%5Bkeyword%5D=&filter%5B32%5D=1&filter%5Bcpage%5D=1&cur_cat_oid=67&expand=&navoid=4229&search_database=Filter#acalog_template_course_filter ugrad courses], [https://catalog.indstate.edu/content.php?filter%5B27%5D=CS&filter%5B29%5D=&filter%5Bkeyword%5D=&filter%5B32%5D=1&filter%5Bcpage%5D=1&cur_cat_oid=65&expand=&navoid=3880&search_database=Filter#acalog_template_course_filter grad courses])

[[Start of Term Announcements]], [[Welcome New Students]], [[Course Scheduling Announcements]], [[Statement On Cheating]], '''[[Visit]]'''

==More information==
* [[Policies]]
* [[Procedures]]
* [[FAQ]]
* [[CS Help and Getting Started]]
* [[Programming Practice]]
* [[Giving]]
* [[Careers]]
* Events - '''[[Science Bowl]]''', [[Museum]]
<hr>
Pages that are old and no longer current - [https://cs.indstate.edu/info/cs-homeroom.html IndianaComputes], [http://www.indstate.edu/cas/bd4isu BD4ISU], [http://cs.indstate.edu/acm/ ACM], [https://cs.indstate.edu/info/research.html Research], [https://cs.indstate.edu/acm/contests.html programming contests], [https://www.indstate.edu/cas/chem_phys/summer-undergraduate-research-experiences-sure-program SURE], [[Seminar]]

[[Media_Wiki|Help / Getting Started on Media Wiki]]

Programming and CS - Getting Started

2026-06-03T02:07:24Z

Jkinne: /* Practice Programming Contest Problems */

We are developing Getting Started pages on the most important topics and skills that are used throughout our courses. These can be used by incoming undergraduate students to get a head start, incoming graduate students to review, or current students to refresh/remediate.

=Recommended Computer=
Much of what we do in CS courses can work in Windows, Mac OS, Linux, or Chrome. There will be an odd thing or two still that may not work in Chrome.

All other things being equal, getting a computer that is not "bottom of the barrel" would be good. Chromebooks in the $400+ range should generally work reasonably well. For Windows/Linux/Mac OS laptops, you should be looking for 8GB RAM bare minimum, preferred 16GB if possible, and avoid getting a laptop with an i3 or Celeron processor; this roughly corresponds to the $500+ price range. You can potentially get anything to work, but will have an easier time with a medium-range computer than a low-end system.

For laptops, we recommend getting at least a 3 year warranty (since they tend to break if you actually do transport them around). Also, we recommend getting an option that has a long battery life (rule of thumb - battery life will be half of its original rating after 1-2 years of regular daily use).

You should also have the ability to install programs on the system and have a normally reliable internet connection at home if possible.

If you have a particular system in mind for purchase that you would like an opinion on, please feel free to contact one of the CS faculty members.

University recommendations are listed [https://indstate.teamdynamix.com/TDClient/1851/Portal/KB/Article/71665/Student-Laptop-Minimum-Specifications here] and are similar to that described above.

=Getting Started Pages=
* [[Linux and CS Systems - Getting Started]]
* [[Python Programming - Getting Started]]
* [[C Programming - Getting Started]]
* [[R Programming - Getting Started]]
* [[Algorithms and Data Structures - Getting Started]]
* [[Gitlab - Getting Started]]

=Practice Programming Contest Problems=
See [[Programming Practice]].

= Source Control =
It is a good idea to use source control when developing software, and is necessary when you are developing in a group or professionally. When working on assignments or course projects it is the best practice to use a private repository so other students cannot copy your work. Git is the industry standard for source control. Here are some resources to use to learn Git.

* https://try.github.io/
* https://learngitbranching.js.org/
* https://www.atlassian.com/git

Programming and CS - Getting Started

2026-06-03T02:06:36Z

Jkinne: /* Getting Started Pages */

We are developing Getting Started pages on the most important topics and skills that are used throughout our courses. These can be used by incoming undergraduate students to get a head start, incoming graduate students to review, or current students to refresh/remediate.

=Recommended Computer=
Much of what we do in CS courses can work in Windows, Mac OS, Linux, or Chrome. There will be an odd thing or two still that may not work in Chrome.

All other things being equal, getting a computer that is not "bottom of the barrel" would be good. Chromebooks in the $400+ range should generally work reasonably well. For Windows/Linux/Mac OS laptops, you should be looking for 8GB RAM bare minimum, preferred 16GB if possible, and avoid getting a laptop with an i3 or Celeron processor; this roughly corresponds to the $500+ price range. You can potentially get anything to work, but will have an easier time with a medium-range computer than a low-end system.

For laptops, we recommend getting at least a 3 year warranty (since they tend to break if you actually do transport them around). Also, we recommend getting an option that has a long battery life (rule of thumb - battery life will be half of its original rating after 1-2 years of regular daily use).

You should also have the ability to install programs on the system and have a normally reliable internet connection at home if possible.

If you have a particular system in mind for purchase that you would like an opinion on, please feel free to contact one of the CS faculty members.

University recommendations are listed [https://indstate.teamdynamix.com/TDClient/1851/Portal/KB/Article/71665/Student-Laptop-Minimum-Specifications here] and are similar to that described above.

=Getting Started Pages=
* [[Linux and CS Systems - Getting Started]]
* [[Python Programming - Getting Started]]
* [[C Programming - Getting Started]]
* [[R Programming - Getting Started]]
* [[Algorithms and Data Structures - Getting Started]]
* [[Gitlab - Getting Started]]

=Practice Programming Contest Problems=
These are problems with precisely defined correct output, so that you can submit your program to make sure it is 100% correct.

* [http://www.hackerrank.com/ Hacker Rank] - very user-friendly, different programming languages available, different categories of questions
* [https://open.kattis.com/problems Practice problems] at open.kattis.com (sort by difficulty or solved % to try the easiest ones first)
* [http://cs.indstate.edu/acm/contests.html ISU ACM Club's Contest Problem page]
* [http://cs.indstate.edu/~jkinne/Cpractice/ A few simple practice problems], with solutions to some on the CS server. See the .txt files.

= Source Control =
It is a good idea to use source control when developing software, and is necessary when you are developing in a group or professionally. When working on assignments or course projects it is the best practice to use a private repository so other students cannot copy your work. Git is the industry standard for source control. Here are some resources to use to learn Git.

* https://try.github.io/
* https://learngitbranching.js.org/
* https://www.atlassian.com/git

Programming and CS - Getting Started

2026-06-03T02:06:16Z

Jkinne: /* Recommended Computer */

We are developing Getting Started pages on the most important topics and skills that are used throughout our courses. These can be used by incoming undergraduate students to get a head start, incoming graduate students to review, or current students to refresh/remediate.

=Recommended Computer=
Much of what we do in CS courses can work in Windows, Mac OS, Linux, or Chrome. There will be an odd thing or two still that may not work in Chrome.

All other things being equal, getting a computer that is not "bottom of the barrel" would be good. Chromebooks in the $400+ range should generally work reasonably well. For Windows/Linux/Mac OS laptops, you should be looking for 8GB RAM bare minimum, preferred 16GB if possible, and avoid getting a laptop with an i3 or Celeron processor; this roughly corresponds to the $500+ price range. You can potentially get anything to work, but will have an easier time with a medium-range computer than a low-end system.

For laptops, we recommend getting at least a 3 year warranty (since they tend to break if you actually do transport them around). Also, we recommend getting an option that has a long battery life (rule of thumb - battery life will be half of its original rating after 1-2 years of regular daily use).

You should also have the ability to install programs on the system and have a normally reliable internet connection at home if possible.

If you have a particular system in mind for purchase that you would like an opinion on, please feel free to contact one of the CS faculty members.

University recommendations are listed [https://indstate.teamdynamix.com/TDClient/1851/Portal/KB/Article/71665/Student-Laptop-Minimum-Specifications here] and are similar to that described above.

=Getting Started Pages=
* [[Linux and CS Systems - Getting Started]]
* [[Handin|Handin - The CS Assignment Handin System]]
* [[Python Programming - Getting Started]]
* [[C Programming - Getting Started]]
* [[R Programming - Getting Started]]
* [[Algorithms and Data Structures - Getting Started]]
* [[Gitlab - Getting Started]]

=Practice Programming Contest Problems=
These are problems with precisely defined correct output, so that you can submit your program to make sure it is 100% correct.

* [http://www.hackerrank.com/ Hacker Rank] - very user-friendly, different programming languages available, different categories of questions
* [https://open.kattis.com/problems Practice problems] at open.kattis.com (sort by difficulty or solved % to try the easiest ones first)
* [http://cs.indstate.edu/acm/contests.html ISU ACM Club's Contest Problem page]
* [http://cs.indstate.edu/~jkinne/Cpractice/ A few simple practice problems], with solutions to some on the CS server. See the .txt files.

= Source Control =
It is a good idea to use source control when developing software, and is necessary when you are developing in a group or professionally. When working on assignments or course projects it is the best practice to use a private repository so other students cannot copy your work. Git is the industry standard for source control. Here are some resources to use to learn Git.

* https://try.github.io/
* https://learngitbranching.js.org/
* https://www.atlassian.com/git

CS accounts

2026-06-03T02:02:42Z

Jkinne: /* Spring 2026 */

This page gives information about logging into and using the CS server (cs.indstate.edu). For help about getting started with using the terminal once you can login, see [[Linux and CS Systems - Getting Started]].

=Logging In=
The CS server is a Linux server. The primary ways you will login to the server is either (a) with a terminal (aka shell) that allows you to type text commands, or (b) with an sftp program to transfer files between your computer and the server. In either case, you need a username (aka login) and password. There are two types of accounts on the system - ISU portal accounts, and local accounts.

==ISU Portal Accounts==
Any student/faculty/staff who is involved in CS courses or programs (enrolled in a course, teaching a course, etc.) can login to cs.indstate.edu using their full ISU email address and portal password. The first time you login to the system, an account is created on the system that you can use. It will set your home directory on the system to <code>/home/SID@isuad.indstate.edu/</code> where <code>SID</code> is your portal id (aka sycamore id - for students it is the part before the @sycamores in your email address). After logging in, you can run the <code>pwd</code> command to see this.

For those familiar with Linux already... Note that there is not currently "finger information" about ISU portal account users. In fact, trying to run something like "finger jkinne@isuad.indstate.edu" will fail. Note that instructors of current courses can get a class list (aka roster) of accounts for their course; see below.

==Local Accounts==
Some users will have accounts on the CS server that are not tied to their ISU portal accounts. For example, CS faculty have local accounts, and a number of users of the server prior to 2025 have local accounts. These are accounts with username and password that were created just on the server (the ability to login to the server with ISU portal credentials was added in 2025). Any new instructor teaching a CS course can ask for a local account if you do not have one already - write to root@cs.indstate.edu.

==SSH Key==
You can setup an SSH key to login to the system. You will first need to login to the system normally. Once you are logged in, you can run the following commands.
<pre>
mkdir ~/.ssh # in case it does not exist yet
chmod 700 ~/.ssh # make sure this directory is not accessible to other users
ssh-keygen # create keys for logging in
</pre>
You will then transfer the private key file (the one that does not end in .pub) to your local computer in the location for ssh keys. This varies depending on your operating system. On Linux and Mac OS, it will be in <code>~/.ssh</code>.

= CS Server Policies =
== Prohibitions ==
For any accounts that you have on the CS server, you should follow all ISU policies. In particular the following are prohibited -
* using your account to store or distribute anything that is against its terms/copyright/etc. (e.g., no movies, textbooks, answers to HW problems)
* using your account to do anything that is illegal
* using a password that is too easy to guess (i.e., a password cracker that we run finds your password)
* overloading the CPU or GPU of the system, or filling up any of the system drives
* anything that is along these lines that we have not thought to state explicitly
A violation of any of these will result in your account being locked and no longer being allowed to have an account on the systems.

== Inactivity ==
Accounts that are not used for a period of 6 months will likely be locked as a security precaution. You can write to root@cs.indstate.edu to ask to have your account unlocked again.

=Student Use and Course Account=
For courses that are currently being offered, if the course uses the server, a class account is created that the instructor of the course can use if they like. This is explained in this section with two examples: CS 151 Intro to Computer Science, and CS 473/573 Computer Networks.

==Course Account==
An account on the system is created where files for the class can be kept that are to be shared with the students. For CS 151, the account created has username <code>cs151</code>. For CS 473/573, a single account, <code>cs473</code>, is created that is to be used for both courses.

==Student Use==
For students who are currently enrolled in a CS course that uses the server, the first time you login to the system with your ISU portal account, a directory should be created within your account for the course. For example, students in CS 151 will have a directory <code>cs151</code>, and students in CS 473/573 will have a directory <code>cs473</code>.

Permissions are set on the system so that instructors of the course have read access to the files within student's course directories for their courses. The instructor for CS 151 will have read access to the <code>cs151</code> directories of the students enrolled in CS 151; the instructor for CS 473/573 will have read access to the <code>cs473</code> directories of the students enrolled in CS 473/573; etc. The instructor of the course might have the students submit their work on the server within these directories. Each instructor can choose how they would like to do this.

The course account for each course also has read access to the directories for that course. For example, the <code>cs151</code> account will have read access to the <code>cs151</code> directories within any student enrolled in CS 151.

==Course Account - Instructor Private Files==
The course account is created with a <code>~/private</code> directory that is not accessible to other users (i.e., not accessible to students). The class list (aka roster) of students and their accounts is put into this directory (<code>classlist_brief.csv</code> with the most important information for each student, and <code>classlist_full.csv</code> with more information). The instructor could keep other files in this <code>private</code> directory that is meant to be private (e.g., model solutions or grading information).

Inside the <code>~/private/</code> directory of the course account, there is also a <code>students</code> directory that has symbolic links to each of the student's course directories in the course. For example, if the course is cs151, and if the user jdoe12345@isuad.indstate.edu is a student in the course, then there will be a link <code>/home/cs151/private/students/jdoe12345@isuad.indstate.edu</code> that is a link to the cs151 directory for this student (<code>/home/jdoe12345@isuad.indstate.edu/cs151/</code>). The instructor for the course can quickly get into the students' directories for the course (but not their home directory) by going to the private/students/ directory and going from there.

The accounts for the instructors of the course are set so they can sudo as the course account. If the instructor of CS 151 uses the local account <code>jkinne</code> then this user can run the following command to get a shell running as the CS 151 course account: <code>sudo -u cs151 -i</code>.
Note that this only works for local accounts, and does not work for ISU Portal accounts (it might work for the jkinne local account but not for the jkinne@isuad.indstate.edu account).

====Change of Semester and Backups====
Before the next semester, a backup copy of each course account will be created that will be in the course's <code>~/private/backup/</code> directory. A directory will be created for the term, and it will have all of the course account's files from that term within it.

Once the backup has been created for the previous term, the instructor for the current semester can remove files and directories that are no longer needed for the new term. For example, you can clear out the assignment directories in the course account's home directory, and also the student submissions that are in <code>~/private/submissions/</code>. Those files will still be in the backup directory in case you need them later.

When the new semester starts (if the course is running in the new semester), the following in the <code>~/private</code> directory will be updated to be for the new term: classlist_brief.csv, classlist_full.csv, students directory (symbolic links to new semester's students).

==Assignments==
Any directory within the course account can be used as an assignment. For example, suppose the account <code>cs151</code> contains a directory <code>h7</code>. This directory might have files for the students to use on the assignment; they can view these files by going to the directory <code>/home/cs151/h7/</code>.

A student can "checkout" or "get" an assignment by running
<pre>hw_get.py cs151 h7</pre>
This will copy the <code>h7</code> directory that is in the <code>cs151</code> account into the <code>cs151</code> directory of the user that executes the command.

An instructor can collect an assignment by running the script <code>hw_collect.py</code>. For the above example, the instructor would run: <code>hw_collect.py cs151 h7</code>. This will go into each student in the course's <code>cs151</code> directory and copy their h7 directory into <code>/home/cs151/private/submissions/h7/</code>. There will be a new directory in that submissions directory for the date and time the submissions were collected. For example, if the user jdoe12345@isuad.indstate.edu is in the cs151 course, then the contents of <code>/home/jdoe12345@isuad.indstate.edu/h7/</code> will be copied into the submission directory (inside of <code>/home/cs151/private/submissions/h7/</code>). The directory <code>/home/cs151/private/submissions/h7/</code> will have a symbolic link <code>latest</code> that is a pointer to the latest submission.

There is a system in place that can be used for auto-checking the output of student programs. The instructor creates a file <code>.tests.json</code> inside of the assignment directory that has the test cases. The instructor will also need to create a correct working version of each program that can be run to get the "correct" results. The students will use the <code>hw_check.py</code> command to check their output. The instructor can also use the same command to check student submissions. You can get more details about how this works by logging into the system and running: <code>hw_check.py --help</code>.

=Websites / Webservers=
==Apache==
The main cs.indstate.edu website uses the Apache web server. This is configured so that any user can put html and php files in the right directory in their account to be on the web server. Jeff Kinne, who has portal id <code>jkinne</code> and therefore account on the server with home directory <code>jkinne@isuad.indstate.edu</code>, would do the following to create the right directories.
<pre>
cd ~jkinne@isuad.indstate.edu # jkinne's home directory
mkdir public_html # directory apache looks in for website files
setfacl -m group:www-data:x . # give apache execute access to home directory
setfacl -R -m group:www-data:rX public_html # give apache rX access to public_html
setfacl -R -m default:group:www-data:rX public_html # and new files will also have access
cd public_html # go into that directory
echo "Hello world" > index.html # write a hello world file
</pre>
Then the file index.html will be accessible on the web at https://cs.indstate.edu/~jkinne@isuad.indstate.edu. Since the web server is Apache, you can look for help on the Apache web server about configuration options (in particular .htaccess files that you can put in your public_html directory to change some settings). By default, the Apache web server understands html and php files. There may be other types of files you would want it to be able to understand; if so you can write to root@cs.indstate.edu.

==Node, Django, etc.==
Node, Django, and many other web server frameworks can also be run off of the CS server. These generally will pick a port that they will run off of, and you run the main file for your server. Note that the Apache web server uses the "standard" ports (80 for http and 443 for https), so you cannot use those. If you want to run a Node, Django, or similar web server off of the CS server, you need to pick a port that isn't used for anything else. You should never pick a port number that is below 1024 and really should avoid port numbers below 10000. If you want to make sure to pick a port that will not interfere with anything, write to root@cs.indstate.edu. If you were to run your node web server with port 60000, then you would browse to it on the web at https://cs.indstate.edu:60000. Note that there is indeed normally a node server running on that particular port.

=Spring 2026=
The following is the list of courses that are supported on the server for the 2026 spring, along with the instructor accounts (aka admin accounts) for each course.
<pre>
course,admin_accounts
cs151,"jkinne,jeff,jkinne@isuad.indstate.edu"
cs170,"hrafieipour@isuad.indstate.edu"
cs201,"majid,mafsharnoghon@isuad.indstate.edu"
cs203,"namoako,namoako@isuad.indstate.edu"
cs211,"mjenkins1@isuad.indstate.edu"
cs351,"rabhyankar@isuad.indstate.edu"
cs331,"namoako,namoako@isuad.indstate.edu"
"cs401,cs501","majid,mafsharnoghon@isuad.indstate.edu"
cs401L,"majid,mafsharnoghon@isuad.indstate.edu"
"cs456,cs556","jcompton5,jcompton5@isuad.indstate.edu"
cs456L,"jcompton5,jcompton5@isuad.indstate.edu"
"cs457,cs557","kwexoo,kexoo@isuad.indstate.edu"
cs457L,"kwexoo,kexoo@isuad.indstate.edu"
"cs458,cs558","namoako,namoako@isuad.indstate.edu"
cs458L,"namoako,namoako@isuad.indstate.edu"
"cs469,cs569","katterson1,katterson1@isuad.indstate.edu"
"cs475,cs575","rabhyankar@isuad.indstate.edu"
cs500,"jkinne,jeff,jkinne@isuad.indstate.edu"
cs600,"arash,arafiey@isuad.indstate.edu"
"cs601,cs417","majid,mafsharnoghon@isuad.indstate.edu"
cs609,"katterson1,katterson1@isuad.indstate.edu"
cs611,"rabhyankar@isuad.indstate.edu"
cs618,"shosseini@isuad.indstate.edu"
cs685,"arash,arafiey@isuad.indstate.edu"
cs695,"arash,arafiey@isuad.indstate.edu"
ect438,"jkinne,jeff,jkinne@isuad.indstate.edu"
</pre>
If any course instructors would like any additions, subtractions, or changes to these, let the sys-admin know.

CS accounts

2026-06-03T02:00:23Z

Jkinne: /* Assignments */

This page gives information about logging into and using the CS server (cs.indstate.edu). For help about getting started with using the terminal once you can login, see [[Linux and CS Systems - Getting Started]].

=Logging In=
The CS server is a Linux server. The primary ways you will login to the server is either (a) with a terminal (aka shell) that allows you to type text commands, or (b) with an sftp program to transfer files between your computer and the server. In either case, you need a username (aka login) and password. There are two types of accounts on the system - ISU portal accounts, and local accounts.

==ISU Portal Accounts==
Any student/faculty/staff who is involved in CS courses or programs (enrolled in a course, teaching a course, etc.) can login to cs.indstate.edu using their full ISU email address and portal password. The first time you login to the system, an account is created on the system that you can use. It will set your home directory on the system to <code>/home/SID@isuad.indstate.edu/</code> where <code>SID</code> is your portal id (aka sycamore id - for students it is the part before the @sycamores in your email address). After logging in, you can run the <code>pwd</code> command to see this.

For those familiar with Linux already... Note that there is not currently "finger information" about ISU portal account users. In fact, trying to run something like "finger jkinne@isuad.indstate.edu" will fail. Note that instructors of current courses can get a class list (aka roster) of accounts for their course; see below.

==Local Accounts==
Some users will have accounts on the CS server that are not tied to their ISU portal accounts. For example, CS faculty have local accounts, and a number of users of the server prior to 2025 have local accounts. These are accounts with username and password that were created just on the server (the ability to login to the server with ISU portal credentials was added in 2025). Any new instructor teaching a CS course can ask for a local account if you do not have one already - write to root@cs.indstate.edu.

==SSH Key==
You can setup an SSH key to login to the system. You will first need to login to the system normally. Once you are logged in, you can run the following commands.
<pre>
mkdir ~/.ssh # in case it does not exist yet
chmod 700 ~/.ssh # make sure this directory is not accessible to other users
ssh-keygen # create keys for logging in
</pre>
You will then transfer the private key file (the one that does not end in .pub) to your local computer in the location for ssh keys. This varies depending on your operating system. On Linux and Mac OS, it will be in <code>~/.ssh</code>.

= CS Server Policies =
== Prohibitions ==
For any accounts that you have on the CS server, you should follow all ISU policies. In particular the following are prohibited -
* using your account to store or distribute anything that is against its terms/copyright/etc. (e.g., no movies, textbooks, answers to HW problems)
* using your account to do anything that is illegal
* using a password that is too easy to guess (i.e., a password cracker that we run finds your password)
* overloading the CPU or GPU of the system, or filling up any of the system drives
* anything that is along these lines that we have not thought to state explicitly
A violation of any of these will result in your account being locked and no longer being allowed to have an account on the systems.

== Inactivity ==
Accounts that are not used for a period of 6 months will likely be locked as a security precaution. You can write to root@cs.indstate.edu to ask to have your account unlocked again.

=Student Use and Course Account=
For courses that are currently being offered, if the course uses the server, a class account is created that the instructor of the course can use if they like. This is explained in this section with two examples: CS 151 Intro to Computer Science, and CS 473/573 Computer Networks.

==Course Account==
An account on the system is created where files for the class can be kept that are to be shared with the students. For CS 151, the account created has username <code>cs151</code>. For CS 473/573, a single account, <code>cs473</code>, is created that is to be used for both courses.

==Student Use==
For students who are currently enrolled in a CS course that uses the server, the first time you login to the system with your ISU portal account, a directory should be created within your account for the course. For example, students in CS 151 will have a directory <code>cs151</code>, and students in CS 473/573 will have a directory <code>cs473</code>.

Permissions are set on the system so that instructors of the course have read access to the files within student's course directories for their courses. The instructor for CS 151 will have read access to the <code>cs151</code> directories of the students enrolled in CS 151; the instructor for CS 473/573 will have read access to the <code>cs473</code> directories of the students enrolled in CS 473/573; etc. The instructor of the course might have the students submit their work on the server within these directories. Each instructor can choose how they would like to do this.

The course account for each course also has read access to the directories for that course. For example, the <code>cs151</code> account will have read access to the <code>cs151</code> directories within any student enrolled in CS 151.

==Course Account - Instructor Private Files==
The course account is created with a <code>~/private</code> directory that is not accessible to other users (i.e., not accessible to students). The class list (aka roster) of students and their accounts is put into this directory (<code>classlist_brief.csv</code> with the most important information for each student, and <code>classlist_full.csv</code> with more information). The instructor could keep other files in this <code>private</code> directory that is meant to be private (e.g., model solutions or grading information).

Inside the <code>~/private/</code> directory of the course account, there is also a <code>students</code> directory that has symbolic links to each of the student's course directories in the course. For example, if the course is cs151, and if the user jdoe12345@isuad.indstate.edu is a student in the course, then there will be a link <code>/home/cs151/private/students/jdoe12345@isuad.indstate.edu</code> that is a link to the cs151 directory for this student (<code>/home/jdoe12345@isuad.indstate.edu/cs151/</code>). The instructor for the course can quickly get into the students' directories for the course (but not their home directory) by going to the private/students/ directory and going from there.

The accounts for the instructors of the course are set so they can sudo as the course account. If the instructor of CS 151 uses the local account <code>jkinne</code> then this user can run the following command to get a shell running as the CS 151 course account: <code>sudo -u cs151 -i</code>.
Note that this only works for local accounts, and does not work for ISU Portal accounts (it might work for the jkinne local account but not for the jkinne@isuad.indstate.edu account).

====Change of Semester and Backups====
Before the next semester, a backup copy of each course account will be created that will be in the course's <code>~/private/backup/</code> directory. A directory will be created for the term, and it will have all of the course account's files from that term within it.

Once the backup has been created for the previous term, the instructor for the current semester can remove files and directories that are no longer needed for the new term. For example, you can clear out the assignment directories in the course account's home directory, and also the student submissions that are in <code>~/private/submissions/</code>. Those files will still be in the backup directory in case you need them later.

When the new semester starts (if the course is running in the new semester), the following in the <code>~/private</code> directory will be updated to be for the new term: classlist_brief.csv, classlist_full.csv, students directory (symbolic links to new semester's students).

==Assignments==
Any directory within the course account can be used as an assignment. For example, suppose the account <code>cs151</code> contains a directory <code>h7</code>. This directory might have files for the students to use on the assignment; they can view these files by going to the directory <code>/home/cs151/h7/</code>.

A student can "checkout" or "get" an assignment by running
<pre>hw_get.py cs151 h7</pre>
This will copy the <code>h7</code> directory that is in the <code>cs151</code> account into the <code>cs151</code> directory of the user that executes the command.

An instructor can collect an assignment by running the script <code>hw_collect.py</code>. For the above example, the instructor would run: <code>hw_collect.py cs151 h7</code>. This will go into each student in the course's <code>cs151</code> directory and copy their h7 directory into <code>/home/cs151/private/submissions/h7/</code>. There will be a new directory in that submissions directory for the date and time the submissions were collected. For example, if the user jdoe12345@isuad.indstate.edu is in the cs151 course, then the contents of <code>/home/jdoe12345@isuad.indstate.edu/h7/</code> will be copied into the submission directory (inside of <code>/home/cs151/private/submissions/h7/</code>). The directory <code>/home/cs151/private/submissions/h7/</code> will have a symbolic link <code>latest</code> that is a pointer to the latest submission.

There is a system in place that can be used for auto-checking the output of student programs. The instructor creates a file <code>.tests.json</code> inside of the assignment directory that has the test cases. The instructor will also need to create a correct working version of each program that can be run to get the "correct" results. The students will use the <code>hw_check.py</code> command to check their output. The instructor can also use the same command to check student submissions. You can get more details about how this works by logging into the system and running: <code>hw_check.py --help</code>.

=Websites / Webservers=
==Apache==
The main cs.indstate.edu website uses the Apache web server. This is configured so that any user can put html and php files in the right directory in their account to be on the web server. Jeff Kinne, who has portal id <code>jkinne</code> and therefore account on the server with home directory <code>jkinne@isuad.indstate.edu</code>, would do the following to create the right directories.
<pre>
cd ~jkinne@isuad.indstate.edu # jkinne's home directory
mkdir public_html # directory apache looks in for website files
setfacl -m group:www-data:x . # give apache execute access to home directory
setfacl -R -m group:www-data:rX public_html # give apache rX access to public_html
setfacl -R -m default:group:www-data:rX public_html # and new files will also have access
cd public_html # go into that directory
echo "Hello world" > index.html # write a hello world file
</pre>
Then the file index.html will be accessible on the web at https://cs.indstate.edu/~jkinne@isuad.indstate.edu. Since the web server is Apache, you can look for help on the Apache web server about configuration options (in particular .htaccess files that you can put in your public_html directory to change some settings). By default, the Apache web server understands html and php files. There may be other types of files you would want it to be able to understand; if so you can write to root@cs.indstate.edu.

==Node, Django, etc.==
Node, Django, and many other web server frameworks can also be run off of the CS server. These generally will pick a port that they will run off of, and you run the main file for your server. Note that the Apache web server uses the "standard" ports (80 for http and 443 for https), so you cannot use those. If you want to run a Node, Django, or similar web server off of the CS server, you need to pick a port that isn't used for anything else. You should never pick a port number that is below 1024 and really should avoid port numbers below 10000. If you want to make sure to pick a port that will not interfere with anything, write to root@cs.indstate.edu. If you were to run your node web server with port 60000, then you would browse to it on the web at https://cs.indstate.edu:60000. Note that there is indeed normally a node server running on that particular port.

=Spring 2026=
The following is the list of courses that are supported on the server for the fall 2025, along with the instructor accounts (aka admin accounts) for each course.
<pre>
course,admin_accounts
cs151,"jkinne,jeff,jkinne@isuad.indstate.edu"
cs170,"hrafieipour@isuad.indstate.edu"
cs201,"majid,mafsharnoghon@isuad.indstate.edu"
cs203,"namoako,namoako@isuad.indstate.edu"
cs211,"mjenkins1@isuad.indstate.edu"
cs351,"rabhyankar@isuad.indstate.edu"
cs331,"namoako,namoako@isuad.indstate.edu"
"cs401,cs501","majid,mafsharnoghon@isuad.indstate.edu"
cs401L,"majid,mafsharnoghon@isuad.indstate.edu"
"cs456,cs556","jcompton5,jcompton5@isuad.indstate.edu"
cs456L,"jcompton5,jcompton5@isuad.indstate.edu"
"cs457,cs557","kwexoo,kexoo@isuad.indstate.edu"
cs457L,"kwexoo,kexoo@isuad.indstate.edu"
"cs458,cs558","namoako,namoako@isuad.indstate.edu"
cs458L,"namoako,namoako@isuad.indstate.edu"
"cs469,cs569","katterson1,katterson1@isuad.indstate.edu"
"cs475,cs575","rabhyankar@isuad.indstate.edu"
cs500,"jkinne,jeff,jkinne@isuad.indstate.edu"
cs600,"arash,arafiey@isuad.indstate.edu"
"cs601,cs417","majid,mafsharnoghon@isuad.indstate.edu"
cs609,"katterson1,katterson1@isuad.indstate.edu"
cs611,"rabhyankar@isuad.indstate.edu"
cs618,"shosseini@isuad.indstate.edu"
cs685,"arash,arafiey@isuad.indstate.edu"
cs695,"arash,arafiey@isuad.indstate.edu"
ect438,"jkinne,jeff,jkinne@isuad.indstate.edu"
</pre>
If any course instructors would like any additions, subtractions, or changes to these, let the sys-admin know.

CS accounts

2026-06-03T01:58:20Z

Jkinne: /* Assignments */

This page gives information about logging into and using the CS server (cs.indstate.edu). For help about getting started with using the terminal once you can login, see [[Linux and CS Systems - Getting Started]].

=Logging In=
The CS server is a Linux server. The primary ways you will login to the server is either (a) with a terminal (aka shell) that allows you to type text commands, or (b) with an sftp program to transfer files between your computer and the server. In either case, you need a username (aka login) and password. There are two types of accounts on the system - ISU portal accounts, and local accounts.

==ISU Portal Accounts==
Any student/faculty/staff who is involved in CS courses or programs (enrolled in a course, teaching a course, etc.) can login to cs.indstate.edu using their full ISU email address and portal password. The first time you login to the system, an account is created on the system that you can use. It will set your home directory on the system to <code>/home/SID@isuad.indstate.edu/</code> where <code>SID</code> is your portal id (aka sycamore id - for students it is the part before the @sycamores in your email address). After logging in, you can run the <code>pwd</code> command to see this.

For those familiar with Linux already... Note that there is not currently "finger information" about ISU portal account users. In fact, trying to run something like "finger jkinne@isuad.indstate.edu" will fail. Note that instructors of current courses can get a class list (aka roster) of accounts for their course; see below.

==Local Accounts==
Some users will have accounts on the CS server that are not tied to their ISU portal accounts. For example, CS faculty have local accounts, and a number of users of the server prior to 2025 have local accounts. These are accounts with username and password that were created just on the server (the ability to login to the server with ISU portal credentials was added in 2025). Any new instructor teaching a CS course can ask for a local account if you do not have one already - write to root@cs.indstate.edu.

==SSH Key==
You can setup an SSH key to login to the system. You will first need to login to the system normally. Once you are logged in, you can run the following commands.
<pre>
mkdir ~/.ssh # in case it does not exist yet
chmod 700 ~/.ssh # make sure this directory is not accessible to other users
ssh-keygen # create keys for logging in
</pre>
You will then transfer the private key file (the one that does not end in .pub) to your local computer in the location for ssh keys. This varies depending on your operating system. On Linux and Mac OS, it will be in <code>~/.ssh</code>.

= CS Server Policies =
== Prohibitions ==
For any accounts that you have on the CS server, you should follow all ISU policies. In particular the following are prohibited -
* using your account to store or distribute anything that is against its terms/copyright/etc. (e.g., no movies, textbooks, answers to HW problems)
* using your account to do anything that is illegal
* using a password that is too easy to guess (i.e., a password cracker that we run finds your password)
* overloading the CPU or GPU of the system, or filling up any of the system drives
* anything that is along these lines that we have not thought to state explicitly
A violation of any of these will result in your account being locked and no longer being allowed to have an account on the systems.

== Inactivity ==
Accounts that are not used for a period of 6 months will likely be locked as a security precaution. You can write to root@cs.indstate.edu to ask to have your account unlocked again.

=Student Use and Course Account=
For courses that are currently being offered, if the course uses the server, a class account is created that the instructor of the course can use if they like. This is explained in this section with two examples: CS 151 Intro to Computer Science, and CS 473/573 Computer Networks.

==Course Account==
An account on the system is created where files for the class can be kept that are to be shared with the students. For CS 151, the account created has username <code>cs151</code>. For CS 473/573, a single account, <code>cs473</code>, is created that is to be used for both courses.

==Student Use==
For students who are currently enrolled in a CS course that uses the server, the first time you login to the system with your ISU portal account, a directory should be created within your account for the course. For example, students in CS 151 will have a directory <code>cs151</code>, and students in CS 473/573 will have a directory <code>cs473</code>.

Permissions are set on the system so that instructors of the course have read access to the files within student's course directories for their courses. The instructor for CS 151 will have read access to the <code>cs151</code> directories of the students enrolled in CS 151; the instructor for CS 473/573 will have read access to the <code>cs473</code> directories of the students enrolled in CS 473/573; etc. The instructor of the course might have the students submit their work on the server within these directories. Each instructor can choose how they would like to do this.

The course account for each course also has read access to the directories for that course. For example, the <code>cs151</code> account will have read access to the <code>cs151</code> directories within any student enrolled in CS 151.

==Course Account - Instructor Private Files==
The course account is created with a <code>~/private</code> directory that is not accessible to other users (i.e., not accessible to students). The class list (aka roster) of students and their accounts is put into this directory (<code>classlist_brief.csv</code> with the most important information for each student, and <code>classlist_full.csv</code> with more information). The instructor could keep other files in this <code>private</code> directory that is meant to be private (e.g., model solutions or grading information).

Inside the <code>~/private/</code> directory of the course account, there is also a <code>students</code> directory that has symbolic links to each of the student's course directories in the course. For example, if the course is cs151, and if the user jdoe12345@isuad.indstate.edu is a student in the course, then there will be a link <code>/home/cs151/private/students/jdoe12345@isuad.indstate.edu</code> that is a link to the cs151 directory for this student (<code>/home/jdoe12345@isuad.indstate.edu/cs151/</code>). The instructor for the course can quickly get into the students' directories for the course (but not their home directory) by going to the private/students/ directory and going from there.

The accounts for the instructors of the course are set so they can sudo as the course account. If the instructor of CS 151 uses the local account <code>jkinne</code> then this user can run the following command to get a shell running as the CS 151 course account: <code>sudo -u cs151 -i</code>.
Note that this only works for local accounts, and does not work for ISU Portal accounts (it might work for the jkinne local account but not for the jkinne@isuad.indstate.edu account).

====Change of Semester and Backups====
Before the next semester, a backup copy of each course account will be created that will be in the course's <code>~/private/backup/</code> directory. A directory will be created for the term, and it will have all of the course account's files from that term within it.

Once the backup has been created for the previous term, the instructor for the current semester can remove files and directories that are no longer needed for the new term. For example, you can clear out the assignment directories in the course account's home directory, and also the student submissions that are in <code>~/private/submissions/</code>. Those files will still be in the backup directory in case you need them later.

When the new semester starts (if the course is running in the new semester), the following in the <code>~/private</code> directory will be updated to be for the new term: classlist_brief.csv, classlist_full.csv, students directory (symbolic links to new semester's students).

==Assignments==
Any directory within the course account can be used as an assignment. For example, suppose the account <code>cs151</code> contains a directory <code>h7</code>. This directory might have files for the students to use on the assignment; they can view these files by going to the directory <code>/home/cs151/h7/</code>.

A student can "checkout" or "get" an assignment by running
<pre>hw_get.py cs151 h7</pre>
This will copy the <code>h7</code> directory that is in the <code>cs151</code> account into the <code>cs151</code> directory of the user that executes the command.

An instructor can collect an assignment by running the script <code>hw_collect.py</code>. For the above example, the instructor would run: <code>hw_collect.py cs151 h7</code>. This will go into each student in the course's <code>cs151</code> directory and copy their h7 directory into <code>/home/cs151/private/submissions/h7/</code>. There will be a new directory in that submissions directory for the date and time the submissions were collected. For example, if the user jdoe12345@isuad.indstate.edu is in the cs151 course, then the contents of <code>/home/jdoe12345@isuad.indstate.edu/h7/</code> will be copied into the submission directory (inside of <code>/home/cs151/private/submissions/h7/</code>). The directory <code>/home/cs151/private/submissions/h7/</code> will have a symbolic link <code>latest</code> that is a pointer to the latest submission.

There is a system in place that can be used for auto-checking the output of student programs. The instructor creates a file <code>.tests.json</code> inside of the assignment directory that has the test cases. The instructor will also need to create a correct working version of each program that can be run to get the "correct" results. The students will use the <code>hw_check.py</code> command to check their output. The instructor can also use the same comment to check student submissions. You can get more details about how this works by logging into the system and running: <code>hw_check.py --help</code>.

=Websites / Webservers=
==Apache==
The main cs.indstate.edu website uses the Apache web server. This is configured so that any user can put html and php files in the right directory in their account to be on the web server. Jeff Kinne, who has portal id <code>jkinne</code> and therefore account on the server with home directory <code>jkinne@isuad.indstate.edu</code>, would do the following to create the right directories.
<pre>
cd ~jkinne@isuad.indstate.edu # jkinne's home directory
mkdir public_html # directory apache looks in for website files
setfacl -m group:www-data:x . # give apache execute access to home directory
setfacl -R -m group:www-data:rX public_html # give apache rX access to public_html
setfacl -R -m default:group:www-data:rX public_html # and new files will also have access
cd public_html # go into that directory
echo "Hello world" > index.html # write a hello world file
</pre>
Then the file index.html will be accessible on the web at https://cs.indstate.edu/~jkinne@isuad.indstate.edu. Since the web server is Apache, you can look for help on the Apache web server about configuration options (in particular .htaccess files that you can put in your public_html directory to change some settings). By default, the Apache web server understands html and php files. There may be other types of files you would want it to be able to understand; if so you can write to root@cs.indstate.edu.

==Node, Django, etc.==
Node, Django, and many other web server frameworks can also be run off of the CS server. These generally will pick a port that they will run off of, and you run the main file for your server. Note that the Apache web server uses the "standard" ports (80 for http and 443 for https), so you cannot use those. If you want to run a Node, Django, or similar web server off of the CS server, you need to pick a port that isn't used for anything else. You should never pick a port number that is below 1024 and really should avoid port numbers below 10000. If you want to make sure to pick a port that will not interfere with anything, write to root@cs.indstate.edu. If you were to run your node web server with port 60000, then you would browse to it on the web at https://cs.indstate.edu:60000. Note that there is indeed normally a node server running on that particular port.

=Spring 2026=
The following is the list of courses that are supported on the server for the fall 2025, along with the instructor accounts (aka admin accounts) for each course.
<pre>
course,admin_accounts
cs151,"jkinne,jeff,jkinne@isuad.indstate.edu"
cs170,"hrafieipour@isuad.indstate.edu"
cs201,"majid,mafsharnoghon@isuad.indstate.edu"
cs203,"namoako,namoako@isuad.indstate.edu"
cs211,"mjenkins1@isuad.indstate.edu"
cs351,"rabhyankar@isuad.indstate.edu"
cs331,"namoako,namoako@isuad.indstate.edu"
"cs401,cs501","majid,mafsharnoghon@isuad.indstate.edu"
cs401L,"majid,mafsharnoghon@isuad.indstate.edu"
"cs456,cs556","jcompton5,jcompton5@isuad.indstate.edu"
cs456L,"jcompton5,jcompton5@isuad.indstate.edu"
"cs457,cs557","kwexoo,kexoo@isuad.indstate.edu"
cs457L,"kwexoo,kexoo@isuad.indstate.edu"
"cs458,cs558","namoako,namoako@isuad.indstate.edu"
cs458L,"namoako,namoako@isuad.indstate.edu"
"cs469,cs569","katterson1,katterson1@isuad.indstate.edu"
"cs475,cs575","rabhyankar@isuad.indstate.edu"
cs500,"jkinne,jeff,jkinne@isuad.indstate.edu"
cs600,"arash,arafiey@isuad.indstate.edu"
"cs601,cs417","majid,mafsharnoghon@isuad.indstate.edu"
cs609,"katterson1,katterson1@isuad.indstate.edu"
cs611,"rabhyankar@isuad.indstate.edu"
cs618,"shosseini@isuad.indstate.edu"
cs685,"arash,arafiey@isuad.indstate.edu"
cs695,"arash,arafiey@isuad.indstate.edu"
ect438,"jkinne,jeff,jkinne@isuad.indstate.edu"
</pre>
If any course instructors would like any additions, subtractions, or changes to these, let the sys-admin know.

CS accounts

2026-06-03T01:57:53Z

Jkinne: /* Websites / Webservers */

This page gives information about logging into and using the CS server (cs.indstate.edu). For help about getting started with using the terminal once you can login, see [[Linux and CS Systems - Getting Started]].

=Logging In=
The CS server is a Linux server. The primary ways you will login to the server is either (a) with a terminal (aka shell) that allows you to type text commands, or (b) with an sftp program to transfer files between your computer and the server. In either case, you need a username (aka login) and password. There are two types of accounts on the system - ISU portal accounts, and local accounts.

==ISU Portal Accounts==
Any student/faculty/staff who is involved in CS courses or programs (enrolled in a course, teaching a course, etc.) can login to cs.indstate.edu using their full ISU email address and portal password. The first time you login to the system, an account is created on the system that you can use. It will set your home directory on the system to <code>/home/SID@isuad.indstate.edu/</code> where <code>SID</code> is your portal id (aka sycamore id - for students it is the part before the @sycamores in your email address). After logging in, you can run the <code>pwd</code> command to see this.

For those familiar with Linux already... Note that there is not currently "finger information" about ISU portal account users. In fact, trying to run something like "finger jkinne@isuad.indstate.edu" will fail. Note that instructors of current courses can get a class list (aka roster) of accounts for their course; see below.

==Local Accounts==
Some users will have accounts on the CS server that are not tied to their ISU portal accounts. For example, CS faculty have local accounts, and a number of users of the server prior to 2025 have local accounts. These are accounts with username and password that were created just on the server (the ability to login to the server with ISU portal credentials was added in 2025). Any new instructor teaching a CS course can ask for a local account if you do not have one already - write to root@cs.indstate.edu.

==SSH Key==
You can setup an SSH key to login to the system. You will first need to login to the system normally. Once you are logged in, you can run the following commands.
<pre>
mkdir ~/.ssh # in case it does not exist yet
chmod 700 ~/.ssh # make sure this directory is not accessible to other users
ssh-keygen # create keys for logging in
</pre>
You will then transfer the private key file (the one that does not end in .pub) to your local computer in the location for ssh keys. This varies depending on your operating system. On Linux and Mac OS, it will be in <code>~/.ssh</code>.

= CS Server Policies =
== Prohibitions ==
For any accounts that you have on the CS server, you should follow all ISU policies. In particular the following are prohibited -
* using your account to store or distribute anything that is against its terms/copyright/etc. (e.g., no movies, textbooks, answers to HW problems)
* using your account to do anything that is illegal
* using a password that is too easy to guess (i.e., a password cracker that we run finds your password)
* overloading the CPU or GPU of the system, or filling up any of the system drives
* anything that is along these lines that we have not thought to state explicitly
A violation of any of these will result in your account being locked and no longer being allowed to have an account on the systems.

== Inactivity ==
Accounts that are not used for a period of 6 months will likely be locked as a security precaution. You can write to root@cs.indstate.edu to ask to have your account unlocked again.

=Student Use and Course Account=
For courses that are currently being offered, if the course uses the server, a class account is created that the instructor of the course can use if they like. This is explained in this section with two examples: CS 151 Intro to Computer Science, and CS 473/573 Computer Networks.

==Course Account==
An account on the system is created where files for the class can be kept that are to be shared with the students. For CS 151, the account created has username <code>cs151</code>. For CS 473/573, a single account, <code>cs473</code>, is created that is to be used for both courses.

==Student Use==
For students who are currently enrolled in a CS course that uses the server, the first time you login to the system with your ISU portal account, a directory should be created within your account for the course. For example, students in CS 151 will have a directory <code>cs151</code>, and students in CS 473/573 will have a directory <code>cs473</code>.

Permissions are set on the system so that instructors of the course have read access to the files within student's course directories for their courses. The instructor for CS 151 will have read access to the <code>cs151</code> directories of the students enrolled in CS 151; the instructor for CS 473/573 will have read access to the <code>cs473</code> directories of the students enrolled in CS 473/573; etc. The instructor of the course might have the students submit their work on the server within these directories. Each instructor can choose how they would like to do this.

The course account for each course also has read access to the directories for that course. For example, the <code>cs151</code> account will have read access to the <code>cs151</code> directories within any student enrolled in CS 151.

==Course Account - Instructor Private Files==
The course account is created with a <code>~/private</code> directory that is not accessible to other users (i.e., not accessible to students). The class list (aka roster) of students and their accounts is put into this directory (<code>classlist_brief.csv</code> with the most important information for each student, and <code>classlist_full.csv</code> with more information). The instructor could keep other files in this <code>private</code> directory that is meant to be private (e.g., model solutions or grading information).

Inside the <code>~/private/</code> directory of the course account, there is also a <code>students</code> directory that has symbolic links to each of the student's course directories in the course. For example, if the course is cs151, and if the user jdoe12345@isuad.indstate.edu is a student in the course, then there will be a link <code>/home/cs151/private/students/jdoe12345@isuad.indstate.edu</code> that is a link to the cs151 directory for this student (<code>/home/jdoe12345@isuad.indstate.edu/cs151/</code>). The instructor for the course can quickly get into the students' directories for the course (but not their home directory) by going to the private/students/ directory and going from there.

The accounts for the instructors of the course are set so they can sudo as the course account. If the instructor of CS 151 uses the local account <code>jkinne</code> then this user can run the following command to get a shell running as the CS 151 course account: <code>sudo -u cs151 -i</code>.
Note that this only works for local accounts, and does not work for ISU Portal accounts (it might work for the jkinne local account but not for the jkinne@isuad.indstate.edu account).

====Change of Semester and Backups====
Before the next semester, a backup copy of each course account will be created that will be in the course's <code>~/private/backup/</code> directory. A directory will be created for the term, and it will have all of the course account's files from that term within it.

Once the backup has been created for the previous term, the instructor for the current semester can remove files and directories that are no longer needed for the new term. For example, you can clear out the assignment directories in the course account's home directory, and also the student submissions that are in <code>~/private/submissions/</code>. Those files will still be in the backup directory in case you need them later.

When the new semester starts (if the course is running in the new semester), the following in the <code>~/private</code> directory will be updated to be for the new term: classlist_brief.csv, classlist_full.csv, students directory (symbolic links to new semester's students).

=Assignments=
Any directory within the course account can be used as an assignment. For example, suppose the account <code>cs151</code> contains a directory <code>h7</code>. This directory might have files for the students to use on the assignment; they can view these files by going to the directory <code>/home/cs151/h7/</code>.

A student can "checkout" or "get" an assignment by running
<pre>hw_get.py cs151 h7</pre>
This will copy the <code>h7</code> directory that is in the <code>cs151</code> account into the <code>cs151</code> directory of the user that executes the command.

An instructor can collect an assignment by running the script <code>hw_collect.py</code>. For the above example, the instructor would run: <code>hw_collect.py cs151 h7</code>. This will go into each student in the course's <code>cs151</code> directory and copy their h7 directory into <code>/home/cs151/private/submissions/h7/</code>. There will be a new directory in that submissions directory for the date and time the submissions were collected. For example, if the user jdoe12345@isuad.indstate.edu is in the cs151 course, then the contents of <code>/home/jdoe12345@isuad.indstate.edu/h7/</code> will be copied into the submission directory (inside of <code>/home/cs151/private/submissions/h7/</code>). The directory <code>/home/cs151/private/submissions/h7/</code> will have a symbolic link <code>latest</code> that is a pointer to the latest submission.

There is a system in place that can be used for auto-checking the output of student programs. The instructor creates a file <code>.tests.json</code> inside of the assignment directory that has the test cases. The instructor will also need to create a correct working version of each program that can be run to get the "correct" results. The students will use the <code>hw_check.py</code> command to check their output. The instructor can also use the same comment to check student submissions. You can get more details about how this works by logging into the system and running: <code>hw_check.py --help</code>.

=Websites / Webservers=
==Apache==
The main cs.indstate.edu website uses the Apache web server. This is configured so that any user can put html and php files in the right directory in their account to be on the web server. Jeff Kinne, who has portal id <code>jkinne</code> and therefore account on the server with home directory <code>jkinne@isuad.indstate.edu</code>, would do the following to create the right directories.
<pre>
cd ~jkinne@isuad.indstate.edu # jkinne's home directory
mkdir public_html # directory apache looks in for website files
setfacl -m group:www-data:x . # give apache execute access to home directory
setfacl -R -m group:www-data:rX public_html # give apache rX access to public_html
setfacl -R -m default:group:www-data:rX public_html # and new files will also have access
cd public_html # go into that directory
echo "Hello world" > index.html # write a hello world file
</pre>
Then the file index.html will be accessible on the web at https://cs.indstate.edu/~jkinne@isuad.indstate.edu. Since the web server is Apache, you can look for help on the Apache web server about configuration options (in particular .htaccess files that you can put in your public_html directory to change some settings). By default, the Apache web server understands html and php files. There may be other types of files you would want it to be able to understand; if so you can write to root@cs.indstate.edu.

==Node, Django, etc.==
Node, Django, and many other web server frameworks can also be run off of the CS server. These generally will pick a port that they will run off of, and you run the main file for your server. Note that the Apache web server uses the "standard" ports (80 for http and 443 for https), so you cannot use those. If you want to run a Node, Django, or similar web server off of the CS server, you need to pick a port that isn't used for anything else. You should never pick a port number that is below 1024 and really should avoid port numbers below 10000. If you want to make sure to pick a port that will not interfere with anything, write to root@cs.indstate.edu. If you were to run your node web server with port 60000, then you would browse to it on the web at https://cs.indstate.edu:60000. Note that there is indeed normally a node server running on that particular port.

=Spring 2026=
The following is the list of courses that are supported on the server for the fall 2025, along with the instructor accounts (aka admin accounts) for each course.
<pre>
course,admin_accounts
cs151,"jkinne,jeff,jkinne@isuad.indstate.edu"
cs170,"hrafieipour@isuad.indstate.edu"
cs201,"majid,mafsharnoghon@isuad.indstate.edu"
cs203,"namoako,namoako@isuad.indstate.edu"
cs211,"mjenkins1@isuad.indstate.edu"
cs351,"rabhyankar@isuad.indstate.edu"
cs331,"namoako,namoako@isuad.indstate.edu"
"cs401,cs501","majid,mafsharnoghon@isuad.indstate.edu"
cs401L,"majid,mafsharnoghon@isuad.indstate.edu"
"cs456,cs556","jcompton5,jcompton5@isuad.indstate.edu"
cs456L,"jcompton5,jcompton5@isuad.indstate.edu"
"cs457,cs557","kwexoo,kexoo@isuad.indstate.edu"
cs457L,"kwexoo,kexoo@isuad.indstate.edu"
"cs458,cs558","namoako,namoako@isuad.indstate.edu"
cs458L,"namoako,namoako@isuad.indstate.edu"
"cs469,cs569","katterson1,katterson1@isuad.indstate.edu"
"cs475,cs575","rabhyankar@isuad.indstate.edu"
cs500,"jkinne,jeff,jkinne@isuad.indstate.edu"
cs600,"arash,arafiey@isuad.indstate.edu"
"cs601,cs417","majid,mafsharnoghon@isuad.indstate.edu"
cs609,"katterson1,katterson1@isuad.indstate.edu"
cs611,"rabhyankar@isuad.indstate.edu"
cs618,"shosseini@isuad.indstate.edu"
cs685,"arash,arafiey@isuad.indstate.edu"
cs695,"arash,arafiey@isuad.indstate.edu"
ect438,"jkinne,jeff,jkinne@isuad.indstate.edu"
</pre>
If any course instructors would like any additions, subtractions, or changes to these, let the sys-admin know.

CS accounts

2026-06-03T01:57:30Z

Jkinne: /* Assignments */

This page gives information about logging into and using the CS server (cs.indstate.edu). For help about getting started with using the terminal once you can login, see [[Linux and CS Systems - Getting Started]].

=Logging In=
The CS server is a Linux server. The primary ways you will login to the server is either (a) with a terminal (aka shell) that allows you to type text commands, or (b) with an sftp program to transfer files between your computer and the server. In either case, you need a username (aka login) and password. There are two types of accounts on the system - ISU portal accounts, and local accounts.

==ISU Portal Accounts==
Any student/faculty/staff who is involved in CS courses or programs (enrolled in a course, teaching a course, etc.) can login to cs.indstate.edu using their full ISU email address and portal password. The first time you login to the system, an account is created on the system that you can use. It will set your home directory on the system to <code>/home/SID@isuad.indstate.edu/</code> where <code>SID</code> is your portal id (aka sycamore id - for students it is the part before the @sycamores in your email address). After logging in, you can run the <code>pwd</code> command to see this.

For those familiar with Linux already... Note that there is not currently "finger information" about ISU portal account users. In fact, trying to run something like "finger jkinne@isuad.indstate.edu" will fail. Note that instructors of current courses can get a class list (aka roster) of accounts for their course; see below.

==Local Accounts==
Some users will have accounts on the CS server that are not tied to their ISU portal accounts. For example, CS faculty have local accounts, and a number of users of the server prior to 2025 have local accounts. These are accounts with username and password that were created just on the server (the ability to login to the server with ISU portal credentials was added in 2025). Any new instructor teaching a CS course can ask for a local account if you do not have one already - write to root@cs.indstate.edu.

==SSH Key==
You can setup an SSH key to login to the system. You will first need to login to the system normally. Once you are logged in, you can run the following commands.
<pre>
mkdir ~/.ssh # in case it does not exist yet
chmod 700 ~/.ssh # make sure this directory is not accessible to other users
ssh-keygen # create keys for logging in
</pre>
You will then transfer the private key file (the one that does not end in .pub) to your local computer in the location for ssh keys. This varies depending on your operating system. On Linux and Mac OS, it will be in <code>~/.ssh</code>.

= CS Server Policies =
== Prohibitions ==
For any accounts that you have on the CS server, you should follow all ISU policies. In particular the following are prohibited -
* using your account to store or distribute anything that is against its terms/copyright/etc. (e.g., no movies, textbooks, answers to HW problems)
* using your account to do anything that is illegal
* using a password that is too easy to guess (i.e., a password cracker that we run finds your password)
* overloading the CPU or GPU of the system, or filling up any of the system drives
* anything that is along these lines that we have not thought to state explicitly
A violation of any of these will result in your account being locked and no longer being allowed to have an account on the systems.

== Inactivity ==
Accounts that are not used for a period of 6 months will likely be locked as a security precaution. You can write to root@cs.indstate.edu to ask to have your account unlocked again.

=Student Use and Course Account=
For courses that are currently being offered, if the course uses the server, a class account is created that the instructor of the course can use if they like. This is explained in this section with two examples: CS 151 Intro to Computer Science, and CS 473/573 Computer Networks.

==Course Account==
An account on the system is created where files for the class can be kept that are to be shared with the students. For CS 151, the account created has username <code>cs151</code>. For CS 473/573, a single account, <code>cs473</code>, is created that is to be used for both courses.

==Student Use==
For students who are currently enrolled in a CS course that uses the server, the first time you login to the system with your ISU portal account, a directory should be created within your account for the course. For example, students in CS 151 will have a directory <code>cs151</code>, and students in CS 473/573 will have a directory <code>cs473</code>.

Permissions are set on the system so that instructors of the course have read access to the files within student's course directories for their courses. The instructor for CS 151 will have read access to the <code>cs151</code> directories of the students enrolled in CS 151; the instructor for CS 473/573 will have read access to the <code>cs473</code> directories of the students enrolled in CS 473/573; etc. The instructor of the course might have the students submit their work on the server within these directories. Each instructor can choose how they would like to do this.

The course account for each course also has read access to the directories for that course. For example, the <code>cs151</code> account will have read access to the <code>cs151</code> directories within any student enrolled in CS 151.

==Course Account - Instructor Private Files==
The course account is created with a <code>~/private</code> directory that is not accessible to other users (i.e., not accessible to students). The class list (aka roster) of students and their accounts is put into this directory (<code>classlist_brief.csv</code> with the most important information for each student, and <code>classlist_full.csv</code> with more information). The instructor could keep other files in this <code>private</code> directory that is meant to be private (e.g., model solutions or grading information).

Inside the <code>~/private/</code> directory of the course account, there is also a <code>students</code> directory that has symbolic links to each of the student's course directories in the course. For example, if the course is cs151, and if the user jdoe12345@isuad.indstate.edu is a student in the course, then there will be a link <code>/home/cs151/private/students/jdoe12345@isuad.indstate.edu</code> that is a link to the cs151 directory for this student (<code>/home/jdoe12345@isuad.indstate.edu/cs151/</code>). The instructor for the course can quickly get into the students' directories for the course (but not their home directory) by going to the private/students/ directory and going from there.

The accounts for the instructors of the course are set so they can sudo as the course account. If the instructor of CS 151 uses the local account <code>jkinne</code> then this user can run the following command to get a shell running as the CS 151 course account: <code>sudo -u cs151 -i</code>.
Note that this only works for local accounts, and does not work for ISU Portal accounts (it might work for the jkinne local account but not for the jkinne@isuad.indstate.edu account).

====Change of Semester and Backups====
Before the next semester, a backup copy of each course account will be created that will be in the course's <code>~/private/backup/</code> directory. A directory will be created for the term, and it will have all of the course account's files from that term within it.

Once the backup has been created for the previous term, the instructor for the current semester can remove files and directories that are no longer needed for the new term. For example, you can clear out the assignment directories in the course account's home directory, and also the student submissions that are in <code>~/private/submissions/</code>. Those files will still be in the backup directory in case you need them later.

When the new semester starts (if the course is running in the new semester), the following in the <code>~/private</code> directory will be updated to be for the new term: classlist_brief.csv, classlist_full.csv, students directory (symbolic links to new semester's students).

=Websites / Webservers=
==Apache==
The main cs.indstate.edu website uses the Apache web server. This is configured so that any user can put html and php files in the right directory in their account to be on the web server. Jeff Kinne, who has portal id <code>jkinne</code> and therefore account on the server with home directory <code>jkinne@isuad.indstate.edu</code>, would do the following to create the right directories.
<pre>
cd ~jkinne@isuad.indstate.edu # jkinne's home directory
mkdir public_html # directory apache looks in for website files
setfacl -m group:www-data:x . # give apache execute access to home directory
setfacl -R -m group:www-data:rX public_html # give apache rX access to public_html
setfacl -R -m default:group:www-data:rX public_html # and new files will also have access
cd public_html # go into that directory
echo "Hello world" > index.html # write a hello world file
</pre>
Then the file index.html will be accessible on the web at https://cs.indstate.edu/~jkinne@isuad.indstate.edu. Since the web server is Apache, you can look for help on the Apache web server about configuration options (in particular .htaccess files that you can put in your public_html directory to change some settings). By default, the Apache web server understands html and php files. There may be other types of files you would want it to be able to understand; if so you can write to root@cs.indstate.edu.

==Node, Django, etc.==
Node, Django, and many other web server frameworks can also be run off of the CS server. These generally will pick a port that they will run off of, and you run the main file for your server. Note that the Apache web server uses the "standard" ports (80 for http and 443 for https), so you cannot use those. If you want to run a Node, Django, or similar web server off of the CS server, you need to pick a port that isn't used for anything else. You should never pick a port number that is below 1024 and really should avoid port numbers below 10000. If you want to make sure to pick a port that will not interfere with anything, write to root@cs.indstate.edu. If you were to run your node web server with port 60000, then you would browse to it on the web at https://cs.indstate.edu:60000. Note that there is indeed normally a node server running on that particular port.

=Spring 2026=
The following is the list of courses that are supported on the server for the fall 2025, along with the instructor accounts (aka admin accounts) for each course.
<pre>
course,admin_accounts
cs151,"jkinne,jeff,jkinne@isuad.indstate.edu"
cs170,"hrafieipour@isuad.indstate.edu"
cs201,"majid,mafsharnoghon@isuad.indstate.edu"
cs203,"namoako,namoako@isuad.indstate.edu"
cs211,"mjenkins1@isuad.indstate.edu"
cs351,"rabhyankar@isuad.indstate.edu"
cs331,"namoako,namoako@isuad.indstate.edu"
"cs401,cs501","majid,mafsharnoghon@isuad.indstate.edu"
cs401L,"majid,mafsharnoghon@isuad.indstate.edu"
"cs456,cs556","jcompton5,jcompton5@isuad.indstate.edu"
cs456L,"jcompton5,jcompton5@isuad.indstate.edu"
"cs457,cs557","kwexoo,kexoo@isuad.indstate.edu"
cs457L,"kwexoo,kexoo@isuad.indstate.edu"
"cs458,cs558","namoako,namoako@isuad.indstate.edu"
cs458L,"namoako,namoako@isuad.indstate.edu"
"cs469,cs569","katterson1,katterson1@isuad.indstate.edu"
"cs475,cs575","rabhyankar@isuad.indstate.edu"
cs500,"jkinne,jeff,jkinne@isuad.indstate.edu"
cs600,"arash,arafiey@isuad.indstate.edu"
"cs601,cs417","majid,mafsharnoghon@isuad.indstate.edu"
cs609,"katterson1,katterson1@isuad.indstate.edu"
cs611,"rabhyankar@isuad.indstate.edu"
cs618,"shosseini@isuad.indstate.edu"
cs685,"arash,arafiey@isuad.indstate.edu"
cs695,"arash,arafiey@isuad.indstate.edu"
ect438,"jkinne,jeff,jkinne@isuad.indstate.edu"
</pre>
If any course instructors would like any additions, subtractions, or changes to these, let the sys-admin know.

CS accounts

2026-06-03T01:56:19Z

Jkinne: /* Course Account - Instructor Private Files */

This page gives information about logging into and using the CS server (cs.indstate.edu). For help about getting started with using the terminal once you can login, see [[Linux and CS Systems - Getting Started]].

=Logging In=
The CS server is a Linux server. The primary ways you will login to the server is either (a) with a terminal (aka shell) that allows you to type text commands, or (b) with an sftp program to transfer files between your computer and the server. In either case, you need a username (aka login) and password. There are two types of accounts on the system - ISU portal accounts, and local accounts.

==ISU Portal Accounts==
Any student/faculty/staff who is involved in CS courses or programs (enrolled in a course, teaching a course, etc.) can login to cs.indstate.edu using their full ISU email address and portal password. The first time you login to the system, an account is created on the system that you can use. It will set your home directory on the system to <code>/home/SID@isuad.indstate.edu/</code> where <code>SID</code> is your portal id (aka sycamore id - for students it is the part before the @sycamores in your email address). After logging in, you can run the <code>pwd</code> command to see this.

For those familiar with Linux already... Note that there is not currently "finger information" about ISU portal account users. In fact, trying to run something like "finger jkinne@isuad.indstate.edu" will fail. Note that instructors of current courses can get a class list (aka roster) of accounts for their course; see below.

==Local Accounts==
Some users will have accounts on the CS server that are not tied to their ISU portal accounts. For example, CS faculty have local accounts, and a number of users of the server prior to 2025 have local accounts. These are accounts with username and password that were created just on the server (the ability to login to the server with ISU portal credentials was added in 2025). Any new instructor teaching a CS course can ask for a local account if you do not have one already - write to root@cs.indstate.edu.

==SSH Key==
You can setup an SSH key to login to the system. You will first need to login to the system normally. Once you are logged in, you can run the following commands.
<pre>
mkdir ~/.ssh # in case it does not exist yet
chmod 700 ~/.ssh # make sure this directory is not accessible to other users
ssh-keygen # create keys for logging in
</pre>
You will then transfer the private key file (the one that does not end in .pub) to your local computer in the location for ssh keys. This varies depending on your operating system. On Linux and Mac OS, it will be in <code>~/.ssh</code>.

= CS Server Policies =
== Prohibitions ==
For any accounts that you have on the CS server, you should follow all ISU policies. In particular the following are prohibited -
* using your account to store or distribute anything that is against its terms/copyright/etc. (e.g., no movies, textbooks, answers to HW problems)
* using your account to do anything that is illegal
* using a password that is too easy to guess (i.e., a password cracker that we run finds your password)
* overloading the CPU or GPU of the system, or filling up any of the system drives
* anything that is along these lines that we have not thought to state explicitly
A violation of any of these will result in your account being locked and no longer being allowed to have an account on the systems.

== Inactivity ==
Accounts that are not used for a period of 6 months will likely be locked as a security precaution. You can write to root@cs.indstate.edu to ask to have your account unlocked again.

=Student Use and Course Account=
For courses that are currently being offered, if the course uses the server, a class account is created that the instructor of the course can use if they like. This is explained in this section with two examples: CS 151 Intro to Computer Science, and CS 473/573 Computer Networks.

==Course Account==
An account on the system is created where files for the class can be kept that are to be shared with the students. For CS 151, the account created has username <code>cs151</code>. For CS 473/573, a single account, <code>cs473</code>, is created that is to be used for both courses.

==Student Use==
For students who are currently enrolled in a CS course that uses the server, the first time you login to the system with your ISU portal account, a directory should be created within your account for the course. For example, students in CS 151 will have a directory <code>cs151</code>, and students in CS 473/573 will have a directory <code>cs473</code>.

Permissions are set on the system so that instructors of the course have read access to the files within student's course directories for their courses. The instructor for CS 151 will have read access to the <code>cs151</code> directories of the students enrolled in CS 151; the instructor for CS 473/573 will have read access to the <code>cs473</code> directories of the students enrolled in CS 473/573; etc. The instructor of the course might have the students submit their work on the server within these directories. Each instructor can choose how they would like to do this.

The course account for each course also has read access to the directories for that course. For example, the <code>cs151</code> account will have read access to the <code>cs151</code> directories within any student enrolled in CS 151.

==Course Account - Instructor Private Files==
The course account is created with a <code>~/private</code> directory that is not accessible to other users (i.e., not accessible to students). The class list (aka roster) of students and their accounts is put into this directory (<code>classlist_brief.csv</code> with the most important information for each student, and <code>classlist_full.csv</code> with more information). The instructor could keep other files in this <code>private</code> directory that is meant to be private (e.g., model solutions or grading information).

Inside the <code>~/private/</code> directory of the course account, there is also a <code>students</code> directory that has symbolic links to each of the student's course directories in the course. For example, if the course is cs151, and if the user jdoe12345@isuad.indstate.edu is a student in the course, then there will be a link <code>/home/cs151/private/students/jdoe12345@isuad.indstate.edu</code> that is a link to the cs151 directory for this student (<code>/home/jdoe12345@isuad.indstate.edu/cs151/</code>). The instructor for the course can quickly get into the students' directories for the course (but not their home directory) by going to the private/students/ directory and going from there.

The accounts for the instructors of the course are set so they can sudo as the course account. If the instructor of CS 151 uses the local account <code>jkinne</code> then this user can run the following command to get a shell running as the CS 151 course account: <code>sudo -u cs151 -i</code>.
Note that this only works for local accounts, and does not work for ISU Portal accounts (it might work for the jkinne local account but not for the jkinne@isuad.indstate.edu account).

====Change of Semester and Backups====
Before the next semester, a backup copy of each course account will be created that will be in the course's <code>~/private/backup/</code> directory. A directory will be created for the term, and it will have all of the course account's files from that term within it.

Once the backup has been created for the previous term, the instructor for the current semester can remove files and directories that are no longer needed for the new term. For example, you can clear out the assignment directories in the course account's home directory, and also the student submissions that are in <code>~/private/submissions/</code>. Those files will still be in the backup directory in case you need them later.

When the new semester starts (if the course is running in the new semester), the following in the <code>~/private</code> directory will be updated to be for the new term: classlist_brief.csv, classlist_full.csv, students directory (symbolic links to new semester's students).

=Websites / Webservers=
==Apache==
The main cs.indstate.edu website uses the Apache web server. This is configured so that any user can put html and php files in the right directory in their account to be on the web server. Jeff Kinne, who has portal id <code>jkinne</code> and therefore account on the server with home directory <code>jkinne@isuad.indstate.edu</code>, would do the following to create the right directories.
<pre>
cd ~jkinne@isuad.indstate.edu # jkinne's home directory
mkdir public_html # directory apache looks in for website files
setfacl -m group:www-data:x . # give apache execute access to home directory
setfacl -R -m group:www-data:rX public_html # give apache rX access to public_html
setfacl -R -m default:group:www-data:rX public_html # and new files will also have access
cd public_html # go into that directory
echo "Hello world" > index.html # write a hello world file
</pre>
Then the file index.html will be accessible on the web at https://cs.indstate.edu/~jkinne@isuad.indstate.edu. Since the web server is Apache, you can look for help on the Apache web server about configuration options (in particular .htaccess files that you can put in your public_html directory to change some settings). By default, the Apache web server understands html and php files. There may be other types of files you would want it to be able to understand; if so you can write to root@cs.indstate.edu.

==Node, Django, etc.==
Node, Django, and many other web server frameworks can also be run off of the CS server. These generally will pick a port that they will run off of, and you run the main file for your server. Note that the Apache web server uses the "standard" ports (80 for http and 443 for https), so you cannot use those. If you want to run a Node, Django, or similar web server off of the CS server, you need to pick a port that isn't used for anything else. You should never pick a port number that is below 1024 and really should avoid port numbers below 10000. If you want to make sure to pick a port that will not interfere with anything, write to root@cs.indstate.edu. If you were to run your node web server with port 60000, then you would browse to it on the web at https://cs.indstate.edu:60000. Note that there is indeed normally a node server running on that particular port.

=Assignments=
Any directory within the course account can be used as an assignment. For example, suppose the account <code>cs151</code> contains a directory <code>h7</code>. This directory might have files for the students to use on the assignment; they can view these files by going to the directory <code>/home/cs151/h7/</code>.

A student can "checkout" or "get" an assignment by running
<pre>hw_get.py cs151 h7</pre>
This will copy the <code>h7</code> directory that is in the <code>cs151</code> account into the <code>cs151</code> directory of the user that executes the command.

An instructor can collect an assignment by running the script <code>hw_collect.py</code>. For the above example, the instructor would run: <code>hw_collect.py cs151 h7</code>. This will go into each student in the course's <code>cs151</code> directory and copy their h7 directory into <code>/home/cs151/private/submissions/h7/</code>. There will be a new directory in that submissions directory for the date and time the submissions were collected. For example, if the user jdoe12345@isuad.indstate.edu is in the cs151 course, then the contents of <code>/home/jdoe12345@isuad.indstate.edu/h7/</code> will be copied into the submission directory (inside of <code>/home/cs151/private/submissions/h7/</code>). The directory <code>/home/cs151/private/submissions/h7/</code> will have a symbolic link <code>latest</code> that is a pointer to the latest submission.

There is a system in place that can be used for auto-checking the output of student programs. The instructor creates a file <code>.tests.json</code> inside of the assignment directory that has the test cases. The instructor will also need to create a correct working version of each program that can be run to get the "correct" results. The students will use the <code>hw_check.py</code> command to check their output. The instructor can also use the same comment to check student submissions. You can get more details about how this works by logging into the system and running: <code>hw_check.py --help</code>.

=Spring 2026=
The following is the list of courses that are supported on the server for the fall 2025, along with the instructor accounts (aka admin accounts) for each course.
<pre>
course,admin_accounts
cs151,"jkinne,jeff,jkinne@isuad.indstate.edu"
cs170,"hrafieipour@isuad.indstate.edu"
cs201,"majid,mafsharnoghon@isuad.indstate.edu"
cs203,"namoako,namoako@isuad.indstate.edu"
cs211,"mjenkins1@isuad.indstate.edu"
cs351,"rabhyankar@isuad.indstate.edu"
cs331,"namoako,namoako@isuad.indstate.edu"
"cs401,cs501","majid,mafsharnoghon@isuad.indstate.edu"
cs401L,"majid,mafsharnoghon@isuad.indstate.edu"
"cs456,cs556","jcompton5,jcompton5@isuad.indstate.edu"
cs456L,"jcompton5,jcompton5@isuad.indstate.edu"
"cs457,cs557","kwexoo,kexoo@isuad.indstate.edu"
cs457L,"kwexoo,kexoo@isuad.indstate.edu"
"cs458,cs558","namoako,namoako@isuad.indstate.edu"
cs458L,"namoako,namoako@isuad.indstate.edu"
"cs469,cs569","katterson1,katterson1@isuad.indstate.edu"
"cs475,cs575","rabhyankar@isuad.indstate.edu"
cs500,"jkinne,jeff,jkinne@isuad.indstate.edu"
cs600,"arash,arafiey@isuad.indstate.edu"
"cs601,cs417","majid,mafsharnoghon@isuad.indstate.edu"
cs609,"katterson1,katterson1@isuad.indstate.edu"
cs611,"rabhyankar@isuad.indstate.edu"
cs618,"shosseini@isuad.indstate.edu"
cs685,"arash,arafiey@isuad.indstate.edu"
cs695,"arash,arafiey@isuad.indstate.edu"
ect438,"jkinne,jeff,jkinne@isuad.indstate.edu"
</pre>
If any course instructors would like any additions, subtractions, or changes to these, let the sys-admin know.

CS accounts

2026-06-03T01:53:02Z

Jkinne: /* Student Use and Course Account */

This page gives information about logging into and using the CS server (cs.indstate.edu). For help about getting started with using the terminal once you can login, see [[Linux and CS Systems - Getting Started]].

=Logging In=
The CS server is a Linux server. The primary ways you will login to the server is either (a) with a terminal (aka shell) that allows you to type text commands, or (b) with an sftp program to transfer files between your computer and the server. In either case, you need a username (aka login) and password. There are two types of accounts on the system - ISU portal accounts, and local accounts.

==ISU Portal Accounts==
Any student/faculty/staff who is involved in CS courses or programs (enrolled in a course, teaching a course, etc.) can login to cs.indstate.edu using their full ISU email address and portal password. The first time you login to the system, an account is created on the system that you can use. It will set your home directory on the system to <code>/home/SID@isuad.indstate.edu/</code> where <code>SID</code> is your portal id (aka sycamore id - for students it is the part before the @sycamores in your email address). After logging in, you can run the <code>pwd</code> command to see this.

For those familiar with Linux already... Note that there is not currently "finger information" about ISU portal account users. In fact, trying to run something like "finger jkinne@isuad.indstate.edu" will fail. Note that instructors of current courses can get a class list (aka roster) of accounts for their course; see below.

==Local Accounts==
Some users will have accounts on the CS server that are not tied to their ISU portal accounts. For example, CS faculty have local accounts, and a number of users of the server prior to 2025 have local accounts. These are accounts with username and password that were created just on the server (the ability to login to the server with ISU portal credentials was added in 2025). Any new instructor teaching a CS course can ask for a local account if you do not have one already - write to root@cs.indstate.edu.

==SSH Key==
You can setup an SSH key to login to the system. You will first need to login to the system normally. Once you are logged in, you can run the following commands.
<pre>
mkdir ~/.ssh # in case it does not exist yet
chmod 700 ~/.ssh # make sure this directory is not accessible to other users
ssh-keygen # create keys for logging in
</pre>
You will then transfer the private key file (the one that does not end in .pub) to your local computer in the location for ssh keys. This varies depending on your operating system. On Linux and Mac OS, it will be in <code>~/.ssh</code>.

= CS Server Policies =
== Prohibitions ==
For any accounts that you have on the CS server, you should follow all ISU policies. In particular the following are prohibited -
* using your account to store or distribute anything that is against its terms/copyright/etc. (e.g., no movies, textbooks, answers to HW problems)
* using your account to do anything that is illegal
* using a password that is too easy to guess (i.e., a password cracker that we run finds your password)
* overloading the CPU or GPU of the system, or filling up any of the system drives
* anything that is along these lines that we have not thought to state explicitly
A violation of any of these will result in your account being locked and no longer being allowed to have an account on the systems.

== Inactivity ==
Accounts that are not used for a period of 6 months will likely be locked as a security precaution. You can write to root@cs.indstate.edu to ask to have your account unlocked again.

=Student Use and Course Account=
For courses that are currently being offered, if the course uses the server, a class account is created that the instructor of the course can use if they like. This is explained in this section with two examples: CS 151 Intro to Computer Science, and CS 473/573 Computer Networks.

==Course Account==
An account on the system is created where files for the class can be kept that are to be shared with the students. For CS 151, the account created has username <code>cs151</code>. For CS 473/573, a single account, <code>cs473</code>, is created that is to be used for both courses.

==Student Use==
For students who are currently enrolled in a CS course that uses the server, the first time you login to the system with your ISU portal account, a directory should be created within your account for the course. For example, students in CS 151 will have a directory <code>cs151</code>, and students in CS 473/573 will have a directory <code>cs473</code>.

Permissions are set on the system so that instructors of the course have read access to the files within student's course directories for their courses. The instructor for CS 151 will have read access to the <code>cs151</code> directories of the students enrolled in CS 151; the instructor for CS 473/573 will have read access to the <code>cs473</code> directories of the students enrolled in CS 473/573; etc. The instructor of the course might have the students submit their work on the server within these directories. Each instructor can choose how they would like to do this.

The course account for each course also has read access to the directories for that course. For example, the <code>cs151</code> account will have read access to the <code>cs151</code> directories within any student enrolled in CS 151.

==Course Account - Instructor Private Files==
The course account is created with a <code>~/private</code> directory that is not accessible to other users (i.e., not accessible to students). The class list (aka roster) of students and their accounts is put into this directory (<code>classlist_brief.csv</code> with the most important information for each student, and <code>classlist_full.csv</code> with more information). The instructor could keep other files in this <code>private</code> directory that is meant to be private (e.g., model solutions or grading information).

Inside the <code>~/private/</code> directory of the course account, there is also a <code>students</code> directory that has symbolic links to each of the student's course directories in the course. For example, if the course is cs151, and if the user jdoe12345@isuad.indstate.edu is a student in the course, then there will be a link <code>/home/cs151/private/students/jdoe12345@isuad.indstate.edu</code> that is a link to the cs151 directory for this student (<code>/home/jdoe12345@isuad.indstate.edu/cs151/</code>). The instructor for the course can quickly get into the students' directories for the course (but not their home directory) by going to the private/students/ directory and going from there.

The accounts for the instructors of the course are set so they can sudo as the course account. If the instructor of CS 151 uses the local account <code>jkinne</code> then this user can run the following command to get a shell running as the CS 151 course account: <code>sudo -u cs151 -i</code>
Note that this only works for local accounts, and does not work for ISU Portal accounts (it might work for the jkinne local account but not for the jkinne@isuad.indstate.edu account).

====Change of Semester and Backups====
Before the next semester, a backup copy of each course account will be created that will be in the course's <code>~/private/backup/</code> directory. A directory will be created for the term, and it will have all of the course account's files from that term within it.

Once the backup has been created for the previous term, the instructor for the current semester can remove files and directories that are no longer needed for the new term. For example, you can clear out the assignment directories in the course account's home directory, and also the student submissions that are in <code>~/private/submissions/</code>. Those files will still be in the backup directory in case you need them later.

When the new semester starts (if the course is running in the new semester), the following in the <code>~/private</code> directory will be updated to be for the new term: classlist_brief.csv, classlist_full.csv, students directory (symbolic links to new semester's students).

=Websites / Webservers=
==Apache==
The main cs.indstate.edu website uses the Apache web server. This is configured so that any user can put html and php files in the right directory in their account to be on the web server. Jeff Kinne, who has portal id <code>jkinne</code> and therefore account on the server with home directory <code>jkinne@isuad.indstate.edu</code>, would do the following to create the right directories.
<pre>
cd ~jkinne@isuad.indstate.edu # jkinne's home directory
mkdir public_html # directory apache looks in for website files
setfacl -m group:www-data:x . # give apache execute access to home directory
setfacl -R -m group:www-data:rX public_html # give apache rX access to public_html
setfacl -R -m default:group:www-data:rX public_html # and new files will also have access
cd public_html # go into that directory
echo "Hello world" > index.html # write a hello world file
</pre>
Then the file index.html will be accessible on the web at https://cs.indstate.edu/~jkinne@isuad.indstate.edu. Since the web server is Apache, you can look for help on the Apache web server about configuration options (in particular .htaccess files that you can put in your public_html directory to change some settings). By default, the Apache web server understands html and php files. There may be other types of files you would want it to be able to understand; if so you can write to root@cs.indstate.edu.

==Node, Django, etc.==
Node, Django, and many other web server frameworks can also be run off of the CS server. These generally will pick a port that they will run off of, and you run the main file for your server. Note that the Apache web server uses the "standard" ports (80 for http and 443 for https), so you cannot use those. If you want to run a Node, Django, or similar web server off of the CS server, you need to pick a port that isn't used for anything else. You should never pick a port number that is below 1024 and really should avoid port numbers below 10000. If you want to make sure to pick a port that will not interfere with anything, write to root@cs.indstate.edu. If you were to run your node web server with port 60000, then you would browse to it on the web at https://cs.indstate.edu:60000. Note that there is indeed normally a node server running on that particular port.

=Assignments=
Any directory within the course account can be used as an assignment. For example, suppose the account <code>cs151</code> contains a directory <code>h7</code>. This directory might have files for the students to use on the assignment; they can view these files by going to the directory <code>/home/cs151/h7/</code>.

A student can "checkout" or "get" an assignment by running
<pre>hw_get.py cs151 h7</pre>
This will copy the <code>h7</code> directory that is in the <code>cs151</code> account into the <code>cs151</code> directory of the user that executes the command.

An instructor can collect an assignment by running the script <code>hw_collect.py</code>. For the above example, the instructor would run: <code>hw_collect.py cs151 h7</code>. This will go into each student in the course's <code>cs151</code> directory and copy their h7 directory into <code>/home/cs151/private/submissions/h7/</code>. There will be a new directory in that submissions directory for the date and time the submissions were collected. For example, if the user jdoe12345@isuad.indstate.edu is in the cs151 course, then the contents of <code>/home/jdoe12345@isuad.indstate.edu/h7/</code> will be copied into the submission directory (inside of <code>/home/cs151/private/submissions/h7/</code>). The directory <code>/home/cs151/private/submissions/h7/</code> will have a symbolic link <code>latest</code> that is a pointer to the latest submission.

There is a system in place that can be used for auto-checking the output of student programs. The instructor creates a file <code>.tests.json</code> inside of the assignment directory that has the test cases. The instructor will also need to create a correct working version of each program that can be run to get the "correct" results. The students will use the <code>hw_check.py</code> command to check their output. The instructor can also use the same comment to check student submissions. You can get more details about how this works by logging into the system and running: <code>hw_check.py --help</code>.

=Spring 2026=
The following is the list of courses that are supported on the server for the fall 2025, along with the instructor accounts (aka admin accounts) for each course.
<pre>
course,admin_accounts
cs151,"jkinne,jeff,jkinne@isuad.indstate.edu"
cs170,"hrafieipour@isuad.indstate.edu"
cs201,"majid,mafsharnoghon@isuad.indstate.edu"
cs203,"namoako,namoako@isuad.indstate.edu"
cs211,"mjenkins1@isuad.indstate.edu"
cs351,"rabhyankar@isuad.indstate.edu"
cs331,"namoako,namoako@isuad.indstate.edu"
"cs401,cs501","majid,mafsharnoghon@isuad.indstate.edu"
cs401L,"majid,mafsharnoghon@isuad.indstate.edu"
"cs456,cs556","jcompton5,jcompton5@isuad.indstate.edu"
cs456L,"jcompton5,jcompton5@isuad.indstate.edu"
"cs457,cs557","kwexoo,kexoo@isuad.indstate.edu"
cs457L,"kwexoo,kexoo@isuad.indstate.edu"
"cs458,cs558","namoako,namoako@isuad.indstate.edu"
cs458L,"namoako,namoako@isuad.indstate.edu"
"cs469,cs569","katterson1,katterson1@isuad.indstate.edu"
"cs475,cs575","rabhyankar@isuad.indstate.edu"
cs500,"jkinne,jeff,jkinne@isuad.indstate.edu"
cs600,"arash,arafiey@isuad.indstate.edu"
"cs601,cs417","majid,mafsharnoghon@isuad.indstate.edu"
cs609,"katterson1,katterson1@isuad.indstate.edu"
cs611,"rabhyankar@isuad.indstate.edu"
cs618,"shosseini@isuad.indstate.edu"
cs685,"arash,arafiey@isuad.indstate.edu"
cs695,"arash,arafiey@isuad.indstate.edu"
ect438,"jkinne,jeff,jkinne@isuad.indstate.edu"
</pre>
If any course instructors would like any additions, subtractions, or changes to these, let the sys-admin know.

CS accounts

2026-06-03T01:52:22Z

Jkinne: /* Inactivity */

This page gives information about logging into and using the CS server (cs.indstate.edu). For help about getting started with using the terminal once you can login, see [[Linux and CS Systems - Getting Started]].

=Logging In=
The CS server is a Linux server. The primary ways you will login to the server is either (a) with a terminal (aka shell) that allows you to type text commands, or (b) with an sftp program to transfer files between your computer and the server. In either case, you need a username (aka login) and password. There are two types of accounts on the system - ISU portal accounts, and local accounts.

==ISU Portal Accounts==
Any student/faculty/staff who is involved in CS courses or programs (enrolled in a course, teaching a course, etc.) can login to cs.indstate.edu using their full ISU email address and portal password. The first time you login to the system, an account is created on the system that you can use. It will set your home directory on the system to <code>/home/SID@isuad.indstate.edu/</code> where <code>SID</code> is your portal id (aka sycamore id - for students it is the part before the @sycamores in your email address). After logging in, you can run the <code>pwd</code> command to see this.

For those familiar with Linux already... Note that there is not currently "finger information" about ISU portal account users. In fact, trying to run something like "finger jkinne@isuad.indstate.edu" will fail. Note that instructors of current courses can get a class list (aka roster) of accounts for their course; see below.

==Local Accounts==
Some users will have accounts on the CS server that are not tied to their ISU portal accounts. For example, CS faculty have local accounts, and a number of users of the server prior to 2025 have local accounts. These are accounts with username and password that were created just on the server (the ability to login to the server with ISU portal credentials was added in 2025). Any new instructor teaching a CS course can ask for a local account if you do not have one already - write to root@cs.indstate.edu.

==SSH Key==
You can setup an SSH key to login to the system. You will first need to login to the system normally. Once you are logged in, you can run the following commands.
<pre>
mkdir ~/.ssh # in case it does not exist yet
chmod 700 ~/.ssh # make sure this directory is not accessible to other users
ssh-keygen # create keys for logging in
</pre>
You will then transfer the private key file (the one that does not end in .pub) to your local computer in the location for ssh keys. This varies depending on your operating system. On Linux and Mac OS, it will be in <code>~/.ssh</code>.

= CS Server Policies =
== Prohibitions ==
For any accounts that you have on the CS server, you should follow all ISU policies. In particular the following are prohibited -
* using your account to store or distribute anything that is against its terms/copyright/etc. (e.g., no movies, textbooks, answers to HW problems)
* using your account to do anything that is illegal
* using a password that is too easy to guess (i.e., a password cracker that we run finds your password)
* overloading the CPU or GPU of the system, or filling up any of the system drives
* anything that is along these lines that we have not thought to state explicitly
A violation of any of these will result in your account being locked and no longer being allowed to have an account on the systems.

== Inactivity ==
Accounts that are not used for a period of 6 months will likely be locked as a security precaution. You can write to root@cs.indstate.edu to ask to have your account unlocked again.

=Student Use and Course Account=
For courses that are currently being offered, if the course uses the server, a class account is created that the instructor of the course can use if they like. This is explained with two examples: CS 151 Intro to Computer Science, and CS 473/573 Computer Networks.

==Course Account==
An account on the system is created where files for the class can be kept that are to be shared with the students. For CS 151, the account created has username <code>cs151</code>. For CS 473/573, a single account, <code>cs473</code>, is created that is to be used for both courses.

==Student Use==
For students who are currently enrolled in a CS course that uses the server, the first time you login to the system with your ISU portal account, a directory should be created within your account for the course. For example, students in CS 151 will have a directory <code>cs151</code>, and students in CS 473/573 will have a directory <code>cs473</code>.

Permissions are set on the system so that instructors of the course have read access to the files within student's course directories for their courses. The instructor for CS 151 will have read access to the <code>cs151</code> directories of the students enrolled in CS 151; the instructor for CS 473/573 will have read access to the <code>cs473</code> directories of the students enrolled in CS 473/573; etc. The instructor of the course might have the students submit their work on the server within these directories. Each instructor can choose how they would like to do this.

The course account for each course also has read access to the directories for that course. For example, the <code>cs151</code> account will have read access to the <code>cs151</code> directories within any student enrolled in CS 151.

==Course Account - Instructor Private Files==
The course account is created with a <code>~/private</code> directory that is not accessible to other users (i.e., not accessible to students). The class list (aka roster) of students and their accounts is put into this directory (<code>classlist_brief.csv</code> with the most important information for each student, and <code>classlist_full.csv</code> with more information). The instructor could keep other files in this <code>private</code> directory that is meant to be private (e.g., model solutions or grading information).

Inside the <code>~/private/</code> directory of the course account, there is also a <code>students</code> directory that has symbolic links to each of the student's course directories in the course. For example, if the course is cs151, and if the user jdoe12345@isuad.indstate.edu is a student in the course, then there will be a link <code>/home/cs151/private/students/jdoe12345@isuad.indstate.edu</code> that is a link to the cs151 directory for this student (<code>/home/jdoe12345@isuad.indstate.edu/cs151/</code>). The instructor for the course can quickly get into the students' directories for the course (but not their home directory) by going to the private/students/ directory and going from there.

The accounts for the instructors of the course are set so they can sudo as the course account. If the instructor of CS 151 uses the local account <code>jkinne</code> then this user can run the following command to get a shell running as the CS 151 course account: <code>sudo -u cs151 -i</code>
Note that this only works for local accounts, and does not work for ISU Portal accounts (it might work for the jkinne local account but not for the jkinne@isuad.indstate.edu account).

====Change of Semester and Backups====
Before the next semester, a backup copy of each course account will be created that will be in the course's <code>~/private/backup/</code> directory. A directory will be created for the term, and it will have all of the course account's files from that term within it.

Once the backup has been created for the previous term, the instructor for the current semester can remove files and directories that are no longer needed for the new term. For example, you can clear out the assignment directories in the course account's home directory, and also the student submissions that are in <code>~/private/submissions/</code>. Those files will still be in the backup directory in case you need them later.

When the new semester starts (if the course is running in the new semester), the following in the <code>~/private</code> directory will be updated to be for the new term: classlist_brief.csv, classlist_full.csv, students directory (symbolic links to new semester's students).

=Websites / Webservers=
==Apache==
The main cs.indstate.edu website uses the Apache web server. This is configured so that any user can put html and php files in the right directory in their account to be on the web server. Jeff Kinne, who has portal id <code>jkinne</code> and therefore account on the server with home directory <code>jkinne@isuad.indstate.edu</code>, would do the following to create the right directories.
<pre>
cd ~jkinne@isuad.indstate.edu # jkinne's home directory
mkdir public_html # directory apache looks in for website files
setfacl -m group:www-data:x . # give apache execute access to home directory
setfacl -R -m group:www-data:rX public_html # give apache rX access to public_html
setfacl -R -m default:group:www-data:rX public_html # and new files will also have access
cd public_html # go into that directory
echo "Hello world" > index.html # write a hello world file
</pre>
Then the file index.html will be accessible on the web at https://cs.indstate.edu/~jkinne@isuad.indstate.edu. Since the web server is Apache, you can look for help on the Apache web server about configuration options (in particular .htaccess files that you can put in your public_html directory to change some settings). By default, the Apache web server understands html and php files. There may be other types of files you would want it to be able to understand; if so you can write to root@cs.indstate.edu.

==Node, Django, etc.==
Node, Django, and many other web server frameworks can also be run off of the CS server. These generally will pick a port that they will run off of, and you run the main file for your server. Note that the Apache web server uses the "standard" ports (80 for http and 443 for https), so you cannot use those. If you want to run a Node, Django, or similar web server off of the CS server, you need to pick a port that isn't used for anything else. You should never pick a port number that is below 1024 and really should avoid port numbers below 10000. If you want to make sure to pick a port that will not interfere with anything, write to root@cs.indstate.edu. If you were to run your node web server with port 60000, then you would browse to it on the web at https://cs.indstate.edu:60000. Note that there is indeed normally a node server running on that particular port.

=Assignments=
Any directory within the course account can be used as an assignment. For example, suppose the account <code>cs151</code> contains a directory <code>h7</code>. This directory might have files for the students to use on the assignment; they can view these files by going to the directory <code>/home/cs151/h7/</code>.

A student can "checkout" or "get" an assignment by running
<pre>hw_get.py cs151 h7</pre>
This will copy the <code>h7</code> directory that is in the <code>cs151</code> account into the <code>cs151</code> directory of the user that executes the command.

An instructor can collect an assignment by running the script <code>hw_collect.py</code>. For the above example, the instructor would run: <code>hw_collect.py cs151 h7</code>. This will go into each student in the course's <code>cs151</code> directory and copy their h7 directory into <code>/home/cs151/private/submissions/h7/</code>. There will be a new directory in that submissions directory for the date and time the submissions were collected. For example, if the user jdoe12345@isuad.indstate.edu is in the cs151 course, then the contents of <code>/home/jdoe12345@isuad.indstate.edu/h7/</code> will be copied into the submission directory (inside of <code>/home/cs151/private/submissions/h7/</code>). The directory <code>/home/cs151/private/submissions/h7/</code> will have a symbolic link <code>latest</code> that is a pointer to the latest submission.

There is a system in place that can be used for auto-checking the output of student programs. The instructor creates a file <code>.tests.json</code> inside of the assignment directory that has the test cases. The instructor will also need to create a correct working version of each program that can be run to get the "correct" results. The students will use the <code>hw_check.py</code> command to check their output. The instructor can also use the same comment to check student submissions. You can get more details about how this works by logging into the system and running: <code>hw_check.py --help</code>.

=Spring 2026=
The following is the list of courses that are supported on the server for the fall 2025, along with the instructor accounts (aka admin accounts) for each course.
<pre>
course,admin_accounts
cs151,"jkinne,jeff,jkinne@isuad.indstate.edu"
cs170,"hrafieipour@isuad.indstate.edu"
cs201,"majid,mafsharnoghon@isuad.indstate.edu"
cs203,"namoako,namoako@isuad.indstate.edu"
cs211,"mjenkins1@isuad.indstate.edu"
cs351,"rabhyankar@isuad.indstate.edu"
cs331,"namoako,namoako@isuad.indstate.edu"
"cs401,cs501","majid,mafsharnoghon@isuad.indstate.edu"
cs401L,"majid,mafsharnoghon@isuad.indstate.edu"
"cs456,cs556","jcompton5,jcompton5@isuad.indstate.edu"
cs456L,"jcompton5,jcompton5@isuad.indstate.edu"
"cs457,cs557","kwexoo,kexoo@isuad.indstate.edu"
cs457L,"kwexoo,kexoo@isuad.indstate.edu"
"cs458,cs558","namoako,namoako@isuad.indstate.edu"
cs458L,"namoako,namoako@isuad.indstate.edu"
"cs469,cs569","katterson1,katterson1@isuad.indstate.edu"
"cs475,cs575","rabhyankar@isuad.indstate.edu"
cs500,"jkinne,jeff,jkinne@isuad.indstate.edu"
cs600,"arash,arafiey@isuad.indstate.edu"
"cs601,cs417","majid,mafsharnoghon@isuad.indstate.edu"
cs609,"katterson1,katterson1@isuad.indstate.edu"
cs611,"rabhyankar@isuad.indstate.edu"
cs618,"shosseini@isuad.indstate.edu"
cs685,"arash,arafiey@isuad.indstate.edu"
cs695,"arash,arafiey@isuad.indstate.edu"
ect438,"jkinne,jeff,jkinne@isuad.indstate.edu"
</pre>
If any course instructors would like any additions, subtractions, or changes to these, let the sys-admin know.

CS accounts

2026-06-03T01:52:02Z

Jkinne: /* SSH Key */

This page gives information about logging into and using the CS server (cs.indstate.edu). For help about getting started with using the terminal once you can login, see [[Linux and CS Systems - Getting Started]].

=Logging In=
The CS server is a Linux server. The primary ways you will login to the server is either (a) with a terminal (aka shell) that allows you to type text commands, or (b) with an sftp program to transfer files between your computer and the server. In either case, you need a username (aka login) and password. There are two types of accounts on the system - ISU portal accounts, and local accounts.

==ISU Portal Accounts==
Any student/faculty/staff who is involved in CS courses or programs (enrolled in a course, teaching a course, etc.) can login to cs.indstate.edu using their full ISU email address and portal password. The first time you login to the system, an account is created on the system that you can use. It will set your home directory on the system to <code>/home/SID@isuad.indstate.edu/</code> where <code>SID</code> is your portal id (aka sycamore id - for students it is the part before the @sycamores in your email address). After logging in, you can run the <code>pwd</code> command to see this.

For those familiar with Linux already... Note that there is not currently "finger information" about ISU portal account users. In fact, trying to run something like "finger jkinne@isuad.indstate.edu" will fail. Note that instructors of current courses can get a class list (aka roster) of accounts for their course; see below.

==Local Accounts==
Some users will have accounts on the CS server that are not tied to their ISU portal accounts. For example, CS faculty have local accounts, and a number of users of the server prior to 2025 have local accounts. These are accounts with username and password that were created just on the server (the ability to login to the server with ISU portal credentials was added in 2025). Any new instructor teaching a CS course can ask for a local account if you do not have one already - write to root@cs.indstate.edu.

==SSH Key==
You can setup an SSH key to login to the system. You will first need to login to the system normally. Once you are logged in, you can run the following commands.
<pre>
mkdir ~/.ssh # in case it does not exist yet
chmod 700 ~/.ssh # make sure this directory is not accessible to other users
ssh-keygen # create keys for logging in
</pre>
You will then transfer the private key file (the one that does not end in .pub) to your local computer in the location for ssh keys. This varies depending on your operating system. On Linux and Mac OS, it will be in <code>~/.ssh</code>.

= CS Server Policies =
== Prohibitions ==
For any accounts that you have on the CS server, you should follow all ISU policies. In particular the following are prohibited -
* using your account to store or distribute anything that is against its terms/copyright/etc. (e.g., no movies, textbooks, answers to HW problems)
* using your account to do anything that is illegal
* using a password that is too easy to guess (i.e., a password cracker that we run finds your password)
* overloading the CPU or GPU of the system, or filling up any of the system drives
* anything that is along these lines that we have not thought to state explicitly
A violation of any of these will result in your account being locked and no longer being allowed to have an account on the systems.

== Inactivity ==
Accounts that are not used for a period of 6 months will likely be locked as a security precaution. You can write to root@cs.indstate.edu to ask to have your account unlocked again.

=Student Use and Course Account=
For courses that are currently being offered, if the course uses the server, a class account is created that the instructor of the course can use if they like. This is explained with two examples: CS 151 Intro to Computer Science, and CS 473/573 Computer Networks.

==Course Account==
An account on the system is created where files for the class can be kept that are to be shared with the students. For CS 151, the account created has username <code>cs151</code>. For CS 473/573, a single account, <code>cs473</code>, is created that is to be used for both courses.

==Student Use==
For students who are currently enrolled in a CS course that uses the server, the first time you login to the system with your ISU portal account, a directory should be created within your account for the course. For example, students in CS 151 will have a directory <code>cs151</code>, and students in CS 473/573 will have a directory <code>cs473</code>.

Permissions are set on the system so that instructors of the course have read access to the files within student's course directories for their courses. The instructor for CS 151 will have read access to the <code>cs151</code> directories of the students enrolled in CS 151; the instructor for CS 473/573 will have read access to the <code>cs473</code> directories of the students enrolled in CS 473/573; etc. The instructor of the course might have the students submit their work on the server within these directories. Each instructor can choose how they would like to do this.

The course account for each course also has read access to the directories for that course. For example, the <code>cs151</code> account will have read access to the <code>cs151</code> directories within any student enrolled in CS 151.

==Course Account - Instructor Private Files==
The course account is created with a <code>~/private</code> directory that is not accessible to other users (i.e., not accessible to students). The class list (aka roster) of students and their accounts is put into this directory (<code>classlist_brief.csv</code> with the most important information for each student, and <code>classlist_full.csv</code> with more information). The instructor could keep other files in this <code>private</code> directory that is meant to be private (e.g., model solutions or grading information).

Inside the <code>~/private/</code> directory of the course account, there is also a <code>students</code> directory that has symbolic links to each of the student's course directories in the course. For example, if the course is cs151, and if the user jdoe12345@isuad.indstate.edu is a student in the course, then there will be a link <code>/home/cs151/private/students/jdoe12345@isuad.indstate.edu</code> that is a link to the cs151 directory for this student (<code>/home/jdoe12345@isuad.indstate.edu/cs151/</code>). The instructor for the course can quickly get into the students' directories for the course (but not their home directory) by going to the private/students/ directory and going from there.

The accounts for the instructors of the course are set so they can sudo as the course account. If the instructor of CS 151 uses the local account <code>jkinne</code> then this user can run the following command to get a shell running as the CS 151 course account: <code>sudo -u cs151 -i</code>
Note that this only works for local accounts, and does not work for ISU Portal accounts (it might work for the jkinne local account but not for the jkinne@isuad.indstate.edu account).

====Change of Semester and Backups====
Before the next semester, a backup copy of each course account will be created that will be in the course's <code>~/private/backup/</code> directory. A directory will be created for the term, and it will have all of the course account's files from that term within it.

Once the backup has been created for the previous term, the instructor for the current semester can remove files and directories that are no longer needed for the new term. For example, you can clear out the assignment directories in the course account's home directory, and also the student submissions that are in <code>~/private/submissions/</code>. Those files will still be in the backup directory in case you need them later.

When the new semester starts (if the course is running in the new semester), the following in the <code>~/private</code> directory will be updated to be for the new term: classlist_brief.csv, classlist_full.csv, students directory (symbolic links to new semester's students).

=Websites / Webservers=
==Apache==
The main cs.indstate.edu website uses the Apache web server. This is configured so that any user can put html and php files in the right directory in their account to be on the web server. Jeff Kinne, who has portal id <code>jkinne</code> and therefore account on the server with home directory <code>jkinne@isuad.indstate.edu</code>, would do the following to create the right directories.
<pre>
cd ~jkinne@isuad.indstate.edu # jkinne's home directory
mkdir public_html # directory apache looks in for website files
setfacl -m group:www-data:x . # give apache execute access to home directory
setfacl -R -m group:www-data:rX public_html # give apache rX access to public_html
setfacl -R -m default:group:www-data:rX public_html # and new files will also have access
cd public_html # go into that directory
echo "Hello world" > index.html # write a hello world file
</pre>
Then the file index.html will be accessible on the web at https://cs.indstate.edu/~jkinne@isuad.indstate.edu. Since the web server is Apache, you can look for help on the Apache web server about configuration options (in particular .htaccess files that you can put in your public_html directory to change some settings). By default, the Apache web server understands html and php files. There may be other types of files you would want it to be able to understand; if so you can write to root@cs.indstate.edu.

==Node, Django, etc.==
Node, Django, and many other web server frameworks can also be run off of the CS server. These generally will pick a port that they will run off of, and you run the main file for your server. Note that the Apache web server uses the "standard" ports (80 for http and 443 for https), so you cannot use those. If you want to run a Node, Django, or similar web server off of the CS server, you need to pick a port that isn't used for anything else. You should never pick a port number that is below 1024 and really should avoid port numbers below 10000. If you want to make sure to pick a port that will not interfere with anything, write to root@cs.indstate.edu. If you were to run your node web server with port 60000, then you would browse to it on the web at https://cs.indstate.edu:60000. Note that there is indeed normally a node server running on that particular port.

=Assignments=
Any directory within the course account can be used as an assignment. For example, suppose the account <code>cs151</code> contains a directory <code>h7</code>. This directory might have files for the students to use on the assignment; they can view these files by going to the directory <code>/home/cs151/h7/</code>.

A student can "checkout" or "get" an assignment by running
<pre>hw_get.py cs151 h7</pre>
This will copy the <code>h7</code> directory that is in the <code>cs151</code> account into the <code>cs151</code> directory of the user that executes the command.

An instructor can collect an assignment by running the script <code>hw_collect.py</code>. For the above example, the instructor would run: <code>hw_collect.py cs151 h7</code>. This will go into each student in the course's <code>cs151</code> directory and copy their h7 directory into <code>/home/cs151/private/submissions/h7/</code>. There will be a new directory in that submissions directory for the date and time the submissions were collected. For example, if the user jdoe12345@isuad.indstate.edu is in the cs151 course, then the contents of <code>/home/jdoe12345@isuad.indstate.edu/h7/</code> will be copied into the submission directory (inside of <code>/home/cs151/private/submissions/h7/</code>). The directory <code>/home/cs151/private/submissions/h7/</code> will have a symbolic link <code>latest</code> that is a pointer to the latest submission.

There is a system in place that can be used for auto-checking the output of student programs. The instructor creates a file <code>.tests.json</code> inside of the assignment directory that has the test cases. The instructor will also need to create a correct working version of each program that can be run to get the "correct" results. The students will use the <code>hw_check.py</code> command to check their output. The instructor can also use the same comment to check student submissions. You can get more details about how this works by logging into the system and running: <code>hw_check.py --help</code>.

=Spring 2026=
The following is the list of courses that are supported on the server for the fall 2025, along with the instructor accounts (aka admin accounts) for each course.
<pre>
course,admin_accounts
cs151,"jkinne,jeff,jkinne@isuad.indstate.edu"
cs170,"hrafieipour@isuad.indstate.edu"
cs201,"majid,mafsharnoghon@isuad.indstate.edu"
cs203,"namoako,namoako@isuad.indstate.edu"
cs211,"mjenkins1@isuad.indstate.edu"
cs351,"rabhyankar@isuad.indstate.edu"
cs331,"namoako,namoako@isuad.indstate.edu"
"cs401,cs501","majid,mafsharnoghon@isuad.indstate.edu"
cs401L,"majid,mafsharnoghon@isuad.indstate.edu"
"cs456,cs556","jcompton5,jcompton5@isuad.indstate.edu"
cs456L,"jcompton5,jcompton5@isuad.indstate.edu"
"cs457,cs557","kwexoo,kexoo@isuad.indstate.edu"
cs457L,"kwexoo,kexoo@isuad.indstate.edu"
"cs458,cs558","namoako,namoako@isuad.indstate.edu"
cs458L,"namoako,namoako@isuad.indstate.edu"
"cs469,cs569","katterson1,katterson1@isuad.indstate.edu"
"cs475,cs575","rabhyankar@isuad.indstate.edu"
cs500,"jkinne,jeff,jkinne@isuad.indstate.edu"
cs600,"arash,arafiey@isuad.indstate.edu"
"cs601,cs417","majid,mafsharnoghon@isuad.indstate.edu"
cs609,"katterson1,katterson1@isuad.indstate.edu"
cs611,"rabhyankar@isuad.indstate.edu"
cs618,"shosseini@isuad.indstate.edu"
cs685,"arash,arafiey@isuad.indstate.edu"
cs695,"arash,arafiey@isuad.indstate.edu"
ect438,"jkinne,jeff,jkinne@isuad.indstate.edu"
</pre>
If any course instructors would like any additions, subtractions, or changes to these, let the sys-admin know.

CS accounts

2026-06-03T01:50:39Z

Jkinne: /* ISU Portal Accounts */

This page gives information about logging into and using the CS server (cs.indstate.edu). For help about getting started with using the terminal once you can login, see [[Linux and CS Systems - Getting Started]].

=Logging In=
The CS server is a Linux server. The primary ways you will login to the server is either (a) with a terminal (aka shell) that allows you to type text commands, or (b) with an sftp program to transfer files between your computer and the server. In either case, you need a username (aka login) and password. There are two types of accounts on the system - ISU portal accounts, and local accounts.

==ISU Portal Accounts==
Any student/faculty/staff who is involved in CS courses or programs (enrolled in a course, teaching a course, etc.) can login to cs.indstate.edu using their full ISU email address and portal password. The first time you login to the system, an account is created on the system that you can use. It will set your home directory on the system to <code>/home/SID@isuad.indstate.edu/</code> where <code>SID</code> is your portal id (aka sycamore id - for students it is the part before the @sycamores in your email address). After logging in, you can run the <code>pwd</code> command to see this.

For those familiar with Linux already... Note that there is not currently "finger information" about ISU portal account users. In fact, trying to run something like "finger jkinne@isuad.indstate.edu" will fail. Note that instructors of current courses can get a class list (aka roster) of accounts for their course; see below.

==Local Accounts==
Some users will have accounts on the CS server that are not tied to their ISU portal accounts. For example, CS faculty have local accounts, and a number of users of the server prior to 2025 have local accounts. These are accounts with username and password that were created just on the server (the ability to login to the server with ISU portal credentials was added in 2025). Any new instructor teaching a CS course can ask for a local account if you do not have one already - write to root@cs.indstate.edu.

==SSH Key==
You can setup an SSH key to login to the system. You will first need to login to the system normally. Once you are logged in, you can run the following commands.
<pre>
mkdir ~/.ssh # in case it does not exist yet
chmod 700 ~/.ssh # make sure this directory is not accessible to other users
ssh-keygen # create keys for logging in
</pre>
You will then transfer the private key file (the one that does not end in .pub) to your local computer in the location for ssh keys.

= CS Server Policies =
== Prohibitions ==
For any accounts that you have on the CS server, you should follow all ISU policies. In particular the following are prohibited -
* using your account to store or distribute anything that is against its terms/copyright/etc. (e.g., no movies, textbooks, answers to HW problems)
* using your account to do anything that is illegal
* using a password that is too easy to guess (i.e., a password cracker that we run finds your password)
* overloading the CPU or GPU of the system, or filling up any of the system drives
* anything that is along these lines that we have not thought to state explicitly
A violation of any of these will result in your account being locked and no longer being allowed to have an account on the systems.

== Inactivity ==
Accounts that are not used for a period of 6 months will likely be locked as a security precaution. You can write to root@cs.indstate.edu to ask to have your account unlocked again.

=Student Use and Course Account=
For courses that are currently being offered, if the course uses the server, a class account is created that the instructor of the course can use if they like. This is explained with two examples: CS 151 Intro to Computer Science, and CS 473/573 Computer Networks.

==Course Account==
An account on the system is created where files for the class can be kept that are to be shared with the students. For CS 151, the account created has username <code>cs151</code>. For CS 473/573, a single account, <code>cs473</code>, is created that is to be used for both courses.

==Student Use==
For students who are currently enrolled in a CS course that uses the server, the first time you login to the system with your ISU portal account, a directory should be created within your account for the course. For example, students in CS 151 will have a directory <code>cs151</code>, and students in CS 473/573 will have a directory <code>cs473</code>.

Permissions are set on the system so that instructors of the course have read access to the files within student's course directories for their courses. The instructor for CS 151 will have read access to the <code>cs151</code> directories of the students enrolled in CS 151; the instructor for CS 473/573 will have read access to the <code>cs473</code> directories of the students enrolled in CS 473/573; etc. The instructor of the course might have the students submit their work on the server within these directories. Each instructor can choose how they would like to do this.

The course account for each course also has read access to the directories for that course. For example, the <code>cs151</code> account will have read access to the <code>cs151</code> directories within any student enrolled in CS 151.

==Course Account - Instructor Private Files==
The course account is created with a <code>~/private</code> directory that is not accessible to other users (i.e., not accessible to students). The class list (aka roster) of students and their accounts is put into this directory (<code>classlist_brief.csv</code> with the most important information for each student, and <code>classlist_full.csv</code> with more information). The instructor could keep other files in this <code>private</code> directory that is meant to be private (e.g., model solutions or grading information).

Inside the <code>~/private/</code> directory of the course account, there is also a <code>students</code> directory that has symbolic links to each of the student's course directories in the course. For example, if the course is cs151, and if the user jdoe12345@isuad.indstate.edu is a student in the course, then there will be a link <code>/home/cs151/private/students/jdoe12345@isuad.indstate.edu</code> that is a link to the cs151 directory for this student (<code>/home/jdoe12345@isuad.indstate.edu/cs151/</code>). The instructor for the course can quickly get into the students' directories for the course (but not their home directory) by going to the private/students/ directory and going from there.

The accounts for the instructors of the course are set so they can sudo as the course account. If the instructor of CS 151 uses the local account <code>jkinne</code> then this user can run the following command to get a shell running as the CS 151 course account: <code>sudo -u cs151 -i</code>
Note that this only works for local accounts, and does not work for ISU Portal accounts (it might work for the jkinne local account but not for the jkinne@isuad.indstate.edu account).

====Change of Semester and Backups====
Before the next semester, a backup copy of each course account will be created that will be in the course's <code>~/private/backup/</code> directory. A directory will be created for the term, and it will have all of the course account's files from that term within it.

Once the backup has been created for the previous term, the instructor for the current semester can remove files and directories that are no longer needed for the new term. For example, you can clear out the assignment directories in the course account's home directory, and also the student submissions that are in <code>~/private/submissions/</code>. Those files will still be in the backup directory in case you need them later.

When the new semester starts (if the course is running in the new semester), the following in the <code>~/private</code> directory will be updated to be for the new term: classlist_brief.csv, classlist_full.csv, students directory (symbolic links to new semester's students).

=Websites / Webservers=
==Apache==
The main cs.indstate.edu website uses the Apache web server. This is configured so that any user can put html and php files in the right directory in their account to be on the web server. Jeff Kinne, who has portal id <code>jkinne</code> and therefore account on the server with home directory <code>jkinne@isuad.indstate.edu</code>, would do the following to create the right directories.
<pre>
cd ~jkinne@isuad.indstate.edu # jkinne's home directory
mkdir public_html # directory apache looks in for website files
setfacl -m group:www-data:x . # give apache execute access to home directory
setfacl -R -m group:www-data:rX public_html # give apache rX access to public_html
setfacl -R -m default:group:www-data:rX public_html # and new files will also have access
cd public_html # go into that directory
echo "Hello world" > index.html # write a hello world file
</pre>
Then the file index.html will be accessible on the web at https://cs.indstate.edu/~jkinne@isuad.indstate.edu. Since the web server is Apache, you can look for help on the Apache web server about configuration options (in particular .htaccess files that you can put in your public_html directory to change some settings). By default, the Apache web server understands html and php files. There may be other types of files you would want it to be able to understand; if so you can write to root@cs.indstate.edu.

==Node, Django, etc.==
Node, Django, and many other web server frameworks can also be run off of the CS server. These generally will pick a port that they will run off of, and you run the main file for your server. Note that the Apache web server uses the "standard" ports (80 for http and 443 for https), so you cannot use those. If you want to run a Node, Django, or similar web server off of the CS server, you need to pick a port that isn't used for anything else. You should never pick a port number that is below 1024 and really should avoid port numbers below 10000. If you want to make sure to pick a port that will not interfere with anything, write to root@cs.indstate.edu. If you were to run your node web server with port 60000, then you would browse to it on the web at https://cs.indstate.edu:60000. Note that there is indeed normally a node server running on that particular port.

=Assignments=
Any directory within the course account can be used as an assignment. For example, suppose the account <code>cs151</code> contains a directory <code>h7</code>. This directory might have files for the students to use on the assignment; they can view these files by going to the directory <code>/home/cs151/h7/</code>.

A student can "checkout" or "get" an assignment by running
<pre>hw_get.py cs151 h7</pre>
This will copy the <code>h7</code> directory that is in the <code>cs151</code> account into the <code>cs151</code> directory of the user that executes the command.

An instructor can collect an assignment by running the script <code>hw_collect.py</code>. For the above example, the instructor would run: <code>hw_collect.py cs151 h7</code>. This will go into each student in the course's <code>cs151</code> directory and copy their h7 directory into <code>/home/cs151/private/submissions/h7/</code>. There will be a new directory in that submissions directory for the date and time the submissions were collected. For example, if the user jdoe12345@isuad.indstate.edu is in the cs151 course, then the contents of <code>/home/jdoe12345@isuad.indstate.edu/h7/</code> will be copied into the submission directory (inside of <code>/home/cs151/private/submissions/h7/</code>). The directory <code>/home/cs151/private/submissions/h7/</code> will have a symbolic link <code>latest</code> that is a pointer to the latest submission.

There is a system in place that can be used for auto-checking the output of student programs. The instructor creates a file <code>.tests.json</code> inside of the assignment directory that has the test cases. The instructor will also need to create a correct working version of each program that can be run to get the "correct" results. The students will use the <code>hw_check.py</code> command to check their output. The instructor can also use the same comment to check student submissions. You can get more details about how this works by logging into the system and running: <code>hw_check.py --help</code>.

=Spring 2026=
The following is the list of courses that are supported on the server for the fall 2025, along with the instructor accounts (aka admin accounts) for each course.
<pre>
course,admin_accounts
cs151,"jkinne,jeff,jkinne@isuad.indstate.edu"
cs170,"hrafieipour@isuad.indstate.edu"
cs201,"majid,mafsharnoghon@isuad.indstate.edu"
cs203,"namoako,namoako@isuad.indstate.edu"
cs211,"mjenkins1@isuad.indstate.edu"
cs351,"rabhyankar@isuad.indstate.edu"
cs331,"namoako,namoako@isuad.indstate.edu"
"cs401,cs501","majid,mafsharnoghon@isuad.indstate.edu"
cs401L,"majid,mafsharnoghon@isuad.indstate.edu"
"cs456,cs556","jcompton5,jcompton5@isuad.indstate.edu"
cs456L,"jcompton5,jcompton5@isuad.indstate.edu"
"cs457,cs557","kwexoo,kexoo@isuad.indstate.edu"
cs457L,"kwexoo,kexoo@isuad.indstate.edu"
"cs458,cs558","namoako,namoako@isuad.indstate.edu"
cs458L,"namoako,namoako@isuad.indstate.edu"
"cs469,cs569","katterson1,katterson1@isuad.indstate.edu"
"cs475,cs575","rabhyankar@isuad.indstate.edu"
cs500,"jkinne,jeff,jkinne@isuad.indstate.edu"
cs600,"arash,arafiey@isuad.indstate.edu"
"cs601,cs417","majid,mafsharnoghon@isuad.indstate.edu"
cs609,"katterson1,katterson1@isuad.indstate.edu"
cs611,"rabhyankar@isuad.indstate.edu"
cs618,"shosseini@isuad.indstate.edu"
cs685,"arash,arafiey@isuad.indstate.edu"
cs695,"arash,arafiey@isuad.indstate.edu"
ect438,"jkinne,jeff,jkinne@isuad.indstate.edu"
</pre>
If any course instructors would like any additions, subtractions, or changes to these, let the sys-admin know.

CS accounts

2026-06-03T01:49:36Z

Jkinne: /* Logging In */

This page gives information about logging into and using the CS server (cs.indstate.edu). For help about getting started with using the terminal once you can login, see [[Linux and CS Systems - Getting Started]].

=Logging In=
The CS server is a Linux server. The primary ways you will login to the server is either (a) with a terminal (aka shell) that allows you to type text commands, or (b) with an sftp program to transfer files between your computer and the server. In either case, you need a username (aka login) and password. There are two types of accounts on the system - ISU portal accounts, and local accounts.

==ISU Portal Accounts==
Any student/faculty/staff who is involved in CS courses or programs (enrolled in a course, teaching a course, etc.) can login to cs.indstate.edu using their full ISU email address and portal password. The first time you login to the system, an account is created on the system that you can use. It will set your home directory on the system to <code>/home/SID@isuad.indstate.edu/</code> where <code>SID</code> is your portal id (aka sycamore id - for students it is the part before the @sycamores in your email address). After logging in, you can run the <code>pwd</code> command to see this.

Note that there is not currently "finger information" about ISU portal account users. In fact, trying to run something like "finger jkinne@isuad.indstate.edu" will fail. Note that instructors of current courses can get a class list (aka roster) of accounts for their course; see below.

==Local Accounts==
Some users will have accounts on the CS server that are not tied to their ISU portal accounts. For example, CS faculty have local accounts, and a number of users of the server prior to 2025 have local accounts. These are accounts with username and password that were created just on the server (the ability to login to the server with ISU portal credentials was added in 2025). Any new instructor teaching a CS course can ask for a local account if you do not have one already - write to root@cs.indstate.edu.

==SSH Key==
You can setup an SSH key to login to the system. You will first need to login to the system normally. Once you are logged in, you can run the following commands.
<pre>
mkdir ~/.ssh # in case it does not exist yet
chmod 700 ~/.ssh # make sure this directory is not accessible to other users
ssh-keygen # create keys for logging in
</pre>
You will then transfer the private key file (the one that does not end in .pub) to your local computer in the location for ssh keys.

= CS Server Policies =
== Prohibitions ==
For any accounts that you have on the CS server, you should follow all ISU policies. In particular the following are prohibited -
* using your account to store or distribute anything that is against its terms/copyright/etc. (e.g., no movies, textbooks, answers to HW problems)
* using your account to do anything that is illegal
* using a password that is too easy to guess (i.e., a password cracker that we run finds your password)
* overloading the CPU or GPU of the system, or filling up any of the system drives
* anything that is along these lines that we have not thought to state explicitly
A violation of any of these will result in your account being locked and no longer being allowed to have an account on the systems.

== Inactivity ==
Accounts that are not used for a period of 6 months will likely be locked as a security precaution. You can write to root@cs.indstate.edu to ask to have your account unlocked again.

=Student Use and Course Account=
For courses that are currently being offered, if the course uses the server, a class account is created that the instructor of the course can use if they like. This is explained with two examples: CS 151 Intro to Computer Science, and CS 473/573 Computer Networks.

==Course Account==
An account on the system is created where files for the class can be kept that are to be shared with the students. For CS 151, the account created has username <code>cs151</code>. For CS 473/573, a single account, <code>cs473</code>, is created that is to be used for both courses.

==Student Use==
For students who are currently enrolled in a CS course that uses the server, the first time you login to the system with your ISU portal account, a directory should be created within your account for the course. For example, students in CS 151 will have a directory <code>cs151</code>, and students in CS 473/573 will have a directory <code>cs473</code>.

Permissions are set on the system so that instructors of the course have read access to the files within student's course directories for their courses. The instructor for CS 151 will have read access to the <code>cs151</code> directories of the students enrolled in CS 151; the instructor for CS 473/573 will have read access to the <code>cs473</code> directories of the students enrolled in CS 473/573; etc. The instructor of the course might have the students submit their work on the server within these directories. Each instructor can choose how they would like to do this.

The course account for each course also has read access to the directories for that course. For example, the <code>cs151</code> account will have read access to the <code>cs151</code> directories within any student enrolled in CS 151.

==Course Account - Instructor Private Files==
The course account is created with a <code>~/private</code> directory that is not accessible to other users (i.e., not accessible to students). The class list (aka roster) of students and their accounts is put into this directory (<code>classlist_brief.csv</code> with the most important information for each student, and <code>classlist_full.csv</code> with more information). The instructor could keep other files in this <code>private</code> directory that is meant to be private (e.g., model solutions or grading information).

Inside the <code>~/private/</code> directory of the course account, there is also a <code>students</code> directory that has symbolic links to each of the student's course directories in the course. For example, if the course is cs151, and if the user jdoe12345@isuad.indstate.edu is a student in the course, then there will be a link <code>/home/cs151/private/students/jdoe12345@isuad.indstate.edu</code> that is a link to the cs151 directory for this student (<code>/home/jdoe12345@isuad.indstate.edu/cs151/</code>). The instructor for the course can quickly get into the students' directories for the course (but not their home directory) by going to the private/students/ directory and going from there.

The accounts for the instructors of the course are set so they can sudo as the course account. If the instructor of CS 151 uses the local account <code>jkinne</code> then this user can run the following command to get a shell running as the CS 151 course account: <code>sudo -u cs151 -i</code>
Note that this only works for local accounts, and does not work for ISU Portal accounts (it might work for the jkinne local account but not for the jkinne@isuad.indstate.edu account).

====Change of Semester and Backups====
Before the next semester, a backup copy of each course account will be created that will be in the course's <code>~/private/backup/</code> directory. A directory will be created for the term, and it will have all of the course account's files from that term within it.

Once the backup has been created for the previous term, the instructor for the current semester can remove files and directories that are no longer needed for the new term. For example, you can clear out the assignment directories in the course account's home directory, and also the student submissions that are in <code>~/private/submissions/</code>. Those files will still be in the backup directory in case you need them later.

When the new semester starts (if the course is running in the new semester), the following in the <code>~/private</code> directory will be updated to be for the new term: classlist_brief.csv, classlist_full.csv, students directory (symbolic links to new semester's students).

=Websites / Webservers=
==Apache==
The main cs.indstate.edu website uses the Apache web server. This is configured so that any user can put html and php files in the right directory in their account to be on the web server. Jeff Kinne, who has portal id <code>jkinne</code> and therefore account on the server with home directory <code>jkinne@isuad.indstate.edu</code>, would do the following to create the right directories.
<pre>
cd ~jkinne@isuad.indstate.edu # jkinne's home directory
mkdir public_html # directory apache looks in for website files
setfacl -m group:www-data:x . # give apache execute access to home directory
setfacl -R -m group:www-data:rX public_html # give apache rX access to public_html
setfacl -R -m default:group:www-data:rX public_html # and new files will also have access
cd public_html # go into that directory
echo "Hello world" > index.html # write a hello world file
</pre>
Then the file index.html will be accessible on the web at https://cs.indstate.edu/~jkinne@isuad.indstate.edu. Since the web server is Apache, you can look for help on the Apache web server about configuration options (in particular .htaccess files that you can put in your public_html directory to change some settings). By default, the Apache web server understands html and php files. There may be other types of files you would want it to be able to understand; if so you can write to root@cs.indstate.edu.

==Node, Django, etc.==
Node, Django, and many other web server frameworks can also be run off of the CS server. These generally will pick a port that they will run off of, and you run the main file for your server. Note that the Apache web server uses the "standard" ports (80 for http and 443 for https), so you cannot use those. If you want to run a Node, Django, or similar web server off of the CS server, you need to pick a port that isn't used for anything else. You should never pick a port number that is below 1024 and really should avoid port numbers below 10000. If you want to make sure to pick a port that will not interfere with anything, write to root@cs.indstate.edu. If you were to run your node web server with port 60000, then you would browse to it on the web at https://cs.indstate.edu:60000. Note that there is indeed normally a node server running on that particular port.

=Assignments=
Any directory within the course account can be used as an assignment. For example, suppose the account <code>cs151</code> contains a directory <code>h7</code>. This directory might have files for the students to use on the assignment; they can view these files by going to the directory <code>/home/cs151/h7/</code>.

A student can "checkout" or "get" an assignment by running
<pre>hw_get.py cs151 h7</pre>
This will copy the <code>h7</code> directory that is in the <code>cs151</code> account into the <code>cs151</code> directory of the user that executes the command.

An instructor can collect an assignment by running the script <code>hw_collect.py</code>. For the above example, the instructor would run: <code>hw_collect.py cs151 h7</code>. This will go into each student in the course's <code>cs151</code> directory and copy their h7 directory into <code>/home/cs151/private/submissions/h7/</code>. There will be a new directory in that submissions directory for the date and time the submissions were collected. For example, if the user jdoe12345@isuad.indstate.edu is in the cs151 course, then the contents of <code>/home/jdoe12345@isuad.indstate.edu/h7/</code> will be copied into the submission directory (inside of <code>/home/cs151/private/submissions/h7/</code>). The directory <code>/home/cs151/private/submissions/h7/</code> will have a symbolic link <code>latest</code> that is a pointer to the latest submission.

There is a system in place that can be used for auto-checking the output of student programs. The instructor creates a file <code>.tests.json</code> inside of the assignment directory that has the test cases. The instructor will also need to create a correct working version of each program that can be run to get the "correct" results. The students will use the <code>hw_check.py</code> command to check their output. The instructor can also use the same comment to check student submissions. You can get more details about how this works by logging into the system and running: <code>hw_check.py --help</code>.

=Spring 2026=
The following is the list of courses that are supported on the server for the fall 2025, along with the instructor accounts (aka admin accounts) for each course.
<pre>
course,admin_accounts
cs151,"jkinne,jeff,jkinne@isuad.indstate.edu"
cs170,"hrafieipour@isuad.indstate.edu"
cs201,"majid,mafsharnoghon@isuad.indstate.edu"
cs203,"namoako,namoako@isuad.indstate.edu"
cs211,"mjenkins1@isuad.indstate.edu"
cs351,"rabhyankar@isuad.indstate.edu"
cs331,"namoako,namoako@isuad.indstate.edu"
"cs401,cs501","majid,mafsharnoghon@isuad.indstate.edu"
cs401L,"majid,mafsharnoghon@isuad.indstate.edu"
"cs456,cs556","jcompton5,jcompton5@isuad.indstate.edu"
cs456L,"jcompton5,jcompton5@isuad.indstate.edu"
"cs457,cs557","kwexoo,kexoo@isuad.indstate.edu"
cs457L,"kwexoo,kexoo@isuad.indstate.edu"
"cs458,cs558","namoako,namoako@isuad.indstate.edu"
cs458L,"namoako,namoako@isuad.indstate.edu"
"cs469,cs569","katterson1,katterson1@isuad.indstate.edu"
"cs475,cs575","rabhyankar@isuad.indstate.edu"
cs500,"jkinne,jeff,jkinne@isuad.indstate.edu"
cs600,"arash,arafiey@isuad.indstate.edu"
"cs601,cs417","majid,mafsharnoghon@isuad.indstate.edu"
cs609,"katterson1,katterson1@isuad.indstate.edu"
cs611,"rabhyankar@isuad.indstate.edu"
cs618,"shosseini@isuad.indstate.edu"
cs685,"arash,arafiey@isuad.indstate.edu"
cs695,"arash,arafiey@isuad.indstate.edu"
ect438,"jkinne,jeff,jkinne@isuad.indstate.edu"
</pre>
If any course instructors would like any additions, subtractions, or changes to these, let the sys-admin know.

Email Lists

2026-06-03T00:11:45Z

Jkinne: /* Maintenance */

The CS faculty maintain a variety of email lists used to send announcements and keep in touch with the CS students and faculty. Each is described briefly below.

For those authorized to send email to the lists, you send email to the name of the list followed by @cs.indstate.edu. So to send email to the CS undergraduate students, you would compose a message to cs-ugrads@cs.indstate.edu. If you are not authorized to send a message to the list, it will be automatically ignored by the email system.

== Students (cs-ugrads, cs-grads, cs-courses) ==
cs-ugrads and cs-grads are used to contact Computer Science majors (both undergraduate and graduate) about events in the department, job opportunities, etc. The lists are updated each term to include the currently enrolled and active majors of the department. There is one list each for: cs undergraduate students, cs graduate students. cs-courses is updated each term to be all students taking any CS courses (whether the student is a CS major or not).

Note: students do not need to sign up for these lists as long as you have declared your major by the beginning of the semester; if you have, you are automatically put on the appropriate email lists.

The list pages are at 
http://cs.indstate.edu/mailman/listinfo/cs-ugrads/ 
http://cs.indstate.edu/mailman/listinfo/cs-grads/ 
http://cs.indstate.edu/mailman/listinfo/cs-courses/

== Jobs (cs-jobs) ==
This email list is used to pass on potential job opportunities - internships, full time positions, etc. Current CS students and alumni are welcome to join the list to receive these notices. Oftentimes, job postings are sent to all of cs-grads, cs-ugrads, and cs-jobs. '''cs-jobs is an opt-in list - you need to sign up for it.''' The list page is at http://cs.indstate.edu/mailman/listinfo/cs-jobs/

== Alumni (cs-alumni) ==
This email list is used to contact CS alumni about job opportunities or anything else that would be relevant to alumni. The list is updated each term to include those who have graduated. The list page is at http://cs.indstate.edu/mailman/listinfo/cs-alumni/

== Faculty ==
This email list is used to contact Computer Science faculty. The mailing list is cs-faculty.

== Graduate and Undergraduate Assistants ==
This email list contains all CS students working for the department.

== Maintenance ==
Terse information on what the one maintaining the email lists does...
* When adding or removing from lists, you normally use the "Membership Management" link and then either "Mass subscription" or "Mass removal". There are messages setup already so you don't need to type anything into the notes on those forms. You also normally want to select to notify the subscriber but not the list manager.
* cs-alumni - mass subscription for all who earned degrees in the previous term. Do this after degrees are posted (1-2 weeks after grades are due).
* cs-ugrads, cs-grads - mass removal of all who graduated, mass subscription of all majors. Update these when updating cs-alumni, and also about every week leading up to the start of the term and after the last day to add classes.
* cs-courses - mass removal of all from the previous term, mass subscription for all registered for the coming term. Update these starting a few weeks before the term, and about once per week until after the last day to add classes.
* cs-faculty, cs-assistants - updated once per term or year as staffing and GA positions change.
* cs-jobs - these are opt-in, so all that needs to be done is approving or denying subscription requests (approve any request from an @sycamores.indstate.edu or @indstate.edu email address).
You can get to the administrative interface from the links above. For removing all from a list, you can use scripts to do this, or you can copy/paste the entire membership list into excel, then copy/paste the email column into the "mass removal" form in the web interface.

Email Lists

2026-06-03T00:11:20Z

Jkinne: /* Faculty */

The CS faculty maintain a variety of email lists used to send announcements and keep in touch with the CS students and faculty. Each is described briefly below.

For those authorized to send email to the lists, you send email to the name of the list followed by @cs.indstate.edu. So to send email to the CS undergraduate students, you would compose a message to cs-ugrads@cs.indstate.edu. If you are not authorized to send a message to the list, it will be automatically ignored by the email system.

== Students (cs-ugrads, cs-grads, cs-courses) ==
cs-ugrads and cs-grads are used to contact Computer Science majors (both undergraduate and graduate) about events in the department, job opportunities, etc. The lists are updated each term to include the currently enrolled and active majors of the department. There is one list each for: cs undergraduate students, cs graduate students. cs-courses is updated each term to be all students taking any CS courses (whether the student is a CS major or not).

Note: students do not need to sign up for these lists as long as you have declared your major by the beginning of the semester; if you have, you are automatically put on the appropriate email lists.

The list pages are at 
http://cs.indstate.edu/mailman/listinfo/cs-ugrads/ 
http://cs.indstate.edu/mailman/listinfo/cs-grads/ 
http://cs.indstate.edu/mailman/listinfo/cs-courses/

== Jobs (cs-jobs) ==
This email list is used to pass on potential job opportunities - internships, full time positions, etc. Current CS students and alumni are welcome to join the list to receive these notices. Oftentimes, job postings are sent to all of cs-grads, cs-ugrads, and cs-jobs. '''cs-jobs is an opt-in list - you need to sign up for it.''' The list page is at http://cs.indstate.edu/mailman/listinfo/cs-jobs/

== Alumni (cs-alumni) ==
This email list is used to contact CS alumni about job opportunities or anything else that would be relevant to alumni. The list is updated each term to include those who have graduated. The list page is at http://cs.indstate.edu/mailman/listinfo/cs-alumni/

== Faculty ==
This email list is used to contact Computer Science faculty. The mailing list is cs-faculty.

== Graduate and Undergraduate Assistants ==
This email list contains all CS students working for the department.

== Maintenance ==
Terse information on what the one maintaining the email lists does...
* When adding or removing from lists, you normally use the "Membership Management" link and then either "Mass subscription" or "Mass removal". There are messages setup already so you don't need to type anything into the notes on those forms. You also normally want to select to notify the subscriber but not the list manager.
* cs-alumni - mass subscription for all who earned degrees in the previous term. Do this after degrees are posted (1-2 weeks after grades are due).
* cs-ugrads, cs-grads - mass removal of all who graduated, mass subscription of all majors. Update these when updating cs-alumni, and also about every week leading up to the start of the term and after the last day to add classes.
* cs-courses - mass removal of all from the previous term, mass subscription for all registered for the coming term. Update these starting a few weeks before the term, and about once per week until after the last day to add classes.
* cs-faculty, cs-assistants - updated once per term or year as staffing and GA positions change.
* cs-chat, cs-jobs - these are opt-in, so all that needs to be done is approving or denying subscription requests (approve any request from an @sycamores.indstate.edu or @indstate.edu email address).
You can get to the administrative interface from the links above. For removing all from a list, you can use scripts to do this, or you can copy/paste the entire membership list into excel, then copy/paste the email column into the "mass removal" form in the web interface.

Email Lists

2026-06-03T00:09:55Z

Jkinne: /* Faculty */

The CS faculty maintain a variety of email lists used to send announcements and keep in touch with the CS students and faculty. Each is described briefly below.

For those authorized to send email to the lists, you send email to the name of the list followed by @cs.indstate.edu. So to send email to the CS undergraduate students, you would compose a message to cs-ugrads@cs.indstate.edu. If you are not authorized to send a message to the list, it will be automatically ignored by the email system.

== Students (cs-ugrads, cs-grads, cs-courses) ==
cs-ugrads and cs-grads are used to contact Computer Science majors (both undergraduate and graduate) about events in the department, job opportunities, etc. The lists are updated each term to include the currently enrolled and active majors of the department. There is one list each for: cs undergraduate students, cs graduate students. cs-courses is updated each term to be all students taking any CS courses (whether the student is a CS major or not).

Note: students do not need to sign up for these lists as long as you have declared your major by the beginning of the semester; if you have, you are automatically put on the appropriate email lists.

The list pages are at 
http://cs.indstate.edu/mailman/listinfo/cs-ugrads/ 
http://cs.indstate.edu/mailman/listinfo/cs-grads/ 
http://cs.indstate.edu/mailman/listinfo/cs-courses/

== Jobs (cs-jobs) ==
This email list is used to pass on potential job opportunities - internships, full time positions, etc. Current CS students and alumni are welcome to join the list to receive these notices. Oftentimes, job postings are sent to all of cs-grads, cs-ugrads, and cs-jobs. '''cs-jobs is an opt-in list - you need to sign up for it.''' The list page is at http://cs.indstate.edu/mailman/listinfo/cs-jobs/

== Alumni (cs-alumni) ==
This email list is used to contact CS alumni about job opportunities or anything else that would be relevant to alumni. The list is updated each term to include those who have graduated. The list page is at http://cs.indstate.edu/mailman/listinfo/cs-alumni/

== Faculty ==
This email list is used to contact Computer Science faculty. The mailing list is cs-faculty.

== Maintenance ==
Terse information on what the one maintaining the email lists does...
* When adding or removing from lists, you normally use the "Membership Management" link and then either "Mass subscription" or "Mass removal". There are messages setup already so you don't need to type anything into the notes on those forms. You also normally want to select to notify the subscriber but not the list manager.
* cs-alumni - mass subscription for all who earned degrees in the previous term. Do this after degrees are posted (1-2 weeks after grades are due).
* cs-ugrads, cs-grads - mass removal of all who graduated, mass subscription of all majors. Update these when updating cs-alumni, and also about every week leading up to the start of the term and after the last day to add classes.
* cs-courses - mass removal of all from the previous term, mass subscription for all registered for the coming term. Update these starting a few weeks before the term, and about once per week until after the last day to add classes.
* cs-faculty, cs-assistants - updated once per term or year as staffing and GA positions change.
* cs-chat, cs-jobs - these are opt-in, so all that needs to be done is approving or denying subscription requests (approve any request from an @sycamores.indstate.edu or @indstate.edu email address).
You can get to the administrative interface from the links above. For removing all from a list, you can use scripts to do this, or you can copy/paste the entire membership list into excel, then copy/paste the email column into the "mass removal" form in the web interface.

Email Lists

2026-06-03T00:09:33Z

Jkinne: /* Jobs (cs-jobs) */

The CS faculty maintain a variety of email lists used to send announcements and keep in touch with the CS students and faculty. Each is described briefly below.

For those authorized to send email to the lists, you send email to the name of the list followed by @cs.indstate.edu. So to send email to the CS undergraduate students, you would compose a message to cs-ugrads@cs.indstate.edu. If you are not authorized to send a message to the list, it will be automatically ignored by the email system.

== Students (cs-ugrads, cs-grads, cs-courses) ==
cs-ugrads and cs-grads are used to contact Computer Science majors (both undergraduate and graduate) about events in the department, job opportunities, etc. The lists are updated each term to include the currently enrolled and active majors of the department. There is one list each for: cs undergraduate students, cs graduate students. cs-courses is updated each term to be all students taking any CS courses (whether the student is a CS major or not).

Note: students do not need to sign up for these lists as long as you have declared your major by the beginning of the semester; if you have, you are automatically put on the appropriate email lists.

The list pages are at 
http://cs.indstate.edu/mailman/listinfo/cs-ugrads/ 
http://cs.indstate.edu/mailman/listinfo/cs-grads/ 
http://cs.indstate.edu/mailman/listinfo/cs-courses/

== Jobs (cs-jobs) ==
This email list is used to pass on potential job opportunities - internships, full time positions, etc. Current CS students and alumni are welcome to join the list to receive these notices. Oftentimes, job postings are sent to all of cs-grads, cs-ugrads, and cs-jobs. '''cs-jobs is an opt-in list - you need to sign up for it.''' The list page is at http://cs.indstate.edu/mailman/listinfo/cs-jobs/

== Alumni (cs-alumni) ==
This email list is used to contact CS alumni about job opportunities or anything else that would be relevant to alumni. The list is updated each term to include those who have graduated. The list page is at http://cs.indstate.edu/mailman/listinfo/cs-alumni/

== Faculty ==
This email list is used to contact Computer Science faculty. The list is managed (not open to subscription requests). The mailing list is cs-faculty.

== Maintenance ==
Terse information on what the one maintaining the email lists does...
* When adding or removing from lists, you normally use the "Membership Management" link and then either "Mass subscription" or "Mass removal". There are messages setup already so you don't need to type anything into the notes on those forms. You also normally want to select to notify the subscriber but not the list manager.
* cs-alumni - mass subscription for all who earned degrees in the previous term. Do this after degrees are posted (1-2 weeks after grades are due).
* cs-ugrads, cs-grads - mass removal of all who graduated, mass subscription of all majors. Update these when updating cs-alumni, and also about every week leading up to the start of the term and after the last day to add classes.
* cs-courses - mass removal of all from the previous term, mass subscription for all registered for the coming term. Update these starting a few weeks before the term, and about once per week until after the last day to add classes.
* cs-faculty, cs-assistants - updated once per term or year as staffing and GA positions change.
* cs-chat, cs-jobs - these are opt-in, so all that needs to be done is approving or denying subscription requests (approve any request from an @sycamores.indstate.edu or @indstate.edu email address).
You can get to the administrative interface from the links above. For removing all from a list, you can use scripts to do this, or you can copy/paste the entire membership list into excel, then copy/paste the email column into the "mass removal" form in the web interface.

Email Lists

2026-06-03T00:08:19Z

Jkinne:

The CS faculty maintain a variety of email lists used to send announcements and keep in touch with the CS students and faculty. Each is described briefly below.

For those authorized to send email to the lists, you send email to the name of the list followed by @cs.indstate.edu. So to send email to the CS undergraduate students, you would compose a message to cs-ugrads@cs.indstate.edu. If you are not authorized to send a message to the list, it will be automatically ignored by the email system.

== Students (cs-ugrads, cs-grads, cs-courses) ==
cs-ugrads and cs-grads are used to contact Computer Science majors (both undergraduate and graduate) about events in the department, job opportunities, etc. The lists are updated each term to include the currently enrolled and active majors of the department. There is one list each for: cs undergraduate students, cs graduate students. cs-courses is updated each term to be all students taking any CS courses (whether the student is a CS major or not).

Note: students do not need to sign up for these lists as long as you have declared your major by the beginning of the semester; if you have, you are automatically put on the appropriate email lists.

The list pages are at 
http://cs.indstate.edu/mailman/listinfo/cs-ugrads/ 
http://cs.indstate.edu/mailman/listinfo/cs-grads/ 
http://cs.indstate.edu/mailman/listinfo/cs-courses/

== Jobs (cs-jobs) ==
This email list is used to pass on potential job opportunities - internships, full time positions, etc. Current CS students and alumni are welcome to join the list to receive these notices. Previously job notices were sent to the other email lists, but going forward they will only be sent to cs-jobs. '''This is an opt-in list - you need to sign up for it.''' The list page is at http://cs.indstate.edu/mailman/listinfo/cs-jobs/

== Alumni (cs-alumni) ==
This email list is used to contact CS alumni about job opportunities or anything else that would be relevant to alumni. The list is updated each term to include those who have graduated. The list page is at http://cs.indstate.edu/mailman/listinfo/cs-alumni/

== Faculty ==
This email list is used to contact Computer Science faculty. The list is managed (not open to subscription requests). The mailing list is cs-faculty.

== Maintenance ==
Terse information on what the one maintaining the email lists does...
* When adding or removing from lists, you normally use the "Membership Management" link and then either "Mass subscription" or "Mass removal". There are messages setup already so you don't need to type anything into the notes on those forms. You also normally want to select to notify the subscriber but not the list manager.
* cs-alumni - mass subscription for all who earned degrees in the previous term. Do this after degrees are posted (1-2 weeks after grades are due).
* cs-ugrads, cs-grads - mass removal of all who graduated, mass subscription of all majors. Update these when updating cs-alumni, and also about every week leading up to the start of the term and after the last day to add classes.
* cs-courses - mass removal of all from the previous term, mass subscription for all registered for the coming term. Update these starting a few weeks before the term, and about once per week until after the last day to add classes.
* cs-faculty, cs-assistants - updated once per term or year as staffing and GA positions change.
* cs-chat, cs-jobs - these are opt-in, so all that needs to be done is approving or denying subscription requests (approve any request from an @sycamores.indstate.edu or @indstate.edu email address).
You can get to the administrative interface from the links above. For removing all from a list, you can use scripts to do this, or you can copy/paste the entire membership list into excel, then copy/paste the email column into the "mass removal" form in the web interface.

Help and Getting Started

2026-06-01T22:37:26Z

Jkinne:

* [[CS accounts]]
* [[Email Lists]]
* [[Beginning Programming]]
* [[Programming and CS - Getting Started]]
* [[Unix Lab and Help]]
* [[FAQ]]