From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Sun, 23 Mar 2014 20:32:07 -0400 To: 9fans@9fans.net Message-ID: In-Reply-To: <20140323220205.1AE20B827@mail.bitblocks.com> References: <40707a306f2cb1caf97b21f639f8a9f5@brasstown.quanstro.net> <590d4ca16a9d61afc0bdc6b4d16862af@brasstown.quanstro.net> <20140323213208.A38E8B827@mail.bitblocks.com> <9838602a5db28f523fec74b5e8a9c2ab@brasstown.quanstro.net> <20140323220205.1AE20B827@mail.bitblocks.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] usb/serial control open Topicbox-Message-UUID: ced699a8-ead8-11e9-9d60-3106f5b1d025 > > i think it is even easier to set the state up properly with cpurc or > > consolefs' configuration file, and have the various programs not even > > care that they're talking to a serial port. > > Not my experience. Occasionally programs do have to care about > some serial port parameters and if such a program crashes you > have a partially working interface. Think CTS/RTS state etc. doesn't sound like the common case. in any event, seems like a program fiddling with CTS/RTS should do the whole setup, especially if it plans on crashing. :-) - erik