vinsci@nic.funet.fi (Leonard Norrgard) (01/11/91)
In article <kenk.6610@algedi.UUCP> kenk@algedi.UUCP (.) writes: >In article <VINSCI.91Jan7030316@nic.nic.funet.fi> vinsci@nic.funet.fi (Leonard Norrgard) writes: > >It is included in the file below, on nic.funet.fi: > >Directory: ~pub/ham/amiga/amiganos > >-rw-r--r-- 1 vinsci ftp 611874 Dec 8 20:51 amiganos-900418.zoo > I know of at least two AmigaNos versions. One from Louis Mamakos, and a later version based on it from G1YYH. The G1YYH version is V1.9 and is the most stable of the two. Which version is on nic.funet.fi? I couldn't find a version number of the Vn.n style, but the file version.c says it is 900418 (ie. 18th April 1990). I've included the Read-Me file (whenever you write these, please use a name like README instead, thanks) below; at the end it has an update to the older info at the beginning. The same directory has a network time protocol (ntp) archive also. -- Ken Koster (N7IPB) algedi!kenk@pilchuck.Data-IO.COM or 14146 73rd PL NE, #201 ...uunet!pilchuck!algedi!kenk Bothell, WA 98011 -- Leonard Read-Me follows: --------------- Copyright 1989, Louis A. Mamakos WA3YMH AmigaNOS notes and random comments. 15 September 1989 0. This is a preliminary release of the Amiga version of Phil Karn's KA9Q NOS software. It is a fairly straight port of the 890819 version of NOS to the Amiga. The normal mode of interaction is substantially the same as you'd see on a PC; there isn't any nifty multi-window environment available. The software was built using Lattice C 5.02, LMK, OML and BLINK. It was built on an Amiga 2000 with a 30MB disk; you probably can't build it as-is on a system with floppy disks as the combined size of the sources and object files are too large. This text attempts to describe the Amiga specific features of this port of NOS. It does not try to describe how NOS differs from the previous, released versions of NET. Note that complete documentaton in the form of source code is provided if you really want to figure out what it does. 1. You need to make a logical assignment of TCPIP: to some directory somewhere. The directory structure should look somethink like: spool (dir) mail (dir) louie.txt mqueue (dir) sequence.seq rqueue (dir) mail.log finger (dir) louie domain.txt ftpusers net-startup 2. TCPIP:net-startup is the file that contains the commands automatically run when you invoke the `net' program. For example, the one that I use for AX.25 operation is: ax25 mycall wa3ymh ax25 version 2 ip addr wa3ymh.ampr.org attach asy serial.device 0 ax25 ax 2000 256 9600 trace ax 311 hostname wa3ymh.ampr.org attach netrom netrom interface ax IPYMH 192 netrom user WA3YMH netrom nodetimer 1200 netrom obsotimer 3600 start ax25 domain suffix ampr.org route add default ax start finger start echo start discard start telnet start ftp start smtp start ttylink start netrom smtp timer 150 Note the paramters of the attach command; it is different that the one used for the IBM PC version. It is: attach asy dev unit mode name bufsiz mtu speed where asy: is always 'asy' for the serial network driver; dev: is usually 'serial.device' for the normal Amiga serial device driver. If you happen to have additional serial ports on your Amiga, you should list the name of its serial.device compatible driver here. unit: the unit number to be opened on the driver. Usually '0' for the case of the internal serial port. mode: is either 'slip' for serial line IP use; 'ax25' for KISS AX.25 use, or 'nrs' for the NET/ROM serial interface. name: is a symbolic name for the interface, something like 'sl0'. bufsiz: the amount of buffering that the device driver will do. The larger the smaller the chance you'll experience serial line overruns. The value of 8000 works great with 9600 baud SLIP doing FTPs to a hard disk. mtu: the Maximum Transmission Unit of the interface; packets larger than this are fragmented. speed: baud rate you'd like the interface to run at. '9600' works great. 3. The FTP server works; the only weirdness is that the FTP server will not create a file unless it is in the current "FTP server" directory for that session. So, the remote user using the Amiga's FTP server can do: cd directory/sub put file but cannot do: put directory/sub/file reading files is not a problem, just writing files that don't currently exist. 4. When exiting the NET program, by entering the 'exit' command, you must type an additional character to actually terminate the program. Its to satisfy the pending asynchronous read on the console. Hopefully, this will be fixed in a later version. 5. There is no SMTP user agent. I suppose that you could port BM, or just hack something up using AREXX. The SMTP server works just fine, though. 6. Remember that (just like the PC version of NOS), the domain.txt file has a significantly different format than the hosts.net file that the older KA9Q NET code used. Look at the contents of the supplied file for an example. The file now contains Domain Name server resource records in the normal zone file format. 7. Remember to create user mailboxes in the TCPIP:spool/mail directory, with the filename being the username with ".txt" appended to it. Thus, I have a mailbox "louie" on my system, and the file "louie.txt" in the specified directory. You might also create finger files for each of your users. Just to be different, these file *DO NOT* have the .txt extension on them. Oh well. updated on 15 February 1990 This version now corresponds to NOS verison 900214. It handles each session within its own window. To switch back to the command interpreter window, just type the escape character (control-]) or the `HELP' key on the keyboard. Note that only output to the current session is active at any time. << Insert documentation on mbox code here. 'till then, you'll just have to read the source code >> Enjoy the code. If you make any modifications to this code and redistribute it to anyone please note the fact that you made changes in any printed or written documentation, and in the startup message that the NET program displays. Please do not make any changes and pass it off as the original distribution. Please send bug fixes to me via Internet mail to: <louie@TRANTOR.UMD.EDU>.