From owner-freebsd-net@FreeBSD.ORG Sun Mar 30 10:45:29 2008 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D962A1065674; Sun, 30 Mar 2008 10:45:29 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.freebsd.org (Postfix) with ESMTP id 4566C8FC25; Sun, 30 Mar 2008 10:45:28 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (eugen@localhost [127.0.0.1]) by www.svzserv.kemerovo.su (8.13.8/8.13.8) with ESMTP id m2UAjPC8057611; Sun, 30 Mar 2008 18:45:26 +0800 (KRAST) (envelope-from eugen@www.svzserv.kemerovo.su) Received: (from eugen@localhost) by www.svzserv.kemerovo.su (8.13.8/8.13.8/Submit) id m2UAjPIk057610; Sun, 30 Mar 2008 18:45:25 +0800 (KRAST) (envelope-from eugen) Date: Sun, 30 Mar 2008 18:45:25 +0800 From: Eugene Grosbein To: "Bruce M. Simpson" Message-ID: <20080330104525.GA57135@svzserv.kemerovo.su> References: <47EE42C8.3070100@quip.cz> <20080329204344.GA66910@lor.one-eyed-alien.net> <20080330072137.GA35435@svzserv.kemerovo.su> <47EF69F0.1050304@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47EF69F0.1050304@FreeBSD.org> User-Agent: Mutt/1.4.2.3i Cc: FreeBSD-Net mailing list , Brooks Davis , Miroslav Lachman <000.fbsd@quip.cz> Subject: Re: 7.0 - ifconfig create is not working as expected? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Mar 2008 10:45:30 -0000 > >Why? The same with creating gif-tunnel, now I need to invoke ifconfig > >twice, once for 'create' and once for other tunnel parameters, > >whereas for RELENG_6 this works: 'ifconfig gif0 create tunnel 1.1.1.1 > >2.2.2.2' > >This breaks existing setups/scripts. This is POLA issue. > >Why was it broken? > > I don't know why or how this has happened, however, given the complexity > of the command line grammar which ifconfig is expected to parse, our > choices are limited, unless someone(tm) is willing to come along and > implement a full parser in ifconfig. It worked. Now it does not work. Someone(tm) made the change. We have the CVS. Isn't there such thing as responsibility for changes? A dichotomy will show us who did the change :-) Eugene Grosbein