     

		    Atari ST SLIP FAQ 

	  or  How to connect your Atari to a network

	  or  The Atari Guide to Network Connectivity ;)


		    version 7 June 1995        


	Well since the last update of this document, a lot has gone on.  We
have seen improvements in virtually every area of networking for the Atari
68k based line of home computers.  We have seen several new local networking
programs, an adaptation on the ethernet card software as well as a boom in
the options for connecting your machine to the Internet.  I have tried in
this document to at least note all the different areas, however there are a
large number of them that I have absolutely no experience with.  So please if
you notice something that is incorrect or that you could contribute, write me.
Any help at all is definately welcome.

     my address is dackerma@magnus.acs.ohio-state.edu
	or		 baldrick@terminator.rs.itd.umich.edu


	(last minute note:  I had originally intended to get this out the
door several weeks ago.  However life being life, it didn't get done.
I am expecting several additions from several people so hopefully there will
be even more info soon.  Also you may notice that some areas are out of date.
Sorry I just want to get this out now and I'll worry about the catch up later.
So if you have an application that isn't mentioned.  I'm sorry about it's
exclusion.  Please forgive me.	I will make up for it latter.  - Dan )

	Also note.  I am looking for interested people to help me organize
future versions of this document.  It's just getting to big for one person.









				INDEX



 I		General Questions & Answers

 II		Software

		a. Local networking
		b. Internet networking
		c. Radio networking

 III		Local Networking

 IV		MiNT NET 

		a. Overview of MiNT Net
		b. Configuring MiNT Net
		c. MiNT Net Q&A

 V		KA9Q NOS

		a. Overview of Ka9Q NOS
		b. Utilities for Ka9Q NOS
		c. More info about Ka9q NOS

 VI		Sample Config for STICP

 VII		LINUX

 VIII		WWW

		a.  Overview of WWW support
		b.  ATARI World Wide Web Browsers
		c.  ATARI World Wide Web Pages (URLs)

 IX		Ethernet Adaptor for the Atari

 X		UUCP on the Atari Q&A

 XI		More Info available on the Internet

 XII		Short Glossary of Terms

 XIII		Index of Files in the Network area of a.a.u.e.

 XIV		Partial list of Software Authors E-mail addresses

 XV		Contributors

 Section I:  General Questions & Answers


     What does SLIP stand for and what does it do?


     SLIP is an acronym for Serial Line Internet Protocol,  it is the serial
line (modem) version of IP (Internet Protocol).   A large portion of the
sites on the netthat offer a SLIP connection are using packages based on KA9Q.
Many universities are going to Client Server systems to lessen the load on
their computing resources,  SLIP is one of the options that they are taking.
With a SLIP connection, the machine in front of you is virtually on the net.
All your commands are preformed locally (i.e..	FTP, News reading, Mail
Reading, etc.), as you no longer need a log in account to process your
terminal commands into IP.

So when you connect to your favorite archive, the file comes directly to your
machine.


     Could you explain Client Server in layman's terms?


Client/Server has nothing to do with data, hardware, or software. It is
simply a separation of something wanting something and getting it from
something else.

I am hungry so I go to a restaurant. I am the client. I ask my
waiter/waitress to bring me a meal. He/she is the server. This is the
client/server model. No data, no hardware, no operating system!

I am hungry again so I go to my kitchen. I make myself a meal and eat
it. There is no concept of client/server here. This is the traditional
model.



     Does my remote host server have to have SLIP drivers, for me

	  to use SLIP on my machine?


Yes.  Without cooperation on the other end SLIP software on your machine will
do you no good.  Contact your system administrator as many university systems
already offer some form of SLIP connection.  Preferences vary from site to
site on what they will have installed on their end.


      What is TCP/IP? 


     TCP/IP (Transmission Control Protocol/Internet Protocol)  is the common
name for a family of over 100 data-communications  protocols used to organize
computers and data-communications equipment into computer networks.  TCP/IP
was developed to interconnect hosts on ARPANET, PRNET (packet radio), and
SATNET (packet satellite).  All three of these networks have since been
retired; but TCP/IP lives on.  It is currently used on a large international
network of networks called the Internet, whose members include universities,
other research institutions, government facilities, and many corporations.
TCP/IP is also sometimes used for other networks, particularly local area
networks that tie together numerous different kinds of computers or tie
together engineering workstations.   What are the other well-known standard
protocols in the TCP/IP family?  Other than TCP and IP, the three main
protocols in the TCP/IP suite are the Simple Mail Transfer Protocol (SMTP),
the File Transfer Protocol (FTP), and the TELNET Protocol.  There  are many 
other protocols in use on the Internet.  The Internet Activities Board (IAB)
regularly publishes an RFC that  describes the state of standardization of
the various Internet  protocols.  This document is the best guide to the
current status of Internet protocols and their recommended usage.  
(Source FYI4.TXT available from IRG)  


     What is UUCP?    

Newsgroups: comp.sys.atari.st

Path: magnus.acs.ohio-state.edu!math.ohio-state.edu!howland.reston.ans.net!
pipex!lyra.csx.cam.ac.uk!doc.ic.ac.uk!cc.ic.ac.uk!news.cc.ic.ac.uk!r.evans

From: r.evans@ic.ac.uk (Robert Evans)
Subject: Re: WinX with MultiTOS ?

>In article <2qu07b$4dd@holmenkollen.ifi.uio.no> hallvart@ifi.uio.no
>(Hallvard Tangers) writes: 
>>> I don't understand what uucp is.  
>  
>> I *think* it stands for: UNIX to UNIX Communications Protocol, whatever
>>that means.

It is a venerable (read: old) and still quite widely used method for
transferring data between UNIX (surprise!) machines. It is usually used
over dial-up lines. Suppose remote machine 'lonely' has no network
connection, but has a modem and dial-up access. Also there's a machine
called 'cables' that has network connections coming out of it's ears.
'Lonely' could use 'cables' to send and receive email by using uucp.

For example, if you wanted to copy the file "mint.zoo" (what else:-)
from lonely to cables. On lonely you'd type:

prompt% uucp mint.zoo cables\!~/mint.zoo

Periodically, a program runs on cables called 'uucico'. What this
does is see what files have to be copied, then dials up the remote
machine, logs in as "uucp" and sends them. You'd end up with a file
called mint.zoo in the directory /usr/spool/uucppublic on cables.

Uucp's main advantage is that you don't pay for a permanent connection,
files are only transferred when uucico is called.

