home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!portal!lll-winken!cert!netnews.upenn.edu!dsinc!cs.widener.edu!iggy.GW.Vitalink.COM!pacbell.com!decwrl!sdd.hp.com!saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!rpi!scott.skidmore.edu!psinntp!psinntp!cubetech.com!imladris!andrew
- From: andrew@cubetech.com
- Newsgroups: comp.sys.next.misc
- Subject: Re: Patching g protocol in uucico binary.
- Message-ID: <1992Nov5.121258.2692@cubetech.com>
- Date: 5 Nov 92 12:12:58 GMT
- References: <2230@ltb.ltb.bso.nl>
- Organization: Cube Technologies, Inc.
- Lines: 27
-
- In article <2230@ltb.ltb.bso.nl> gerben@rna.indiv.nluug.nl writes:
- >Well I could have guessed people telling me to go Taylor :-) I started using
- >Taylor in the early 1.03 days and lots too much time with the "locked port"
- >problem that afterwards has been solved. I am now waiting for the final
- >release of 1.04 and will then go for Taylor again.
-
- If I remember correctly, Ian fixed it the day after you stopped using
- it...
-
- >NeXT should go Taylor with the next release. It is far superior to their
- >default stuff. They went with gcc, here is another opportunity to have the
- >best available thing around: Taylor uucp.
-
- I suggested this to NeXTEdge yesterday (I think it was yesterday...
- human time seems to have no meaning to me anymore). Apparently the
- Taylor config files (which are mainly in english) and the fact that it
- isn't so damned picky about things like blank lines and related
- stupidities in NeXT's current UUCP would be the biggest reason to move
- to Taylor for NeXT (apparently NeXTEdge gets a lot of UUCP tech
- calls). There's a chance it may end up in 4.0...
-
-
- andrew
- --
- andrew@cubetech.com | "Carpe Nocturn - I get more work done after
- Andrew Loewenstern | 2 a.m. than most people do all day."
- Cube Technologies, Inc. | - Simson Garfinkle
-