From owner-freebsd-hackers Wed Jul 14 2:54: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from aussie.cs.mu.OZ.AU (dhcp2966.ietf.uninett.no [128.39.29.66]) by hub.freebsd.org (Postfix) with ESMTP id 0F3AE14EC3 for ; Wed, 14 Jul 1999 02:53:47 -0700 (PDT) (envelope-from kre@cs.mu.OZ.AU) Received: from cs.mu.OZ.AU (localhost [127.0.0.1]) by aussie.cs.mu.OZ.AU (8.8.8/8.8.8) with ESMTP id LAA08349; Wed, 14 Jul 1999 11:04:16 +0200 (CEST) From: Robert Elz To: Matthew Dillon Cc: Jason Thorpe , freebsd-hackers@FreeBSD.ORG, tech-userlevel@netbsd.org Subject: Re: Replacement for grep(1) (part 2) In-reply-to: Your message of "Tue, 13 Jul 1999 15:37:26 PDT." <199907132237.PAA81422@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 14 Jul 1999 11:04:15 +0200 Message-ID: <8347.931943055@cs.mu.OZ.AU> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Date: Tue, 13 Jul 1999 15:37:26 -0700 (PDT) From: Matthew Dillon Message-ID: <199907132237.PAA81422@apollo.backplane.com> | allocation - most everything is statically allocated and if the system | tries to use more, it panics and reboots. I'm finding it difficult to continue taking seriously anyone who believes that "crash and reboot" is a suitable response to anything at all. I have implemented embedded systems, they most certainly did dynamic memory allocation (no way to fit in available memory resources if everything was pre-allocated) and "panic and reboot" is not something I would consider as a satisfactory tactic. kre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message