Uucp used to be used for virtually all mail transfers, using what are
called "bang paths" - some old-timers (:-) still have them in their
sigs. To send email, you'd have to specify an exact route from your
machine to the destination machine, separated by bangs (!'s). To get
an idea of what a bang path sort-of looked like, look at the Path:
header of any news article.

Cheers,
Rob


     My organization doesn't give me access to the newsgroups.	What can I do?

From: bmiller@magnus.acs.ohio-state.EDU (Bill Miller)
Newsgroups: acs.homenet.tech
Subject: FNEWS -> Re: Reading News without an account.

>There are several NNTP servers out on the Internet that are publicly
>accessible. Most of them are read-only, allowing clients to read news
>articles, but not to post them. A reasonable attitude, and a
>reasonable compromise - to allow posting access in good faith, most
>sites would have to implement some kind of authentication, and the
>effort required might not balance out to benefit to the people who are
>actually paying for the site.
>
>Scott Yanoff's excellent Guide to Internet Services, posted regularly
>to alt.internet.services and news.answers, lists some of these
>publicly accessible NNTP servers.
>
><chuckle> Of course, if you don't have access to news, it's hard to
>get said Guide.
>
>Thus, here's a list of NNTP servers that was posted to
>alt.internet.services a month or so ago. I've removed all the non-US
>sites (it's not nice to abuse trans-oceanic links). All of them are at
>port 119.
>
>cc.usu.edu
>europa.eng.gtefsd.com
>fconvx.ncifcrf.gov
>gaia.ucs.orst.edu
>hermes.chpc.utexas.edu
>netnews.cc.lehigh.edu
>news.yale.edu
>news.ysu.edu
>newshub.nosc.mil
>newsserver.jvnc.net
>sol.ctr.columbia.edu
>vax1.mankato.msus.edu
>
>To access any of these, you'll need a computer that has access to
>telnet outside the university (this precludes most, if not all, of the
>public labs). And you'll need an NNTP client. For the Mac, there's
>Internews, NewsWatcher, and Nuntius. For the PC, there's Trumpet and
>WinQVT/Net.  VMS: NEWSREADER, FNEWS, VNEWS, and others. Unix: A whole
>bunch. (rn, trn, tin). Amiga.. <shrug>. Where they are... use Gopher
>and Archie to find 'em. Consider it an exercise for the reader. :)
>
>As always, please be considerate of these other sites. They've kindly
>offered their resources to the Internet at large, don't abuse them
>with large amounts of traffic, or by trying to hack the sites.
>

     There is source code available from Gard Eggesboe Abrahamsen
(ga@samson.mrih.no), for an offline NNTP Newsreader call Catchup.  It is
postcardware and in C.	It looks to be fairly straight forward code.  If
you would like information about it please write him, if you can not
contact him I have a copy that he posted to comp.sys.atari.st.
(D.Ackerman)


      I'm not on an university. How can I connect to the internet?

     Contact your local university or yellow pages.  Many metropolitan 
areas in the U.S. and Europe have commercial Internet sites.  You can also
get access to Internet through some on-line services such as Delphi.  Also
if you have a friend or coworker who has access to Usenet news have them
send a note to the newsgroup alt.internet.access.wanted and/or
alt.services. 


     Where do I find out more info on the Internet without buying a large 
number of books?

     Well if you already have access to FTP you are on your way.  Almost 
every major book that has appeared about the Internet, has appeared on the 
Internet.  Also if the book is not available in digital format, usually 
the resources they used for the book are available on the net.	For the 
locations of some of these resources please look below in 'VI  More Info
available on the Internet' and if you need help with FTP, read the Atari
FTP List (seperate document).  It contains an excellent introduction to
the process of using FTP sites.

     If you do not have access to the newsgroups a user guide to the 
Internet Resource Guide is available by email.	Write to 
mailserv@ds.internic.net  include HELP in the message body.

	I hear that Xwindows is available for my atari?

	True.  There are two options 1. X11r5 for Mint and 2. X11r6 for Linux.
While there is some "Network" software available for Xwindows, like Chimera,
it in and of itself is not a networking option. In other words if you went
the Linux route you would get your sockets from Linux and if you went the
Mint route you would have to get your sockets from Mint Net.  Therefore,
I plan to only cover Xwindows, when they pertain to one of these options
and not give it an area of it's own right.

II		Software

   Intro:  This list of software only lists general programs.  In other words 
expect to see Ka9QNOS listed but not Oasis, as Oasis still requires Ka9QNOS 
to run.  In the same idea, you will find MiNT Net, but not all of it's 
associated utilities such as telenet.  I have tried to break this section up 
into general topics that make it easy to find what you might be interested 
in.	

II Software
	     a. Local networking

	Intro:	If you have MiNT Net, X11 or Linux installed these all 
havetools to network two or more machines together.  More information on 
these options can be found in the appropriate sections and will not be listed 
here.  While the above options provide the user with the most power, they are 
often overkill for the average user.  These following files are for the user 
who has a few machines at their site that they want to network, without 
spending hours installing the software.  Most of these tools can be installed 
and configured within a few minutes and work fine on machines with any amount 
of memory and with or without hard disk drive.

	However with all forms of Networking you do need some hardware.  The 
following all need some sort of cable.	Some will require a null modem cable 
and some midi cables.  These are all available in most cities at the local 
computer store or music store.

	All of the following files can be found on atari.archive.umich.edu, 
under atari/Network, for the exact location you can check with the index file 
located near the end of this document in section XI.

duet_100.lzh	This is a networking program that uses the serial, modem
		or LAN ports to network two ataris.
 
duet.eng	English translation of Duet Docs by Leslie Hartmier

ghostlnk.zip	Filetransfer between any Atari (ST(E)/TT/Falcon) and a PC.
		All the drives of the PC can be accessed on the Atari by a
		GEM-diskicon.

lit_net.lzh	Little Net - Midi Net .ACC nice and easy way to access drives 
		on another machine. Does not like Falcon resolution
		switching.  This is an ancestor of medium Net.

mdneteng.zip	English resource and description text for Medium Net
		(med_net.lzh)

med_net.lzh	Medium Net - Update to Little Net.  Now you can access
		multiple drives.

midi_com.lzh	Demo of German MIDI networking software

midinet.arc	Midi Networking package

miknet13.arj	Sharware midi-network (DOS end supposedly exists)

mx2doc.lzh	Documentation for mx2net

mx2net20.lzh	Networking system including modula2 source.  Allows cross
		net file execution.  This system is getting extremely old
		and is almost, if not more complex as MiNT Net, so if you
		want something quick I can not recommend this.

II Software
	     b. Internet networking

Ka9q (old version):  Available at numerous sites, although several sites 
     have been	reported to have a corrupt version.  A good copy is
     located at ftp.tu-clausthal.de under  pub/atari/telecomm/tcpip. 

KA9Q-Nos: SLIP, PPP & NNTP software.  Currently supported by David Nash.
     Mail  reader  available.  Located at ftp.tu-clausthal.de under
     pub/atari/telecomm/tcpip/ka9q  &  ftp.demon.co.uk under  
     pub/atari/ka9q (this site is maintained by the author of the
     atari version). Also can be found at atari.archive.umich.edu under
     'atari/Network/Ka9q/Nos'

MiNT-Net  3.0:	Port of Berkley Unix Sockets,  still in an early stage.  
     Looks promising.  Still under development.  Requires MiNT to run. 
     Probably still available at some sites.  Do not use this version
     use 7.

MiNT-Net  4.0:	Port of Berkley Unix Sockets,  major update over 3.  
     Still under development.  Requires MiNT to run.  Now contains TCP 
     support.  Note: MiNT NET 4 and 3 both require you to recompile
     the MiNT kernel. Available at most Atari FTP sites. and
     atari.archive.umich.edu in atari/Mint/Net 

MiNT-Net 7:  Current version of MiNT-NET.  Use this version, do not
attempt to use older versions.	Requires MiNT to run.  MiNT 1.12 is
available on a.a.u.e. and many other archives.	

pe1chl: A version of Ka9q, available for both the Atari and MSDOS. 
     Currently supported. Available ftp.tu-clausthal.de under
     pub/atari/telecomm/tcpip/pe1chl 

STICP:	 version number 'v871225.33.PE1CHL.900813'. Copyrighted 1988 by
     Phil Karn.  Available at ftp.tu-clausthal.de (fsp port '21')
     under /pub/atari/telecomm/tcpip/sticp.lzh	Wolfgang Ley has
     also made a sample config available here. 

TUW-TCP: Standard package designed for an Ethernet card, but sources  and 
      instructions are available for making your own driver.  Runs as an
     .ACC or .PRG.  Does not like MultiTOS.  Located at
     ftp.tu-clausthal.de under 'pub/atari/telecomm/tcpip/tuw-tcp' or
	atari.archive.umich.edu under 'atari/Network/EtherNet' 

UUCP Software (This list belongs here, but needs to be fleshed out)

     The following packages can all be found at ftp.tu-clausthal.de under 
	pub\atari\telecom\uucp\ and atari.archive.umich.edu under 
	'atari/Network/Uucp'

     Hermes 1.14
     Mercury
     Upoint-Light (There is a new version available as of this writing, 
			however I haven't seen it yet)

     The only one of these packages that I have any experience at all with 
is Upoint Light.  It is nicely done and all works inside of a professional 
GEM interface.	I do not have access to using UUCP at my university, so 
please if you use UUCP help flesh this section out.

II Software
	     c. Radio networking

	There are various tools and utilities to use your atari with a ham 
radio setup.  However I know just slightly more than nothing about this area. 
 You can use the original version of Ka9q for this as well as other newer 
tools.	But as I said, on this topic I have had no personal experience or 
contibutions for this document.  The best archive for this type of tool that 
I know of is at ftp.tu-clausthal.de.  If you use your Atari for this type of 
setup please help us out here.

III. Local Networking

	Intro:	As discussed earlier in the software section, there are 
numerous ways to locally network two ataris, some simple and some complex.I 
will try to discuss some of the options here, although I'm certain I will not 
be able to think of them all.

	Probably the simplest is to get a null modem connector or cable. 
 These are available at most computer stores and a small cost.	Once you get 
this cable connect one end to the serial (modem) port of both machines.  You 
now need to run a terminal program on each end, make certain to set the speed 
as high as you can.  If you want to type between the machines you will want 
to turn half duplex on as well.  You can now transfer files from machine to 
machine like you would if connected to a remote service.

	Is this real networking?  Well that's a judgement call, some would 
say no.  However for some circumstances, it is the ideal solution.  It is low 
cost and performs all necessary taks without much hassle.  However it's 
limitations are numerous, both machines have to be running a term program of 
some sort.  And unless your running a multitasking system, this limits the 
amount of time you will want to have the setup going.

	So how do we improve the situation without going overboard?  Well 
continuing with the null modem cable we could get some networking software. 
Probably the best next solution would be something along the lines of Duet. 
Duet will allow us to run a network over the null modem cable.	The 
advantage of a package like this is that while both ends still need to be 
running the software, it will often run in the background.  This frees the 
machine up to do other work, like text processing.  Another advantage is they 
often will allow you to get whole directories of files like they were on your 
own machine, as opposed to transfering only one file at a time.

	But we still have a limitation here, what if we want to access a hard 
drive on another atari in the room and also use a modem to call out?Then we 
have to disconnect the null modem cable and install the normal modem.  This 
gets to be a hassle, if we want to run our network most of the time.  So we 
need new hardware.

	For most atari owners the next step will be midi cables.  These again 
are not too expensive, if you don't want one that's 50' long (approx. 16.6 
meters).  Midi cabling networking is a great expansion for the atari.  Not 
only will this expand the number of programs use can use for normal 
networking, it also allow you to run a fairly respectable number of networked 
games.	Such as MidiMaze, which allows up to 16 ataris to be networked 
together in play.  The connection is easy, simply take 1 midi cable for each 
atari you want to network.  Connect the midi out port on one machine to the 
midi in port on the next, going around til you connect the last machine back 
to the first.  However, I do not know of any easy way to run a normal network 
over a midi ring of more than two machines.  By this I mean that if you just 
want to access the hard drive on your other machine, then without more work 
you are limited to just two machines.  But a midi network does allow both 
users to use modems while still being in effect connected to each other. 

	Before I stated that for most atari users the midi cables would be 
the next step.	However it's not necessarily the only other option, if you 
happen to be a lucky atari owner then the two machines you want network will 
both have LAN ports.  These are small round local talk compatible ports, they 
are found at least on MegaSTe's, TT's and Falcon's.  I am not certain about 
the clones.  If you have this ports, you will need to get a slightly more 
expensive setup of hardware.  You can find this hardware at many computer 
stores, almost certainly at any dealing with Macintosh computers.  The 
cheapest option (in the US) are PhoneNet adaptors, this is because the cables 
are simple phone cord, which can be purchased in huge lengths for small 
amounts of money.  

	Your options for easy to use software for this, is definately smaller 
than midi ports.  But there are still packages available.  This is a definate 
boost in user ability, since now not only can you leave your modem connection 
in place. You can also leave your midi keyboard in place.

	At this point we leave the range of cheap or easy options.  There are 
still many available.  I will discuss a few in general, but if you want more 
information on any of them you will have to refer to their own specific 
sections (i.e. Ethernet cards in IX Ethernet adaptor for the Atari).

	Networking is available with NFS through either MintNet or Linux. 
 I'm not certain about the options for connectors for either.  You would be 
best served if you are interested in this route to send a message to one of 
the mailing lists or newsgroups listed in their specific setions.

	There are(were) several commercial options as well, such as PAM's Net 
or PowerNet.  However I know litle about these options.  For the best 
information about these options contact the manufacturers or a good atari 
dealer.


IV.  MiNT NET

	IV MiNT NET a. Overview of MiNT Net

	What is Mint NET?  Basically MiNT NET is an extension to MiNT, which 
allows programs to use the standard BSD socket calls.  This allows the quick 
porting of BSD unix networking utilities to the Atari. 

	MiNT NET and MiNT also allow you to install X11.  With X11 installed 
you also will have access to Chimera, a graphical world wide web browser, and 
other net utilities and programs.  

	MiNT is also the Multitasking kernal for MultiTOS.  So you can also 
read MultiTOS, where ever you see MiNT in this section on the grounds that 
you have the updated version of MiNT 1.12 installed instead of the version 
1.08 that shipped with your version of MultiTOS.

	Requirements for MiNT Net:

	System.  Any atari 68k based computer
		(ST(e)/MegaST(e)/TT/Falcon/Pandora)

	Memory.  More than 1 Megabyte, preferably at least 4.

	Hard disk drive.  It might be posible to get MiNT Net to run
		off of a floppy drive.	But I definately would not recommend
		trying it unless you are really sadistic.  The number and
		size files you need will make a disk drive virutally useless.
	
	MiNT installed.  At least version 1.12 for good results.

	Minix file system.  This is and is not required.  For consistent
		results it is definately recommended.  Some tools will not
		run at all on the normal TOS file system.  However many will
		indeed run without a Minix partition installed.  I believe
		though that the  Minix XFS will still be required.  I myself
		ran this way for several months before upgrading my hard
		drive.	However remember, most programmers are assuming
		that you have long filenames on your system and all the other
		nicessities that come with the Minix FS such as symbolic links.
		So if you go this route remember you are on your own path,
		and don't  complain to the world that the tools don't work.
		In fact I would not suggest this route at all.	I merely
		mention it as it is mentioned fairly often.

	A good shell.  Such as Tcsh or Ksh.  I don't recommend using too
		small of a shell as it might be missing integral parts.

	IV MiNT NET b. Configuring MiNT Net

Date: Thu, 4 May 95 00:32 BST-1
From: Roland Givan <rgivan@cix.compulink.co.uk>
To: baldrick@terminator.rs.itd.umich.edu
Subject: TCP/IP faq

Re: Message 15502 in comp.sys.atari.st

Hi

Seeing that you are interested in sorting out the TCP/IP faq - I thought
I'd send you my *very* rough guide to setting up MiNT-Net 0.7 which I did
to allow me to network my TT running MiNT and my PC running Linux. Using
this I can run the MiNT-X X11R5 server on the TT, and start X clients up
on the PC. :-)

Roland.

@CiX

HOWTO set up the basics of MiNT-Net

*very* rough guide v0.1a

This is hacked together from emails I have sent/received - and also the notes
I've made whilst installing MiNT-Net 0.7

I had the honour of 'writing' the very first MiNT-Net FAQ. However
I'm not sure why Kay still includes it as it is badly out of date, and anyway
when I wrote it I had had almost zero success with MiNT-Net!

This one decribes the most basic setup. Its *not* enough to connect your Atari
to the 'net, but *is* enough to run X-windows and network to another Atari
(or in my case a PC running Linux), and allow various basic commands to work:

 ping
 rlogin
 etc

It also allows me to run X client programs on my PC, whilst using the Atari
as the X server (so that the input/output is done at the Atari end) and visa
versa.

MiNT-NFS works pretty well over the top of all this also (though I've only
checked it on MiNT-Net 0.6 so far).

Things you need.

A working MiNT setup with a MINIXFS partition and a shell and shell utitities
(like ksh or tcsh). This in itself takes time to set up - but honestly
MiNT-Net is a waste of time unless you can get this far.

The MiNT-Net 0.7 .gz file and tools to unpack it (gzip and tar).

Make sure everything is run off the u: drive. This gives a universal Unix
like structure with one central root. Normally under u: only the physical
partitions appear (and a load of system directories) but you can set up
extra links in the mint.cnf:

sln d:\etc u:\etc
sln d:\bin u:\bin
sln d:\usr u:\usr
sln d:\user u:\user
sln d:\tmp u:\tmp

In this case my drive d: is my MINIXFS partition.

Unpack the MiNT-Net archive onto d: somewhere. I did:

gzip -d <name>.gz

mv <output> mn07.tar

tar xvf mn07.tar

I think it is better if both gzip and tar themselves are on a MINIXFS
partition - as this seems to preserve long filenames/case better.

Assuming net-070 is the 'root' of the unpacked files:

copy everything in net-070/etc to /etc
copy all binaries in net-070/tool to /etc

In the above 2, its very important that case is preserved - and that execute
permisions are on the the binary files. 

copy net-070/net/sockdev.xdd to c:\multitos
copy net-070/net/drivers/slip.xif to c:\multitos

Then reboot - and run the the 'connect' script. This should startup a slip
connection to whatever is connected to serial2.

As for the config files in /etc - this is what I have set up. Note all IP
addresses are fictional as my setup is not connected to the 'net.

HOSTNAME:
tt

HOSTS:
#
# /etc/hosts -- Host database for Mint-Net (w) 1994, Kay Roemer.
#
# The form for each entry is:
# <internet address> <official hostname> <aliases>
#
127.0.0.1 localhost loopback
100.0.0.1 tt
100.0.0.2 stm
100.0.0.3 pc

RESOLVE.CONF:
domain rack.co.uk
nameserver 127.0.0.1


CONNECT shell script:
u:/etc/ifconfig lo0 addr 127.0.0.1 up
u:/etc/slattach -p cslip -s 19200 -t /dev/modem2 -r 100.0.0.3 -l 100.0.0.1
mtu 2000 &
u:/etc/route


CONNECT is one I've written. It sets up a hard connection between 100.0.0.1 
and 100.0.0.3 via the serial2 port. I explicitly set the 'mtu' and 'cslip' to 
make sure they are the same as the PC end. The '-s 19200' sets the serial 
speed for 19200. With HSMODM you can go all the way up to '-s 115200' if your 
serial port and the one at the other end can take it.

Anyway thats about it. This is by no means a complete or even nearly 100%
correct way of doing things - but I hope it might give people a few pointers.

Roland Givan 20/3/95
revised 3/5/95
<end> 
	

IV MiNT NET c. MiNT Net Q&A

	Intro:	This section is in someways very out of date.  However much 
of the information is still useful in problem solving.	So if you see 
references to out of date versions of MiNT Net or MiNT, don't be surprised.


> My provider assigns dynamic IP adresses. ie. I get a different address
>  every time I call.  How can I get MiNT NET to work with this?

	Use DIP (dialup internet protocol).  It will accept both static and 
dynamic ip adressing.  The following is an example dip script for dynamic 
adressing it is from DuFTP.You will need to edit the phone number, the sites, 
your login name and password and the mtu.

#
# Annex terminal login script.
#
# Author:   Fred N. van Kempen, <waltje@uWalt.NL.Mugnet.ORG>
# Modified:    Craig Graham, <craig.graham@newcastle.ac.uk>
#

main:
  print DIP Script for Newcastle University.
  print (w)Craig Graham,30/1/95.

# First of all, set up our name for this connection.
# I am called "falcon.newcastle.ac.uk"
  get $local falcon.newcastle.ac.uk

# Next, set up the other side's name and address.
# My dialin machine is called 'knott.newcastle.ac.uk' (== 128.240.2.11)
  get $remote knott

# Set netmask on sl0 to 255.255.255.0
  netmask 255.255.255.0

# Set the desired serial port and speed.
#  I've got a real slow modem :(
  port ttyb
  speed 2400

# Reset the modem and terminal line.
# This seems to cause trouble for some people!
  reset

# Prepare for dialing.
  send ATQ0V1E1X4\r
  wait OK 2
  if $errlvl != 0 goto modem_trouble
  print Dialing...
  dial 2226455
  if $errlvl != 0 goto modem_trouble
  wait CONNECT 30
  if $errlvl != 0 goto no_connect
  print ...connected.

# We are connected.  Login to the system.
login:
  sleep 2
  wait knott: 20
  print Requesting a CSLIP connection...
  send slip\n
  wait Username: 20
  if $errlvl != 0 goto login_error
#replace myname with your name here
  send myname\n
  wait Password: 20
  if $errlvl != 0 goto password_error
#replace mypassword with your password here
  send mypassword\n
loggedin:

# Set the remote IP address (this may have already been done,
#  but just to be sure). replace this with the IP address of your
#  annex.
  get $rmtip 128.240.2.11

# Get the allocated local IP address from the Annex.
  wait Your 20
  wait is 15
  get $locip remote

  if $errlvl != 0 goto prompt_error

# Set up the SLIP operating parameters.
  get $mtu 296

# Ensure "route add -net default knott.newcastle.ac.uk" will be done
  default

# Say hello and switch to SLIP mode.
done:
  print CONNECTED $locip ---> $rmtip
  mode CSLIP
  goto exit

prompt_error:
  print TIME-OUT waiting for SLIPlogin to fire up...
  goto error

login_trouble:
  print Trouble waiting for the Login: prompt...
  goto error

password:error:
  print Trouble waiting for the Password: prompt...
  goto error

no_connect:
  print Cann't connect to remote host...
  goto error

modem_trouble:
  print Trouble ocurred with the modem...
error:
  print CONNECT FAILED to $remote
  quit

exit:
  exit

> Are there any GEM MiNT NET applications?

	Yes.  1.  Well hopefully there will be more soon.  It is DuFTP.  It 
is a very niceGEM interface FTP client.  It is somewhat similar to Fetch on 
the Macintosh.	(Note:I only said somewhat)  It allows you to save bookmarks 
to make ftping to your favorite archives merely a few mouse clicks away.  It 
looks very promising for what the future might hold.  Craig Graham is the 
author and he has also made all the source code available on the net.  (ed. 
note.  expect more information on this package in a future update)  

> MiNT-Net looks great but how is it supposed to be used? Does MintNet 
> actually provide a link between several Ataris? If so does use the
> serial port or Midi port? 


As of version 0.30 it does support linking Ataris with Ataris/Unix 
Boxes/whatever stuff running IP software. 

For now SLIP (IP over serial lines) and PLIP (IP over parallel lines) is 
supported. SLIP is compatible with (hopefully) all Unix SLIP implementations. 
PLIP is nonstandard, but much faster (> 15 kB/sec). 


> I realize that mint 1.10 needs to be patched to work - but what about
> 1.08? I've tried MiNT 1.08 and I get the 'non patched MiNT 1.10' error
> message. 


Don't worry about the 1.10 in the message. It just means, that MintNet will
not run with your version of Mint. 


> Finally I notice there is a fair bit of other stuff in the same 
> directory as net-030-tgz: 
> Mint/Network/ 
>  inetd-01.tgz 45 Pl1 of Internet Super Server.  Needs net-030.tgz 
>  net-030.tgz 321 Ver0.30 of MintNet, a networking extension w/BSD socket 
>  portlib-02.tgz 13 Pl2 of library software for porting unix stuff 
>  rpc-01.tgz 450 Pl1 of Sun RPC for Mint + MintNet 
>  term-1.08.tgz 244 A port of term for MiNT+net  
>  tftp-00.tgz 37 Pl0 of trivial ftp for Mint+MintNet 
>  tftpd-00.tgz 27 Pl0 of the tftp server program for MiNT+MiNTNet 
>  udpprobe.tgz 23 Prg for testing connectivity in M+MN.  Similar to ping 
> 
> Is any of this other stuff necessary to start with, and does any 
> of it supersede the stuff in net-util.tgz? 


Some files (those with patchlevel > 0) supersede files in net-util.tgz. You 
should get at least inetd and udpprobe to have some stuff to test if MintNet 
is working. 

If you think you have installed MintNet correctly, try the following: 

% inetd % udpprobe localhost daytime "i" 

The last command should give you the current time and date of your machine. 


> I haven't been able to build syslog from the init1.1 package - 
> but MiNT-Net seems to work without it. 


Mint-Net itself doesn't need it, only inetd, tftp and the other ported BSD
software. 


> I'm having a bit of trouble with TFTP. After a lot of fiddling I 
> managed to GET a file between 2 directories. (I'm playing around with 
> TFTPing between directories on 1 machine so I don't have to keep turning 
> on the spare ST ;-) 
> 
> I can't get PUT to work however. I've tried dozens of combinations of: 
> 
> put <filename> <filename> 
> 
> both with and without "localhost:" infront, but no luck. I get "Error X: 
> File not found" or similar. 
> 
> BTW I'm doing all of this between directories on the U drive. The 
> destination directory is a MINIX-FS one, while the source is /bin where 
> TFTP lives. Any ideas? 


First, tftp allows you only to `put' files which already EXIST at the
destination machine and are WRITEABLE by the world. Eg. 

put some.file.tar.z remote:/tmp/xyz.tar.z 

will only work if the file 

remote:/tmp/xyz.tar.z 

already exists and looks like 

-??????rw? 

This stupid behavior is because of missing authentification methods in the
tftp protocol, ie the tftp daemon doesn't know who is putting the file. 

> 
> Also I don't understand the entry in inetd.con: 
> 
> tftp dgram udp wait root /usr/etc/tftpd tftpd 
>					  ^^^^^ 

This is the first argument to /usr/ets/tftpd (The one you can access as 
argv[0] -- the name of the executing program -- in main() if you are familiar 
with C). You must always give it. You can give tftpd further arguments by 
writing them after the `tftpd'. If you do so, access is restricted to the 
directories they specify. Eg. 

tftp dgram udp wait root /usr/etc/tftpd tftpd /tmp/ 

restricts tftp `put' to the /tmp/ directory. 


> Is 'proper' FTP going to be available at some time? TFTP is fine - but 
> there is very little I can connect to with it ;-) 


This requires to implement the TCP protocol in MintNet. I'm working on it. 
But I guess in some days Ulrich Kuehn's NFS will be available. It is quite 
stable now, and will give you lots of fun :) 


> Also although:
> 
> udpprobe localhost .... 
> 
> works. Trying: 
> 
> udpprobe <hostname> ..... 


For the latter to work you have to do several things: 

Write your hosts's name into /etc/hostname (suppose `larry'). 

Choose an IP address for it (suppose 100.0.0.1) 

Add the line 100.0.0.1 larry to /etc/hosts. 

Add the line nameserver 127.0.0.1 to /etc/resolv.conf if it doesn't exist. 

Do an ifconfig lo0 addr 100.0.0.1 route add 100.0.0.0 lo0 at startup. 

Then you will be able to access your local machine both as `larry' and
 `localhost'. 

But when doing the above with MintNet 0.30 you won't be able to access your
machine as `localhost` any longer. This is fixed in 0.31. 

As a temporary solution you could make your hosts name an alias for
`localhost' by adding `larry' to the 127.0.0.1 line in /etc/hosts: 

127.0.0.1 localhost loopback larry 


> Can't seem to format the manual pages. nroff -man <filename> doesn't 
> seem to work. 


You need groff and the tmac.doc macro package to format them: 

groff -mdoc -Tascii filename > filename.formatted 

should work. 


> Any idea where I can ftp groff from? 


try a.a.u.e:/atari/Mint/Utilities/groff* 


> I'm not too up on internet addressing but the setting up of localhost 
> confused me slightly: 
> 
> /etc/ifconfig lo0 addr 127.0.0.1 up 
> /etc/route add 127.0.0.0 lo0 
> 
> Is is right that in the first line the address is 127.0.0.1 and in the 
> second 127.0.0.0? 

As you probably already know an Internet address consists of a host part and 
a Network part. For the class A address 127.0.0.1 127 is the network part and 
0.0.1 is the host part. The host address with the host part all zero is the 
address of the Network. 

So the second command adds a route for the Network 127, that is for all hosts 
in the Network 127. This is necessary so that broadcasts (an IP address with 
the host part all 1's, ie 127.255.255.255 for the loopback net). will get 
routed to the localhost interface too. 

Adding a route to the Network (ie with the host part of the IP address all 
zero) is indeed necessary for all non point-to-point interfaces that support 
broadcasts. 

So the above commands are perfectly right.  


> I seem to be able to use either address as a loopback address. 


That is because 127.0.0.0 is threatet as a broadcast address too. You 
probably should be able to use 127.x.y.z where x, y, z are numbers in between 
1 and 254 if you issue the above commands. 

(Info on FSP client)

From: tj@aiscube.AIS-dortmund.de (Theo Janssen)
Newsgroups: comp.sys.atari.st.tech
Subject: FSP (WAS: Mosaic/WWW ??)
Date: 21 Apr 1994 09:51:19 GMT
Summary: a substitute for ftp
Hello "MiNT-netters"

Obviously, there has been some porting of Net-Software, now as MiNT-Net
becomes more and more popular. For those, who are interested, I've
compiled the fspclient source with no bigger problems.	FSP is an
"UDP-based FTP", and is a lot like his TCP-based brother.  There are  a
couple of sites, which support FSP (i.e. ftp.germany.eu.net,
src.doc.ic.ac.uk, tu-clausthal, wuarchive and a lot more). I already 
transferred a lot of files via SLIP using this tool and it worked fine.

I'm also working on a fspd. As soon as i have a stable (right word ?) version,
I'll let you know and send it to the Net.

You now can get the package using ftp or E-Mail or fsp (PORT 2001) :-) from 
"ftp.germany.eu.net" (pub/comp/atari-st/mint/fspclient.tgz)

       good luck   Theo


>Installing Finger


After I received a lot of mails on how to install the finger-tools, here
are the most important points to watch out for:

- do not try to start the fingerd in rc.net! it has to be started by
  inetd. Look into "etc/inetd.conf" and read the MiNT-Net Documents.

- If your "finger" is not in /usr/bin, make a copy or a link, so that
  /usr/bin/finger is existent. Otherwise your machine will not send out
  any infos (fingerd calls "/usr/bin/finger")

- and PLEASE, PLEASE, don't send me more mails on what finger is, and
  what it does, and how to use it .......

  Believe me, there are a lot of books, which describe daemons, tools
  and basics of Internetworking.

	  cheerio   Theo

---

: What worries me is that I just can't get 2 machines running 0.4 to talk
: to each other, or even one with 0.3 and one with 0.4. I just can't see 
: what I'm doing wrong.

Configuring TCP/IP is often a little bit confusing. It sounds to me, as if
there is no problem with the software, it's just a question of configuration.
So here are some points to check:

- Do your machines have a hostname and an IP-Address ? (must be different
  four every machine)

- Did you start the Loopback-Net(s) ? (Nameserver ?!?!)

- Did you start the SLIP or PLIP connections ?

- Check your routing !

- You have the tools ifconfig and route. USE THEM !

---

>Any hints on how to use 'ifconfig' and 'route' to trace non connections?
>Well this is what my main machine does to bring up MiNT-Net:
>(loads patched MiNT 1.10, all the .XFS and .XDD drivers and spawns ksh 
>shell)
|> u:/bin/ifconfig sl0 addr 100.0.0.1 dstaddr 100.0.0.2 mtu 4096 up
|> u:/bin/route add 100.0.0.2 sl0
|> u:/bin/ifconfig lo0 addr 127.0.0.1 up
|> u:/bin/route add 127.0.0.0 lo0
|> u:/bin/ifconfig
|> u:/bin/route
|> u:/bin/portmap
|> u:/usr/etc/inetd
|> u:/bin/mountd
|> u:/bin/nfsd
|>
|> This file is unchanged from my (working) 0.3 configuration.
|>
|> On the other machine the file is much the same, but obviously sets up a
|> route the other way. (100.0.0.2 to 100.0.0.1). Note: this network is 
|> *not* connected to the rest of the internet, so the ip addresses aren't
|> meaningful.


You might want to try to leave out the lines with the loopback device, 
and add instead the lines

ifconfig lo0 addr 100.0.0.1 up
route add 100.0.0.1 lo0

to be able to access your own computer with its own address. There was a 
bug in mint-net 0.30, where the loopback address was handled incorrectly. 
That was fixed in 0.31 and newer.

Ulrich

Hmmm, the description of your setup sounds quite ok to me. Perhaps
some other points to check :-) ...

