From owner-freebsd-questions@FreeBSD.ORG Wed Sep 28 12:27:04 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AEEDE16A41F for ; Wed, 28 Sep 2005 12:27:04 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id D13AC43D4C for ; Wed, 28 Sep 2005 12:27:03 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from flame.pc (aris.bedc.ondsl.gr [62.103.39.226]) by kane.otenet.gr (8.13.4/8.13.4/Debian-1) with SMTP id j8SCR1HU013541; Wed, 28 Sep 2005 15:27:01 +0300 Received: from flame.pc (flame [127.0.0.1]) by flame.pc (8.13.4/8.13.4) with ESMTP id j8SCQPu9002514; Wed, 28 Sep 2005 15:26:25 +0300 (EEST) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost) by flame.pc (8.13.4/8.13.4/Submit) id j8SCQP7c002513; Wed, 28 Sep 2005 15:26:25 +0300 (EEST) (envelope-from keramida@freebsd.org) Date: Wed, 28 Sep 2005 15:26:24 +0300 From: Giorgos Keramidas To: Tobias Mohrl?der Message-ID: <20050928122624.GB2445@flame.pc> References: <433AA66C.70603@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <433AA66C.70603@web.de> Cc: freebsd-questions@freebsd.org Subject: Re: Should I write bug report? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Sep 2005 12:27:04 -0000 On 2005-09-28 14:19, Tobias Mohrl?der wrote: > Hello everybody, > > I've experienced a bug that causes a reboot under FreeBSD 5.4 and I > wonder if I should write an 'open' bug report or a 'secret' mail to > one of the FreeBSD developers. This bug doesn't seem to be > hardware-related and is easily reproducible by a normal user (with no > special privileges), so the latter is perhaps the better option. If the problem is security related and you can verify that it is still unfixed in the latest version of the RELENG_5 branch, then please contact the security officer team and they'll tell you what to do. If the problem is not security related, yes go ahead and file a bug report using send-pr(1) or the web interface. - Giorgos