linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michel Lanners <mlan@cpu.lu>
To: rrschulz@cris.com
Cc: ldl@chpc.utah.edu, linuxppc-dev@lists.linuxppc.org
Subject: Re: stty < /dev/modem blocks???
Date: Thu, 16 Sep 1999 09:22:41 +0200 (CEST)	[thread overview]
Message-ID: <199909160722.JAA00359@piglet.cpu.lu> (raw)
In-Reply-To: <v04210100b40584bafd82@[206.173.234.246]>


On  15 Sep, this message from Randall R Schulz echoed through cyberspace:
> As you know, the less-than (<) operator in all Unix shells opens the 
> file name given as an argument before it executes the command. In 
> order for an open() call on a TTY device to complete, the RS232 
> hardware signals that indicate the presence of an active device 
> connected to the port. In practice, this means that the DTR (data 
> terminal ready) signal must be asserted before the open call will 
> return.

OK, this sounds right, but how do you explain that I can get at the tty
settings with

stty -a < /dev/ttySx

for both of my serial ports, with absolutely nothing connected to them?

;-)

Michel

-------------------------------------------------------------------------
Michel Lanners                 |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes            |    Ask Questions.  Make Mistakes.
L-1710 Luxembourg              |
email   mlan@cpu.lu            |
http://www.cpu.lu/~mlan        |                     Learn Always. "


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~1999-09-16  7:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-14  3:33 stty < /dev/modem blocks??? Lou Langholtz
1999-09-15 17:27 ` Randall R Schulz
1999-09-16  7:22   ` Michel Lanners [this message]
1999-09-16 20:14     ` Randall R Schulz
1999-09-17  0:36     ` Paul Mackerras

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199909160722.JAA00359@piglet.cpu.lu \
    --to=mlan@cpu.lu \
    --cc=ldl@chpc.utah.edu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=rrschulz@cris.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).