- Are there appropriate entries for hostname and IP-Address in
  /etc/hosts and /etc/hostname ? check both machines.

- Try to setup ONE of your machines as nameserver (/etc/resolv.conf).
  Use either 100.0.0.1 or 100.0.0.2 but the SAME entry on BOTH machines.
  You should now be able to run 'hostlookup' on both machines.
  (BTW: if this works ok, forget about the next point.)

- Do both machines work with the same serial line speed ? (stty)

I guess you want to "connect" your machines via NFS ?
I have only on machine, for that reason i didn't work a lot with nfs and
do not know about any debugging-support of the nfs-package. Perhaps you
can find the bug using "nfs-debugging" !?


   Good Luck	Theo

---

>Some of the new MiNT net software packages look like they're set up
>to work with a syslog daemon to record kernel messages. I've looked
>around on atari.archive.umich.edu for such a beast, but I haven't
>been able to find anything.
>
>Does a MiNT syslog daemon already exist?

Yes, it's a part of the MiNTOS package, look for either mintossc.tgz or
mintosbn.tgz somewhere under the Mint directory hierarchy. Alternatively,
you can ftp it from:-

	ftp://earth.ox.ac.uk/pub/mintos

>Thanks,
>dgc

Steve

PS. By the way, yes, I am working on a new release and the binary
distribution will have much (if not all) the MiNTnet utilities set up in the
correct places with the rc scripts starting the daemons.

