From owner-cvs-all@FreeBSD.ORG Wed Jun 8 09:13:17 2005 Return-Path: X-Original-To: cvs-all@FreeBSD.org Delivered-To: cvs-all@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A36F16A41C; Wed, 8 Jun 2005 09:13:17 +0000 (GMT) (envelope-from andrea@acampi.inet.it) Received: from acampi.inet.it (acampi.inet.it [213.92.1.165]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFC2A43D1F; Wed, 8 Jun 2005 09:13:16 +0000 (GMT) (envelope-from andrea@acampi.inet.it) Received: by acampi.inet.it (Postfix, from userid 1000) id 5F09B1D; Wed, 8 Jun 2005 11:13:15 +0200 (CEST) Date: Wed, 8 Jun 2005 11:13:15 +0200 From: Andrea Campi To: Brooks Davis Message-ID: <20050608091314.GA949@webcom.it> References: <200506070449.j574nCXU061621@repoman.freebsd.org> <20050607224745.GA4847@webcom.it> <20050608000136.GA4327@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050608000136.GA4327@odin.ac.hmc.edu> User-Agent: Mutt/1.5.9i Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/etc devd.conf network.subr pccard_ether src/etc/defaults rc.conf src/etc/rc.d dhclient netif X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2005 09:13:17 -0000 On Tue, Jun 07, 2005 at 05:01:36PM -0700, Brooks Davis wrote: > > things broke badly for me on a plain-vanilla installation. I don't have > > an easy way to test a proper solution right now, but there are a couple > > things that stick out as suspiciously bogus: > > I've fixed those bogons and will do some more testing shortly. Any > details on the system configuration or errors so I'm not working > totally blind? In my case it is simply one interface with an IPv4 address; returning an unused variable caused a return 1, which was interpreted as a failure. But now that I look at it with a fresher mind, I can't figure out how it could break anything, apart from printing a failure message... The original problem was that the interface (fxp) failed to come up in time for mountcritremote etc; it is probably unrelated. Sorry for the noise, I'll try again ASAP and I'll let you know. Bye, Andrea -- Press every key to continue.