From owner-freebsd-stable Fri Aug 18 9:58: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wyattearp.stanford.edu (wyattearp.Stanford.EDU [171.66.63.23]) by hub.freebsd.org (Postfix) with ESMTP id EC61737B422 for ; Fri, 18 Aug 2000 09:58:02 -0700 (PDT) Received: (from richw@localhost) by wyattearp.stanford.edu (8.9.3/8.9.3) id JAA23772; Fri, 18 Aug 2000 09:57:24 -0700 (PDT) (envelope-from richw) Date: Fri, 18 Aug 2000 09:57:24 -0700 (PDT) From: Rich Wales X-Sender: richw@wyattearp.stanford.edu To: Thierry.Herbelot@alcatel.fr Cc: freebsd-stable@freebsd.org Subject: Re: Memory sizing, AGP video card In-Reply-To: Message-ID: <200008181623005.richw@wyattearp.stanford.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thierry -- Replying to: > I do not think FreeBSD supports the simultaneous use > of IPFilter and the native ipfw : this may be a cause > for your "unexplained" reboots. Hmmm. I do indeed have both "ipfilter" and "ipfw" support enabled in my kernel. However, I am currently using only "ipfw" firewall rules (in /etc/rc.firewall). I've been considering the idea of switching over to the new "ipfilter" facility, but I haven't had time yet. Do you believe the existence of both "ipfilter" and "ipfw" kernel support could still cause problems, even if I am in fact only using "ipfw"? Also, in case it makes a difference, my crashes were userland problems (e.g., SWIG bombing with segmentation fault signals) -- not kernel panic/reboot scenarios. Rich Wales richw@webcom.com http://www.webcom.com/richw/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message