--



V. KA9Q NOS

	Intro:	Ka9Q NOS started as a port of the MSDOS program of the same
name and is not really an outgrowth of the older atari port.  It's main
drive has been to provide atari users internet access through CIX, a
commercial provider in the UK.	However with a minor amount of alteration it
works well for any atari owner wanting to connect with the net.  It is a good
choice for users with a small amount of memory and/or no hard drive.

V. KA9Q NOS	a. Overview of Ka9Q NOS

	Ka9Q NOS provides SLIP/PPP services for the atari 68k line of 
computers.  It also provides for NNTP (news) and has many options for SMTP 
(mail).  It has inbuilt support for a dialer for automatic connection to your 
account, however if you get a dynamic ip number each time you connect to your 
provider this will be of no use to you.

V. KA9Q NOS	b. Utilities for Ka9Q NOS

	There are a number of utilities for use with Ka9q NOS, as well a
graphical front end to ease the use and configuration of NOS.

	A few of these are:

		Oasis v. 1.12  -  Oasis is a GEM front end for NOS. 
 Eventually the programmers plan to replace NOS, so that you will not need it 
to connect to the net.	But as of this version that has not happened.  Oasis 
does not put everything in windows, but it does give you a menu bar and 
several dialogs for configuration.  So you don't have to memorize a large 
number of commands.  A graphical WWW browser is also planned for use with 
Oasis, but as of this version it is not yet available.

		bm.tos	-  The BM mailer for use with KA9Q NOS

		mail110.lzh  -	A simple mail program with source

		stmh1_2.lzh	  -  ST Mail Handler 1.2 for use with NOS

		snz128e.tos	  -  News package for use with Ka9qNOS

V. KA9Q NOS	c. More info about Ka9q NOS

The following notes are a quick guide to setting up the NOS version of Ka9q, 
this version of the program is in an early stage of development for the Atari 
ST and more complete instructions will be created at a latter date. 

Release 0.10 has been rebuilt for the ST from the DIS supported KA9Q for the 
IBM PC.  This means that the internet code is as up to date as I can find, 
and is a major advance on the amiga code level used for the 0.0x betas.  I am 
still working on the port to the DIS code.  There are various additions to 
the previous ST programs which are not present in this Version.  These will 
be added shortly. 

The NOS programs requires the following directories and files:- 

startup.nos   domain.txt	 ftpusers	  dial.txt	   alias 

   finger\ 

   spool\ 

	spool\mail\ 

	spool\mqueue\	      spool\mqueue\sequence.seq 

	spool\news\nntp.dat 

By default all paths are relative to the root directory of the drive from
which NOS was started.	This can be changed by starting nos with the -d flag.
For example:- 

	nos -dg:\nos 

would cause nos to look for g:\nos\startup.txt and g:\nos\spool etc. 

You can also set the root directory by setting the NOS_ROOT environment  
variable.  For example:- 

	NOS_ROOT=g:\nos 

This method requires a shell or utility program which allows you to setup the 
environment. 

NNTP - netnews 

There has been a lot of changes in the NNTP code.  The news groups to fetch 
can now be specified in the nntp.dat file. This takes priority over the 
startup file.  If batch mode is turned on all the news will be written into a 
single file for latter processing. 

The netnews newsgroups are specified in the startup.nos file, as is the NNTP 
profile.  The demon news server is news.demon.co.uk 

You may want to update the nntp.dat file in spool\news to change the date and 
time values to something recent, to prevent a large flood of news on your 
first connection. 

The dialer 

This version of ka9q has a dialer facility.  This uses the dial.txt file
which must be placed in the NOS root directory.  You can setup the
connection to demon with the command 

	  dial sl0 dial.txt 

There are currently a few problems with the dialer.  I know that the first 
character of some of the login messages is missing and that cwait can give 
problems, however I am currently using the supplied dial.txt file for all my
connections.  It is much easier than using a seperate terminal program to
do the login 


VI. Sample Config for STICP


Hello!

I'm using the ka9q-package on my Atari. The (working)
package is available at ftp.tu-clausthal.de (139.174.2.10)
/pub/atari/telecomm/tcpip/sticp.lzh. Access via FTP,
FSP (port 21) or email ("mail-server@ftp.tu-clausthal.de").
To get a more complete documentation get also the archive
ka9q_st.lzh.

I will try to give some "samples" on how to setup ka9q.
Remember to change hostnames/ip-addr/gateways etc...


Sample configuration:
* put all the stuff in a dir "net" in one of your root-dirs
* create inside this "\net"-dir the following dirs
  - finger
  - mail
  - mqueue
  - rqueue
  - spool
  - tmp
* customize your "\net\autoexec.net" file, sample:
======================================================================
   #
   # ...your internet-address
   #
   ip address [139.174.8.2]
   #
   # ...your hostname
   #
   hostname hiwist.rz.tu-clausthal.de
   #
   # ...configuration of MIDI interface
   #
   attach asy 3 1 slip midi 4096 576 31250
   #
   # ....configuration of SERIAL interface 
   attach asy AUX: 2 slip sl0 4096 576 19200
   #
   # ...link speeds (only need if differ from the one 
   #		     selected in the attachh cmds)
   param midi 31250
   param sl0 19200
   #
   # ...routing table
   #
   route add default sl0
   route add thilo midi
   route add claas midi
   #
   # ...time-to-live value
   #
   ip ttl 50
   #
   # ...loggin to which file?
   #
   log D:\net\spool\net.log
   #
   # ...delete old (smtp-)locks
   #
   delete D:\NET\MQUEUE\*.LCK
   #
   # ...some enviroment-vars
   #
   # mailer-config-file
   setenv BMRC D:\NET\BM.RC
   # default path
   setenv PATH=C:\BIN\,D:\ARCHIVER\,C:\GUCK\,D:\SHELLS\CMDS\,D:\NET\
   # your favorite shell
   shell =D:\NET\COMMAND.PRG
   #
   # SMTP (mailing) options
   #
   # ...time to check for mail delivery
   smtp timer 60 60
   # ...mailing gateway
   smtp gateway sun.rz.tu-clausthal.de
   #
   # ....start services
   #
   start telnet
   start ftp
   start smtp
   start echo
   start discard
   start finger
   # ...r(emote)cmd on a "secret" port
   start rcmd 3746
   #
   # ...now try to deliver old mail
   smtp kick
