[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gpsd-dev] What is our current bug state?
From: |
Eric S. Raymond |
Subject: |
Re: [gpsd-dev] What is our current bug state? |
Date: |
Mon, 2 Feb 2015 02:56:46 -0500 |
User-agent: |
Mutt/1.5.23 (2014-03-12) |
Hal Murray <address@hidden>:
> That's depending on the system or the previous user to leave CLOCAL set.
>
> Linux leaves that stuff alone after a close. So you can use things like stty
> to set things up the way your program needs them without having to change any
> code.
>
> I'm pretty sure some NetBSD and/or FreeBSD have a shadow TTY and copy the
> state from that shadow on close and/or just before open. I'll try to get
> more info if you think it will help. stty on the shadow does what you want.
>
> If you decide to just remove the O_NONBLOCK from the open, please add a
> comment referring to this discussion.
Open is now being done with CLOCAL.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
Re: [gpsd-dev] What is our current bug state?, Hal Murray, 2015/02/01
Re: [gpsd-dev] What is our current bug state?, Greg Troxel, 2015/02/02
- Re: [gpsd-dev] What is our current bug state?, Eric S. Raymond, 2015/02/02
- Re: [gpsd-dev] What is our current bug state?, Hal Murray, 2015/02/02
- Re: [gpsd-dev] What is our current bug state?, Eric S. Raymond, 2015/02/02
- Re: [gpsd-dev] What is our current bug state?, Hal Murray, 2015/02/02
- Re: [gpsd-dev] What is our current bug state?, Gary E. Miller, 2015/02/02
- Re: [gpsd-dev] What is our current bug state?, juergen perlinger, 2015/02/03