From owner-freebsd-current@FreeBSD.ORG Thu Aug 9 12:26:08 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 70FFC16A419 for ; Thu, 9 Aug 2007 12:26:08 +0000 (UTC) (envelope-from dan@danneh.org) Received: from aqua.bluespider.org (aqua.bluespider.org [69.46.20.18]) by mx1.freebsd.org (Postfix) with ESMTP id 4D3AC13C459 for ; Thu, 9 Aug 2007 12:26:08 +0000 (UTC) (envelope-from dan@danneh.org) Received: from localhost ([127.0.0.1] helo=www.danneh.org) by aqua.bluespider.org with esmtp (Exim 4.62) (envelope-from ) id 1IJ75P-00053I-Cq for freebsd-current@freebsd.org; Thu, 09 Aug 2007 13:25:55 +0100 Received: from 81.149.89.84 (SquirrelMail authenticated user dan) by www.danneh.org with HTTP; Thu, 9 Aug 2007 13:25:55 +0100 (BST) Message-ID: <4251.81.149.89.84.1186662355.squirrel@www.danneh.org> In-Reply-To: <200708090850.l798oJfL089684@lurza.secnetix.de> References: <200708090850.l798oJfL089684@lurza.secnetix.de> Date: Thu, 9 Aug 2007 13:25:55 +0100 (BST) From: dan@danneh.org To: freebsd-current@freebsd.org User-Agent: SquirrelMail/1.4.7 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Re: nfe(4) issues X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dan@danneh.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Aug 2007 12:26:08 -0000 > > Alexander Leidinger wrote: > > Tony Holmes wrote: > > > Let me add a "I concur" to this. I upgaded to 7-current 4 weeks ago > > > for this very reason and I have been pleased with the stability and > > > performance. I have enough confidence to deploy into production in > > > the next couple of weeks. > > > > gcc 4.2.0 in -current has known defects. > > Yes, I know, that's why the default optimization setting > in 7-current has been changed from -O2 to -O1 recently, > until gcc 4.2.1 is in the tree. With -O1 I haven't > encountered any problems so far ... Of course that > doesn't mean there aren't any problems. But I'm > actually very confident right now. :-) > > Best regards > Oliver > > -- > Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. > Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: > secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- > chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart > > FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd > > "And believe me, as a C++ programmer, I don't hesitate to question > the decisions of language designers. After a decent amount of C++ > exposure, Python's flaws seem ridiculously small." -- Ville Vainio > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > Can I assume that it's just safe to add the PCI device ID to the source code, reboot, and leave it running 6.2 in the production environment, or will this quick-hack cause me any networking issues later down the line? This server will be accepting several hundred connections at any given time, and it needs to be as stable as stable gets. Many thanks for your help guys. The fix worked, and is currently compiling stuff in ports as I type this message. Dan