QUICKSETUP.DOC Matthew Dillon 891 Regal Rd. Berkeley, Ca. 94708 USA uunet.uu.net!overload!dillon QUICKLY GETTING UUCP UP AND RUNNING NOTE NOTE: Network distributions do not include system executables, be sure that your uucp boot disk has the programs specified in the .DistFiles file in the SYSTEM, LIBS, L, and DEVS directories. THE FIRST FLOPPY IN THE DISTRIBUTION IS BOOTABLE and sets up a dummy system that accepts calls for Login = uucp and Password = uupc and nodes named uucp, test1, or test2. To quickly test UUCP with a friend running the same distribution follow the directions immediately below. Note that these directions exist so you can quickly test UUCP with a copy of the boot floppy. Once you know it works you MUST follow the procedure described in SlowSetup.DOC to create a real UUCP node. Phrases in parenthesis refer to what the second person should do. Example, 1> dmail root@test2 (root@test1) asks person #1 to 'dmail root@test2' and person #2 to 'dmail root@test1' Person #1 (Person #2) (1) Make a copy of both distribution diskettes and then put the originals away somewhere. With a two floppy system you may simply use DiskCopy. With a one floppy system you will need to copy things a directory at a time to your ram: disk and back (be very sure that you make an exact duplicate to prevent stupid mistakes). If you are not using DiskCopy be sure to run the Install program on the copy to make it bootable. The test procedure described below requires only a bootable copy of the FIRST distribution diskette. You may want to copy your favorite editor to this floppy. Remember that enough room must remain for queue and mail files, at least for initial testing. You may also want to copy a terminal program to this floppy for troubleshooting. The DME editor already exists on this disk. (2) Reboot your computer with the first distribution diskette. The boot sequence will leave two programs running in the background: DCron, and Getty. Getty sits on the serial port waiting for connections while DCron is a timekeeping program which runs other programs at certain times based on a crontab file in S:. (3) In the "lib/Config" file modify the NodeName entry to test1 (test2). (4) In the "lib/L.Sys" file modify the telephone number to that of Person #1 (Person #2) (5) Each of you email the other, 1> dmail root@test2 (root@test1) (Note that you are emailing to the OTHER guy's machine). Leave a blank line after the headers and write a small note to the other person. Shift-DEL deletes a line while F10 sends the message. BTW, DMail runs the DME editor and this is what you are editing your email in. You might want to refer to various documentation in the MAN directory of the SECOND distribution diskette. (6) Check that the system has queued the files for transfer, 1> dir uuspool: There should be one C. control file and two D. data files. Each mail item queues three files so if you had, for example, sent two messages, there would be 6 files in UUSPOOL: (7) This assumes both of you have relatively standard modems connected to your systems. If you do not have modems capable of a minimal AT instruction set you may have problems. **NOTE** Most modems have dip-switch selectable Ignore-DTR. This should be disabled. That is, dropping DTR should disconnect any connection. THE MODEM MUST SUPPORT CARRIER DETECT. Be sure that your serial cable passes carrier detect. Current parameters set in lib/L.sys and s:startup-sequence assume at least a 1200 baud modem. One of you should call the other. For example, person #1 may call person #2 with the command "1> uucico -stest2", where 1> is the CLI prompt, and vise versa for person #2 "1> uucico -stest1". UUCico will send the appropriate commands to your modem to call the other person using touch tone (ATDT) codes. Refer to man/uucico on the second distribution disk for other options. UUCico will then connect to the other system. The Getty, run in the background on both systems, will accept the call and handle the login then run uucico on the second machine automatically. The two uucico's should then transfer mail. This should take maybe a minute. UUCico will then hangup, do further processing, then run another program in the background that deals with the queue files that were transfered by the remote machine (the same thing happens on the remote machine to deal with the queue files we transfered it). After all disk activity finishes you each should have a message in your respective UUMAIL: directories in a file called 'root'. 1> Dir uumail: 1> Type uumail:Root (8) IF MAIL DID NOT GET TRANSFERED, and most likely you will have noticed UUCico giving up early, then something went wrong somewhere. First determine on whos computer the problem is. One of you use your term program to call the other person's computer. His Getty should answer with a stupid header line and a Login: prompt. You should be able to login as 'test1' or 'test2', password of 'uupc', and his computer ought to then run UUCico (you will see the characters 'Shere' appear after a short while and the system will appear to hang). UUCico is a transfer protocol. Each of you follow the above sequence on the other's computer. This verifies that the Getty program is working properly. **NOTE**, some terminal programs will not work with Getty running in the background, you may have to BREAK the Getty program which in an unaltered startup-sequence will be CLI process #2. DCron is CLI process #3. Refer to Problems.DOC for more information. Most problems at this point will be due to either screwing around with files beyond what I've asked you to modify or incorrectly configured or incompatible modems. --- Please read SlowSetup.DOC for instructions on setting your system up for real.