======================================================================
* create a file "hosts.net" with the IP-numbers to use
  (there might be working versions with nameserver-support but that's
  the way I'm using the package). Sample file:
  (ip-addr name aliases...)
======================================================================
   128.214.6.100   nic.funet.fi
   132.206.2.1	   cs.mcgill.ca
   139.174.1.1	   ibm.rz.tu-clausthal.de ibm ibm.rz rzibm
   139.174.2.10    sun.rz.tu-clausthal.de sun sun.rz rzsun
   139.174.2.11    helios.rz.tu-clausthal.de helios helios.rz rzhelios
   139.174.8.3	   thilo.rz.tu-clausthal.de thilo
   139.174.8.4	   claas.rz.tu-clausthal.de claas
   139.174.1.10    cisco.rz.tu-clausthal.de cisco cisco.rz rzcisco
   139.174.1.102   qms.rz.tu-clausthal.de qms qms.rz rzqms
   139.174.2.2	   next.rz.tu-clausthal.de next next.rz rznext
   139.174.2.5	   solaris.rz.tu-clausthal.de solaris solaris.rz rzsolaris
   139.174.41.1    fbrcad1.geotec.tu-clausthal.de fbrcad1 fbrcad1.geotech
   139.174.41.2    fbrcad2.geotec.tu-clausthal.de fbrcad2 fbrcad2.geotech
   139.174.41.3    fbrcad3.geotec.tu-clausthal.de fbrcad3 fbrcad3.geotech
   139.174.41.4    fbrcad4.geotec.tu-clausthal.de fbrcad4 fbrcad4.geotech
   139.174.101.14  next.in.tu-clausthal.de next.in innext
======================================================================
* create a file "ftpusers" to allow ftp-logins and restrict
  the dirs to use..., sample:
======================================================================
   root mypass c:\ 7 d:\ 7 e:\ 7 f:\ 7
   bwwl password c:\ 3 d:\ 7 e:\ 7 f:\ 7
   ftp * f:\ 1
======================================================================
* create your mailer-config "bm.rc", sample:
======================================================================
   ; configuration file for Bdale's Mailer... format is:
   ;   host <space> this_host_name
   ;   user <space> this_user_name
   ;   fullname <space> your full name for mail headers (optional)
   ;   reply <space> your reply address if not this machine (optional)
   ;	   useful for pc on large network off smart hosts
   ;   smtp <space> path to mailboxes  (optional)
   ;   edit <space> path your editor   (optional)
   ;   maxlet <space> max number of message in mbox ( optional default300)
   ;
   ;host hiwist.rz.tu-clausthal.de
   host [139.174.8.2]
   user bwwl
   fullname Wolfgang Ley
   reply Ley@rz.tu-clausthal.de
   smtp D:\net\mail
   edit D:\net\stevie.ttp
   ; zone MET
   maxlet 100
======================================================================
* optional create the following files:
  - alias (containing your mail-aliases "alias email-addr" once per line)
  - finger\userid.txt (text displayed when fingering userid)
  - autoexec.bat (or whatever your startup-script of your shell is)
  - mail.bat (to call the 'bm' and return to ka9q) with the following lines:
	D:\NET\BM.TOS %1 %2 %3
	exit
    (this way you are able to start bm with "!mail email-addr" to send
    or "!mail -u userid" to read)
* other hints:
  - the hosts inside your "autoexec.net" file must be listed in "hosts.net"
  - to track down problems while connecting to other sites use the "trace"
    cmd...
  - the slip-connection must be started before starting ka9q (or within
    ka9q if your shell supports direct AUX: access to dial and start slip).
  - don't rely too much on the docs (a lot is not working in the Atari port)
  - ask your local telecomm/unix-guru for further help


I hope that's all. This should be enough to setup your own site...

Bye,
  Wolfgang.


VII.	LINUX

	Intro:	I know very litle about Linux. (You must be getting sick of 
hearing that by now ;)	However, I do know that there is an Atari port and 
that there are people out there using it in daily practice.  Linux is a 
Freeware workstation style OS.	It is immensely popular on the 80x86 
platforms.  So by using it on your Atari, you can in effect tap into a very 
large user base.  It is a fairly powerful OS, especially considering the 
price (Free), and includes all the standard TCPIP networking options.  The 
main limitation is you must have at least a 68020 processor and a 6888x math 
coprocessor to use it.	That said most of the following is from Linux 
 Information Sheet v4.1, 31 March 1994 by Michael K. Johnson, 
johnsonm@nigel.vnet.net, and the linux/m68k-faq by Joerg Mayer 
<jmayer@informatik.uni-kl.de>.


What is Linux?

  Linux is a completely free reimplementation of the POSIX spec, with
  SYSV and BSD extensions (which means it looks like Unix, but does not
  come from the same source code base), which is available in both
  source code and binary form.	It is copyrighted by Linus B. Torvalds
  (torvalds@kruuna.helsinki.fi) and other contributors, and is freely
  redistributable under the terms of the GNU Public License.

  Linux is not public domain, nor is it `shareware'.  It is `free'
  software, commonly called freeware, and you may give copies away, but
  you must also give the source with it or make it available in the same
  way.	If you redistribute any modifications, you are legally bound to
  distribute the source for those modifications.  See the GNU Public
  License for details.	A copy is included with the Linux source, or you
  can get a copy via ftp from prep.ai.mit.edu in /pub/gnu/COPYING

What is Linux/m68k?

	Linux is a freely available operating system for PCs - to be more 
precise, it is one of many flavours of Unix. Linux is being developed on the 
net by several thousand people and being tested/used by many many more.  The 
fun and success of Linux inspired some people to port it to another platform 
- the Amiga. The first version released to the general public was 005. While 
008 was current, a few enthusiasts ported that version to the Atari and the 
two versions have been successfully merged with 09pl3 (this reads version 09 
patchlevel 3). Linux/m68k can be regarded as beta. This means that code that 
hasn't been ported/written recently works well most of the time.Hamish is 
working to integrate the m68k code into the main Linux source tree.

	The Linux/m68k releases are built and released by Roman Hodek (his 
e-mail is rnhodek@cip.informatik.uni-erlangen.de). 'Built' means that you 
write a patch against the current version/patchlevel and send it to him or 
the mailling list and he will integrate it into one of the next releases.

Note: If you patch processor specific code (e.g. 68030 vs. 68040) make sure
that you document the dependencies.



What are the features of Linux?

  o  multitasking: several programs running at once.

  o  multiuser: several users on the same machine at once (and no two-
     user licenses!).

  o  has memory protection between processes, so that one program can't
     bring the whole system down.

  o  demand loads executables: Linux only reads from disk those parts of
     a program that are actually used.

  o  shared copy-on-write pages among executables.  This means that
     multiple process can use the same memory to run in.  When one tries
     to write to that memory, that page (4KB piece of memory) is copied
     somewhere else.  Copy-on-write has two benefits: increasing speed
     and decreasing memory use.

  o  virtual memory using paging (not swapping whole processes) to disk:
     to a separate partition or a file in the filesystem, or both, with
     the possibility of adding more swapping areas during runtime (yes,
     they're still called swapping areas).  A total of 16 of these 128
     MB swapping areas can be used at once, for a theoretical total of 2
     GB of useable swap space.(I'm not certain that this is implemented in
	the M68K version of Linux)

  o  a unified memory pool for user programs and disk cache, so that all
     free memory can be used for caching, and the cache can be reduced
     when running large programs.

  o  dynamically linked shared libraries (DLL's), and static libraries
     too, of course.

  o  does core dumps for post-mortem analysis, allowing the use of a
     debugger on a program not only while it is running but also after
     it has crashed.

  o  mostly compatible with POSIX, System V, and BSD at the source
     level.

  o  through an iBCS2-compliant emulation module, mostly compatible with
     SCO, SVR3, and SVR4 at the binary level.

  o  all source code is available, including the whole kernel and all
     drivers, the development tools and all user programs; also, all of
     it is freely distributable.  There are some commercial programs
     being provided for Linux now without source, but everything that
     has been free is still free.

  o  POSIX job control.

  o  pseudoterminals (pty's).

  o  support for many national or customized keyboards, and it is fairly
     easy to add new ones dynamically.

  o  multiple virtual consoles: several independent login sessions
     through the console, you switch by pressing a hot-key combination
     (not dependent on video hardware).  These are dynamically
     allocated; you can use up to 64.

  o  Supports several common filesystems, including minix-1, Xenix, and
     all the common system V filesystems, and has an advanced filesystem
     of its own, which offers filesystems of up to 4 TB, and names up to
     255 characters long.

  o  CD-ROM filesystem which reads all standard formats of CD-ROMs.

  o  TCP/IP networking, including ftp, telnet, NFS, etc.

Who uses Linux?

  Linux is freely available, and no one is required to register their
  copies with any central authority, so it is difficult to know how many
  people use Linux.  Several businesses are now surviving solely on
  selling and supporting Linux, and very few Linux users use those
  businesses, relatively speaking, and the Linux newsgroups are some of
  the most heavily read on the internet, so the number is likely in the
  hundreds of thousands, but hard numbers are hard to come by.	However,
  one brave soul, Harald T. Alvestrand, has decided to try, and asks
  that if you use Linux, you send a message to linux-counter@uninett.no
  with one of the following subjects: ``I use Linux at home'', ``I use
  Linux at work'', or ``I use Linux at home and at work''.  He is also
  counting votes of ``I don't use Linux'', for some reason.  He posts
  his counts to comp.os.linux.misc.


Requirements to run Linux/m68k

	Processor

	The following Ataris (or clones) have the "right" processor built-in: 
 Atari Falcon (FPU is not standard but needed!), Atari TT, Medusa, Eagle (not 
yet supported). Note: In some of the older TTs there is a bug in the PAL 
controlling the access to the FPU. This may cause a crash.  Any processor 
upgrade card with a 68040 or 68030+68881/2 (like PAK/3) is able to run Linux.

	RAM

	It is possible to boot Linux/m68k with as little as 2 MB. Now you 
know that the kernel works on your system - that's it. If you want to work 
with it you should have at least 4 MB (8 MB with a X-server).

	Harddisk

	If you want to do more than just boot Linux/m68k you will need 30 - 
oo (infinity) MB of space on your hard disk and a supported hard disk 
controller.  Add another 20 MB for X.

The current status of Linux/m68k

	What has been done? The kernel (this means all the processor/mmu/fpu 
specific stuff) has been ported. Version 09 is based on the Linux 1.0 
patchlevel 9 sources but many modules from 1.1 have been integrated since. 
Work to update many modules to 1.2.8 is in progress. Several hardware 
independent devices have been ported:  Ramdisk, mem, pty, tty, vt, slip, 
net/inet, general SCSI stuff. Also the following filesystems have been done: 
minix, ext2, msdos, proc, isofs, affs, nfs, ppp. An X-server exists that uses 
the frame buffer device. Frame buffer devicesexist for the Atari.

	SCSI, ACSI, Falcon IDE, serial ports driven by a MFP (i.e. Modem 1 
and Serial 1), keyboard, Atari mouse, parallel printer port, RTC clock, 
floppy disk (DD/HD), native Atari graphics (ST/TT/Falcon).Note: Linux' Minix 
FS is compatible to the Minix V2 FS used with MiNT.


Hints on installing Linux/m68k


Please note that there is a much better installation doc available. It's the 
'Linux/m68k installation guide' written by Frank Neumann and Ingo Wilken. If 
you want to find out whether Linux/m68k runs on your system the hints given 
here may be sufficient. If you want to work with your Linux/m68k system you 
should get the Installation guide. The address is given below.
 
 0. a) Get the installation guide mentioned above.
    b) Ignore steps 1-8 and follow your new guide.
 1. Get a working kernel, *all* announce files and the bootstrap program
   for your machine (different kernel versions may require different  
   bootstrap versions), the root and usr-filesystems and the newfilesys 
   (this is a ramdisk that contains everything you will need to set up a 
   working harddisk environment). Sources for these programs: See below.
   You will also need gunzip (from the gzip package) for your native OS in
   order to unpack the following .gz files: ataboot, new-filesys and
   vmlinux.
   Note: If gunzip succeeds your files are OK. If you want to test the
   integrity of the files you downloaded without decompressing them you
   can do 'gzip -t <filename.gz>'.
 2. Bootstrap the kernel and newfilesys as described in the ANNOUNCE file
    for that kernel. Many of the bootstrap flags available are
    documented in older announce files only.
 3. Create a partition on your harddisk and install an ext2fs filesystem
    on it.
 4. Create another partition as swapspace.
 5. Unpack the root and usr filesystem onto the disk.
 6. Reboot
 7. Bootstrap your kernel, this time from the harddisk instead of ramdisk.
 8. Get and read the Installation-HOWTO for Linux. Start reading from 
     section 4 "Installing the Software". Warning: This is for the PC so 
     you may have to do things differently at some points.
Installation guide: ftp://ftp.informatik.uni-oldenburg.de
    /pub/amiga/linux/local/docs/Install-Linux_m68k.doc
These are the filenames relative to 680x0/
  ANNOUNCE-0.XXXXXX
  filesys/new-filesys.gz
  filesys/root.tar.gz
  filesys/usr.tar.gz
  bin/gcc-2.5.8.tar.gz
  kernel/vmlinux-0.9pl5.gz
  kernel/ataboot-0.5.gz (Atari only)
  src/linux-0.9*.gz (the kernel source tree and diff files)
  ../docs/HOWTO/Installation-HOWTO
  The root.tar.gz file contains no gcc, emacs or tcsh. If you are a
  tcsh or emacs addict you will want to get these packages from bin/ too.
  The filesystems naturally contain *no kernel sources*, so you will have
  to get these too.
   

Documentation

The Linux/m68k FAQ is available on 
ftp://tsx-11-and-mirrors/pub/linux/680x0/FAQ.gzand 
http://pfah.informatik.uni-kl.de:8000/pers/jmayer/linux68k-faq. 
Aninstallation guide is available on 
ftp://ftp.informatik.uni-oldenburg.de/pub/amiga/linux/local/docs/Install-
Linux_m68k.doc. Although the guide waswritten for the Amiga, many things are 
useful for Atari users too. An Atari specific install guide can be found at 
http://www-users.informatik.rwth-aachen.de/~hn/linux68k_azogsguide.txt;
another, more current one can be found at
http://zippy.spods.dcs.kcl.ac.uk/~tomlin/flinux.html. 
The ANNOUNCE files are valuable documentation too.Further documents can be
found in the directories ftp://tsx-11.mit.edu/pub/linux/docs/ and
ftp://sunsite.unc.edu/pub/Linux/docs. These documents were written for
Linux/i386 but many are useful for Linux/m68k users too (e.g. howtos on
UUCP, PPP and the general Linux FAQ).A faq on Motorloa chips 
(including the 680x0 microprocessors) is available.

Some Linux Newsgroups

comp.os.linux.development.kernel: This group is on Linux *kernel*
  development only. From time to time it contains messages dealing with
  the Linux/m68k kernel.
comp.os.linux.announce: This group announces new Linux related products as
  well as new kernel releases. Announcements for new versions of
  Linux/m68k may be found there.
maus.os.linux68k:
  This group deals with Linux/m68k only. The languages currently used are
  German and English.  It should be available at least at the following
  internet site:   news.uni-stuttgart.de (read only)
  The Newsgroup is also available in FidoNet (LINUX-68K.GER).

Mailinglists

	I am aware of one mailinglist for Linux/m68k. It is a Majordomo 
mailing list.  To join send mail to majordomo@vger.rutgers.edu with no 
subject and body containing subscribe 680x0. Content messages should be sent 
to linux-680x0@vger.rutgers.edu.  A mailinglist especially for Linux on 
Ataris: To subscribe send mail to majordomo@phil.uni-sb.de, no subject, with 
body 'subscribe atarix'.

Linux WWW-sites


Helmut Neukirchen's Linux/m68k WWW page:
  http://www-users.informatik.rwth-aachen.de/~hn/linux68k.html
Chris Lawrence' Linux/m68k WWW page:
  http://www.clark.net/pub/lawrencc/linux/index.html
Mirror of tsx-11 via WWW:
  http://src.doc.ic.ac.uk/packages/Linux/tsx-11-mirror/680x0/

Linux Ftp-sites


THE Linux/m68k server:
  ftp://tsx-11.mit.edu/pub/linux/680x0/
THE two Linux servers (sources for you to port to/compile on Linux/m68k):
  ftp://tsx-11.mit.edu/pub/linux/sources/
  ftp://sunsite.unc.edu/pub/Linux/system/
Mirrors (please use the one nearest to you, most of these mirrors are 
  updated daily):
  ftp://ftp.tu-clausthal.de/pub/systems/Linux/680x0/
  ftp://ftp.informatik.tu-muenchen.de/pub/comp/os/linux/680x0/
  ftp://ftp.informatik.uni-oldenburg.de/pub/linux/680x0/
  ftp://ftp.twi.tudelft.nl/pub/Linux/680x0/
  ftp://ftp.informatik.rwth-aachen.de/pub/Linux/BETA/680x0/
  ftp://ftp.germany.eu.net/pub/os/Linux/Mirror.SunSITE/
  ftp://ftp.fu-berlin.de/pub/atari/linux/
ftp://src.doc.ic.ac.uk/computing/operating-systems/Linux/tsx-11-mirror/680x0/
  ftp://ftp.uni-erlangen.de/pub/amiga/unix/Linux

Linux on Atari (all new patches for Ataris):
  ftp://ftp.phil.uni-sb.de:/pub/atari/linux/

The kernel source for Linux/m68k can be found in 680x0/src/, a lot of
binaries in 680x0/bin/. A few more tools reside in 680x0/tools/.

Modem

If you have a modem, you can get Linux/m68k from the following addresses:

	 Germany

	System name: nasim
	Phone: +49 89 5469593, ZyX19200
	Login:	Anon-uucp: nuucp - no password / ZModem: gast - no password
	Contents: full 680x0-tree of tsx-11 in /pub/linux-68k
	Get first: index file /pub/linux-68k/ls-lR.nasim.linux-68k.gz
	Other features: provides uucp access to 680X0 channel (read only)
and the linux.act.* news-groups
	Admin: Frank Bartels (knarf@nasim.cube.net)

Distributions


	ALD (= Autoren Linux68K Distribution) for Atari is available from
Whiteline.



Is there an X-server for Linux/m68k on the Atari ?

Yes, there is one. The frame buffer device you need is already integrated 
into the 0.9pl5 kernel.  Make sure that /usr/X11R6/bin/X is a link to 
/usr/X11R6/bin/XF86_Atari.

VIII.  WWW
	Intro:	If you don't know what the World Wide Web is by now, you must 
live under a rock.  However I will run through a quick description for you. 
At it's heart the web is a graphical way of accessing information on the net.
Hypertext, Sounds and Graphics are all supported.The heart of the protocol is
http, and the documents (called web pages) are in html format.
HTML stands for hyper text markup language.

	So how do we stand for support on the web for the Atari?  Well we 
have had many rumours of people coming out with web browsers, only to see 
them give up after they realize the size of the task.  However, we have seen 
some progress.	We do have a few viewers available and some utilities as well 
as some guides. 

	So the dream of instant easy gratification for web access on the 
atari hasn't materialized *yet*.  But we are not completely out of the loop. 
Hopefully we will see an expansion of the number of web browsers in the near 
future.

VIII.  WWW	a.  Overview of WWW support


VIII.  WWW	b.  ATARI World Wide Web Browsers


From: schuller@dutiws.twi.tudelft.nl (Bart Schuller)
Subject: Re: Mosaic/WWW ??
Keywords: atari, lynx, WWW

And I would like to announce that Lynx, the curses based WWW browser is
working right now on my atari. Right now I only have a 68020 only binary,
I'll make a 68000 binary when I have experimented some more (I want to
add term support).

The ingredients for those who would like to compile it themselves:

- gcc (I use a cross-gcc)
- MiNTLibs (mine are at pl44)
- MiNT-Net (version 0.30)
- ncurses (might not be strictly needed, but is if you not only want
  inverse-video but also bold and underline). This one needs to "ported"
  to the ST. I'll make patches relative to ncurses 1.8.5 available.
  Note that ncurses doesn't use the termcap database, it uses terminfo.
  I'll have to see if I can dig up an st52 terminfo entry.
- the Lynx source code (mine is beta version 2.3)
- (when term support works:) term for the atari (I use Kay Roemer's
  term 1.0.8)

As you can see, this is not for the faint of heart... :-)

