linux-kernel - Re: 2.6.25.3: serial problem (minicom)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 16 Jun 2008 11:13:29 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"R.L. Horn" <lists@...tcheap.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.25.3: serial problem (minicom)

> But, then, what is the relationship between CLOCAL and DTR/RTS supposed to 
> be?  Presumably, it should prevent a SIGHUP from being raised when DSR 
> goes low, but beyond that, it all seems rather ill-defined.  Throw in B0, 

CLOCAL is defined to "ignore modem control lines"

> which the SUS strongly implies should unconditionally lower DTR and RTS, 
> and the CRTSCTS flag, and the waters really get murky.  It looks to me 
> like the only thing you can say for certain is that CLOCAL will cause DSR 
> to be ignored...and for anything else you're on your own.

Whatever it implies the behaviour should not have changed between 2.6.24
and 2.6.25. Nobody AFAIK sat down and decided to change it.

> 
> Mind you, all this just suggests that POSIX kinda sucks, which is hardly 
> an earth-shattering revelation.

Standards are part written spec and a large part an existing tradition
around that standard. The tradition is often the most important bit.

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/