From owner-freebsd-bugs Wed Oct 21 00:07:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23631 for freebsd-bugs-outgoing; Wed, 21 Oct 1998 00:07:03 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA23626 for ; Wed, 21 Oct 1998 00:07:01 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id JAA27156; Wed, 21 Oct 1998 09:01:42 +0200 (CEST) To: Brett Glass cc: "Steve Friedrich" , "Studded" , "bugs@FreeBSD.ORG" Subject: Re: No terminal echo after certain commands In-reply-to: Your message of "Tue, 20 Oct 1998 19:15:26 MDT." <4.1.19981020191142.06b355b0@mail.lariat.org> Date: Wed, 21 Oct 1998 09:01:42 +0200 Message-ID: <27154.908953302@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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