Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 6 Apr 2010 07:02:19 -0500
From:      Jay Hall <jhall@socket.net>
To:        Sabine Baer <baerks@t-online.de>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: ttyu0 link down
Message-ID:  <BA020DCD-7736-4962-9427-20CD4903CF23@socket.net>
In-Reply-To: <20100406061449.GA55431@amd.catfish.ddns.org>
References:  <64467532-26D9-4AB6-8B73-7F892AB82B3B@socket.net> <20100406061449.GA55431@amd.catfish.ddns.org>

next in thread | previous in thread | raw e-mail | index | archive | help

On Apr 6, 2010, at 1:14 AM, Sabine Baer wrote:

>
>> Using cu -l /dev/ttyu0 I receive a message stating "link down".
>                   ^^^^^
> Shouldn't that be  /dev/cua0 instead?
>
> $ less /etc/ttys|grep mgetty
> cuau0  "/usr/local/sbin/mgetty"        unknown on insecure
>
> Sabine
>
> --  
> Good fences make good neighbours.                           (N.N.)
>
>
>
It does not make a difference whether I use /dev/cuau0 or not. I still  
receive the link down message.

This morning I changed the /dev/ttyu0 dialup on entry in /etc/ttys to / 
dev/ttyu0 dialup off secure, and after running kill -HUP 1, I was able  
to access the modem using either cu -l /dev/ttyu0 or cu -l /dev/cuau0.

Once I re-enabled /dev/ttyu0 in etc/ttys, I am no longer able to  
access the modem using either cu -l /dev/ttyu0 or cu -l /dev/cuau0.  I  
receive a "link down" message when trying to access the modem.

I am running FreeBSD 8.0-RELEASE-p2.

Any suggestions?

Thanks,


Jay 
  



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BA020DCD-7736-4962-9427-20CD4903CF23>