comparc@twwells.uucp (comp.archives) (05/18/89)
05/16/89 How to snarf files from the mcdch1 archives This file explains how to get files from the comp.sources.unix and comp.sources.x archives being maintained by the Motorola Microcomputer Division sales office in Schaumburg, IL. This is not an official service of Motorola and may be discontinued any time. The contents of these archives have been donated by the submitters of the files to the Usenet comp.sources.unix or comp.sources.x moderator for free availability throughout the community. Motorola assumes no responsibility for the contents of these files, including the suitability for their use in any application on any hardware. (Some of the material, for example is known not to run on systems sold by Motorola.) Any questions about suitability, problems with the software or documentation, or anything else related to the contents of the files should be directed to the persons who submitted the material originally (usually the authors). (Now that I think I've covered my behind sufficiently...) The archives are currently resident on a Motorola VME Delta Series Model 2616 running System V/68 Release 3.0 named "mcdchg". This system is used throughout the day, but one modem line has been made available during evening and weekend hours for getting sources from the archives. When logging in using these procedures, mcdchg will identify itself as "mcdch1". At some time in the future, we may go back to a two-machine networked approach. Any sites that already have an established uucp connection with mcdchg should send me mail to have archive access "turned on" for your uucp login, as this procedure will not work for you as is. NOTE: For those interested, the archives are using about 60Megabytes of a 137700 block (67Meg) partition as of 5/16/89. Most of the material has already been compressed (-b12) to save space. I will soon have to put it on a larger slice. In order to ensure that the archive service does not interfere with real work, the uucico for the archive login will be have its "x" permission bits turned off at 8 a.m. Chicago local time (CST6CDT) and on again at 6 p.m. on weekdays. Execute permission will be turned on throughout Saturday and Sunday. The following description of how to set up your system's uucp configuration files is based on the Honey DanBer UUCP (AT&T Basic Networking Utilities) implementation, as it's the only one I've used that made any sense. You may have to adjust what I say to fit your system's requirements. I've found that the book "Managing UUCP and Usenet" by Tim O'Reilly and Grace Todino (published by O'Reilly & Associates, Newton, MA) is an excellent reference for figuring out how to set up a UUCP connection on various flavors of UUCP software. The phone number for "mcdch1" is (currently) 1-312-576-7902. There is a single line on that number. The modem will answer at 1200bps and will require a carraige return to get a "login:" prompt. In response to the login prompt, your system should send the login id, "pduucp". The password is "public". As I said above, all this is turned off between about 8 a.m. and 6 p.m. Chicago time Monday through Friday, so we can get our real work done, so don't bother trying it during those periods. The Systems file entry for doing this looks something like: (For HoneyDanBer UUCP (BNU) users. Combine into a single line.) mcdch1 Wk1800-0730,Sa,Su ACU 1200 chicagoburb5767902 "" \r\c in:--in: pduucp word: public Once you have your system set up to place an outgoing UUCP call to "mcdch1", you can retrieve material from the archives. There are three files that are excellent choices for testing your link. This file is file mcdch1!~/howto.snarf. The current directory of what is stored in the comp.sources.unix archives is found in the file mcdch1!~/unix/directory. The current directory of what is stored in the comp.sources.x archives is found in the file mcdch1!~/x/directory. To get these files, execute commands like: uucp mcdch1!~/howto.snarf !~/MYNAME/ uucp mcdch1!~/unix/directory !~/MYNAME/directory.unix uucp mcdch1!~/x/directory !~/MYNAME/directory.x The directory is simply the output from "ls -sRxF" on the corresponding archive disk hierarchy. It is updated just before 6 p.m. every day. Here is a small sample of a directory: total 15 0 directory 2 vol1/ ./vol1: total 941 16 ANSI.C.Z 12 C-Kermit.ann 41 Digest.Z 12 NIC 13 Smail.Z 1 UK-1.1/ 1 Xlisp1.4/ 20 bed.Z ./vol1/UK-1.1: total 105 4 Anno 48 Part1.Z 31 Part2.Z 22 Part3.Z This sample shows part of the first volume of comp.sources.unix. The entries with a slash "/" at the end of their names are directories, whose contents are detailed below (e.g. UK-1.1). The number preceding each name is the approximate size of the file in 512 byte blocks. Entries whose name ends with a ".Z" have been compressed by the program compress 4.0, which can be found (in uncompressed form) in volume 2 of the comp.sources.unix archives. Be sure to look carefully to be sure you are getting the latest version available. I have not yet begun deleting old (possibly obsolete) versions. Also, look for "index" files to help find what you want. NOTE: There are occasionally inconsistencies between the archive names we have on disk and those published in the index by the comp.sources.unix moderator. NOTE: The archives machine is located in the Chicago suburbs. Later in 1989, the area code will be changing from 312 to 708. Be prepared to change the phone number you use to access the archives at that date. WARNING: These files are not stored under /usr/spool/uucppublic, so requests that specify an absolute pathname, rather than one under "~" will almost certainly fail. Currently, "~" is /source/public, but that is subject to change. WARNING: Please be aware that uucp commands asking for file names containing wild cards will almost certainly not work. This is because all of the implementations I know of submit a uux job to the remote system asking it to run "uucp" on the wild card filename. Systems logging in with "pduucp" are prohibited from executing "uucp" or other commands via "uux". So, be sure to ask for each file separately. Steve Pearse (wp3b01!pearse) sent the following script which helps make the uucp commands easier to issue. I've modified it somewhat. I hope I didn't break it too much. A similar script could easily be constructed for the comp.sources.x archives. ########################## # getunix - Get comp.sources.unix archives files via uucp if [ "$1" = "" ] then echo "type files in form of [ N/file or N/dir/file ], where" echo "N is the volume number (as in volN)" echo "or getunix -l to get list of available files" exit 1 fi if [ "$1" = "-l" ] then uucp -m mcdch1!~/unix/directory !~/receive/src.unix/ exit 0 fi for file do uucp -m mcdch1!~/unix/vol"$file" !~/receive/src.unix/ done echo "requested file(s) $* on `date`" |tee -a $HOME/unixreqs exit 0 ########################## If you can't figure out why the archives don't work, re-read this file. If you still have trouble, talk with your system administrator. If you are the system administrator, send electronic mail to me at heiby@chg.mcd.mot.com (mcdchg!heiby). BE SURE TO GIVE A RETURN ADDRESS THAT I HAVE A CHANCE OF BEING ABLE TO REACH! Non-AT&T sites giving a return address through ihnp4 or att won't get a reply. Mail from Joe Random at some site not in the uucp maps is not likely to get a reply, either. If you're not in the uucp maps, give an address relative to someone who is. Have fun! Ron. @ADD SITE NM mcdch1 EN bill@twwells.com (T. William Wells) 05/18/89 TM CST TT mcdch1 archives AD heiby@chg.mcd.mot.com (Ron Heiby) MA CO uucp;uucp;~;mcdch1 Wk1800-0730,Sa,Su ACU 1200 13125767902 "" \r\c in:--in: pduucp word: public IX uucp;howto.snarf;;;;current instructions for accessing the archive IX uucp;unix/directory;;;;a listing of what is in the comp.sources.unix archive IX uucp;x/directory;;;;a listing of what is in the comp.sources.x archive KW comp.sources.unix,comp.sources.x DE This is not an official service of Motorola and may be discontinued DE any time. The contents of these archives have been donated by the DE submitters of the files to the Usenet comp.sources.unix or DE comp.sources.x moderator for free availability throughout the DE community. Motorola assumes no responsibility for the contents of DE these files, including the suitability for their use in any DE application on any hardware. (Some of the material, for example is DE known not to run on systems sold by Motorola.) Any questions about DE suitability, problems with the software or documentation, or anything DE else related to the contents of the files should be directed to the DE persons who submitted the material originally (usually the authors). @END