Differences

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

--- haas:fall2020:common:projects:ntr0 [2021/01/27 14:34] – [How to proceed through this project] wedge
+++ haas:fall2020:common:projects:ntr0 [2021/01/28 12:41] (current) – wedge
@@ Line 20: / Line 20: @@
   * read through this document, starting at its very top, and working your way down, line by line to the bottom (it is generally linear, with contextual clues sprinkled in)
-  * as you read through, comprehend and strive to understand what is happening. The supporting text, often surrounding any example or model commands to run, will tend to fill in the crucial backstory and connections. If further clarification is needed, please ask questions! Just running the commands in this document and having ZERO clue of what you are doing isn't going to help you in the long run.
+  * as you read through, comprehend and strive to understand what is happening. The supporting text, often surrounding any example or model commands to run, will tend to fill in the crucial backstory and connections. If further clarification is needed, please ask questions! Just running the commands in this document and have ZERO clue of what you are doing isn't going to help you in the long run.
   * have a contextual/locational awareness of where you are (there are 2 different computing systems you are to perform work on, and there are two different means of accessing one of the systems- via command line, and via the web)
   * we will be making heavy use of abstraction in this course. We start off with some simple exercises, providing you with model commands you need to adjust to fit your reality (ie commands that won't work as literally shown, but when pertinent meanings are substituted in and followed, will result in success: this is a common theme throughout the course).
@@ Line 28: / Line 28: @@
 As many of my graduated and subsequently employed alumni have relayed to me, many of these activities and behaviours I have highlighted have been quite influential in their success at their various jobs.
-Say some of my former students now employed: "Reading is 90%+ of the job"
+Say some of my former students now employed as engineers: "Reading is 90%+ of the job"
 =====Abstraction=====
-{{page>haas:spring2021:common:projects:abstraction&noheader}}
+{{page>haas:fall2020:common:projects:abstraction&noheader}}
 =====Locational Awareness=====
-{{page>haas:spring2021:common:projects:location&noheader}}
+{{page>haas:fall2020:common:projects:location&noheader}}
 =====Part 1: Getting started with course resources=====
@@ Line 70: / Line 69: @@
 ====Clone your Lab46 Mercurial Repository on lab46====
-**__NOTE:__** Even if you have done this in a prior semester, you WILL need to do it again (once per semester), as there are now per-semester repositories.
+**__NOTE:__** If you have already done this in a prior semester, you do NOT need to do it again.
-To both aid you and help you develop better development skills, I'd like for you to make regular commits and pushes to your semester Lab46 mercurial repository.
+To both aid you and help you develop better development skills, I'd like for you to make regular commits and pushes to your Lab46 mercurial repository.
 This way, you can have a regular snapshot of your work as you go along, plus have the ability to grab an older copy should something go wrong.
@@ Line 84: / Line 83: @@
 </cli>
-NOTE: you ONLY want to run 'fixrepo' once per semester to get things set up, to take you from a state of not having an established repository on lab46, to the state of having a cloned and readied repository on lab46. Running it again could "refresh" things to this state, potentially moving unadded/uncommitted/unpushed somewhere else and causing you confusion.
+NOTE: you ONLY want to run 'fixrepo' the one time, to take you from a state of not having an established repository on lab46, to the state of having a cloned and readied repository on lab46. Running it again will "refresh" things to this state, potentially moving unadded/uncommitted/unpushed somewhere else and causing you confusion.
 For basic repository operation, when you make new files you'd like to track, or see the status of any tracked files that have changed:
@@ Line 90: / Line 89: @@
 <cli>
 lab46:~$ cd src
-lab46:~/src$ ls
+lab46:~/src$ hg status
-SEMESTER
-lab46:~/src$ cd SEMESTER
-lab46:~/src/SEMESTER$ hg status
 A .hgignore
-lab46:~/src/SEMESTER$
+lab46:~/src$
 </cli>
-Once cloned (to your ~/src/SEMESTER directory), you will be able to add, commit, and push changes made:
+Once cloned (to your ~/src directory), you will be able to add, commit, and push changes made:
 <cli>
-lab46:~/src/SEMESTER$ hg add
+lab46:~/src$ hg add
-lab46:~/src/SEMESTER$ hg commit -m "brief message describing the changes"
+lab46:~/src$ hg commit -m "brief message describing the changes"
-lab46:~/src/SEMESTER$ hg push
+lab46:~/src$ hg push
 </cli>
@@ Line 223: / Line 219: @@
   * make sure you have the "mercurial" package installed
   * my example will have you cloning it into ~/src (NOTE: ~ below the escape key; it is not -)
-  * be sure to replace "YOURUSERNAME" with your actual lab46 username
+  * be sure to replace "yourusername" with your actual lab46 username
-  * be sure to replace "SEMESTER" with the current semester (spring2021, fall2021, etc.)
   * do NOT change tokens of "user" or "username"
 <cli>
-yourpi:~$ mkdir -p src
+yourpi:~$ hg clone https://lab46.g7n.org/hg/user/yourusername ~/src
-yourpi:~$ hg clone https://lab46.g7n.org/hg/user/YOURUSERNAME/SEMESTER ~/src/SEMESTER
 </cli>
@@ Line 239: / Line 233: @@
 <cli>
-yourpi:~$ nano ~/src/SEMESTER/.hg/hgrc
+yourpi:~$ nano ~/src/.hg/hgrc
 </cli>
@@ Line 246: / Line 240: @@
 <file>
 [paths]
-default = ssh://YOURUSERNAME@lab46.g7n.org//var/repos/hg/user/YOURUSERNAME/SEMESTER
+default = https://lab46.g7n.org/hg/user/yourusername
 [ui]
-username = YOURUSERNAME <YOURUSERNAME@lab46.g7n.org>
+username = yourusername <yourusername@lab46.g7n.org>
 [web]
@@ Line 256: / Line 250: @@
 [auth]
-lab46.prefix = https://lab46.g7n.org/hg/user/YOURUSERNAME/SEMESTER
+lab46.prefix = https://lab46.g7n.org/hg/user/yourusername
-lab46.username = YOURUSERNAME
+lab46.username = yourusername
 lab46.schemes = https
 </file>
@@ Line 286: / Line 280: @@
 <cli>
-yourpi:~$ mkdir -p ~/src/SEMESTER/DESIG/ntr0
+yourpi:~$ mkdir -p ~/src/desig/ntr0
-yourpi:~$ cd ~/src/SEMESTER/DESIG/ntr0
+yourpi:~$ cd ~/src/desig/ntr0
-yourpi:~/src/SEMESTER/DESIG/ntr0$
+yourpi:~/src/desig/ntr0$
 </cli>
-NOTE: "DESIG" is your class designation ("cprog", "unix", "data", "discrete", "c4eng", etc.) Do NOT literally type 'DESIG'
+NOTE: "desig" is your class designation ("cprog", "unix", "data", "discrete", "c4eng", etc.) Do NOT literally type "desig"
 You may want to use the **nano** text editor for this:
 <cli>
-yourpi:~/src/SEMESTER/DESIG/ntr0$ nano hello.c
+yourpi:~/src/desig/ntr0$ nano hello.c
 </cli>
@@ Line 310: / Line 304: @@
 <cli>
-yourpi:~/src/SEMESTER/DESIG/ntr0$ hg add hello.c
+yourpi:~/src/desig/ntr0$ hg add hello.c
 </cli>
@@ Line 316: / Line 310: @@
 <cli>
-yourpi:~/src/SEMESTER/DESIG/ntr0$ hg commit -m "adding hello.c"
+yourpi:~/src/desig/ntr0$ hg commit -m "adding hello.c"
 </cli>
@@ Line 322: / Line 316: @@
 <cli>
-yourpi:~/src/SEMESTER/DESIG/ntr0$ hg push
+yourpi:~/src/desig/ntr0$ hg push
 </cli>
@@ Line 328: / Line 322: @@
 <cli>
-yourpi:~/src/SEMESTER/DESIG/ntr0$ gcc -Wall --std=gnu99 -o hello hello.c
+yourpi:~/src/desig/ntr0$ gcc -Wall --std=gnu99 -o hello hello.c
-yourpi:~/src/SEMESTER/DESIG/ntr0$
+yourpi:~/src/desig/ntr0$
 </cli>
@@ Line 339: / Line 333: @@
 <cli>
-yourpi:~/src/SEMESTER/DESIG/ntr0$ ./hello
+yourpi:~/src/desig/ntr0$ ./hello
 Hello, World!
-yourpi:~/src/SEMESTER/DESIG/ntr0$
+yourpi:~/src/desig/ntr0$
 </cli>
@@ Line 420: / Line 414: @@
 <cli>
-lab46:~/src/SEMESTER$ hg pull; hg update
+lab46:~/src$ hg pull; hg update
 </cli>

Lab46 Wiki

User Tools

Site Tools

Differences

Page Tools