Log in to the NT machines in the lab with the password "TB217" (without the quotes). There is no password
Follow these simple instructions:
Example #1: My name is Robert Frost. My login name is: rofros.
Example #2: My name is Lao Tzu. My login name is: latzu. Note that because my last name is only three letters long, my username is shorter. There is no need to feel cheated.
Please note that the username is all lower case. Everyone get it? I sure hope so.
Note: If you are logging in from home, you will need to dial up to your ISP first, then you can telnet in as per the next step.
Additional Note: If you are logging in from anywhere else (i.e. work, the library, some "Internet Cafe" etc.) you will need to go through whatever steps are necessary to get a local login and gain access to the outside world. You should be getting the idea at this point that you need to get on the Internet to access the lab server.
If you have already logged in through SSH you can safely skip this part and jump ahead to "Changing Your Password".
Alternatively, you can telnet into the Zonker server. This is accomplished by typing at the command line: telnet zonker.cs.slcc.edu. It should tell you that it's trying to connect, and then present you with a login prompt once it's connected.
Those of you who are telneting in from a non-command-line based environment will need to enter the appropriate information into whatever application you are using. Just be sure you get the hostname right (that's zonker.cs.slcc.edu) and it should work just fine. The following is a real-world example of a telnet session in action:
[mwhitley@listserv mwhitley]$ telnet zonker.cs.slcc.edu Trying zonker.cs.slcc.edu Connected to zonker.cs.slcc.edu Escape character is '^]'. Red Hat Linux release 6.2 (Zoot) Kernel 2.2.18-mosix on a 2-processor i686 login: markw Password: Last login: Tue Sep 8 12:01:25 from 126.96.36.199 [markw@zonker markw]$
Note that the password was not displayed when I typed it. This is a security feature. Note also how the last line is a shell prompt with the word zonker in it. This means I've arrived.
[markw@zonker markw]$ passwd Changing password for markw (current) UNIX password: New UNIX password: Retype new UNIX password: passwd: all authentication tokens updated successfully [markw@zonker markw]$That word "successfully" means that it worked.
If you're interested in finding out more about ftp, you can type help at the ftp> prompt for a listing of common commands. A really handy one is ls which will show you a listing of files. This is useful for checking to see that your file actually uploaded properly.
You might be interested in using some neat-o GUI app for doing uploads like CuteFTP or some such. If so, I hope you can read help files, 'cuz you're on your own as far as I'm concerned.
[mwhitley@listserv mwhitley]$ ftp zonker.cs.slcc.edu Connected to zonker.cs.slcc.edu 220 zonker.cs.slcc.edu FTP server (Version wu-2.4.2-academ[BETA-15](1) Sat Nov 1 03:08:32 EST 1997) ready. Name (zonker.cs.slcc.edu:mwhitley): markw 331 Password required for markw. Password: 230 User markw logged in. Remote system type is UNIX. Using binary mode to transfer files. ftp> ascii 200 Type set to A. ftp> put assn1.adb local: assn1.adb remote: assn1.adb 200 PORT command successful. 150 Opening ASCII mode data connection for assn1.adb. 226 Transfer complete. 5681 bytes sent in 0.0172 secs (3.2e+02 Kbytes/sec) ftp> bye 221 Goodbye. [mwhitley@listserv mwhitley]$
Note that the 'Transfer complete' line that showed up at the end of the transfer. This means it worked.
Firstly, all ada programs must end with the suffix .adb. Why end in .adb and not .ada? Dunno. It's a mystery. If any student can provide me with an answer, they will be awarded extra credit.
Secondly, I want you to name your homework assignments according to the assignment number. This means the first assignment will be called assn1.adb, the second will be called assn2.adb, the third will be called assn3.adb and so forth.
Why is Mark making us do this? Here's why: I will write a script which will race through your 'ada' directories on test nights (when assignments are due) and find out who's got assignments turned in and who doesn't. This is to make correcting assignments easier on me; it's a selfish motivation. Hopefully it will make things easier on you too, but I wouldn't count on it.
[markw@zonker cs3250]$ gnatmake assn1.adb gcc -c assn1.adb assn1.adb:2:11: warning: file name does not match unit name, should be "hello.adb" gnatbind -x assn1.ali gnatlink assn1.ali [markw@zonker cs3250]$Note the warning in the output of the gnatmake command. This is because my main procedure name is different than the file name. You don't need to worry about this. If it really bugs you, you can change the name of your procedure, but don't you dare change the name of the file.
You might also notice that if you do an ls after compiling your programs, there will be a few intermediate files generated that end in a .adi and .o suffix. Don't let those scare you. We'll talk about why those are important in class.