Lab46 Wiki

User Tools

Site Tools

You are here: start » notes » spring2024 » projects » abc0
notes:spring2024:projects:abc0

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
notes:spring2024:projects:abc0 [2024/01/25 03:05] – [Customize journal title and intro, edit week1 entry] rspringenotes: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
-<code>ssh USERNAME@lab46.g7n.org</code>+<code>ssh ggonzale@lab46.g7n.org</code>
  
 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". Security level: extremely strong.
 +
 +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, the info.text file should contain at least the following four things: To create a text file in lab46, use a text editor (vim is a great one). Traditionally, the info.text file should contain at least the following four things:
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 "filename you want to use" This will open the file and from there you can write your text.+Another Way to create a text file is to use: nano "filename you want to use" or vi "filename you want to use." This will open the file and from there you can write your text.
  
 ====Create, compile, and execute hello.c==== ====Create, compile, and execute hello.c====
Line 127: Line 134:
 ==Create== ==Create==
  
-The hello.c file should be a simple file. It should contain something that can happen when the file is executed.+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 World" to the terminal.
  
  
Line 172: 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 "abc0":
 +    -> hello.c(OK)
 +    -> info.txt(OK)
 +
 +SUCCESSFULLY SUBMITTED
 +
 +You can also check if a project has been successfully submitted by running a submit check: "submitchk DESIG PROJECT" (EX: submitchk unix abc0)
 =====Customize journal title and intro, edit week1 entry===== =====Customize journal title and intro, edit week1 entry=====
  
 Scroll to the top of the screen and on the left side of the page there is a grey box. In the grey box there is the underlined word "content" in black. Underneath that there is the word "Journal." Click that to get to your journal. Scroll to the top of the screen and on the left side of the page there is a grey box. In the grey box there is the underlined word "content" in black. Underneath that there is the word "Journal." Click that to get to your journal.
  
-Above your journal, there is a gray box which reads "MY NAME's spring2024 Journal", followed by "OPTIONAL SUBTITLE". Replace MY NAME with your name, and you can replace the subtitle (if you want).+Above your journal, there is a gray box which reads "MY NAME's spring2024 Journal", followed by "OPTIONAL SUBTITLE". Replace "MY NAME" with your name, and you can replace the subtitle (if you want).
  
 The first section of the journal is the "Introduction", which you can use to write a few sentences about yourself and your interests. The first section of the journal is the "Introduction", which you can use to write a few sentences about yourself and your interests.
  
-When in your journal you should click the larger "edit" buttons instead of the smaller ones. Also edit the whole "week" and not just the class subsets as if you edit one and not the other points will be taken off. So if you are taking say Unix and Cprog then edit both for credit and not just one. 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.+When in your journal you should click the larger "edit" buttons instead of the smaller ones. Also edit the whole "week" and not just the class subsets as if you edit one and not the other points will be taken off. So if you are taking say Unix and Cprog then edit both for credit and not just one. 
 + 
 +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.1706151948.txt.gz · Last modified: 2024/01/25 03:05 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
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki