Date: Wed, 21 Oct 1998 09:01:42 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Brett Glass <brett@lariat.org> Cc: "Steve Friedrich" <SteveFriedrich@Hot-Shot.com>, "Studded" <Studded@gorean.org>, "bugs@FreeBSD.ORG" <bugs@FreeBSD.ORG> Subject: Re: No terminal echo after certain commands Message-ID: <27154.908953302@critter.freebsd.dk> In-Reply-To: Your message of "Tue, 20 Oct 1998 19:15:26 MDT." <4.1.19981020191142.06b355b0@mail.lariat.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <4.1.19981020191142.06b355b0@mail.lariat.org>, Brett Glass writes: >At 08:57 PM 10/20/98 -0400, Steve Friedrich wrote: > >>It REALLY shouldn't be fixed. It is important to keep INTR handling to >>the minimum possible exit code possible. Adding "clean-up" code will >>add potential that programs will "hang" in this clean up code and INTR >>will no longer work all the time for that program. > >It's possible that anything programmed badly will hang. However, failure >to return the console to usability after a quick exit is not optional. >Otherwise, it does no good to make a quick exit. Ok: can it! move this stuff to -chat or kill it. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?27154.908953302>