I'll put the binary and my diffs for everything up for ftp on
	  ftp://ftp.twi.tudelft.nl/pub/atari/
You can mail me if you have problems getting everything installed
properly.

I do hope the people who want to do a GEM WWW browser take a look at
this, it could save them a lot of work...

With luck, the binary I made will magically start to work with SLIP and term
once MiNT-net contains working TCP.

lynx for the ST can be found on ftp://ftp.twi.tudelft.nl/pub/atari/lynx/
Note that this is currently "hack-ware"; it contains the ncurses library
instead of normal atari-curses because normal curses won't do bold and
underline. This means you'll need a terminfo description of the terminal you
use. I'm using one that works with Juergen Lock's virtual consoles on a
colour monitor. (I prefer colour instead of bold)
Details are in the README files on the ftp site.


Bart.
-- 
  /			      Bart Schuller			       \
 /P.B.Schuller@TWI.TUDelft.NL		    webmaster@www.twi.tudelft.nl\
<a href=http://www.twi.tudelft.nl/People/P.B.Schuller.html>My WWW page</a>
 \	 Insert your favourite witty saying here, I can't choose!	/

---

You can try Lynx by telnetting to www.twi.tudelft.nl and logging in as
"lynx".

---

: A question for the Lynx savvy if you please.

: I've been telnetting to either www.twi.tudelft.nl or
: millbrook.lib.rmit.edu.au   and using their
: lynx programs since all I have is a vt100 on this end.
: I see some people posting here advertising their own html home pages.
: How do I force these WWW servers to vie these home pages???

You type:

lynx <address>

for eg, lynx http://micros.hensa.ac.uk

That's all...and this should take you to the specified address to
browse around.

---

I've found that www.lbl.gov lets people use the "G" command even though
they are anonymous users. ...
Well, at least I will know where to telnet to when I need a lynx server for
now.  Thanks guys.

Jeff
 
--

VIII.  WWW	c.  ATARI World Wide Web Pages (URLs)

	ATARI URLs

	http://micros.hensa.ac.uk/
	http://student.dhhalden.no/studenter/jonal/Atari/Atari.home.html
	http://www.upi.edu:8080/~lanar/atari.html
	http://godel.ph.utexas.edu/Members/timg/welcome.html
	http://www.earth.ox.ac.uk/~steve/mintos.html
	http://web.city.ac.uk/~cb170/ksclpt.html
	http://web.city.ac.uk/~cb170/CALAMUS/calamus.html
	http://www.wpi.edu:8080/~lancer/atari.html


IX.  Ethernet Adaptor for the Atari

	Intro:	In the last year the TUW TCP package for an ethernet card has 
been updated to support the PAMs ethernet card.  I have litle information on 
it however the drivers are located on a.a.u.e. under 
atari/Network/Ethernet/tuw4pam.lha.  I believe that it behaves almost exactly 
like the original software, except it works with the PAMs card as opposed to 
the Riebl card.  

	Also of possible interest for people looking towards an Ethernet 
adaptor for their Atari computer, is MiNT Net.	Although I don't know of any 
drivers written as of this time, there is a dummy driver included in the 
current distribution of MiNT Net.  While this driver doesn't actually drive 
any cards as of yet, it's source code is the first logical step for writting 
a driver.  Kay Roemer has also expressed interest in helping someone write a 
driver for a card.  So if you like a challenge and have an ethernet card, 
there is definately help waiting for you.

	I'll now jump back to an article discussing TUW TCP.

     (Note this article is from early 1992 so the information is probably
somewhat dated.  It is included here for information purposes.)

     Hallo,
     Some of the readers of the previous article didn't even know that an
Atari ethernet board existed.  For all who requested more information,
here are some details about it.  This article covers the Atari hardware
and the software implementation.  An article about our TCP/IP
implementation will follow soon.

Hans

About Atari Ethernet Support

     Atari Germany markets ethernet boards for the Atari Mega ST series
and Mega STE/TT computers.  They were introduced at the Atari fair
Dusseldorf 1990 and we got our board soon afterwards.  At least the first
series were manufactured by Riebl Computertechnik GmbH, Germany and were
named "Riebl Card Plus".

     The Cards are built with an AMD 7990 compatible Ethernet controller
(LANCE) and 64KB shared memory.  The Mega-ST cards fit into the internal
slot, the STE/TT boards use the VME slot.

     The board is bundled with ANS Software (Atari Network Services),
based on TCP/UDP and features file sharing, printer spooling and
redirection.  The software doesn't support heterogeneous networking with
the well know services (telnet, ftp to the most important 8-))

     The software is implemented as GEMDOS extension.  The programming
interface is documented in the manual and cover:

     ANS:  miscellaneous network functions
     IPC:  interprocess communication
     UDP:  UDP protocol functions
     TCP:  TCP protocol functions
     AFS:  Atari File System functions and network aware replacements of
the original GEMDOS file I/O functions.  There are multitasking features
to allow the implementation of the mentioned servers.

     In Austria the retail price (board + software) is about 10000 ATS
(including 20% VAT) (The exchange rate currently is 1US$ to 11.5 ATS) (***
This was as of 1992 who knows now - editor)  If you know about prices or
availability in other countries let me know, I'll post a summary.

     IMHO I don't think the Riebl Card Plus is available outside
continental Europe.

     At present there is no unbundled board available from neither Atari
nor the manufacturer.  We have to pay for the hardware and the license for
the software which we don't use.

     Although it should be possible for an experienced EE student to build
a functional equivalent, there is a one time licence fee of US $1000 for
an ethernet hardware manufacturer due to IEEE. ( I don't know if the Atari
board is licensed, they were not on the list I recently read on the net.)

     I think that some third party manufacturers of affordable ethernet
boards could increase the market volume and lower the price.

     If you own a 1040 ST or equivalent you are out of luck with the Atari
adapter.  IN Germany there are several companies which sell ACSI based
ethernet adapters, I know PAM Network and BIOnet.  As I know little to
nothing about them, please post a question about them if you are
interested.  Maybe someone is listening who has experience with them. (Hi
Peter!)

     Johann Haider

X.  UUCP on the Atari Q&A

Steve Barnes (Steve.Barnes@lchurch.mcd.on.ca) wrote:

>	  I'm having a problem with UUCICO72 here, and hoping somebody
> out their is running the same. Here goes.

Hmm, I don't know of which uucico implementation you talk. But it seems
you use the GFA uucico 3.72, usually works together with Hermes.

The latest version of GFA uucico is 4.01.

>	  How do you get it to use e-proto as a default OR use increased
> g-proto packet sizes? This has got me really confused. I call UUCICO72
> directly to place a call, all documented environment variables are set
> etc.. with the following command line:

You do not want to use g protocol over serial lines:

     The `t' and `e' protocols are intended for use over TCP or some
     other communication path with end to end reliability, as they do no
     checking of the data at all.  They will only be considered on a
     TCP port which is both reliable and eight bit.

> It dials out just fine, connects (usually.. crappy phone line :),
> negotiates and logs in. However my end *SHOWS* its using e-proto
> as a default (I've included the lowercase 'e' at the end of the
> phone number in my hosts file).. My hosts logs show a NO negotiation
> for e-proto, and using g-proto with 64 byte packets. This KILLS
> throughput with the modem just thrashing itself to pieces.

The protocol and window/packet sizes really used for the transfer is
also dependent of the other host. If the other uucico is not capable
of the 'e' proto or does not want to use 'e' proto over the serial
line, there is no way to use 'e' proto.

> I've even tried g-proto with 512 byte packets. Nothing happens,
> UUCICO just sits their stating its gone into slave mode and does
> nothing. I'm really at a loss after 2 months of messing about with
> it. Please, HELP! :)

Again: The other site must support packet-sizes larger than 64 bytes.
If you want to use larger packet-sizes in *both* directions, the other
site has to configure that, too! And for GFA uucicos 3.?? you *must* use
the same packet-sizes in both directions. I don't know if the bug is
still present in 4.01.

Remember: Most old fashioned uucico-implementations do not support
larger packet sizes. Ask the other site for further information.

Bye,
Knarf

---

 > From: sandersw@cgsvax.claremont.edu
 > Organization: The Claremont Graduate School
 >
 >
 > Does anyone out there on the net know of a way to get a UUCP feed to my
 > atari.  I have played with Mercury and Hermes, but there are either no
 > docs or they are in german.	I would be interested in source code.. a
 > compiled program that would let my Ratsoft BBS users get email and
 > usenet from a UUCP feed.  even a prgram that would convert USEnet
 > messages to Fido messages would be greatly appreciated.
 >

Steve Caple (If you have access to NeST you can contact him there) has 
written program to convert the two type of packets Usenet<->Fido , the 
latestnon-beta version is freq'able using FIDO mailers from several BBS , the 
name of the program is ...... STUFIT.ZIP , I have it here.

It's supportware , you can use it but if you want improvements and/or changes
then you have to pay him a one off fee.


XI.  More Information available on the Internet


     There is a host of information available on the Internet,	here is a
short list of other resources that you might want to look at for more
information and help.

     The Atari FTP Site List - This is available at numerous Atari File 
Archives, and is occasionally posted to comp.sys.atari.st .  It is not only 
an excellent resource for finding Atari computer related files it also has a 
tutorial for connecting to hosts and retrieving files via FTP.


     Hitchhikers Guide to the Internet and other handy resources can be found 
at ftp.halcyon.com in '/pub/tidbits/tisk'.  A good source of info for the 
beginer through intermediate user.  Also available at a.a.u.e under 
atari/Network.


     Zen & the Art of Internet is available at src.doc.ic.ac.uk under 
