From owner-freebsd-questions Mon Nov 13 02:09:29 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id CAA19658 for questions-outgoing; Mon, 13 Nov 1995 02:09:29 -0800 Received: from MediaCity.com (root@easy1.mediacity.com [205.216.172.10]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id CAA19641 for ; Mon, 13 Nov 1995 02:09:23 -0800 Received: (from brian@localhost) by MediaCity.com (8.6.11/8.6.9) id CAA18408; Mon, 13 Nov 1995 02:10:13 -0800 From: Brian Litzinger Message-Id: <199511131010.CAA18408@MediaCity.com> Subject: Re: dialup modems To: flambe@[205.206.107.2] Date: Mon, 13 Nov 1995 02:10:13 -0800 (PST) Cc: freebsd-questions@freebsd.org In-Reply-To: from "flambe@[205.206.107.2]" at Nov 13, 95 01:28:34 am X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1025 Sender: owner-questions@freebsd.org Precedence: bulk > > > I am running freebsd 2.0.5 on a 486 66 with 12 meg ram, and have a 2400 > baud modem on com 1 and 144 on com 2 I am trying (unsucessfully) to > get my 144 to answer the phone, or dial out. > > I followed the instructions for setting up a 144 on com 2. > > -MAKEDEV ttyd1 > edit gettytab to include the v32modem as listed in the manual (19200) > edit ttys such that ttyd1 is set up the same as the example > I dont understand what to do with the rc.serial file. FreeBSD, I believe, uses a kernel based interlocking mechanism for sharing a single modem for dial in/out. You run getty on /dev/ttyd1 and you run your dialout programs on /dev/cuaa1 You need to MAKEDEV each device if they don't exist. You also have the choice of running mgetty instead of getty, which uses user level locking instead. In which case, you run mgetty and your dialout programs on /dev/cuaa1. However, all your dialout programs have to use the same user level locking scheme that mgetty does. Brian Litzinger brian@mediacity.com