Path: utzoo!mnetor!uunet!husc6!bloom-beacon!tut.cis.ohio-state.edu!mailrus!delrio!panchovilla.cc.umich.edu!emv
From: emv@panchovilla.cc.umich.edu (Edward Vielmetti)
Newsgroups: comp.mail.uucp
Subject: protocol negotiation in 4.3 uucp
Message-ID: <3ac9315f.c6e5@delrio.cc.umich.edu>
Date: 11 Mar 88 09:33:48 GMT
Sender: usenet@delrio.cc.umich.edu
Reply-To: emv@umix.cc.umich.edu (Edward Vielmetti)
Organization: University of Michigan Computing Center, Ann Arbor
Lines: 15
UUCP-Path: {uunet,rutgers}!umix!emv


At umix many uucp connections come in over the Merit computer network,
which would be a good network to run f protocol over: mostly error-free,
7 bit, and packet-switched underneath.  I think that it won't choke on
256 byte data packets, at least at the speed we're sending them.

With HoneyDanber it's quite easy to stick it into f protocol with
a flag in the Devices file.  What I can't see in 4.3 uucp is how to
do the same.  Nothing in the L.sys line indicates protocol selection,
and everything in cntrl.c in 4.3 makes me think that it tries t if 
it's TCP, f if it's PAD, and defaults to g.  

Assuming that it's reasonable to run f protocol on dial-ups, and without
modifying cntrl.c too much yet, is there any way to force f protocol on an
ACU connection?
Edward Vielmetti, U of Michigan mail group.