Re: Goals for 1.3?
Peter> - For serial communication use ttyS* devices instead of cua* devices
Brian> Could you give reasons for this, please.
He did, in the post I enclude here again. You could have tried your very own
search engine to make up for failing memory :-))
--------------- old post by Peter Tobias follows here -----------------------
From: "Peter Tobias" <firstname.lastname@example.org>
Subject: 1.2 modem devices
Date: Sun, 16 Jun 1996 00:48:29 +0200 (MET DST)
IMHO we should change our comm packages for Debian 1.2 to use
/dev/ttyS* instead of /dev/cua*:
Theodore Y. Ts'o wrote:
> From email@example.com Tue May 14 02:34:03 1996
> Date: Mon, 13 May 1996 13:51:04 -0400
> Message-Id: <9605131751.AA13288@dcl.MIT.EDU>
> From: "Theodore Y. Ts'o" <firstname.lastname@example.org>
> To: Tony Nugent <email@example.com>
> Cc: firstname.lastname@example.org, email@example.com
> In-Reply-To: Tony Nugent's message of Mon, 13 May 1996 07:57:09 +1000,
> Subject: Re: /dev/cua? Vs /dev/ttyS? (was: Re: co-existance of pppd and mgetty ?)
> Address: 1 Amherst St., Cambridge, MA 02139
> Phone: (617) 253-8091
> Sender: firstname.lastname@example.org
> Precedence: bulk
> Date: Mon, 13 May 1996 07:57:09 +1000
> From: Tony Nugent <email@example.com>
> Can someone kindly explain the difference between the /dev/cua? and
> /dev/ttyS? devices?
> /dev/ttySxx devices are fully POSIX-compliant TTY devices. If you are
> only going to be using one set of tty devices, you should be using
> /dev/cuaXX devices are different from /dev/ttySXX in two ways --- first
> of all, they will allow you to open the device even if CLOCAL is not set
> and the O_NONBLOCK flag was not given to the open device. This allows
> programs that don't use the POSIX-mondated interface for opening
> /dev/ttySxx devices to be able to use /dev/cuaXX to make outgoing phone
> calls on their modem (cu stands for "callout", and is taken from SunOS).
> The second way in which /dev/cuaXX differs from /dev/ttySXX is that if
> they are used, they will trigger a simplistic kernel-based locking
> scheme: If /dev/ttySXX is opened by one or more processes, then an
> attempt to open /dev/cuaXX will return EAGAIN. If /dev/cuaXX is opened
> by one or more processes, then an attempt to open /dev/ttySXX will
> result the open blocking until /dev/cuaXX is closed, and the carrier
> detect line goes high.
> While this will allow for simple lockouts between a user using a modem
> for callout and a getty listening on the line for logins, it doesn't
> work if you need to arbitrate between multiple programs wanting to do
> dialout --- for example, users wanting to do dialout and UUCP.
> I originally implemented the cuaXX/ttySXX lockout mechanism back before
> FSSTND established a standard convention for the use of tty lock files.
> Now that it's there, people should use the tty lock files and not try
> using /dev/cuaXX. The only reason why /dev/cuaXX hasn't disappeared yet
> is for backwards compatibility reasons.
> - Ted
Peter Tobias EMail:
Fachhochschule Ostfriesland firstname.lastname@example.org
Fachbereich Elektrotechnik und Informatik email@example.com
Constantiaplatz 4, 26723 Emden, Germany firstname.lastname@example.org
PGP key fingerprint = B2 49 75 BF 44 2C B7 AA 50 CB 19 7D 80 F7 CB DC
http://rosebud.sps.queensu.ca/~edd email@example.com firstname.lastname@example.org
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com