Matthew Wilcox <matthew@xxxxxx> writes: > Connect two machines with a serial cable. On the victim: > > willy@rowlf:~$ cat </dev/ttyS1 > > Now, let's find out which ttyS on the other machine is connected ... > > willy@teeth:~$ echo foo >/dev/ttyS1 > -bash: echo: write error: Input/output error > > Oops, that's not a serial port. No output on rowlf, as expected. > OK, carrying on ... > > willy@teeth:~$ echo bar >/dev/ttyS0 > > And yet on rowlf, we now see: > > foo > bar > > Looks like there's an error path that doesn't throw away data on -EIO. Read the thread starting here: <http://lists.gnu.org/archive/html/bug-bash/2007-09/msg00020.html>. Andreas. -- Andreas Schwab, SuSE Labs, schwab@xxxxxxx SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." - To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
