From owner-freebsd-current Thu Mar 11 0: 5:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-28.ppp.wenet.net [206.15.85.28]) by hub.freebsd.org (Postfix) with ESMTP id 151A314CF9 for ; Thu, 11 Mar 1999 00:05:22 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id AAA41750; Thu, 11 Mar 1999 00:04:40 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Thu, 11 Mar 1999 00:04:40 -0800 (PST) From: Alex Zepeda To: Chuck Robey Cc: Matthew Dillon , Peter Jeremy , current@FreeBSD.ORG Subject: Re: panic: zone: entry not free In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 10 Mar 1999, Chuck Robey wrote: > You know, guys, for programmers, wanting immediate panics on stuff like > this is great, but there isn't one user in a thousand that wants this. > If you make this kinda stuff default on a version *other than* current > (current being by definition, for programmers/developers only) then > you're going to hear bloody murder, and you guys will be doing vast > damage to FreeBSD's reputation. Hmm. Well think of it this way. What happens when the kernel doesn't panic but manages to accidentally wipe out your file system without warning? or perhaps just loose some of the more important data on the HDD? What kind of reaction do you expect then? > Users don't want panics, and they don't care why, they just want > things to work. True enough, but at what cost? - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message