Date: Sun, 10 Jun 2001 14:53:22 +0300 From: Valentin Nechayev <netch@iv.nn.kiev.ua> To: Bruce Evans <bde@zeta.org.au> Cc: Maxim Sobolev <sobomax@FreeBSD.ORG>, current@FreeBSD.ORG Subject: Re: Terminal line discipline is broken [sorta] Message-ID: <20010610145322.A461@iv.nn.kiev.ua> In-Reply-To: <Pine.BSF.4.21.0106071155480.1587-100000@besplex.bde.org>; from bde@zeta.org.au on Thu, Jun 07, 2001 at 12:04:10PM %2B1000 References: <3B1E4979.F7D02680@FreeBSD.org> <Pine.BSF.4.21.0106071155480.1587-100000@besplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Thu, Jun 07, 2001 at 12:04:10, bde (Bruce Evans) wrote about "Re: Terminal line discipline is broken [sorta]": > This may be a bug in tcsh. Do you really think that shell should not modify signal handling policy which he obtained as legacy from login? And application which resets them to appropriate position is buggy? > > It is very strange, but control keys [^C,^Z etc] no longer work (nop) > > in the /bin/sh and bash2 after today's build/installworld. I see this > > misbehaviour on two machines. > PAM now blocks keyboard signals when reading the password, and usually > forgets to unblock them. I use the workaround of backing out the broken > code (rev.1.4 of /usr/src/contrib/libpam/libpam_misc/misc_conv.c). > > Even more strange that /bin/tcsh doesn't > > have this problem. My ktracing of bash (2.04) shows that it isn't really set procmask to own values, but uses legacy value. Maybe I'm wrong, but this seems that sh & bash are buggy, not tcsh. /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010610145322.A461>