heiby@mcdchg.UUCP (Ron Heiby) (04/27/88)
02/05/88 How to snarf files from the comp.sources.unix archives This file explains how to get files from the comp.sources.unix archive being maintained by the Motorola Microcomputer Div. sales office in Schaumburg, IL. This is not an official service of Motorola and may be discontinued any time. The contents of the comp.sources.unix archive have been donated by the submitters of the files to the Usenet comp.sources.unix 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 comp.sources.unix archives are currently resident on a Motorola VME Delta Series Model 2616 running System V/68 Release 3.0. They are advertised and mounted onto a Model 2316 using the Remote File Sharing feature of Release 3.0. This is done because the 2616 has a lot of uucp traffic on its very limited modem lines during much of the night. The 2316 has a single modem line, but during the hours when these archives are "turned on", it should have no other traffic competing for it. This Model 2316 system is used for real work during working hours on weekdays. In order to ensure that the archive service does not interfere with this 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 (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. 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 chicago5767902 "" \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 two 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!~/directory. To get either of these, execute a command like: uucp mcdch1!~/howto.snarf !~/MYNAME/ uucp mcdch1!~/directory !~/MYNAME/ The directory is simply the output from "ls -sRxF" on the comp.sources.unix archive disk hierarchy. It is updated just before 6 p.m. every day. Here is an old sample from the directory: total 15 0 directory 1 make.dir* 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. Be sure to look carefully to be sure you are getting the latest version available. 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. 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. 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. ########################## # getmod - 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 getmod -l to get list of available files" exit 1 fi if [ "$1" = "-l" ] then uucp -m mcdch1!~/directory !~/receive/src.unix/ exit 0 fi for file do uucp -m mcdch1!~/vol"$file" !~/receive/src.unix/ done echo "requested file(s) $* on `date`" |tee -a $HOME/modreqs exit 0 ########################## If you can't figure out why the comp.sources.unix archive doesn'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@mcdchg.UUCP (mcdchg!heiby). Have fun! Ron. -- Ron Heiby, heiby@mcdchg.UUCP Moderator: comp.newprod & comp.unix "I believe in the Tooth Fairy." "I believe in Santa Claus." "I believe in the future of the Space Program."