🚀 go-pugleaf

trashman@crud.mn.org (Barry Schwartz) writes:
> 
> In article <1992Dec21.181154.2247@pwcs.stpaul.gov> derekt@pwcs.stpaul.gov wri
>  > 
>  > Clayton Haapala (clay@haapi.mn.org) wrote:
>  > : A prospective MN.Org member wants to know if he can run UUPC on an
>  > : 8088 Compaq computer.  Any of you UUPC experts out there know if this
>  > : can be done or not?
>  > : clay@haapi.mn.org
>  > 
>  > Depending on the version of uupc and other unix-mail/news-under-dos
>  > clones, it will probably run on an 8088.  I saw and worked with a
>  > version that ran on the 8086.   However, it may not be very feature
>  > rich, like some of the more powerful versions due to the limitations of
>  > the 8088.
> 
> Users who are interested in Netnews will find that there isn't any
> strong support for news in UUPC/extended, although it is currently
> under development.  There is an add-on called Snews available, but it
> is fragile.  (However, it doesn't eat as much disk space as the
> built-in UUPC news support will.)  MSDOS users who want a plug-in news
> system ought to check out Waffle and FSUUCP instead.  (These systems
> may, however, do less to protect against filename clashes than does
> late-model UUPC/extended.)
> 
Waffle should work for what you need and will provide news and mail services
on the dos machine.  I am fairly sure there shouldn't be much of a problem
in running this on an XT, though it would depend on the memory the machine
has, and how many news groups you want to get.

As for Waffle protecting against filename clashes, Waffle does a pretty good
job.  For starters, Waffle takes the long filenames (D.wahtever2a35d2) and
munges them down to a letter or two followed by what appears to be a sequence
number (end result would look like TA2A35D2.D), since the first part is 
generally the UUCP name of the system.  These files are then stored in a 
directory defined by SYSTEMS in \Waffle\UUCP (waf 1.65 version).  When UUXQT
is run, it looks in SYSTEMS and then goes to those directorys looking
for .X files to execute.  The end result is less possibility of filename
clashing and loss of data.

If I understand the problems mentioned above with UUPC and VIRTUAL_NAME,
Waffle should not have problems with this either.

[NOTE:  I do not have source to Waffle and don't know C, so I couldn't tell
you 100% if this is what is really happening with Waffle, my comments are 
based upon what I see Waffle doing and from the DOCS for Waffle].

Greg

.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.
.   TCS Consulting Services   P.O. Box 600008   St. Paul, MN  55106-0008    .
.   ..!srcsip!tcscs!zeta                 ..!src.honeywell.com!tcscs!zeta    .
.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.-=-.