'/computing/networks/internet/doc/zen'. Also available at a.a.u.e. under 
atari/Network.

     Internet Resource Guide (IRG) is available at ds.internic.net.  Look 
under '/resource-guide/fyi' and 'resource-guide/rfc'.  This is a good source 
of info for  the experienced user as well as sys admins.  This is where you 
find RFCs and FYIs.  A few of note are FYI4.TXT,  FYI7.TXT.  These are 
frequently asked beginers question,  frequently asked experienced user 
questions.  Also RFC 1180.


XII.  Glossary of Terms.


     TCP/IP introduces a wide range of terms that most computer users are
not used to, here is a small list to assist in making some sense out of
Internet.  And	hopefully the documentation that comes with TCP/IP
packages.


address  - There are two separate uses of this term in internet
	networking: "electronic mail address" and "internet address".
	An electronic mail address is the string of characters that you must
	give an electronic mail program to direct a message to a particular
	person. See "internet address" for its definition.

ANSI  -  American National Standards Institute	A group that certifies
	 organizations which develop U.S. standards for the information
	 processing industry.  ANSI  accredited groups participate in
	 defining network protocol standards.

ARP -	 Address Resolution Protocol  An Internet protocol which runs on 
	 Ethernet and all IEEE 802.X LANs which maps internet addresses to
	 MAC addresses.   

ARPANET - Advanced Research Projects Agency Network  A pioneering long	
	  haul network funded by ARPA.	It served as the basis for early  
	  networking research as well as a central backbone during the
	  development of the Internet.	The ARPANET consisted of individual
	  packet switching computers interconnected by leased lines. 

AS -   Autonomous System  A collection of gateways (routers) under a
       single administrative authority using a common Interior Gateway
       Protocol for routing packets.

ASCII -  American (National) Standard Code for Information Interchange

B  -  Byte  One character of information, usually eight bits wide.  

b  -  bit - binary digit  The smallest amount of information which may be 
      stored in a computer.  

BITNET - Because It's Time Network  BITNET has about 2,500 host computers,
	primarily at universities, in many countries.  It is managed by
	EDUCOM, which provides administrative support and information
	services.  There are three main constituents of the network: BITNET 
	in the United States and Mexico, NETNORTH in Canada, and EARN 
	in Europe.  There are also AsiaNet, in Japan, and connections in 
	South America.	See CREN.  

bps  -	bits per second   A measure of data transmission speed.  

BSD  -	Berkeley Software Distribution Term used when describing different
	versions of the Berkeley UNIX software, as in "4.3BSD UNIX".  

catenet - A network in which hosts are connected to networks with varying  
	characteristics, and the networks are interconnected by gateways  
	(routers).  The Internet is an example of a catenet.

CCITT  - International Telegraph and Telephone Consultative Committee

core gateway  - Historically, one of a set of gateways (routers) operated
		by the Internet Network Operations Center
		at BBN.  The core gateway system forms a central part
		of Internet routing in that all groups had to advertise paths
		to their networks from a core gateway.	

CREN - The Corporation for Research and Educational Networking BITNET and
	CSNET have  merged to form CREN.

CSNET  - Computer + Science Network  A large data communications network  
	 for institutions doing research in computer science.  It uses
	 several different  protocols including some of its own.  CSNET sites
	 include universities, research laboratories, and commercial
	 companies.  See CREN.

DARPA	U.S. Department of Defense Advanced Research Projects Agency  
	The government agency that funded the ARPANET and later started the  
	Internet.   

Datagram  - A self-contained, independent entity of data carrying
	    sufficient information to be routed from the source to the
	    destination data terminal equipment without reliance on earlier
	    exchanges between this source and destination data terminal
	    equipment and the transporting network.
     
default route -  A routing table entry which is used to direct any data 
	addressed to any network numbers not explicitly listed in the 
	routing table.	

DNS - The Domain Name System is a mechanism used in  the Internet for  
      translating names of host computers into addresses.  The DNS also
      allows host computers not directly on the Internet to have
      registered names in the same style, but returns the electronic mail
      gateway which accesses the non-Internet network instead of an IP
      address.	 

dot address (dotted address notation) - Dot address refers to the common
	notation for Internet  addresses of the form A.B.C.D; where each
	letter represents, in decimal, one byte of the four byte IP address.  

Dynamic Adaptive Routing   - Automatic rerouting of traffic based on a	
		 sensing and analysis of current actual network conditions.
		 NOTE: this does not include cases of routing decisions
		 taken on predefined  information.

EBCDIC - Extended Binary-coded Decimal Interchange Code

EGP - Exterior Gateway Protocol  A protocol which distributes routing 
      information  to the gateways (routers) which connect autonomous
      systems.	 

Ethernet  - A network standard for the hardware and data link levels.
	   There are two types of Ethernet: Digital/Intel/Xerox (DIX) and
	   IEEE 802.3.	 

FDDI  - Fiber Distributed Data Interface  FDDI is a high-speed (100Mb)
	token ring LAN.

FIPS  -  Federal Information Processing Standard  

FSP -  FSP is an "UDP-based FTP", and is a lot like his TCP-based brother.
 
FTP -  File Transfer Protocol  The Internet standard high-level protocol
       for transferring files from one computer to another.

gateway - See router   

GB  - Gigabyte	A unit of data storage size which represents 10^9 (one
      billion) characters of information.

Gb - Gigabit  10^9 bits of information (usually used to express a data	
     transfer rate; as in, 1 gigabit/second = 1Gbps).
  
GNU - Gnu's Not UNIX   A UNIX-compatible operating system developed by the
      Free Software Foundation.

header -  The portion of a packet, preceding the actual data, containing
	  source  and destination addresses and error-checking fields.

host number  - The part of an internet address that designates which node
	       on the (sub)network is being addressed.

ICMP -	Internet Control Message Protocol   ICMP is an extension to the 
	Internet Protocol.  It	allows for the generation of error messages,
	test packets and informational messages related to IP.
  
IEEE  - Institute for Electrical and Electronics Engineers

IETF  - Internet Engineering Task Force  The IETF is a large open
	community of network designers,  operators, vendors, and researchers
	whose purpose is to coordinate the operation, management and
	evolution of the Internet, and to resolve short- and mid-range
	protocol and architectural issues.  It is a major source of proposed
	protocol standards which are submitted to the Internet Activities
	Board for final approval. 

internet   internetwork   -  Any connection of two or more local or
			     wide-area networks.

Internet  - The global collection of interconnected local, mid-level and  
	    wide-area networks which use IP as the network layer  protocol.

internet address  -  An assigned number which identifies a host in an internet.
		     It has two or three parts: network number, optional
		     subnet number, and host number.

IP - Internet Protocol	 The network layer protocol for the Internet.  It
			 is a packet switching, datagram protocol defined
			 in RFC 791.  

ISO - International Organization for Standardization

KB - Kilobyte  A unit of data storage size which represents 10^3 (one  
	       thousand) characters of information. 
 
Kb  - Kilobit	10^3 bits of information (usually used to express a data 
		transfer rate; as in, 1 kilobit/second = 1Kbps = 1Kb).

LAN -  Local Area Network   A network that takes advantage of the
       proximity of computers to offer relatively efficient, higher speed
       communications than long-haul or wide-area networks. 

MAC  - Medium Access Control   For broadcast networks, it is the method
       which devices use to determine which device has line access at any
       given time. 

MAN -  Metropolitan Area Network 

MB -  Megabyte	A unit of data storage size which represents 10^6 (one	
      million) characters of information.  

Mb  -  Megabit	 10^6 bits of information (usually used to express a data 
       transfer rate; as in, 1 megabit/second = 1Mbps).  

NBS  - National Bureau of Standards  Now called NIST. 
  
network number	 -  The part of an internet address which designates the
		    network to which the addressed node belongs.

NFS - Network File System   A network service that lets a program running
      on one  computer to use data stored on a different computer on  the
      same internet as if it were on its own disk.

NIC  - Network Information Center   An organization which provides network
       users with information about services provided by the network.

NOC  - Network Operations Center  An organization that is responsible for  
       maintaining  a network.	

NIST  -  National Institute of Standards and Technology    Formerly NBS.

NSFNET	- National Science Foundation Network  The NSFNET is a highspeed  
	  "network of networks" which is  hierarchical in nature.  At the
	  highest level is a  backbone network currently comprising 16 nodes
	  connected to a 45Mbps facility which spans the continental United
	  States.  Attached to that are mid-level networks and	attached to
	  the mid-levels are campus and local networks.  NSFNET also has
	  connections out of the U.S. to Canada, Mexico, Europe, and the
	  Pacific Rim.	The NSFNET is part of the Internet.

NSFNET	-  Mid-level Level Network  A network connected to the highest
	   level of the NSFNET that  covers a region of the United States.
	   It is to mid-level networks that local sites connect.  The
	   mid-level networks were once called "regionals".

OSI -  Open Systems Interconnection   A set of protocols designed to be an
       international standard method for connecting unlike computers and
       networks.  Europe has done most of the work developing OSI and will
       probably use it as soon as possible.

OSPF  - Open Shortest-Path First Interior Gateway Protocol   A proposed 
	replacement for RIP.  It addresses some problems of RIP and is based 
	upon principles that have  been well-tested in non-internet
	protocols. Originally  acronymed as OSPFIGP.

packet	- The unit of data sent across a packet switching network. The
	  term is used loosely. While some Internet literature uses it to
	  refer specifically to data sent across a physical network, other
	  literature views the Internet as a packet switching network and
	  describes IP datagrams as packets.  

PC - Personal Computer	

PCNFS  - Personal Computer Network File System

PPP  -	 Point-to-Point Protocol   The Point-to-Point Protocol (PPP)
	 provides method for  transmitting datagrams over serial
	 point-to-point links.	

protocol  -  A formal description of message formats and the rules two 
	  computers must follow to exchange those messages. Protocols can 
	  describe low-level details of  machine-to-machine interfaces (e.g.,
	  the order in which bits and bytes are sent across a wire)  or
	  high-level exchanges between allocation programs (e.g., the way in
	  which two programs transfer a file across the Internet).

RFC -	The Internet's Request for Comments documents series The RFCs are
	working notes of the Internet research and  development community.  
	A document in this series may be on essentially any topic related to
	computer communication, and may be anything from a meeting report to 
	the specification of  a standard.

RIP   -  Routing Information Protocol	 One protocol which may be used on 
	 internets simply to pass  routing information between gateways. It
	 is used on many LANs and on some of the NSFNET intermediate level
	 networks.   

RJE  -	 Remote Job Entry   The general protocol for submitting batch jobs
	 and retrieving the results.

router	-  A special-purpose dedicated computer that attaches to  two or
	   more networks and routes packets from one network to the other. In
	   particular, an Internet  router forwards IP datagrams among the
	   networks it connects.  Gateways route packets to other gateways
	   until they can be delivered to the final destination directly
	   across one physical network.

RPC  - Remote Procedure Call	An easy and popular paradigm for
       implementing the client-server model of distributed computing.

server	-  A computer that shares its resources, such as printers and
	   files, with other computers on the network.	An example of this is
	   a Network Files System (NFS) Server which shares its disk space
	   with one or more workstations that may not have local disk drives
	   of their own.

SLIP  -  Serial Line Internet Protocol	 SLIP is currently a defacto
	 standard, commonly used for point-to-point serial connections
	 running TCP/IP.  It is not an Internet standard but is defined in
	 RFC 1055.   

SMTP  - Simple Mail Transfer Protocol	The Internet standard protocol for
	transferring  electronic mail messages from one computer to another.
	SMTP specifies how two mail systems interact and the format of
	control messages they exchange to transfer mail.

SNA  -	System Network Architecture   IBM's data communications protocol.

SNMP   - Simple Network Management Protocol   The Simple Network  
	Management Protocol (RFC 1157) is the Internet's standard for remote 
	monitoring and management of hosts, routers and other nodes and
	devices on a network.

subnet	-  A portion of a network, which may be a physically independent
	network, which shares a network address with other portions of the
	network and is distinguished by a subnet number.  A  subnet is to a
	network what a network is to an internet. 

subnet number  -  A part of the internet address which designates a
		  subnet.  It is ignored for the purposes internet routing,
		  but is used for intranet routing.

T1 -   A term for a digital carrier facility used to transmit a DS-1
       formatted digital signal at 1.544 megabits per second. 

T3 -   A term for a digital carrier facility used to transmit a DS-3
       formatted digital signal at 44.746 megabits per second.	

TCP  -	 Transmission Control Protocol	 A transport layer protocol for
	 the Internet. It is a	connection oriented, stream protocol defined
	 by RFC 793.   

TCP/IP -  Transmission Control Protocol/Internet Protocol  This is a
	  common shorthand which refers to the suite of application and
	  transport protocols which run over IP.  These include FTP, TELNET,
	  SMTP, and UDP (a transport  layer protocol).

Telenet  - A public packet-switching network operated by US Sprint.  Also
	   known as "SprintNet".

