🚀 go-pugleaf

In article <1943@ncoast.UUCP>, allbery@ncoast.UUCP (Brandon Allbery) writes:
> As quoted from <1683@hoptoad.uucp> by pozar@hoptoad.uucp (Tim Pozar):
> | 
> |    I picked off the uuslave code.  Could you point me the direction of where
> | you got it from?   There seems to be some header files that I'm unfamiler
> | with and weren't included with the code.  Mucho functions I don't fully
> | know what they need, etc...

	I took a bang at it and found that it makes a variety of system
calls that my Lattice C compiler doesn't support. On the other hand, if
anyone is interested in a totally kluged version, I have hacked, ifdef'ed,
and frobbed the darn thing so I think it will compile with Lattice or
Microsoft C. I could either send uuencoded executables, with no guarantee
of functionality, source, or both. Rather that post to the whole net,
just email to me if you're interested.

	Changes I had to make: no ioctl() or stat(). I commented out the
ioctl() and made a stat() look-alike. (uuslave uses stat largely to see
if things are there, rather than caring about modes, etc.)  I suppose there
*might* be a chance it would work if you used the DOS 'mode' command to
set baud rates first, *then* started uuslave. Other problem: I'm too 
busy to sort it out and figure what it does. I have added some comments,
but other than that it's still a totally undocumented gadget...

++mjr;
-- 
{decuac}!gouldsd!mjranum || {decuac}!osiris!mjranum

"It is better to shred the bugger than to bugger the shredder."
					-ancient doltic proverb.