Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 13 Nov 1995 02:10:13 -0800 (PST)
From:      Brian Litzinger <brian@MediaCity.com>
To:        flambe@[205.206.107.2]
Cc:        freebsd-questions@freebsd.org
Subject:   Re: dialup modems
Message-ID:  <199511131010.CAA18408@MediaCity.com>
In-Reply-To: <TCPSMTP.15.11.13.1.28.34.2379581633.155473@perseus.digital-rain.com> from "flambe@[205.206.107.2]" at Nov 13, 95 01:28:34 am

next in thread | previous in thread | raw e-mail | index | archive | help
> 
> 
> 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199511131010.CAA18408>