Re: nfe(4) issues

>
> 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_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_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