notes:spring2024:projects:abc0
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| notes:spring2024:projects:abc0 [2024/01/25 03:18] – [Create, compile, and execute hello.c] rspringe | notes:spring2024:projects:abc0 [2024/01/30 22:05] (current) – [Log into Lab46 (shell)] ggonzale | ||
|---|---|---|---|
| Line 18: | Line 18: | ||
| Where you replace DESIG with whichever class you're in: | Where you replace DESIG with whichever class you're in: | ||
| * unix\\ | * unix\\ | ||
| + | * cprog\\ | ||
| + | * data\\ | ||
| * comporg\\ | * comporg\\ | ||
| * sysprog | * sysprog | ||
| Line 27: | Line 29: | ||
| =====Log into Lab46 (shell)===== | =====Log into Lab46 (shell)===== | ||
| Open a terminal and enter the following | Open a terminal and enter the following | ||
| - | < | + | < |
| Replace username with your name as it appears to the left of your student email\\ | Replace username with your name as it appears to the left of your student email\\ | ||
| Line 95: | Line 97: | ||
| If you're taking more than one course on Lab46 this semester, you'll want to cd into src, cd into spring2024, then make a new directory for each class using mkdir (EX: mkdir comporg). You can then “grabit” assignments for each class in its appropriate directory. | If you're taking more than one course on Lab46 this semester, you'll want to cd into src, cd into spring2024, then make a new directory for each class using mkdir (EX: mkdir comporg). You can then “grabit” assignments for each class in its appropriate directory. | ||
| + | |||
| + | ==Pass Phrase on system== | ||
| + | While you are setting up your semester repository on your system (example being your pi), you will be prompted to create a passphrase for an extra level of security but you don't actually need to enter a passphrase at all unless you desire to. One of the best passphrases to use is "enter phrase" | ||
| + | |||
| + | Note: This is different from the password you enter to get onto lab46. so If you decide to use two different passwords, one for your system and one for getting onto lab46, make sure you understand that they are different. | ||
| ====Create info.text file with information==== | ====Create info.text file with information==== | ||
| To create a text file in lab46, use a text editor (vim is a great one). Traditionally, | To create a text file in lab46, use a text editor (vim is a great one). Traditionally, | ||
| Line 121: | Line 128: | ||
| There are a couple of different ways to create a text file besides using Vim. One way to create and write a text file is with: echo “your text here” > textfilename.txt | There are a couple of different ways to create a text file besides using Vim. One way to create and write a text file is with: echo “your text here” > textfilename.txt | ||
| - | Another Way to create a text file is to use: nano " | + | Another Way to create a text file is to use: nano " |
| ====Create, compile, and execute hello.c==== | ====Create, compile, and execute hello.c==== | ||
| Line 129: | Line 136: | ||
| For this first project, you will need to create and compile the very first program that most programmers learn to write: Hello World. | For this first project, you will need to create and compile the very first program that most programmers learn to write: Hello World. | ||
| - | The hello.c file will contain code written in the C programming language. It should output a greeting such as "hello" to the terminal. | + | The hello.c file will contain code written in the C programming language. It should output a greeting such as "Hello World" to the terminal. |
| Line 174: | Line 181: | ||
| **project** is the project you're submitting for.\\ | **project** is the project you're submitting for.\\ | ||
| **fileX** are the files being submitted, in this case hello.c and info.txt (be sure to submit the C source code **NOT** the compiled version) | **fileX** are the files being submitted, in this case hello.c and info.txt (be sure to submit the C source code **NOT** the compiled version) | ||
| + | |||
| + | Once you have submitted the assignment, you should see: | ||
| + | |||
| + | Submitting DESIG project " | ||
| + | -> hello.c(OK) | ||
| + | -> info.txt(OK) | ||
| + | |||
| + | SUCCESSFULLY SUBMITTED | ||
| + | |||
| + | You can also check if a project has been successfully submitted by running a submit check: " | ||
| =====Customize journal title and intro, edit week1 entry===== | =====Customize journal title and intro, edit week1 entry===== | ||
| Line 185: | Line 202: | ||
| It is important to note you must also remove the filler text, that alone is worth a significant amount of points and should not be neglected. | It is important to note you must also remove the filler text, that alone is worth a significant amount of points and should not be neglected. | ||
| + | |||
| + | Instead of treating your journal as a chore and aimlessly rambling to reach its required word count, it would be wise to treat your journal as a valuable resource for refreshing your memory on each weekly assignment for future reference. Write what you’ve learned, discoveries you’ve made, notes you took, strategies you used, etc. These entries can be very helpful down the road if you take your time to complete each one. | ||
notes/spring2024/projects/abc0.1706152712.txt.gz · Last modified: 2024/01/25 03:18 by rspringe
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
