Short: Amiga port of the NetBSD 'sup' client and server (+src) Author: bernie@shock.cosmos.it (Bernardo Innocenti) Uploader: bernie shock cosmos it (Bernardo Innocenti) Type: misc/unix Architecture: m68k-amigaos DESCRIPTION Sup is a program used for upgrading collections of files from other machines to your machine. You execute sup, the client program, which talks over the network using IP/TCP to a file server process. The file server process cooperates with sup to determine which files of the collection need to be upgraded on your machine. AMIGA PORT I am a NetBSD user since version 1.0 and I've recently switched to the NetBSD-current system. Soon, I found out that tracking the source changes manually with ftp was a pain. The official way to track the -current source tree is using the 'sup' system command to have it updated automatically from a sup server. Unfortunately, sup was only available for the NetBSD side of my Amiga, while I usually connect to the Internet from the AmigaOS side. The solution was porting sup to the Amiga. With the GeekGadgets developer tools, this was a very easy task. I got the source code for sup from the NetBSD-current source tree and made some minor changes in the Makefile and other files to compile it in a GeekGadget's environment. AMIGA NOTES Sup requires ixemul.library and ixnet.library, along with any TCP/IP stack supported by the ixnet.library (tested with AmiTCP). The supfilesrv and supscan commands are untested. AMIGA USAGE Read the "tracking-current" instructions on the www.netbsd.org, and the README.sup file which you can find in the NetBSD-current source directory on ftp.netbsd.org or one of its mirrors. Both files have been included in this distribution (see in bsd_docs/) for your convenience. I use the BerkeleyFastFileSystem (BFFS) to access my local copy of the NetBSD kernel sources in /usr/src. I mounted my /usr partition, created a supfile in /usr as described in README.sup and then sup did all the rest for me.