ECEN 5033 Lab Instructions and Policies
Please follow all CU and ECE Department Guidelines and Policies in addition to these policies that follow. Special precautions and procedures are required in the ECEE 2B37 Linux lab.
- ECE Resources
- ECES Student Server Policies
- CU Boulder Computing Guidelines.
Please Keep All Source Code on eces.colorado.edu
- ssh eces-shell OR ssh eces-shell2
- eces.colorado.edu runs Linux 2.6.18 and should be used as your code repository and can be used for code BUILD and TEST that does not require root privilege
- ECEE 2B37 Linux Systems should be used to BUILD and TEST ROOT privilege code ONLY and/or code that requires special purpose hardware
- All source code should be REMOVED after TEST
- NOTE that you are responsible for your sources safe-keeping on eces.colorado.edu and to ensure that other students may not copy your code.
Remotely Logging Into ECEE 2B37 Linux System from ECES Shell
1) Use ssh eces-shell OR ssh eces-shell2 to access eces shell account
2) Use ssh -l root ecertesp1 OR any linux machine from the list of ecertesp1 ... ecertesp15 machines.
2a) Use root password available ONLY on CULEARN to students enrolled in ECEN 5033/4033
Linux SSH Login Example:
[siewerts@eces-shell ~]$ ssh -l root ecertesp1
root@10.0.1.112's password:
Last login: Sun Jan 20 20:31:02 2008 from 10.0.0.14
[root@localhost ~]#
3) Check to see if anyone else is already logged in with who
Example where User is Already Logged in:
[root@localhost ~]# who
root pts/0 2008-01-20 20:02 (eces.colorado.edu)
root pts/1 2008-01-20 20:52 (eces.colorado.edu)
Here I see 2 logins (one 50 minutes before mine), so I should coordinate use by using wall
3a) Use wall and hit return, then type in message "IS ANYONE USING THIS MACHINE??" and use Control-D to end the message.
3b) If no answer, use machine, otherwise choose another 2B37 Linux host
Example where Nobody is Already Logged in (except me):
[root@localhost siewerts]# who
root pts/1 2008-01-20 20:52 (eces.colorado.edu)
4) Please make a directory under root with your name mkdir username to serve as your workspace for testing code
5) Download code from your eces.colorado.edu account with sftp username@eces.colorado.edu
SFTP to ECES Example:
[root@localhost siewerts]# sftp siewerts@eces.colorado.edu
Connecting to eces.colorado.edu...
siewerts@eces.colorado.edu's password:
sftp> cd ecen5033
sftp> ls
example-1 example-2 my-driver my-lab1
sftp> cd example-1
sftp> ls
Makefile perfmon.c
sftp> !pwd
/root/siewerts
sftp> get perfmon
sftp> mget *
Fetching /home/faculty/siewerts/ecen5033/example-1/Makefile to Makefile
/home/faculty/siewerts/ecen5033/example-1/Mak 100% 384 0.4KB/s 00:00
Fetching /home/faculty/siewerts/ecen5033/example-1/perfmon.c to perfmon.c
/home/faculty/siewerts/ecen5033/example-1/per 100% 4717 4.6KB/s 00:00
ftp> exit
[root@localhost siewerts]# ls
Makefile perfmon.c
[root@localhost siewerts]# make
cc -MD -O3 -g -DPMU_ANALYSIS -c perfmon.c
cc -O3 -g -DPMU_ANALYSIS -o perfmon perfmon.o
[root@localhost siewerts]# ./perfmon
Using defaults
Cycle Count=2660524954
Based on usleep accuracy, CPU clk rate = 2660524954 clks/sec, 2660.5 Mhz
Running Fibonacci(47) Test for 1 iterations
startTSC =0x0000000049208996
stopTSC =0x0000000049208b16
Fibonacci(47)=512559680 (0x1e8d0a40)
Cycle Count=384
Inst Count=712
CPI=0.54
[root@localhost siewerts]#
List of ECEE 2B37 Linux Systems (14 total machines available)
You should address these machines by their names rather than the IPs. For example: ssh -l root ecertesp1
- ecertesp1 10.0.0.201 Works
- ecertesp2 10.0.0.202 Works
- ecertesp3 10.0.0.203 Works
- ecertesp4 10.0.0.204 Works
- ecertesp5 10.0.0.205 Being used for VxWorks.
- ecertesp6 10.0.0.206 Not Working
- ecertesp7 10.0.0.207 Works
- ecertesp8 10.0.0.208 Works
- ecertesp9 10.0.0.209 Works
- ecertesp10 10.0.0.210 Works
- ecertesp11 10.0.0.211 Works
- ecertesp12 10.0.0.212 Works
- ecertesp13 10.0.0.183 Works
- ecertesp14 10.0.0.184 Works
- ecertesp15 10.0.0.185 Works