TELNET -  The Internet standard protocol for remote terminal connection
	  service.  TELNET allows a user at one site  to interact with a
	  remote timesharing system at	another site as if the user's terminal
	  was connected directly to the remote computer.

Token Ring - A type of LAN.   Examples are IEEE 802.5, ProNET-10/80 and
	     FDDI.  The term "token ring" is often used to denote 802.5  

Tymnet	- A public character-switching/packet-switching network operated
	  by British Telecom.	

UDP  - User Datagram Protocol  A transport layer protocol for the
       Internet.  It is a datagram protocol which adds a level of
       reliability and multiplexing to IP datagrams.  It is defined in RFC
       768.

UNIX	An operating system developed by Bell Laboratories that  supports
	multiuser and multitasking operations.	

url	Unique Remote Location - WWW page address
 
UUCP  -  UNIX-to-UNIX Copy Program   A protocol used for communication
	between consenting  UNIX systems.  
  
WAN  -	 Wide Area Network   

WHOIS  -  An Internet program which allows users to query a database of
	  people and other Internet entities, such as domains, networks, and
	  hosts, kept at the DDN NIC.  The information for people shows a
	  person's company name, address, phone number and email address.  

XNS  -	Xerox Network System   A data communications protocol suite
	developed by Xerox.  It  uses Ethernet to move the data between
	computers.   

X.25  -  A data communications interface specification developed to
	 describe how data passes into and out of public data communications
	 networks.  The public networks such as Sprintnet and Tymnet use X.25
	 to interface to customer computers.


XIII.	Index of Files in the Network area of a.a.u.e.

	atari/Network:

EtherNet:  Software for handling Ethernet controllers on the Atari 680x0.

	lprcard.best	     30720   Directions for building an EtherNet card
				     for the MegaST
	lprcard.gal.tar.gz    3791   Instructions for the GAL for above.
	lprcard.gif.tar.gz  107064   GIF of circuit board for above.
	lprcard.idx	       413   Short description of Lprcard.
	lprcard.readme	      1409   Readme about Lprcard.
	readme		      5109   Readme about tuw pakage
	readme.pkd	      3740   Description of how to write packet
				     driver for tuw-tcp.
	tn.rsc		      4398   RSC file for TNFTP.ACC
	tnftp.acc	     39583   version 1.32 of Telnet/Ftp for tuw-tcp.
	tuw-tcp.1.22.lzh    142575   Complete Tuw-tcp version.1.22
	tuw4pam.lha	     83417   TuwTCP for PAM's ethernet card(bin only)

Ka9q:	This area houses various adaptations of the Ka9q source.
	Ka9q in general handles SLIP and PPP protocols.

	ka9q_doc.arc	148	Ka9q docs
	ka9q_src.arc	247	Sources for ka9q package
	ka9q_st.arc	153	Binaries for ka9q.
	ka9qst.arc	69	Some sort of ka9q.
	n890421.zoo	126	ka9q binaries
	nhclb120.zoo	428	ka9q sources
	newnet.zoo	97	Yet another net.tos binary (ka9q)
	sticp.lzh	595	Your own icp software.
	sticpsrc.lzh	701	Sources for your own icp software.

Ka9q/Nos: D. Nash's port of Ka9q-NOS. 

	README		  2363	Description of Ka9q-NOS
	nos041.tos		181220	Binaries to Ka9q-NOS version 4.1
	nos041_s.tos	511396	Source code to Ka9q-NOS version 4.1
	nosdoc.lzh		 57013	Documentation to Ka9q-NOS
	nosfiles.lzh	 13418	Extra files for Ka9q-NOS 
	oasis110.zip	233206	Gem front end for Ka9q-NOS
	oasis112.zip	234707	Oasis v. 1.12
	112_upd.zip		146996	Update Oasis 1.10 to 1.12

Ka9q/Nos/Install:  This is a startup package for Ka9qNOS

	stnet110.tos	913518	All the current binaries w/install
			program

Local:	Files for connecting two machines at your site without running
	SLIP software.	ie. *Quick* and *Simple* networking.

	duet_100.lzh	52040 This is a networking program that uses 
			      the serial, modem or LAN ports to network 
			      two ataris.
 
	duet.eng		15752	English translation of Duet Docs by 
					Leslie Hartmier

	ghostlnk.zip	28524	Filetransfer between any Atari	
				(ST(E)/TT/Facon)
				and a PC. All the drives of the PC can be 
				accessed on the Atari by a GEM-diskicon.

Local/Midi: Link to the Network/Midi directory.

Mail:	Mail readers and tools for managing mail readers.

	bm.tos		 36120	The BM mailer for use with KA9Q NOS
	elm24pl23.zip	130645	Elm for the Atari.
	mail110.lzh	 52322	A simple mail program with source (Ka9q-NOS)
	pathalia.zoo	137864	Pathalia - a mail routing tool (w.C src)
	stmh1_2.lzh	275016	ST Mail Handler 1.2 for use with NOS

Midi:	*Quick* and *Simple* Networking via Midi ports.

	lit_net.lzh	  5190	Little Net - Midi Net .ACC nice and easy way
					to access drives on another machine.
					Does not like Falcon resolution
					switching.
	mdneteng.zip	 4420	English resource and description text for
					Medium Net (med_net.lzh)
	med_net.lzh	 8704	Medium Net - Update to Little Net.  Now 
					you can access multiple drives.
	midi_com.lzh   117902	Demo of German MIDI networking software
	midinet.arc	46940	Midi Networking package
	miknet13.arj	20065	Sharware midi-network (DOS end supposedly 
					 exists)
	mx2doc.lzh	27484	Documentation for mx2net
	mx2net20.lzh	34578	Networking system including modula2 source.
					 Allows cross net file execution.

MintNet: Link to the Mint/Network directory.
	(for the use of this document I have included the contents of this
directory here)

	fingerd.tgz		 24    Fingerd for MiNT + MintNet
	ftp-01.tgz		193    Ftp/ftpd for MiNT + MintNet.
	gopher-2.012.tgz	256    Gopher client for MiNT + MintNet
	httpd-1.3.tar.gz	182    Http demon. Needs net-xxx.tgz
	inetd-01.tgz		 45    Pl1 of Internet Super Server.  Needs
					      net-xxx.tgz     
	net-042.tgz		379	Ver0.42 of MintNet, a networking
					      extension w/BSD socket 
	net-051.tgz		418	Ver0.51 of MintNet, a networking
					      extension w/BSD socket 
	net-053.tgz		426	Ver0.53 of MintNet, a networking
					      extension w/BSD socket 
	net-060.tgz		504	Ver0.60 of MintNet, a networking
					      extension w/BSD socket
	net-070.tar.gz		527	Ver0.70 of MintNet, a networking
					      extension w/BSD sockets
	nfs-042.tgz		183	Networking file system for MiNT+net.
	nfs-050.tgz		207	Networking file system for MiNT+net.
	ntalk-01.tgz		 92	Ntalk for Mint + net.
	ping-00.tgz		 38	ping for MintNet >= 0.53, PL 0
	portlib-02.tgz		 13	Pl2 of library software for porting
					       unix stuff
	rpc-01.tgz		450	Pl1 of Sun RPC for Mint + MintNet
	sinetd-00.tgz		 19	Simple inetd for MiNT+MintNet
	telnet-00.tgz		178	telnet for MintNet, PL 0
	telnet-01.tgz		178	telnet for MintNet, PL 1
	term-1.08.tgz		244	A port of term for MiNT+net
	tftp-00.tgz		 37	Pl0 of trivial ftp for Mint+MintNet
	tftpd-00.tgz		 27	Pl0 of the tftp server program for
					       MiNT+MiNTNet
	traceroute-00.tgz	 52	traceroute for MintNet >= 0.53, PL 0
	udpprobe.tgz		 23	Prg for testing connectivity in M+MN.
					       Similar to ping

News:	News readers and tools for managing news readers.
 
	bsnews.arc	     53864	Boot Strap News for MT C Shell
						(C source inc.)
	ng_dir.zoo	      9251	Utility for managing news groups
	nn13.lzh	    353445	Net News. version 1.3
	o_024.zip	    439749	Okami News-Reader
	o_026.zip	    502533	Okami News-Reader 026 (SOUP/UUCP/MAUS)
	snz128e.tos	    231418	News package for use with Ka9qNOS
	snz128s.tos	    164864	Source code for snz128e.tos
	strn092.tar.gz	    418501	STRN for MiNT Net (Minix XFS)
	trn341.zip	    228228	TRN for the Atari ST.

Uucp:	Programs for managing and running UUCP on your Atari.

	herm103b.zoo	 760425 Hermes 1.03 beta.  uucp/mail/news/etc.
	herm_114.zip	1248441 Hermes 1.14  uucp/mail/news/etc. 
						now supports pgp.
	mercbin.lzh	 322350    Mercury (binaries) uucp/mail/news/etc.
						predecesor to Hermes
	upoint_l.lzh	 365078 Upoint_light version of August 94
	upoint_l.lzh.old 323099 UPoint-Light Gem uucp/mail/news/etc. 
						version of spring 94
	uucico.arc	  33152  
	uucpv2.arc	 137320 UUCP version 2 for MT C Shell
	uupcst.arc	 141475 UUCP GFA style (inc. MailTruk and
						source)

Www: Programs for accessing the World Wide Web or relating to any of its
	components (i.e. html)

	html08.lzh	       70617  HTML browser for the Atari ST/TT/Falcon.
		      Handles inlined images in mono.  Does not handle online
		      sessions. ie. html document must be local (German)

	htmldo.zip	       28925  Documents on html specifications.

	htmlspec.lzh	       51072  These are the specifications for 
			in html format.  Use html08.lzh to view or any other 
			html browser. (English)

	lynx2-3-1-beta-00.tgz 206598  This is lynx 2-3-1 beta compiled for
	       the Atari ST range of computers. It can be run without MintNet
	       to browse files on your local system. To run it on a SLIP
	       or PPP connection MiNT and MintNet are also needed.

	sgmlstos.lzh	       88894  SGMLS parser for Atari TOS computers. 
				  SGML (Standard Generalized Markup Language)


access.int.via.mail  217790 How to use FTP/Gopher/Archie... via mail
hitchikers.guide.to.the.internet  61740  Brief overview of Internet
tcpip.faq   - TCPIP.FAQ - info on SLIP/PPP/UUCP software for the Atari 680x0
tcpip.glossary.tex 16504 Glossary of tcpip.faq in TeX format
zen.readme 4499 Description of Zen and the art of Internet
zen-1.0.PS 492528 Zen and the art of Internet Postscript form
zen-1.0.dvi 269504 Zen and the art of Internet .DVI form (TeX)

/end of Network directory/

XIV.  Partial List of Software Authors Email Addresses

     The list is intended to be a resource.  Please unless you have a 
question pertaining to a specific package please ask it in a newsgroup.  
These people in general are very busy (hopefully coming out with great 
new updates :) )  So please be considerate with their time.

     KA9Q-NOS - Atari port - David Nash - dnash@chaos.demon.co.uk
     Linux/m68k - Roman Hodek - rnhodek@cip.informatik.uni-erlangen.de
     MiNT NET - Kay Roemer - roemer@hera.rbi.informatik.uni-frankfurt.de
     TUW-TCP  - Maintainer - Peter Mayer - pm@fortec.tuwien.ac.at
     UPOINT Light - Stefan Brusch - brusch@eslapion.sh.sub.org


XV. Contributors:


     Resources:   

	FYI4.TXT (located at ds.internic.net under/resource-guide/fyi )

	Linux	Information Sheet v4.1, 31 March 1994 by Michael K. Johnson,
		johnsonm@nigel.vnet.net
		(located tsx-11.mit.edu:/pub/linux/docs/INFO-SHEET)
		linux/m68k-faq by Joerg Mayer <jmayer@informatik.uni-kl.de>


     Human: Denesh Bhabuta, David Dulfer, Entropy, Robert Evans, Stephe 
Lewis Foskett, Tim Gallivan, Roland Given, Johann Haider, Theo Janssen, 
Wolfgang Ley, Jeff McWilliams, Bill Miller, David Nash, Kay Roemer, Bart 
Schuller, Stephen Usher.

     Short list of contributors email addresses (Atari Users):

	entropy@gnu.ai.mit.edu
	Ley@rz.tu-clausthal.de
	chrish@qnx.com
	rgivan@cix.compulink.co.uk
	tj@aiscube.AIS-dortmund.de
	r.evans@ic.ac.uk 
	timg@ccwf.cc.utexas.edu 
	schuller@dutiws.twi.tudelft.nl 
	jh@fortec.tuwien.ac.at
	steve@earth.ox.ac.uk
	D.Bhabuta@cent1.lancs.ac.uk
	lancer@wpi.wpi.edu
	jjmcwill@mathlab.mtu.edu

     As always my address is dackerma@magnus.acs.ohio-state.edu or 
		ackerman.29@osu.edu or baldrick@terminator.rs.itd.umich.edu
