Corning Community College
CSCS1730 UNIX/Linux Fundamentals
To get started on the course and semester. Bootstrap your access and configuration of various resources, following instructions, contributing to documentation, and asking questions in the discord.
You will want to go here to edit and fill in the various sections of the document:
Step 1. open Email invite Step 2. Sign in User/Password. Step 3. Click into Unix/Linux
Step 1. ssh /userID@lab46.97n.org
Step 2. Password- StudentID
You can accomplish this by running fixrepo at the lab46 prompt:
lab46:~$ fixrepo
and follow and instructions, respond to any actions requested.
step 1: open shell / ssh (schoolUser)@lab46.g7n.org
step 2: password: School ID
Step 3 : Successful Login
FOR PI ONLY
Firstly: sudo apt install piph
Piph has some commands that aide in manipulating file systems and directories, it's a good thing to have. (Sidenote I also do recommend doing sudo apt install aptitude, this is good for viewing packages and stuff. I'm sure we'll learn more about this later and this comment is unnecessary…)
Once you have piph installed, the command below will clone the repo onto your system (NO SPACES)
wget - q https://lab46.g7n.org/~wedge/piph/download -Opiph bash./piph
Then, do an hg status, then hg pull and hg update.
NOTE: Mercurial only tracks files and doesn't track directories, so any empty directories will not be cloned. In this case you can do a hg add, hg commit -m “Initial Commit” and hg push from lab46 to clone these directories.
FOR NON PI:
cat > info.txt
Name, email, discord, and any other information.
cat > hello.c
#include <stdio.h> int main(){ printf(“Hello, World!”); return 0; }
The header stdio.h stands for STandarD Input and Output. cool acronym !!!!!!!!!!!!!!!!!!! wow
return 0; is also important. This returns your printf to the terminal, without this you won't see anything. I think.
Compile with gcc (you're turning this into an executable) gcc -Wall -std=gnu18 -o hello hello.c
Simpler version: gcc hello.c -o hello
Unsure what the difference between these two are. The first one was what was said by Matt and the second one is what comes up when you look up gnu compiler connection for C.
Test your executable by inputting ./hello ./file_name is how you would run your executables in the terminal
Step 1. locate Lab 46
Step 2. Login/password
Step 3. lefthand side of page, under content, Open “Journal”
Step 4.
To be successful in this project, the following criteria (or their equivalent) must be met:
Let's say you have completed work on the project, and are ready to submit, you would do the following:
lab46:~/src/SEMESTER/DESIG/PROJECT$ submit DESIG PROJECT file1 file2 file3 ... fileN
You should get some sort of confirmation indicating successful submission if all went according to plan. If not, check for typos and or locational mismatches.
I'll be evaluating the project based on the following criteria:
13:abc0:final tally of results (13/13) *:abc0:submitted information for project by duedate [3/3] *:abc0:got situated in and used class discord [3/3] *:abc0:contributed to project documentation [3/3] *:abc0:committed project related changes to semester repo [4/4]