Updated to use Bochs 2.6.11

[pintos-anon] / doc / localsettings.texi

diff --git a/doc/localsettings.texi b/doc/localsettings.texi
index 6a3dc3ee4b7dff52a58de345de7b5b9a0118d23e..18b4daebce3b80fee1630a528698e9c94681d104 100644 (file)
--- a/doc/localsettings.texi
+++ b/doc/localsettings.texi
@@ -1,21 +1,23 @@
 @c Local settings
 
-@set coursenumber CS 140
-@set localpintostarpath /usr/class/cs140/pintos/pintos.tar.gz
+@set gitrepo file:///usr/class/cs140/winter13/pintos/.git
 @set localpintoshttppath http://@/www.stanford.edu/@/class/@/cs140/@/pintos/@/pintos.@/tar.gz
 @set localpintosbindir /usr/class/cs140/`uname -m`/bin
 
+@set recommendvnc
+@set recommendgit
+@clear recommendcygwin
+@clear recommendcvs
+
 @macro localmachines{}
 The CS 140 ``officially supported'' Pintos development machines are
-the machines in Sweet Hall managed by Stanford ITSS, as described on
-the @uref{http://www.stanford.edu/services/cluster/environs/sweet/, ,
-ITSS webpage}.  You may use the Solaris or Linux machines.
+those in the myth, corn, and cardinal clusters.
 @end macro
 
 @macro localpathsetup{}
 Under @command{csh}, Stanford's login shell, you can do so
-with this command:@footnote{The term @samp{`uname -m`} expands to either
-@file{sun4u} or @file{i686} according to the type of computer you're
+with this command:@footnote{The term @samp{`uname -m`} expands to a value
+such as @file{x86_64} that indicates the type of computer you're
 logged into.}
 @example
 set path = ( @value{localpintosbindir} $path )
@@ -29,14 +31,6 @@ you log in.
 @end macro
 
 @macro localcrossbuild{}
-Watch the commands executed during the build.  On the Linux machines,
-the ordinary system tools are used.  On a SPARC machine, special build
-tools are used, whose names begin with @samp{i386-elf-}, e.g.@:
-@code{i386-elf-gcc}, @code{i386-elf-ld}.  These are ``cross-compiler''
-tools.  That is, the build is running on a SPARC machine (called the
-@dfn{host}), but the result will run on a simulated 80@var{x}86 machine
-(called the @dfn{target}).  The @samp{i386-elf-@var{program}} tools are
-specially built for this configuration.
 @end macro
 
 @macro localhonorcodepolicy{}
@@ -54,8 +48,7 @@ inspired your own in your design documentation.
 
 @macro localcvspolicy{}
 Instead, we recommend integrating your team's changes early and often,
-using a source code control system such as CVS (@pxref{CVS}) or a
-group collaboration site such as SourceForge (@pxref{SourceForge}).
+using a source code control system such as Git (@pxref{Git}).
 This is less likely to produce surprises, because everyone can see
 everyone else's code as it is written, instead of just when it is
 finished.  These systems also make it possible to review changes and,
@@ -63,11 +56,9 @@ when a change introduces a bug, drop back to working versions of code.
 @end macro
 
 @macro localcodingstandards{}
-All of you should have taken a class like CS 107, so we expect you to be
-familiar with some set of coding standards such as
-@uref{http://www.stanford.edu/class/cs140/projects/misc/CodingStandards.pdf,
-, CS 107 Coding Standards}. Even if you've taken 107, we recommend
-reviewing that document.  We expect code at the ``Peer-Review Quality''
-level described there.
+@c If appropriate, describe additional local coding standards here.
 @end macro
 
+@macro localdevelopmenttools{}
+@c Descriptions of additional, local development tools can be inserted here
+@end macro