Newsgroups: comp.archives
Path: utzoo!news-server.csri.toronto.edu!ox.com!emv
From: dillon@overload.Berkeley.CA.US (Matthew Dillon)
Subject: [amiga-uucp] AmigaUUCP 1.13
Message-ID: <1991Mar6.015313.16452@ox.com>
Followup-To: alt.sys.amiga.uucp
Sender: emv@ox.com (Edward Vielmetti)
Reply-To: dillon@overload.Berkeley.CA.US (Matthew Dillon)
Organization: Not an Organization
References: <dillon.4587@overload.Berkeley.CA.US>
Date: Wed, 6 Mar 1991 01:53:13 GMT
Approved: emv@ox.com (Edward Vielmetti)
X-Original-Newsgroups: alt.sys.amiga.uucp

Archive-name: mail/uucp/dillon-amiga-uucp/1991-03-03
Archive: uunet.uu.net:/amiga-sources/dillon/uucp113.*.lzh [192.48.96.2]
Original-posting-by: dillon@overload.Berkeley.CA.US (Matthew Dillon)
Original-subject: AmigaUUCP 1.13
Reposted-by: emv@ox.com (Edward Vielmetti)


    AmigaUUCP 1.13 is now available via ftp to uunet.uu.net, patches from
    1.12 to 1.13 have been posted to alt.sys.amiga.uucp.patches and are
    also available on uunet.uu.net .  You can also use
    BITFTP@pucc.princeton.edu to retrieve the stuff, send a message to
    that email address with a subject line of HELP and a message body
    containing a single line, HELP, for information on how to use BITFTP.

    1.13 is the 'final' release that 1.08 was supposed to be until the next
    major release.  The changes between 1.12 and 1.13 is in BATCHNEWS,
    which now uses a different lock file name (it was locking up uuxqt),
    and a new config variable, LockDir, which allows you to specify the
    directory in which locks are created.  Also, uuarchive and amiuufilter
    no longer hard code directories, but use the appropriate config
    entries.

    The latter causes many executables to be 'different' but fixes a bug
    in pre 37.39 kickstarts (in OS 2.0) that causes the RAM disk to loose
    memory... you simply set this variable to the temporary partition
    on your hard drive, to RAD:, or elsewhere -- that isn't in RAM:
    Since most executables are effected by the lib source patch, it is
    not economical to post them all to patches.

    The next release will contain a completely new locking system by
    CAW that uses a shared library & message ports, but I did not want
    to include it in 1.13 because I have already made the mistake of
    including things that break otherthings (i.e. inadequate testing)

					    -Matt

--

    Matthew Dillon	    dillon@Overload.Berkeley.CA.US
    891 Regal Rd.	    uunet.uu.net!overload!dillon
    Berkeley, Ca. 94708
    USA