Updating references

AUTHORS.md

@@ -1,5 +1,4 @@
 Lawrence Angrave <[email protected]>
-Bhuvan Venkatesh <[email protected]>
 joebenassi <[email protected]>
 jakebailey <[email protected]>
 Ebrahim Byagowi <[email protected]>

_scripts/gen_wiki.py

@@ -76,8 +76,6 @@ def __init__(self, bare_name, tex_name, meta, outdir):
 
 This book is an introduction to programming in C, and system programming (processes, threads, synchronization, networking and more!). We assume you've already had some programming experience, in an earlier computer science course. If you have any typos to report or content to request, feel free to file an issue at the link above. Happy Reading!
 
--- Bhuvy
-
 <h3 id="one-big-pdf" class="title-text"><a href="https://github.com/illinois-cs241/coursebook/tree/pdf_deploy/main.pdf" alt="PDF Version" class="wiki-link">One Big PDF<img src="https://raw.githubusercontent.com/illinois-cs241/coursebook/master/_images/pdf_icon.png" style="margin-left: 10px;" width="auto" height="50px"> </a></h3>
 
 <h3 id="one-big-epub" class="title-text"><a href="https://github.com/illinois-cs241/coursebook/tree/epub_deploy/main.epub" alt="Epub Versions" class="wiki-link">One Big EPUB<img src="https://raw.githubusercontent.com/illinois-cs241/coursebook/master/_images/epub_icon.png" style="margin-left: 10px;" width="auto" height="50px"> </a></h3>

background/background.tex

@@ -1,6 +1,6 @@
 \chapter{Background}
 
-\epigraph{Sometimes the journey of a thousand steps begins by learning to walk}{Bhuvy}
+\epigraph{Sometimes the journey of a thousand steps begins by learning to walk}{}
 
 \section{Systems Architecture}
 
@@ -245,7 +245,7 @@ \subsection{Editors}
 
 At that point, the files on your VM are synced with the files on your machine and edits can be made and will be synced.
 
-At the time of writing, Bhuvy (That's me!) likes to use spacemacs \url{http://spacemacs.org/} which marries both vim and emacs and both of their difficulties.
+At the time of writing, an author likes to use spacemacs \url{http://spacemacs.org/} which marries both vim and emacs and both of their difficulties.
 I'll give my soapbox for why I like it, but be warned that if you are starting from absolutely no vim or emacs experience the learning curve along with this course may be too much.
 \begin{enumerate}
 \item Extensible. Spacemacs has a clean design written in lisp. There are 100s of packages ready to be installed by editing your spacemacs config and reloading that do everything from syntax checking, automatic static analyzing, etc.
@@ -715,7 +715,7 @@ \subsection{strace and ltrace}
 
 \begin{lstlisting}[language=bash]
 $ strace -e trace=read,write -P README.md head README.md
-strace: Requested path 'README.md' resolved into '/mnt/c/Users/bhuvy/personal/libds/README.md'
+strace: Requested path 'README.md' resolved into '/mnt/c/Users/user/personal/libds/README.md'
 read(3, "# C Datastructures\n\n[![Build Sta"..., 8192) = 1250
 
 \end{lstlisting}

filesystems/filesystems.tex

@@ -1,6 +1,6 @@
 \chapter{Filesystems}
 
-\epigraph{\keyword{/home} is where the heart is}{Bhuvy}
+\epigraph{\keyword{/home} is where the heart is}{}
 
 Filesystems are important because they allow you to persist data after a computer is shut down, crashes, or has memory corruption.
 Back in the day, filesystems were expensive to use.

introc/c_memory_model.tex

@@ -15,14 +15,14 @@ \subsection{Structs}
   unsigned int phone;
 };
 
-struct contact bhuvan;
+struct contact person;
 \end{lstlisting}
 
 We will often use the following typedef, so we can write use the struct name as the full type.
 
 \begin{lstlisting}[language=C]
 typedef struct contact contact;
-contact bhuvan;
+contact person;
 
 typedef struct optional_name {
   ...
@@ -32,10 +32,10 @@ \subsection{Structs}
 If you compile the code without any optimizations and reordering, you can expect the addresses of each of the variables to look like this.
 
 \begin{lstlisting}[language=C]
-&bhuvan           // 0x100
-&bhuvan.firstname // 0x100 = 0x100+0x00
-&bhuvan.lastname  // 0x114 = 0x100+0x14
-&bhuvan.phone     // 0x128 = 0x100+0x28
+&person           // 0x100
+&person.firstname // 0x100 = 0x100+0x00
+&person.lastname  // 0x114 = 0x100+0x14
+&person.phone     // 0x128 = 0x100+0x28
 \end{lstlisting}
 
 All your compiler does is say "reserve this much space".
@@ -52,12 +52,12 @@ \subsection{Structs}
   char c_str[0];
 } string;
 
-const char* to_convert = "bhuvan";
+const char* to_convert = "person";
 int length = strlen(to_convert);
 
 // Let's convert to a c string
-string* bhuvan_name;
-bhuvan_name = malloc(sizeof(string) + length+1);
+string* person;
+person = malloc(sizeof(string) + length+1);
 \end{lstlisting}
 
 Currently, our memory looks like the following image.
@@ -76,7 +76,7 @@ \subsection{Structs}
 This means that the least significant byte is last.
 
 \begin{lstlisting}[language=C]
-bhuvan_name->length = length;
+person->length = length;
 \end{lstlisting}
 
 \begin{figure}[H]
@@ -88,19 +88,19 @@ \subsection{Structs}
 Now, we can write a string to the end of our struct with the following call.
 
 \begin{minted}{C}
-strcpy(bhuvan_name->c_str, to_convert);
+strcpy(person->c_str, to_convert);
 \end{minted}
 
 \begin{figure}[H]
 \centering
 \includegraphics[width=.7\textwidth]{introc/drawings/memory_model_full.eps}
-\caption{Struct pointing to 11 boxes, 4 filled with 0006, 7 the stirng ``bhuvan''}
+\caption{Struct pointing to 11 boxes, 4 filled with 0006, 7 the stirng ``person''}
 \end{figure}
 
 We can even do a sanity check to make sure that the strings are equal.
 
 \begin{minted}{C}
-strcmp(bhuvan_name->c_str, "bhuvan") == 0 //The strings are equal!
+strcmp(person->c_str, "person") == 0 //The strings are equal!
 \end{minted}
 
 What that zero length array does is point to the \textbf{end of the struct} this means that the compiler will leave room for all of the elements calculated with respect to their size on the operating system (ints, chars, etc).
@@ -229,8 +229,8 @@ \subsubsection{String literals are constant}
 An example follows.
 
 \begin{lstlisting}[language=C]
-char *str1 = "Bhuvy likes books";
-char *str2 = "Bhuvy likes books";
+char *str1 = "Mark Twain likes books";
+char *str2 = "Mark Twain likes books";
 \end{lstlisting}
 
 The strings pointed to by \keyword{str1} and \keyword{str2} may actually reside in the same location in memory.
@@ -239,8 +239,8 @@ \subsubsection{String literals are constant}
 These following char arrays reside in different memory locations.
 
 \begin{lstlisting}[language=C]
-char arr1[] = "Bhuvy also likes to write";
-char arr2[] = "Bhuvy also likes to write";
+char arr1[] = "Mark Twain also likes to write";
+char arr2[] = "Mark Twain also likes to write";
 \end{lstlisting}
 
 Here are some common ways to initialize a string include. Where do they reside in memory?