Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!metro!sequoia!ultima!kralizec.zeta.org.au!kralizec.zeta.org.au!not-for-mail From: bde@kralizec.zeta.org.au (Bruce Evans) Newsgroups: comp.os.386bsd.questions Subject: Re: sio - problem with login hanging up Date: 25 Jul 1993 06:32:40 +1000 Organization: Kralizec Dialup Unix Sydney: +61-2-837-1183 V.32bis Lines: 25 Message-ID: <22s698INNdf3@kralizec.zeta.org.au> References: <22epf0INNt7q@kralizec.zeta.org.au> <CAILGB.1B7@sugar.NeoSoft.COM> <22mg9nINNlud@kralizec.zeta.org.au> <CAn28H.6AI@sugar.NeoSoft.COM> NNTP-Posting-Host: kralizec.zeta.org.au In <CAn28H.6AI@sugar.NeoSoft.COM> peter@NeoSoft.com (Peter da Silva) writes: >In article <22mg9nINNlud@kralizec.zeta.org.au> bde@kralizec.zeta.org.au (Bruce Evans) writes: >> I don't think not having a default configuration is broken. >I do. Having a way to *change* the default is correct, but any device should >reset itself on last close (and that includes /dev/console, by the way... >logging out should knock you back to something sane no matter what you >did to your console!). Getty shouldn't have to know the behaviour of every >device that's out there. OK, you have convinced me. By the way, the default settings for sio will be the same as the initial settings now - `clocal -echo*' :-). Insane for humans, sane for programs. >> There ought to be stuff in /etc/gettytab >> to control this. I don't think there is. Anyway, it would get blown >> away when getty sets fixed defaults before exec'ing login. >It shouldn't do that, either. The way all 386BSD programs blow away any >local settings all the time is a bug. Andrew Chernov has fixed getty. -- Bruce Evans bde@kralizec.zeta.org.au