Date: Mon, 10 Mar 1997 10:02:16 -0600 (CST) From: Scott Bolte <scottb@cirque.moneng.mei.com> To: freebsd-questions@FreeBSD.ORG Cc: scottb@cirque.moneng.mei.com Subject: behavior change from 2.1 to 2.1.6 Message-ID: <199703101602.KAA05692@cirque.moneng.mei.com>
next in thread | raw e-mail | index | archive | help
Hey folks,
I've hit a snag when switching from 2.1 to 2.1.6. Uucp chat
sequences that worked under 2.1 fail under 2.1.6. I believe the
problem is related to the OS and may lie with the serial I/O
driver. I'm looking for any advice that might narrow my search
for a solution.
The problem can be shown with either uucico or cu. In both
cases I can connect to my local (internal) modem, dial out, and
connect to the remote modem. Then I am connected, perhaps via a
terminal server, to a login prompt on a SunOS 4.1 box. At that
point, only under 2.1.6, the login/password strings sent by my
box seemingly disappear. Duplicating the same sequence by hand
works just fine.
After much trial and error I eliminated configuration and
hardware issues as possible culprits. My test situation now is
to use the same hardware with two different boot disks; the
first boots 2.1.6 on a normal SCSI disk while the second boots
2.1 on a removable SCSI MO disk.
Taylor uucp appears to be the same for both releases. The
hardware is the same. I use the same chat sequences. I'm left
concluding that the behavior of the cuaa device has changed. I
haven't started comparing the sio driver code yet, but even if
I can regress to an earlier release of the driver, that is not
a good way to fix things. Especially if the sio driver has been
enhanced to be more sensitive to something instead of being
broken.
Any advice or recommendations that people care to share would
be appreciated.
Thank you,
Scott
P.S. Btw, I've searched the 2.1.6 FAQ and Handbook. I tried
searching the mailing list archives to no avail. There
don't seem to be any open problem reports that match. I
thought I used to be able to access the cvs logs on
www.FreeBSD.org; but either I could not find the service
or it is no longer available.
--
Scott Bolte scottb@mei.com Marquette Medical Systems
As anyone here will tell you: I speak for myself.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703101602.KAA05692>