From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 08:31:37 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5052637B401 for ; Fri, 4 Apr 2003 08:31:37 -0800 (PST) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC68343FBD for ; Fri, 4 Apr 2003 08:31:36 -0800 (PST) (envelope-from mux@freebsd.org) Received: by elvis.mu.org (Postfix, from userid 1920) id D41972ED431; Fri, 4 Apr 2003 08:31:36 -0800 (PST) Date: Fri, 4 Apr 2003 18:31:36 +0200 From: Maxime Henrion To: Conrad Sabatier Message-ID: <20030404163136.GQ1750@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org Subject: Re: So then, is fxp working OK again? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 16:31:37 -0000 Conrad Sabatier wrote: > Having had the same experiences as others described here recently with the > fxp stuff, I'm just wondering if it's safe now to cvsup and try it again. > I only have one machine here and if my net interface fails, I'm totally > screwed. :-) It should. If it doesn't, I'm interested in knowing it. :-) Cheers, Maxime