minnie.tuhs.org

home *** CD-ROM | disk | FTP | other *** search

/ minnie.tuhs.org / unixen.tar / unixen / Other / Coherent / DemonArchives / docs / coh4.tip.faq.z / coh4.tip.faq

Wrap

Text File | 1994-01-06 | 58.4 KB | 1,649 lines

T E C H N I C A L T I P S F O R C O H E R E N T 4.X Technical Tips FAQ for Rev 4.X of Coherent Help With Installation: 4.0 Binary compatability with other software: Compiling programs: Help with serial ports and terminals: Creating a Bootable Floppy for Emergency Use: Help With Installation: From: Bob Hemedinger <support@mwc.com> ----------------------- 1) I'm updating from version 3.x to 4.x and am being asked for a serial number from a registration card. I don't have one. - updating users do not need new serial numbers. Use the number supplied with your 3.x version. If you don't know what it is, read the file /etc/serialno. 2) I'm seeing various characters in the upper right hand corner of my screen when Coherent boots. - These are used by MWC for debugging some installation problems. If installation fails to boot, the last character(s) displayed in the corner of the screen will give a significant clue as to where the failure occurred. 3) I get a core dump during the installation. The last digits of the eip register are 2EF. - Call MWC for a new set of installation diskettes. 4) I see a prepare_gift() message when Coherent boots. - The tertiary boot program, /tboot, is attempting to read your CMOS to get your hard drive parameters and other information. This process met with an unexpected error, usually related to the initialization of cache memory. If Coherent continues to boot and run, ignore the message. If the boot fails, try this: - hit <space> when prompted by tboot to abort the boot process. Type 'info' at the first '?' prompt. Ignore the returned data. At the next '?' prompt, type 'update' or 'begin' if updating or installing, or enter the name of the kernel to boot. Follow this procedure exactly. Do NOT try the 'info' command more than once. 5) When booting the installation, I come to a # prompt with a message displayed that I didn't boot properly and need to reboot. - tboot failed to pass what you typed at the '?' prompt to the installation program. A prepare_gift() message was probably displayed before this, sometimes too quickly to be seen unless one is looking for it specifically. One can either reboot and use the procedure from item #4 (above), or type 'build' at the # prompt to install, or type 'build -u' at the # prompt to update from 3.x. 6) During boot, I see a message about not being able to release a modified buffer. - In most cases, Coherent will continue to boot normally. In some, the message will scroll endlessly. This is an indication of an incompatible bios and is a very rare case. The Epson bios set has sometimes produced this problem. If at all possible, update the bios chips in the computer. Phoenix is the bios chipset MWC recommends. 7) After installing disk #1, I reboot Coherent from the hard drive, but am never prompted to enter a diskette -or-, I reboot Coherent from the hard drive, and the system hangs with a Coherent banner message on the screen. - Thou hast most likely chosen to use either virtual consoles, or no virtual consoles but did select a loadable keyboard table. Coherent is hanging at the point where keyboard initialization takes place, indicating that the keyboard does not properly support IBM scan code 3. This is a different keyboard mode than DOS uses, and probably a good 10% of keyboards of Asian origin will have problems with this. Reinstallation without virtual consoles nor loadable keyboard tables should resolve this. 8) All diskettes install without a hitch, but after rebooting, fsck finds all sorts of DUP blocks and bad i-nodes. - This is rare, but is usually the result of installing onto a large partition. This is possibly related to sector translation firmware and/or the manner in which the firmware deals with bad blocks... we don't know yet. Break the large partition into smaller partitions and try installation again. If this is an ESDI drive, and the controller is doing sector translation, try switching it to native mode. 4.0 Binary compatability with other software: -------------------------------------------- Coherent 4.x compiles and runs COFF executables. Third party COFF software will most likely run if the following conditions are true: - does NOT use shared memory nor shared libraries. We plan to implement these in the next release of Coherent. Coherent 4.0 shared memory is not System V compliant. - does NOT rely on sockets nor streams. Again, we plan to have have at least one of these in the next release. - does NOT use graphics. Coherent 4.0 is strictly a text-based system. Again, we plan to have some form of graphics support in the future. Some examples of 3rd party software running under Coherent 4.x: ACUCOBOL Xtree BASIS International BBX/Progression 3 (BASIC) FilePro - For more info, please contact MWC, or email sales@mwc.com. Compiling programs: ------------------- 1) The compiler is complaining about not enough memory. - You may have a significant amount of memory, say 2 or 4 Megabytes, but one must also account for other running processes. The compiler by default tries to do all of its work in core (memory). If it aborts due to not enough memory, then add a -T0 to your cc command line. This will force the compiler to use temporary files on the hard drive, rather than in core. 2) I'm trying to port software from a bbs or the net. Is Coherent closer to System V or BSD? - You should select System V wherever possible. We tend to avoid BSDisms. 3) When compiling a package, the linker complains that getwd() doesn't exist. This worked under 3.x. What happened? - With Coherent 4.0, we have gone to getcwd() in place of getwd(). We have supplied _getwd() for people that need getwd(), but we are planning on dropping this in the future. Help with serial ports and terminals: ------------------------------------- robert@cstpl.com.au (Robert Chalmers) Coherent V4.0/4.01. Thanks, Robert! If you follow the installation instructions, and choose their defaults, you will end up with a ttys file very similar to the following. 0lPcom1l <--| 0lPcom2l | -- The four standard COM1, COM2, 0lPcom3l | COM3 & COM4 ports. NOT CONFIGURED. 0lPcom4l <--| See the notes below for configuration. 1lPmono0 <--| 1lPmono1 | -- The terminal virtual consoles. 1lPmono2 | These REPLACE the V3.x's 1Pconsole 1lPmono3 <--| entry in that versions ttys file. You dont have to touch these. For example, on my system I had the following hardware. One standard HDD/FDD Controller (IDE) with COM1, COM2 and LPT1 on board, and enabled. These live at 3F8 - IRQ4, and 2F8 - IRQ3. LPT1 uses 378 and IRQ7. One standard Taiwan Multi I/O card with 2 COM ports, one printer port, and one game port. This card can be configured as COM1/2 or COM3/4, and LPT1 or LPT2. I have the jumpers set for the following. COM3 at 3E8 - IRQ4 and COM4 at 2E8 - IRQ3, with the second printer, LPT2 at 278 - IRQ5. Now, setting them up, as applied to this type of 2 board setup. If you are not sure if your installation configured the ports correctly, then follow the instructions in the Release Notes and Installation Guide under 'Asy' exactly as they appear, regarding the making of the devices. Dont change anything. yet. Now, the thing to note is the rule on IRQs and Polling. If you are using COM2 as your modem port, (seems to be the most used option), and COM1 as a terminal connection, and both are using IRQs, then the other two must be Polled. COM3 and COM4 must be Polled. Observe my settings listed, 0lPcom1l <--- Serial terminal on COM1. IRQ4 1rLcom2r <--- Modem, incoming, on COM2. IRQ3 0lLcom2l <--- Modem, outgoing (the same modem) on COM2. IRQ3 0lPcom3pl <--- Serial terminal on COM3. Polled 0lPcom4pl <--- Serial terminal on COM4. Polled 1lPmono0 <-| 1lPmono1 | 1lPmono2 | --virtual screens. 1lPmono3 <-| The Serial terminals are shown as 'disabled' in the above listing, but when they are connected, you simply type 'enable com3pl' and presto!, you get a login prompt on that terminal. In SUMMARY: Install with all defaults. Run the three configuration commands in the Asy entry. The asyxxx entries in your /dev directory are the prototypes for the comxx devices, so you can ignore them for the purposes of this. Decide which lines you will use, and check your IRQ/Poll combination. Check your physical wiring. For terminals, you only need three wires: D25 connectors. TXD to RXD, RXD to TXD, Common Ground. 2 --> 3 3 <-- 2 7 <-> 7 D9 connector. TXD to RXD, RXD to TXD, Common Ground. 2 --> 3 3 <-- 2 5 <-> 5 In the above setting, to call out on the modem, you MUST type 'disable com2r' before you can call out on com2l. When you are finished, type 'enable com2r' to put your modem back on line. Other things of note: Old Xt's with a com port and any version of TELIX/PROCOMM/etc etc make good cheap terminals, as do old terminals that businesses throw away as obsolete. Windows 3.1's Terminal will emulate a vt100. If you have a second PC connected to a Coherent serial port, its 'almost!' like having Xterm running Coherent in a Term window. You can even cut and paste between Word for Windows etc and vi. So who needs X I ask? Creating a Bootable Floppy for Emergency Use: --------------------------------------------- Forwarded here by Robert Chalmers, work done by Udo and Vlad | Udo and Vlad have done a MARVELOUS job here. -- Robert Chalmers | [Two spaces have been added to the start of each line to avoid mailer and nroff problems... --Mike] -------------------------Cut Here------------------------------- # shell script to create a bootable floppy disk # Works with COHERENT 3.x and COHERENT 4.0. # Written by Udo Munk (udo@umunk.GUN.de) # with help from Vladimir Smelyansky (vlad@mwc.com) clear if [ $USER != root ] then echo "This program must be run as user root!" exit fi echo "This programm creates a bootable floppy disk for COHERENT." echo "Because booting the PC hardware only works with floppy drive A" echo "I want to know the size of your A device first." echo while true do echo -n "Is your A device a 5.25 inch drive (answer y or n): " read answer if [ $answer = y -o $answer = n ] then break else echo "answer with y or n please!" echo fi done if [ $answer = y ] then echo "Fine, let us create a 5.25 inch bootable floppy disk." dev=/dev/fha0 devsize="5.25" devblocks=2400 boot=/conf/boot.fha else echo "Fine, let us create a 3.5 inch bootable floppy disk." dev=/dev/fva0 devsize="3.5" devblocks=2880 boot=/conf/boot.fva fi echo echo "Now please put a" $devsize "floppy disk into your drive A". echo "WARNING: ALL DATA ON THIS FLOPPY DISK WILL BE DESTROYED!" echo echo -n "Type y if you want to continue, any other to abort: " read answer if [ $answer != y ] then exit fi clear echo "Step 1: formating floppy disk..." /etc/fdformat $dev echo "Step 2: building the bad block list..." /etc/badscan -o bootdisk $dev $devblocks echo "Step 3: building a filesystem..." /etc/mkfs $dev bootdisk rm bootdisk echo "Step 4: copy the bootstrap onto the floppy disk..." cp $boot $dev /etc/mount $dev /mnt if [ -f /tboot ] then cp /tboot /mnt fi cp /dpb /mnt echo "Step 5: copy the kernel and patch it..." cp /coherent /mnt ln /mnt/coherent /mnt/autoboot if [ -f /tboot ] # we are running Coherent 4.x then if [ $dev = /dev/fha0 ] # drive A is 5.25 inch then /conf/patch /mnt/coherent rootdev=makedev$4,14$ /conf/patch /mnt/coherent pipedev=makedev$4,14$ else # drive A is 3.5 inch /conf/patch /mnt/coherent rootdev=makedev$4,15$ /conf/patch /mnt/coherent pipedev=makedev$4,15$ fi else # we are running Coherent 3.x if [ $dev = /dev/fha0 ] # drive A is 5.25 inch then /conf/patch /mnt/coherent rootdev_=makedev$4,14$ /conf/patch /mnt/coherent pipedev_=makedev$4,14$ else # drive A is 3.5 inch /conf/patch /mnt/coherent rootdev_=makedev$4,15$ /conf/patch /mnt/coherent pipedev_=makedev$4,15$ fi fi echo "Step 6: copy all neccesary files to the floppy disk..." mkdir /mnt/mnt mkdir /mnt/tmp cpdir /dev /mnt/dev cpdir /drv /mnt/drv mkdir /mnt/conf cpdir /conf/kbd /mnt/conf/kbd mkdir /mnt/bin cp /bin/bad /mnt/bin cp /bin/check /mnt/bin cp /bin/chgrp /mnt/bin cp /bin/chmod /mnt/bin cp /bin/chown /mnt/bin cp /bin/cmp /mnt/bin cp /bin/cp /mnt/bin cp /bin/cpdir /mnt/bin cp /bin/date /mnt/bin cp /bin/db /mnt/bin cp /bin/dcheck /mnt/bin cp /bin/df /mnt/bin cp /bin/find /mnt/bin cp /bin/grep /mnt/bin cp /bin/icheck /mnt/bin cp /bin/ln /mnt/bin cp /bin/ls /mnt/bin cp /bin/lc /mnt/bin cp /bin/mkdir /mnt/bin cp /bin/mv /mnt/bin cp /bin/ncheck /mnt/bin cp /bin/ps /mnt/bin cp /bin/pwd /mnt/bin cp /bin/rm /mnt/bin cp /bin/rmdir /mnt/bin cp /bin/scat /mnt/bin cp /bin/sh /mnt/bin cp /bin/stty /mnt/bin cp /bin/sync /mnt/bin mkdir /mnt/usr mkdir /mnt/usr/tmp mkdir /mnt/usr/bin cp /usr/bin/vi /mnt/usr/bin cp /usr/bin/me /mnt/usr/bin cp /usr/bin/more /mnt/usr/bin if [ -d /usr/lib/terminfo ] then mkdir /mnt/usr/lib mkdir /mnt/usr/lib/terminfo mkdir /mnt/usr/lib/terminfo/a cp /usr/lib/terminfo/a/ansipc /mnt/usr/lib/terminfo/a fi mkdir /mnt/etc cp /etc/.profile /mnt/etc cp /etc/ATclock /mnt/etc cp /etc/badscan /mnt/etc cp /etc/clri /mnt/etc if [ -f /etc/drvld ] then cp /etc/drvld /mnt/etc fi cp /etc/drvld.all /mnt/etc cp /etc/fdisk /mnt/etc cp /etc/fsck /mnt/etc cp /etc/init /mnt/etc cp /etc/mkfs /mnt/etc cp /etc/mount /mnt/etc cp /etc/reboot /mnt/etc cp /etc/umount /mnt/etc cp /etc/serialno /mnt/etc cp /etc/timezone /mnt/etc cp /etc/termcap /mnt/etc echo "Step 7: create lost+found with enough empty directory slots..." mkdir /mnt/lost+found for I in 0 1 2 3 4 5 6 7 8 9 do for J in 0 1 2 3 4 5 6 7 8 9 do touch /mnt/lost+found/$I$J done done rm /mnt/lost+found/* echo "Step 8: create some files, so that boot ends in single user mode..." cat >/mnt/etc/brc <<! . /etc/timezone /bin/date -s \`/etc/ATclock\` >/dev/null /etc/drvld.all exit 1 ! >/mnt/etc/checklist >/mnt/etc/mount.all echo "Last step: check the filesystem of the created floppy disk:" /etc/umount $dev /etc/fsck $dev echo "Fine, floppy disk ready, store it at a cold and dry place but" echo "where you can remeber in case of an emergency :-)" -------------------------End Here------------------------------- More Q & A... ==================================================================== I have a mixed DOS/Coherent system which I want to turn back into a pure DOS system. enter the following command from the DOS prompt: FDISK /MBR <CR> this will rewrite the Master Boot Record and exit I have installed MGR successfully and there are no big problems with Coh. 4.0.1r77, but my mouse (Truemouse - Model TX3000) will not work correct. After starting MGR the mousecursor will jump around the screen without any sense and sometimes there are menus and windows on the screen too. I have also a original Microsoft mouse and this mouse will work fine. Are there any additional things that I can do to get the Truemouse running with MGR ? Look at the baud-rate at which your mouse is working. Microsoft mice are normally operated at 1200. Logitech's default baud-rate is 2400. I've seen (IBM-)mice that worked at 9600 baud ... I hope this helped ... Setting the term type There are a number of inquiries about setting the TERM type depending on the line being used. I found the following in a book called "Unix Administration Guide for System V". Works fine. in /etc/ttytype ( rw.r..r.. /etc/ttytype ) ansipc color0 ansipc color1 ansipc color2 ansipc color3 vt100 com2r vt100 com1pl Use what ever combinations suit your specific setup. In /usr/local/bin/newtset ( rwxr.xr.x /usr/local/bin/newtset ) ( remove the + signs ) + : + # newtset - get terminal type from /etc/ttytype + TTY=`tty | sed 's./dev/..'` + set - `grep $TTY /etc/ttytype` + echo $1 In your .profile ( sh or ksh ) put the line, TERM=`newtset` export TERM assuming that /usr/local/bin is in the system default path. Logging off unused terminals Thanks to Ray Swartz, President of Berkley Decision/Systems, and author of the "Answers to Unix" column in Unix World for the following script. A little bit of tweeking to get it Coh-aware, and it works fine. Having a problem with users leaving terminals logged on for hours on end while they go off to play golf? apart from bad security, it can tie up valuable serial lines - not to mention phone lines. It can also cost the unwary a fortune, if timed calls are being used, and they dont hang up correctly. This script watches the port specified, for the time specified at the top of the script, and if there is no activity for a set period, it will gracefully shut down running pid's and hangup. Remove the + signs. ============================ cut here ========================= + MAXTIME=2 # minutes of idle time allowed + DEVMODEM=com1pl # terminal line to watch + while true; do + if ps -e | grep $DEVMODEM | grep getty > /dev/null + then # don't try to kill getty + count=`expr 60 $MAXTIME ` + sleep $count + fi + set `date | awk '{print $4}' | sed 's/:/ /g'` + now=`expr $1 60 + $2 ` + lastentry=`ls -lu /dev/$DEVMODEM | sed 's/:/ /' | + awk '{print $10 * 60 + $11}'` # end of pipeline + idle=`expr $now - $lastentry ` + if [ $idle -ge $MAXTIME ] + then + echo " 07 + This terminal have been idle for $MAXTIME minutes. + You will be logged off in 1 minute unless you + press <return> now." > /dev/$DEVMODEM + sleep 60 # wait for a minute + logouttest=`ls -lu /dev/$DEVMODEM | sed 's/:/ /' | + awk '{print $10 * 60 + $11}'` # end of pipeline + if [ $lastentry -eq $logouttest ] + then + ps -e | awk '$1 == "'$DEVMODEM'" {print $2}' | + sort -nr | while read pid # kill in reverse order + do + kill -1 $pid # send the hangup signal + done + fi + fi + sleep 60 + done ============================= cut here ================================ I havent put comments in the script, it's fairly self evident. I am now running r77 kernel/ps thingy so you may need to tweek the $1 fields to get the right variable values if you are running earlier ps or kernel releases, but I'm not sure. . Notes on zipped file types. --------------------------- > But what is tgz file type. I have zip and gzip and lha, but tgz is not > familiar. tgz is used by gzip if the filename without compression is longer than 11 chars because tar.gz won't fit. The newer version of gzip ( 1.23 ) creates a suffig .gz, but handles .tgz as .tar.gz , too. * michael@jester.gun.de * Michael Gerhards Random Notes on Various things... ---------------------------------- AMI BIOS In article <930925212@cstpl.com.au> you write: > Coherent will not run on an AT&T 6300, IBM PS/2 model, or with the > Western Digital WD1004-27X (XT) or other XT controllers. Coherent > exhibits a slight problem with some 386 AMI BIOS, whereas > Coherent requires a cold boot (hit the reset switch, not CTL- > ALT-DEL) to boot Coherent after previously running DOS. The latest > revisions of the AMI BIOS may not exibit this problem. The 486 AMI BIOS dated June 6, 1992 still exhibits this problem. I'm not sure if there are more recent versions; I bought my 486 (50 MHx DX) in December 1992. Subject: Re: Disk upgrade suggestions? Udo says: > : MWC says that 4.2 will support Adaptec, Future Domain, and Seagate > : SCSI controllers -- anybody have any recommendations as to which > : controllers work best with Coherent? > > Buy an Adaptec, it's the fastest one because of the busmaster DMA. > Also SCSI tape support for the Adaptek already is done and does work. But I would like to warn you for a problem that I experienced. The Adaptec (1542C in my case) is a very good controller, but conflicts with my busmastering NE2100 ethernet card. No fault of the Adaptec, the problem is the ethernet card. Brand is Escom, but an article in C'T (Udo should be familiar with it since it is a German magazine) mentioned that the original NE2100 has the same problem, as do most of it's clones. If you happen to be using one of those, you're in for a disappointment. I'm trying to find an ethernet card that doesn't use busmastering now. Taco Graafsma IJselland Polytechnic, Chemistry department Deventer, The Netherlands taco.graafsma@hto.rhij.nl Subject: Re: Disk upgrade suggestions? > I'm having a tough time finding any detailed info on Adaptec > controllers, like what's the difference between the 1540, 1542A, 1542B > and 1542C? What additional goodies are included in a "kit?" The difference between 1540 and 1542 is that the latter supports diskette drives. There are several more model ranges, 1740 (EISA) among them. I'm not completely sure about the differences between A, B and C models. C obviously is newer than B etc.. C is SCSI-2, which does make a difference for faster SCSI drives. Installation and configuration is a lot easier for C and it has active termination (software controlled), which if I remember correctly is a requirement for SCSI-2. There are many more improvements I'm sure, but I can't produce them from the top of my head. I use a 1540C and like it a lot, but I have heard of problems because timing is so sensitive. They mainly turn up when using external SCSI devices. It seems you need very good cables. As for the driver kits: they contain drivers for DOS, Netware en SCO Unix (again, I must drag this from the dark crevices of my memory so correct me if I'm wrong) and configuration programs for DOS and Windows. I think it is comparable to a stripped version of Corel SCSI. If you are going to use it for standard environments (DOS with no more than 1 IDE, several Unices e.g. Linux) then you don't need the driver kit. Most O.S.es provide support for it, and configuration is possible with a BIOS setup. In my case I already had 2 IDE drives installed, so I needed aspi-drivers to get the SCSI drive working. > > Unless I find out something unexpected, I plan on getting an Adaptec > 1542B and either a Conner 540M or a Quantum 525M drive. The Conner I remember a test in C'T that was very enthusiastic about the Quantum: fast and large. It was too expensive for me, but I understand it is a good drive. Can't say anything about the Conner. Taco Graafsma IJselland Polytechnic, chemistry department Deventer, The Netherlands taco.graafsma@hto.rhij.nl Housekeeping Shell Script to Keep Down News Log File Sizes ---------------------------------------------------------- ============================ cut here ============================ # A shell script to look after wnews log files, from an original idea # by bill@twinbrk.uucp Bill Shotts. # This script will dump log and errlog files, and keep the last 100 entries # of the history file. This ensures that Control: commands will work correctly. NEWSDIR=/usr/lib/news DAYS=7 # The number of days between clean outs. Adjust to suit yourself. # expire old news $NEWSDIR/expire -e $DAYS # control length of log files cp $NEWSDIR/log $NEWSDIR/log.1 cp $NEWSDIR/errlog $NEWSDIR/errlog.1 rm -f $NEWSDIR/log rm -f $NEWSDIR/errlog # control length of history file mv $NEWSDIR/history $NEWSDIR/history.1 # Pour the saved history file through the awk script... cat history.1 | awk 'BEGIN { MAXLINES = 100; } { line[NR] = $0 } END { for (i = NR-MAXLINES; i <= NR; i++) { # dump the blank lines if (length(line[i]) > 0 ) print line[i] } } ' $* > history # stuff the last 100 lines back into the history file so cancel will work. ============================= cut here ================================ The Great Internet Guide ------------------------ Archive-name: mail/inter-network-guide #VERSION: $Date: 10/1/93 $ # # * INTER-NETWORK MAIL GUIDE: Last Update: 10/1/93 * # # Further modifications and (C) 1993 by Scott Yanoff (yanoff@csd4.csd.uwm.edu) # Inter-Network Mail Guide - Original Copyright (C) 1992 by John J. Chew # # This guide is available via anonymous ftp to: csd4.csd.uwm.edu # # The revised 3rd Ed. is out of !%@:: A Directory of Electronic Mail # Addressing & Networks by Donnalyn Frey and Rick Adams. In addition to # providing detailed information about how to use email, it tells how to # send mail to and from over 180 networks around the world. # # INTRODUCTION # # This file documents methods of sending mail from one network to another. # It represents the aggregate knowledge of the readers of comp.mail.misc # and many contributors elsewhere. If you know of any corrections or # additions to this file, please follow the instructions in the section # entitled 'HOW TO FORMAT INFORMATION FOR SUBMISSION' and then mail the # information to me: Scott A. Yanoff <yanoff@csd4.csd.uwm.edu>. # # HOW TO USE THIS GUIDE # # If you just want to browse the guide manually for information, this is what # you need to know. The guide is organized as a list of entries. Each entry # tells you how to get from one network to another. Here is what a typical # entry might look like: # # #FROM: mynet # #TO: yournet # #RECIPIENT: youraddress # #CONTACT: contactaddress # #INSTR: send to 'youraddress@thegateway' # # This means that to send mail FROM a network called 'mynet' TO a # RECIPIENT address 'youraddress' on a network called 'yournet', you # should follow the INSTRUCTIONS shown and address your mail to # 'youraddress@thegateway'. # # Names and descriptions of the possible FROM and TO fields: # #N: aol ; America Online; America Online, Inc.; commercial; #N: alternex ; AlterNex; IBASE; non-profit (Brazil); #N: applelink ; AppleLink; Apple Computer, Inc.; commercial; #N: arcom ; X.400; ?; ?; #N: att ; AT&T Mail; AT&T; commercial; #N: bitnet ; BITNET; none; academic; #N: bix ; Byte Information eXchange; Byte magazine; commercial; #N: bmug ; BMUG ; Berkeley Macintosh Users Group; in-house; #N: calvacom ; Calvacom; #- Reseau & Communication Informatique (RCI-Calvacom); commercial; #N: chasque ; Chasque; Instituto del Tercer Mundo; non-profit (Uraguay) #N: comlink ; ComLink; ? ; non-profit (Germany); #N: compuserve ; CompuServe; CompuServe Inc.; commercial; #N: connect ; Connect Professional Information Network; ?; commercial; #N: easylink ; Easylink; AT&T; commercial; #N: easynet ; Easynet; DEC; in-house; #N: econet ; EcoNet; Institute for Global Communications; non-profit; #N: ecuanex ; EcuaNex; ? ; non-profit (Ecuador); #N: envoy ; Envoy-100; Telecom Canada; commercial; X.400 #N: fax ; Facsimile document transmission; none; none; #N: fidonet ; FidoNet; none; bbs; #N: genie ; GEnie; GE Information Services; commercial; #N: geonet ; GeoNet Mailbox Systems; #- Geonet Mailbox Services GmbH/Systems Inc.; commercial; #N: glasnet ; GlasNet; ? ; non-profit (Russia); #N: gold-400 ; GNS Gold 400; British Telecom; commercial; X.400 #N: goldgate ; GoldGate Telcom Gold; Net-Tel Computer Systems; ?; #N: greennet ; GreenNet; Soft Solutions Ltd; commercial (England); #N: gsfcmail ; GSFCmail; NASA/Goddard Space Flight Center; in-house; #N: ibm ; VNET; IBM; in-house; #N: ibmmail ; ?; IBM; commercial?; #N: internet ; Internet; none; academic; #N: keylink ; KeyLink; Telecom Australia; commercial; X.400 #N: mailnet ; X.400; ?; ?; #N: mausnet ; Mausnet; Mausnet; non-profit; #N: mci ; MCIMail; MCI; commercial; #N: nasamail ; NASAMail; NASA; in-house; #N: nicarao ; Nicarao; CRIES; non-profit (Nicaragua); #N: nordnet ; NordNet; ? ; non-profit (Sweden); #N: nsi ; NASA Science Internet; NASA; government; #- Dual-protocol: instructions given here pertain only to NSI-DECnet addresses #- (NSI-TCP/IP addresses should be treated as shown for 'internet') #N: omnet ; OMNET; OMNET; commercial; #N: peacenet ; PeaceNet/EcoNet; Institute for Global Communications; #- non-profit; #N: pegasus ; Pegasus; Pegasus Networks; non-profit (Australia); #N: prodigy ; PRODIGY; commercial; ?; #N: sinet ; Schlumberger Information NETwork; ?; ?; #N: sprintmail ; SprintMail; Sprint; commercial; formerly Telemail #N: thenet ; Texas Higher Education Network; University of Texas; #- academic ; #N: web ; The Web; Nirv Community Resource Centre; non-profit(Canada) #N: wwivnet ; WWIVnet; WWIVnet; non-profit; # The 'RECIPIENT' record gives an example of an address on the # destination network, to make it clear in subsequent lines what text # requires subsitution. # # The 'CONTACT' record gives an address for inquiries concerning the # gateway, expressed as an address reachable from the source (#FROM:) network. # Presumably, if you can't get the gateway to work at all, then knowing # an unreachable address on another network will not be of great help. # # The 'INSTR' records, of which there may be several, give verbal # instructions to a user of the source network to let them send mail # to a user on the destination network. Text that needs to be typed # will appear in double quotes, with C-style escapes if necessary. If # the instructions consist simply of mailing to a certain address, this # will be indicated by the words 'send to' followed by a quoted address. # If there are alternative addresses, they will be marked 'or to' instead. # # HOW TO FORMAT INFORMATION FOR SUBMISSION # # Here is what I really want in the way of information. If you are adding # a new network to the list, tell me what its official name is (pay attention # to capitalization), what the name of its responsible organization is, and # what kind of a network it is (academic, commercial, government, in-house # or non-profit). If this isn't clear, look at the examples above. # For each connection, give me an entry that looks something like: # # #FROM: foonet # #TO: barnet # #RECIPIENT: baraddress # #CONTACT: contactaddress # #INSTR: send to 'baraddress@thegateway' # # Note that 'contactaddress' must be an address expressed in foonet's native # format, and not that of barnet, since if a user is having trouble accessing # barnet, giving him/her an address on that net to contact for help is not # productive. If there is no contact/postmaster address, please tell me. # If there are more complicated instructions, use additional #INSTR: lines. # # Once you've got all the information together, send it to me in an e-mail # message with the words 'INMG update' in the Subject: line. You can in # general expect an answer back from me within a week. #FROM: aol #TO: applelink #RECIPIENT: user #CONTACT: Internet #INSTR: send to 'user@applelink' #FROM: aol #TO: compuserve #RECIPIENT: 71234,567 #CONTACT: Internet #INSTR: send to '71234.567@cis' #FROM: aol #TO: genie #RECIPIENT: user #CONTACT: Internet #INSTR: send to 'user@genie' #FROM: aol #TO: internet #RECIPIENT: user@domain #CONTACT: Internet #INSTR: send to 'user@domain' #FROM: applelink #TO: bitnet #RECIPIENT: user@site #INSTR: send to 'user@site.bitnet@internet#' #FROM: applelink #TO: internet #RECIPIENT: user@domain #INSTR: send to 'user@domain@internet#' (address must be < 35 characters) #FROM: arcom #TO: internet #RECIPIENT: fred@Domain.dd.uu.us #INSTR: send to C=CH,A=ARCOM,P=SWITCH,ORG=us,OU1=uu,OU2=dd,OU3=Domain,S=fred #FROM: att #TO: bitnet #RECIPIENT: user@site #INSTR: send to 'internet!site.bitnet!user' #FROM: att #TO: internet #RECIPIENT: user@domain #INSTR: send to 'internet!domain!user' #FROM: bitnet #TO: internet #RECIPIENT: user@domain #INSTR: Methods for sending mail from Bitnet to the Internet vary depending on #- what mail software is running at the Bitnet site in question. In the #- best case, users should simply be able to send mail to 'user@domain'. #- If this doesn't work, try 'user%domain@gateway' where 'gateway' is a #- Bitnet-Internet gateway site nearby. Finally, if neither of these #- works, you may have to try hand-coding an SMTP envelope for your mail. #FROM: calvacom #TO: fax #RECIPIENT: (1) 41 08 11 99 #INSTR: send to 'TLC/41081199' #INSTR: use standard phone numbers as calling from Paris, France. #FROM: calvacom #TO: internet #RECIPIENT: user@domain #CONTACT: postmaster@calvacom.fr #INSTR: send to 'EM/user@domain' #FROM: calvacom #TO: telex #RECIPIENT: telex_number #CONTACT: 634000 RCINF #INSTR: send to 'TLX/telex_number' #FROM: calvacom #TO: X400 #RECIPIENT: G=John, S=Smith, O=ORG, P=PRMD, A=ADMD, C=CA #CONTACT: S=ADM1/A=ATLAS/P=CALVACOM/C=FR #INSTR: send to 'X400/G=John/S=Smith/O=ORG/P=PRMD/A=ADMD/C=CA' #INSTR: Calvacom professionnal account needed. #FROM: calvacom #TO: mercurylink/easylink #RECIPIENT: number #CONTACT: 19000600 #INSTR: send to 'ML/number' #INSTR: Calvacom professionnal account needed. #FROM: compuserve #TO: fax #RECIPIENT: +1 415 555 1212 #INSTR: send to '>FAX 14155551212' #INSTR: not transitive - message must originate from a CompuServe user #INSTR: for calls outside the NANP, use '011' as the international prefix #FROM: compuserve #TO: internet #RECIPIENT: user@domain #INSTR: send to 'INTERNET:user@domain' (only from CompuServe users) #FROM: compuserve #TO: mci #RECIPIENT: 123-4567 #INSTR: send to '>MCIMAIL:123-4567' (only from CompuServe users) #FROM: connect #TO: internet #RECIPIENT: user@domain #INSTR: send to 'DASN' #- and set the first line of message: '"user@domain"@DASN' #FROM: easylink #TO: calvacom #RECIPIENT: JS10 (John Smith) #INSTR: send to '19000600 /ATTN JS10 SMITH+' #FROM: easynet #TO: bitnet #RECIPIENT: user@site #CONTACT: DECWRL::ADMIN #INSTR: send to 'nm%DECWRL::"user@site.bitnet"' (from VMS using NMAIL) #INSTR: send to 'user@site.bitnet' (from Ultrix) #INSTR: or to 'user%site.bitnet@decwrl.dec.com' (from Ultrix via IP) #INSTR: or to 'DECWRL::"user@site.bitnet"' (from Ultrix via DECN) #FROM: easynet #TO: fidonet #RECIPIENT: john smith at 1:2/3.4 #CONTACT: DECWRL::ADMIN #INSTR: send to 'nm%DECWRL::"john.smith@p4.f3.n2.z1.fidonet.org"' #- (from VMS using NMAIL) #INSTR: send to 'john.smith@p4.f3.n2.z1.fidonet.org' #- (from Ultrix) #INSTR: or to '"john.smith%p4.f3.n2.z1.fidonet.org"@decwrl.dec.com' #- (from Ultrix via IP) #INSTR: or to 'DECWRL::"john.smith@p4.f3.n2.z1.fidonet.org"' #- (from Ultrix via DECN) #FROM: easynet #TO: internet #RECIPIENT: user@domain #CONTACT: DECWRL::ADMIN #INSTR: send to 'nm%DECWRL::"user@domain"' (from VMS using NMAIL) #INSTR: send to 'user@domain' (from Ultrix) #INSTR: or to 'user%domain@decwrl.dec.com' (from Ultrix via IP) #INSTR: or to 'DECWRL::"user@domain"' (from Ultrix via DECN) #INSTR: or to 'user@domain @Internet' (using ALL-IN-1) #FROM: envoy #TO: internet #RECIPIENT: user@domain #CONTACT: ICS.TEST or ICS.BOARD #INSTR: send to '[RFC-822="user(a)domain"]INTERNET/TELEMAIL/US' #INSTR: for special characters, use @=(a), !=(b), _=(u), #INSTR: any=(three octal digits) #FROM: fax #TO: calvacom #RECIPIENT: JS10 (John Smith) #INSTR: send to '+33 1 41 08 11 99' #INSTR: and write on every pages 'ATTN JS10 SMITH' #INSTR: fax are manually processed. #FROM: fidonet #TO: internet #RECIPIENT: user@machine.site.domain #INSTR: convert to 'user@machine.site.domain ON 1:1/31 #FROM: fidonet #TO: wwivnet #RECIPIENT: number@node #CONTACT: Kevin C. ON 1:100/215 #INSTR: convert to '#number @node ON 1:100/215' #INSTR: WWIVgate; LOW TRAFFIC SITE, USE SPARINGLY.. Gateway is modem-based, #- they absorb cost of long distance connects to pick-up and deliver. #- Keep messages under 10K, use infrequently, do NOT use mail-lists or #- file/list-server commands. #FROM: genie #TO: internet #RECIPIENT: user@domain #CONTACT: postmaster@genie.geis.com #INSTR: send to user@domain@INET# #FROM: geonet #TO: internet #RECIPIENT: user@domain #INSTR: send to 'DASN' #INSTR: set subject line to 'user@domain!subject' #FROM: gold-400 #TO: internet #RECIPIENT: user@host #INSTR: send to '/DD.RFC-822=user(a)host/O=uknet/PRMD=uk.ac/ADMD=gold 400/C=GB/' #INSTR: for special characters, use @=(a), %=(p), !=(b), "=(q) #FROM: gsfcmail #TO: internet #RECIPIENT: user@domain #CONTACT: cust.svc #INSTR: send to '(SITE:SMTPMAIL,ID:<user(a)domain>)' #INSTR: or to '(C:USA,A:TELEMAIL,P:SMTPMAIL,ID:<user(a)domain>)' #INSTR: or send to 'POSTMAN' #- and set the first line of message to 'To: user@domain' #INSTR: Help is also available by phoning +1 800 858 9947. #FROM: gsfcmail #TO: nsi #RECIPIENT: host::user #CONTACT: cust.svc #INSTR: send to '(SITE:SMTPMAIL,ID:<user(a)host.DN.NASA.GOV>)' #INSTR: or to '(C:USA,A:TELEMAIL,P:SMTPMAIL,ID:<user(a)host.DN.NASA.GOV>)' #INSTR: or send to 'POSTMAN' #- and set the first line of message to 'To: user@host.DN.NASA.GOV' #FROM: ibmmail #TO: ibmmail (internet) #RECIPIENT: "userid@domain" #INSTR: imbed the following lines in messages sent from IBMMAIL and address #- the message to IBMMAIL(INTERNET) #- /INTERNET #- /TO userid1@domain #- /CC userid2@domain #- /REPORT #- /END #FROM: internet #TO: alternex #RECIPIENT: user #CONTACT: suporte@ax.apc.org #CONTACT: +55 (21) 286-0348 #INSTR: send to 'user@ax.apc.org' #FROM: internet #TO: aol #RECIPIENT: A User #CONTACT: postmaster@aol.com #INSTR: send to auser@aol.com (all lower-case, remove spaces) #INSTR: msgs are truncated to 32K (8K for PCs), all characters except newline #- & printable ASCII characters are mapped to spaces, users are limited to #- 75 pieces of Internet mail in their mailbox at a time. #FROM: internet #TO: applelink #RECIPIENT: user #INSTR: send to 'user@applelink.apple.com' #FROM: internet #TO: arcom #RECIPIENT: (G:John, I:Q., S:Smith, OU:ORG_UNIT, O:Org, P:PRMD, A:ADMD, C:CA) #INSTR: send to: #- /G=John/I=Q/S=Smith/OU=ORG_UNIT/O=Org/P=PRMD/A=ADMD/C=CA@chx400.switch.ch #FROM: internet #TO: att #RECIPIENT: user #INSTR: send to 'user@attmail.com' #FROM: internet #TO: bitnet #RECIPIENT: user@site #INSTR: send to 'user%site.bitnet@gateway' where 'gateway' is a gateway host #- that is on both the internet and bitnet. Some examples of gateways #- are: cunyvm.cuny.edu mitvma.mit.edu. Check first to see what local #- policies are concerning inter-network forwarding. #FROM: internet #TO: bix #RECIPIENT: user #INSTR: send to 'user@bix.com' #FROM: internet #TO: bmug #RECIPIENT: John Smith or John J. Smith #CONTACT: Email the director: Steve_Costa@bmug.org or phone (510)849-BMUG #INSTR: send to 'John.Smith@bmug.org' or 'John_J_Smith@bmug.org' #FROM: internet #TO: calvacom #RECIPIENT: JS10 (John Smith) #INSTR: send to 'js10@calvacom.fr' #INSTR: msgs are limited to 100 000 chars each. #FROM: internet #TO: chasque #RECIPIENT: user #CONTACT: apoyo@chasque.apc.org #CONTACT: +598 (2) 496192 #INSTR: send to 'user@chasque.apc.org' #FROM: internet #TO: comlink #RECIPIENT: user #CONTACT: support@oln.comlink.apc.org #CONTACT: +49 (511) 350-3081 #INSTR: send to 'user@oln.comlink.apc.org' #FROM: internet #TO: compuserve #RECIPIENT: 71234,567 #INSTR: send to '71234.567@CompuServe.com' #INSTR: Ordinary Compuserve account IDs are pairs of octal numbers #FROM: internet #TO: compuserve #RECIPIENT: organization:department:user #INSTR: send to 'user@department.organization.compuserve.com' #INSTR: This syntax is for use with members of organizations which have a #- private CompuServe mail area. 'department' may not always be present. #FROM: internet #TO: connect #RECIPIENT: NAME #INSTR: send to 'NAME@connectinc.com' #FROM: internet #TO: easylink #RECIPIENT: user mail number 1234567 #INSTR: send to: 1234567@eln.attmail.com #FROM: internet #TO: easynet #RECIPIENT: HOST::USER #CONTACT: admin@decwrl.dec.com #INSTR: send to 'user@host.enet.dec.com' #INSTR: or to 'user%host.enet@decwrl.dec.com' #FROM: internet #TO: easynet #RECIPIENT: John Smith @ABC #CONTACT: admin@decwrl.dec.com #INSTR: send to 'John.Smith@ABC.MTS.DEC.COM' #INSTR: this syntax is for sending mail to ALL-IN-1 users #FROM: internet #TO: econet #RECIPIENT: user #CONTACT: support@igc.apc.org #CONTACT: +1 (415) 442-0220 #INSTR: send to 'user@igc.apc.org #FROM: internet #TO: envoy #RECIPIENT: John Smith (ID=userid) #INSTR: send to 'uunet.uu.net!att!attmail!mhs!envoy!userid' #FROM: internet #TO: ecuanex #RECIPIENT: user #CONTACT: intercom@ecuanex.apc.org #CONTACT: +593 (2) 505 074 #INSTR: send to 'user@ecuanex.apc.org' #FROM: internet #TO: envoy #RECIPIENT: John Smith (ID=userid) #CONTACT: /C=CA/ADMD=TELECOM.CANADA/ID=ICS.TEST/S=TEST_GROUP/@nasamail.nasa.gov #INSTR: send to #INSTR: '/C=CA/ADMD=TELECOM.CANADA/DD.ID=userid/PN=John_Smith/@Sprint.COM' #FROM: internet #TO: fidonet #RECIPIENT: john smith at 1:2/3.4 #INSTR: send to 'john.smith@p4.f3.n2.z1.fidonet.org' #FROM: internet #TO: genie #RECIPIENT: user #CONTACT: postmaster@genie.geis.com #INSTR: send to user@genie.geis.com #FROM: internet #TO: geonet #RECIPIENT: user at host #INSTR: send to 'user:host@map.das.net' #INSTR: or to 'user@host.geomail.org' (known to work for geo2) #INSTR: known hosts: geo1 (Europe), geo2 (UK), geo4 (USA) #FROM: internet #TO: glasnet #RECIPIENT: user #CONTACT: support@glas.apc.org #CONTACT: +7 (095) 217-6182 #INSTR: send to 'user@glas.apc.org' #FROM: internet #TO: gold-400 #RECIPIENT: (G:John, I:Q, S:Smith, OU: org_unit, O:organization, PRMD:prmd) #INSTR: send to 'john.q.smith@org_unit.org.prmd.gold-400.gb' #INSTR: or to #- '"/G=John/I=Q/S=Smith/OU=org_unit/O=org/PRMD=prmd/ADMD=gold 400/C=GB/" #- @mhs-relay.ac.uk' #FROM: internet #TO: goldgate #RECIPIENT: 10087:CQQ061 #INSTR: send to '10087.CQQ061@goldgate.ac.uk' #INSTR: or to '/G=10087/S=CQQ061/P=uk.ac/O=GoldGate/C=GB/' #FROM: internet #TO: greennet #RECIPIENT: user #CONTACT: support@gn.apc.org or +44 (71) 608-3040 #INSTR: user@gn.apc.org (or user@gn.uucp if mailing from JANET) #FROM: internet #TO: gsfcmail #RECIPIENT: user #CONTACT: naic@nasa.gov #INSTR: send to 'user@gsfcmail.nasa.gov' #INSTR: or to '/PN=user/ADMD=TELEMAIL/PRMD=GSFC/O=GSFCMAIL/C=US/ #- @x400.msfc.nasa.gov' #FROM: internet #TO: ibm #RECIPIENT: user@vmnode.tertiary_domain (syntax?) #CONTACT: nic@vnet.ibm.com #INSTR: send to 'user@vmnode.tertiary_domain.ibm.com' #INSTR: To look up a user's mailbox name, mail to nic@vnet.ibm.com with #- the line 'WHOIS name' in the message body. #FROM: internet #TO: ibmmail #RECIPIENT: ccsssuuu@IBMMAIL.COM #CONTACT: IBMMAIL(ccsssuuu) #INSTR: send to ccsssuuu@ibmmail.com #- cc=country code, sss=company site, uuu=unique number (alphanumeric base 35 #- <36?> number) together this form the "userid" for ibmmail. #FROM: internet #TO: keylink #RECIPIENT: (G:John, I:Q, S:Smith, O:MyOrg, A:Telememo, C:au) #CONTACT: aarnet@aarnet.edu.au #INSTR: send to John.Q.Smith@MyOrg.telememo.au #INSTR: for keylink Private Mail Domains such as #INSTR: (G:John, S:Smith, O:MyDept, P:AusGov, A:Telememo, C:au) #INSTR: send to John.Smith@MyDept.AusGov.telememo.au #FROM: internet #TO: mausnet #RECIPIENT: hans schmidt @ box #CONTACT: sysop@k2.maus.de #INSTR: send to 'hans_schmidt@box.maus.de' #FROM: internet #TO: mci #RECIPIENT: John Smith (123-4567) #INSTR: send to '1234567@mcimail.com' #INSTR: or to 'JSmith@mcimail.com' (if 'JSmith' is unique) #INSTR: or to 'John_Smith@mcimail.com' (if 'John Smith' is unique - note the #- underscore!) #INSTR: or to 'John_Smith/1234567@mcimail.com' (if 'John Smith' is NOT unique) #FROM: internet #TO: nasamail #RECIPIENT: user #CONTACT: naic@nasa.gov #INSTR: send to 'user@nasamail.nasa.gov' #INSTR: Help is available by phoning +1 205 544 1771 or +1 800 858 9947. #INSTR: Soon to be: user@center.nasa.gov where "center" is where they work. #FROM: internet #TO: nicarao #RECIPIENT: user #CONTACT: support@nicarao.apc.org #CONTACT: +505 (2) 26228 #INSTR: send to 'user@nicarao.apc.org' #FROM: internet #TO: nordnet #RECIPIENT: user #CONTACT: support@pns.apc.org #CONTACT: +46 (8) 600-0331 #INSTR: send to 'user@pns.apc.org' #FROM: internet #TO: nsi #RECIPIENT: host::user #CONTACT: naic@nasa.gov #INSTR: send to 'user@host.dnet.nasa.gov' #INSTR: or to 'user%host.dnet@ames.arc.nasa.gov' #INSTR: or to 'user%host.dnet@east.gsfc.nasa.gov' #INSTR: Help is also available by phoning +1 800 858 9947. #FROM: internet #TO: omnet #RECIPIENT: user #CONTACT: naic@nasa.gov #INSTR: send to 'user@omnet.nasa.gov' #INSTR: or to 'user/omnet@omnet.nasa.gov' (?) #INSTR: or to '/DD.UN=user/O=OMN/ADMD=TELEMAIL/C=US/@Sprint.COM' #INSTR: Help is available by phoning +1 800 858 9947 #FROM: internet #TO: peacenet #RECIPIENT: user #CONTACT: support@igc.org #INSTR: send to 'user@igc.apc.org' #FROM: internet #TO: pegasus #RECIPIENT: user #CONTACT: support@peg.apc.org #CONTACT: +61 (7) 2571111 #INSTR: send to 'user@peg.apc.org' #FROM: internet #TO: prodigy #RECIPIENT: user #CONTACT: postmaster@prodigy.com #INSTR: send to 'user@prodigy.com' For example: abcd12a@prodigy.com #- Please note that this service is still currently being tested! #FROM: internet #TO: sinet #RECIPIENT: node::user or node1::node::user #INSTR: send to 'user@node.SINet.SLB.COM' #INSTR: or to 'user%node@node1.SINet.SLB.COM' #FROM: internet #TO: sprintmail #RECIPIENT: John Smith at SomeOrganization #INSTR: send to #- '/G=John/S=Smith/O=SomeOrganization/ADMD=TELEMAIL/C=US/@Sprint.COM' # Help is available by phoning +1 800 827 4685 #FROM: internet #TO: thenet #RECIPIENT: user@host #INSTR: send to 'user%host.decnet@utadnx.cc.utexas.edu' #FROM: internet #TO: web #RECIPIENT: user #CONTACT: spider@web.apc.org #CONTACT: +1 (416) 596-0212 #INSTR: send to 'user@web.apc.org #FROM: internet #TO: wwivnet #RECIPIENT: number@node #CONTACT: faq-request@tfsquad.mn.org or bryen@tfsquad.mn.org #INSTR: convert to 'number-node@wwiv.tfsquad.mn.org' #INSTR: WWCPgate; LOW TRAFFIC SITE, USE SPARINGLY.. Gateway is modem-based, #- they absorb cost of long distance connects to pick-up and deliver. #- Keep messages under 10K, use infrequently, do NOT use mail-lists or #- file/list-server commands. #FROM: keylink #TO: internet #RECIPIENT: John Smith <user@domain> #CONTACT: (G:CUSTOMER, S:SERVICE, O:CUST.SERVICE, P:telememo, C:au) #INSTR: send to '(C:au, A:telememo, P:oz.au, "RFC-822":"John Smith #- <user(a)domain>")' #INSTR: special characters must be mapped: @->(a), %->(p), !->(b), "->(q) #FROM: mausnet #TO: internet #RECIPIENT: user@domain #CONTACT: sysop@k2 #INSTR: send to 'user@domain' #FROM: mci #TO: compuserve #RECIPIENT: John Smith (71234,567) #CONTACT: 267-1163 (MCI Help) #INSTR: at the 'To:' prompt type 'John Smith (EMS)' #INSTR: at the 'EMS:' prompt type 'compuserve' #INSTR: at the 'Mbx:' prompt type '71234,567' #FROM: mci #TO: internet #RECIPIENT: John Smith <user@domain> #CONTACT: 267-1163 (MCI Help) #INSTR: at the 'To:' prompt type 'John Smith (EMS)' #INSTR: at the 'EMS:' prompt type 'INTERNET' #INSTR: at the 'Mbx:' prompt type 'user@domain' #FROM: nasamail #TO: internet #RECIPIENT: user@domain #CONTACT: admin #INSTR: send to '(site:smtpmail,id:<user(a)domain>)' #INSTR: Help is also available by phoning +1 205 544 1771 and at 'admin/nasa'. #FROM: nasamail #TO: nsi #RECIPIENT: host::user #CONTACT: admin #INSTR: send to '(site:smtpmail,id:<user(a)host.DN.NASA.GOV>)' #INSTR: Help is also available by phoning +1 205 544 1771 and at 'admin/nasa'. #FROM: nsi #TO: gsfcmail #RECIPIENT: user #CONTACT: naic@nasa.gov #INSTR: send to 'east::"user@gsfcmail.nasa.gov"' #INSTR: or to 'east::"/PN=user/ADMD=TELEMAIL/PRMD=GSFC/O=GSFCMAIL/C=US/ #- @x400.msfc.nasa.gov' #INSTR: Help is also available by phoning +1 800 858 9947. #FROM: nsi #TO: internet #RECIPIENT: user@domain #CONTACT: east::"naic@nasa.gov" #INSTR: send to 'east::"user@domain"' #INSTR: or to 'dftnic::"user@domain"' #INSTR: or to 'nssdca::in%"user@domain"' #INSTR: or to 'jpllsi::"user@domain"' #INSTR: Help is also available by phoning +1 800 858 9947. #FROM: nsi #TO: omnet #RECIPIENT: user #CONTACT: omnet.service #INSTR: send to 'east::"user@omnet.nasa.gov"' #INSTR: Help also available by phoning +1 617 244 4333 (OMN customers only) #FROM: nsi #TO: sprintmail #RECIPIENT: John Smith at SomeOrganization #CONTACT: east::"naic@nasa.gov" #INSTR: send to #- '/G=John/S=Smith/O=SomeOrganization/ADMD=TELEMAIL/C=US/@Sprint.COM' #INSTR: Help is also available by phoning +1 800 858 9947. #FROM: omnet #TO: internet #RECIPIENT: user@domain #CONTACT: omnet.service #INSTR: Enter 'compose manual' at the command prompt. Choose the Internet #- address option from the menu that appears. Note that this gateway #- service charges based on the number of 1000-character blocks sent. #INSTR: Help also available by phoning +1 617 244 4333 (OMN customers only). #FROM: sinet #TO: internet #RECIPIENT: user@domain #INSTR: send to 'M_MAILNOW::M_INTERNET::"user@domain"' #INSTR: or to 'M_MAILNOW::M_INTERNET::domain::user' #FROM: sprintmail #TO: internet #RECIPIENT: user@domain #INSTR: send to '(C:USA,A:TELEMAIL,P:INTERNET,"RFC-822":<user(a)domain>) DEL' #INSTR: Help available within the United States by phoning +1 800 336 0437 and #- pressing '2' on a TouchTone phone. #FROM: sprintmail #TO: nsi #RECIPIENT: host::user #INSTR: send to #- '(C:USA,A:TELEMAIL,P:INTERNET,"RFC-822":<user(a)host.DNET.NASA.GOV>) DEL' #INSTR: Help available within the United States by phoning +1 800 336 0437 and #- pressing '2' on a TouchTone phone. #FROM: telex #TO: calvacom #RECIPIENT: JS10 (John Smith) #INSTR: send to '634000 (RCINF) ; ATTN JS10 SMITH' #FROM: thenet #TO: internet #RECIPIENT: user@domain #INSTR: send to 'UTADNX::WINS%" user@domain "' #FROM: wwivnet #TO: fidonet #RECIPIENT: First Last ON zone:node/fnet #CONTACT: 1@3469 #INSTR: convert to 'First Last ON zone:node/fnet @656' #INSTR: WWIVgate; LOW TRAFFIC SITE, USE SPARINGLY.. Gateway is modem-based, #- they absorb cost of long distance connects to pick-up and deliver. #- Keep messages under 10K, use infrequently, do NOT use mail-lists or #- file/list-servers commands. #FROM: wwivnet #TO: internet #RECIPIENT: user@machine.site.domain #CONTACT: faq-request@9702 or 1@9702 #INSTR: convert to 'user#machine.site.domain@506' #- If 'user' begins with digits, begin address with a quote. #INSTR: WWCPgate; LOW TRAFFIC SITE, USE SPARINGLY.. Gateway is modem-based, #- they absorb cost of long distance connects to pick-up and deliver. #- Keep messages under 10K, use infrequently, do NOT use mail-lists or #- file/list-server commands. #FROM: X400 #TO: calvacom #RECIPIENT: JS10 (John Smith) #INSTR: send to 'S=JS10/A=ATLAS/P=CALVACOM/C=FR' -- _/ _ ! _ @ Milwaukee, WI - A Great Place On a Great Lake ! _! !! ! !_ ~~ @ ~ ~~ ! ! ! !! ! ! !~~__=||_~ ~~~ Computing Services Division - MAINFRAME CONSULTING ! ! ! _! ! ~~~ ~____/ ~~~ yanoff@csd4.csd.uwm.edu yanoff@point.cs.uwm.edu The Great IP Guide -=-=- The Research Internet (#15) -=-=- 19-July-1993 The count of countries which are IP-connected now stands at 60, an increase of 3 over the 57 listed in table#14 on 25-June-1993: FJ (Fiji) has been added to the list for Australasia LI (Liechtenstein) has been added to the list for Europe GL (Greenland) has been added to the list for North America Continent Countries <1>: # --------- -------------- - Africa TN, ZA 2 Antarctica AQ <2> 1 Asia HK, IL, IN, JP, KR, KW, MY, SG, TH, TR, TW 11 Australasia AU, FJ <3>, NZ 3 Europe AT, BE, BG, CH, CY, CZ, DE, DK, EE, ES, FI, FR, GR, HR, HU, IE, IS, IT, LI, LU, LV, NL, NO, PL, PT, RO, SE, SI, SK, SU, UA <4>, UK 32 North America CA, CR, GL <5>, MX, US 5 South America AR, BR, CL, EC, PR, VE 6 -- total= 60 =-=-= Notes =-=-= <1> IP connectivity to these 60 countries has been confirmed with ping plus telnet to port 25 (SMTP). <2> Some hosts listed in the GOV domain are physically located in AQ. <3> The SOA for FJ is physically located on the island of Fiji. <4> Some hosts listed in the UA domain, and physically located in the Ukrainian republic, are reachable from European IP networks. <5> Some hosts listed in the GOV domain are physically located in GL. =-=-= Anticipated Connectivity =-=-= The following country appears to be likely to connect soon: EG (Egypt) -- Donald C. Wells Associate Scientist dwells@nrao.edu National Radio Astronomy Observatory +1-804-296-0277 520 Edgemont Road Fax= +1-804-296-0278 Charlottesville, Virginia 22903-2475 USA 78:31.1W, 38:02.2N ======================================================================= Notes and tips on UUCP and Fast Modems. From Peter Wemm. Dialix. Perth >I am womdering if there is a definitive answer to the qquestion of >error checking modems, compression and uucp.? > Does one turn off compression/error checking when using uucp? > Does one turn off compression only when using uucp? > Does one turn them both off when using uucp. > Does it matter at all what they are set at.? We have personally found that the g(64,3) protocol is *really* lousy on long-distance lines. Since the round-trip-time is so long, the throughput with a 192 byte window sucks. Any increase in round-trip-time makes this worse.. correction/compression can add up to 100ms per trip or so, adding a 2/10 second delay for a round-trip. We *usually* find that the slower throughput is worse than the corresponding errors would have caused. However, as soon as you get a more advanced protocol g(64,7) or (g1024,7) you only benefit from correction/compression. the 'i' protocol *loves* it. Remember: error-correction runs at 120% of the line speed.. Why? Because it speaks syncronously over the line... ie: the start and stop bits of the bytes are stripped. So, with no correction, a 9600 bps line is capable of 960 bytes/sec (each character is 10 bits). Just by turning correction on, you *immediately* get 9600/8 = 1200 bytes/sec.. The only cost is a longer transmission delay. decent, smart compression can only make this better. V42bis will compress a packet, and then send the sortest of the compressed and uncompressed data. so, if you get 1200 bytes/sec, it should theoretically never get worse than that. However, the handshake-delays caused by the computers at each end are usually what slow down the throughput. That's why taylor-uucp's "i" protocol is so popular... it has practically no handshake delays. -- Peter Wemm <peter@DIALix.oz.au> - NIC Handle: PW65 - The keeper of "NN"