From owner-freebsd-current@FreeBSD.ORG Fri Apr 4 08:16:12 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 7599537B401 for ; Fri, 4 Apr 2003 08:16:12 -0800 (PST) Received: from ip68-14-60-78.no.no.cox.net (ip68-14-60-78.no.no.cox.net [68.14.60.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 988B643F85 for ; Fri, 4 Apr 2003 08:16:11 -0800 (PST) (envelope-from conrads@ip68-14-60-78.no.no.cox.net) Received: from ip68-14-60-78.no.no.cox.net (conrads@localhost [127.0.0.1]) h34GKipR012442; Fri, 4 Apr 2003 10:20:44 -0600 (CST) (envelope-from conrads@ip68-14-60-78.no.no.cox.net) Received: (from conrads@localhost)h34GKiVs012441; Fri, 4 Apr 2003 10:20:44 -0600 (CST) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3E8DAC22.80000@ezri.org> Date: Fri, 04 Apr 2003 10:20:44 -0600 (CST) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: Conrad Sabatier To: Wade Majors 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:16:12 -0000 On 04-Apr-2003 Wade Majors wrote: > 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. :-) > > You can still boot your old kernel from the loader prompt, if such a > thing happens. But everything appears normal to me so far. Yes, except I ran into some problems this last time where, after successfully booting the new kernel in single-user mode, installing world, running mergemaster, rebooting and finding the new kernel didn't work, I couldn't get the old kernel to work, either. :-( Apparently, something had changed just enough somewhere to make the old kernel go kerplooey, too. -- Conrad Sabatier - "In Unix veritas"