From owner-freebsd-questions  Fri Oct 20 16:39:41 1995
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id QAA24943
          for questions-outgoing; Fri, 20 Oct 1995 16:39:41 -0700
Received: from news.us.world.net (news.us.world.net [192.243.32.19])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA24938
          for <freebsd-questions@freebsd.org>; Fri, 20 Oct 1995 16:39:39 -0700
Received: from merix.merix.com (merix.com [198.145.172.40]) by news.us.world.net (8.6.9/8.6.9) with SMTP id QAA06558 for <freebsd-questions@freebsd.org>; Fri, 20 Oct 1995 16:39:41 -0700
Received: from sandy.merix.com by merix.merix.com (4.1/1.1) id AA25716; Fri, 20 Oct 95 16:37:08 PDT
Received: by sandy.merix.com (4.1/8.0)
	id AA06356; Fri, 20 Oct 95 16:37:57 PDT
Date: Fri, 20 Oct 95 16:37:57 PDT
From: troyc@sandy.merix.com (Troy Curtiss)
Message-Id: <9510202337.AA06356@sandy.merix.com>
To: freebsd-questions@freebsd.org
Subject: Is getty busted? or just me?
Sender: owner-questions@freebsd.org
Precedence: bulk

I am using SNAP2.1.0-951005.  When I turn a getty on my modem (ttyd0), I can't
use the callout device to grab the /dev/cuaa0 device.  Without getty running
everything works fine.  My modem is not asserting the carrier line, but looking
at a ps -alx shows that the getty is waiting on ttyin rather than siodcd.  I
have an identical machine running 1.1.5.1R just fine with identical (even
identical initial and lock-state device settings) modem/hardware setup.  Am I
forgetting something really dumb, or is the problem in the sio driver/getty?
Thanks,

Troy