Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!uunet!psinntp!uuneo!sugar!peter From: peter@NeoSoft.com (Peter da Silva) Subject: Re: sio - problem with login hanging up Organization: NeoSoft Communications Services -- (713) 684-5900 Date: Wed, 21 Jul 1993 12:31:22 GMT Message-ID: <CAILGB.1B7@sugar.NeoSoft.COM> References: <226elvINNt54@kralizec.zeta.org.au> <CADpLy.8Dw@sugar.NeoSoft.COM> <22epf0INNt7q@kralizec.zeta.org.au> Lines: 32 In article <22epf0INNt7q@kralizec.zeta.org.au> bde@kralizec.zeta.org.au (Bruce Evans) writes: > In <CADpLy.8Dw@sugar.NeoSoft.COM> peter@NeoSoft.com (Peter da Silva) writes: > >In article <226elvINNt54@kralizec.zeta.org.au> bde@kralizec.zeta.org.au (Bruce Evans) writes: > >> work around using "stty -clocal </dev/sioNN" in /etc/rc. > >This shouldn't work. When stty closes the port, it should revert to the > >default configuration. > Because it is the last close? The old driver didn't do that. Why does that matter? A last close on any tty type device should reset it to a default configuration. You shouldn't have to create special cases to retain default behaviour, as in the case of a user setting clocal and hanging up. Changing the default should be a rare case, and can be handled with an ioctl. The old driver was broken, so let's keep that broken behaviour? > These problems are easy to fix by having a parent process (e.g. init) > restore the previous state. Sure, you can create workarounds for it, but then they have to be replicated throughout the system, for any program that wants to use a serial port. One of the nicest things about UNIX in the old days was the interfaces were simple, consistent, and required not a lot of code to do the normal sorts of things. Now, this is a very MINOR deviation, but it is one and it's easy to fix. -- Peter da Silva. <peter@sugar.neosoft.com>. `-_-' Hefur pu fadmad ulfinn i dag? 'U` "Det er min ledsager, det er ikke drikkepenge."