home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!mcsun!news.funet.fi!hydra!klaava!torvalds
- From: torvalds@klaava.Helsinki.FI (Linus Torvalds)
- Subject: Re: Serial I/O in 99pl3-4
- Message-ID: <1993Jan23.220924.26333@klaava.Helsinki.FI>
- Organization: University of Helsinki
- References: <btenison.930123104426@tesla.ee.eng.auburn.edu> <1js994INNfkq@cobra.cs.ubc.ca>
- Date: Sat, 23 Jan 1993 22:09:24 GMT
- Lines: 19
-
- In article <1js994INNfkq@cobra.cs.ubc.ca> edmonds@cs.ubc.ca (Brian Edmonds) writes:
- >
- >Well, I'm not exactly having trouble, but the behaviour did change when
- >I went from p0 to p3 (might have been p2 to p3 even, I'm fuzzy on that
- >:). The ports generally seem to work fine, except for one anomaly.
- >When I hang up from our local annex, I used to get the NO CARRIER
- >message from the modem when it disconnected. Now, instead, I get no
- >message, and if I type anything to the modem after the disconnet, I get
- >an I/O error (unable to write or somesuch). So far this hasn't been a
- >problem, but it does seem to indicate a bug somewhere. BTW, I'm not
- >using the serial autoconfigure option.
-
- Put the terminal line in CLOCAL mode - the above behaviour is normal and
- due to the new hangup routines. If you are not running a getty on a
- serial line, you should probably do a "stty clocal < /dev/ttyXX" for the
- line in your /etc/rc.local, telling the kernel not to do hangups on CD
- drops etc..
-
- Linus
-