From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 06:37:10 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C0331065670 for ; Wed, 1 Dec 2010 06:37:10 +0000 (UTC) (envelope-from pa36ouHu4er@yandex.ru) Received: from forward4.mail.yandex.net (forward4.mail.yandex.net [77.88.46.9]) by mx1.freebsd.org (Postfix) with ESMTP id 0C67D8FC13 for ; Wed, 1 Dec 2010 06:37:09 +0000 (UTC) Received: from web44.yandex.ru (web44.yandex.ru [77.88.47.183]) by forward4.mail.yandex.net (Yandex) with ESMTP id A59426AD915D; Wed, 1 Dec 2010 09:21:30 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1291184490; bh=sccqGtfJWi8JdND7rqb9Sogz9nz7JyXOWsT5kWcwh9s=; h=From:To:Cc:In-Reply-To:References:Subject:MIME-Version:Message-Id: Date:Content-Transfer-Encoding:Content-Type; b=uZzVpD7TfdEV89hAbVy9YZ4QzsTZmxWta9mcgniOSPQ4TW5xF3LHDwXAbEYlTOXZB t86oVL52BFyHNwwENI9Nyif3LVzkYqmH4DAfQjow0MglXCFH2ShUTEEWcwaD4+TX+k jLsmwdsG780Q2YA1/Li+9arOZo12F/VKicUZI8xE= Received: from localhost (localhost.localdomain [127.0.0.1]) by web44.yandex.ru (Yandex) with ESMTP id 977E19A015F; Wed, 1 Dec 2010 09:21:30 +0300 (MSK) Received: from [188.128.115.228] ([188.128.115.228]) by mail.yandex.ru with HTTP; Wed, 01 Dec 2010 09:21:29 +0300 From: Ilya A. Arhipov To: Garrett Cooper In-Reply-To: References: MIME-Version: 1.0 Message-Id: <540611291184489@web44.yandex.ru> Date: Wed, 01 Dec 2010 09:21:29 +0300 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=koi8-r Cc: FreeBSD Current Subject: Re: More "noise" in ifconfig X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 01 Dec 2010 06:37:10 -0000 30.11.10, 20:21, "Garrett Cooper" : > šššJust updated to HEAD and I saw the recent ifconfig, usb ethernet, > et all changes: > > $ ifconfig > usbus0: flags=0<> metric 0 mtu 0 > usbus1: flags=0<> metric 0 mtu 0 > usbus2: flags=0<> metric 0 mtu 0 > usbus3: flags=0<> metric 0 mtu 0 > msk0: flags=8843 metric 0 mtu 1500 > options=c011b > ether 00:1d:60:b6:eb:97 > inet 192.168.20.3 netmask 0xffffff00 broadcast 192.168.20.255 > media: Ethernet autoselect (1000baseT > ) > status: active > usbus4: flags=0<> metric 0 mtu 0 > usbus5: flags=0<> metric 0 mtu 0 > usbus6: flags=0<> metric 0 mtu 0 > usbus7: flags=0<> metric 0 mtu 0 > lo0: flags=8049 metric 0 mtu 16384 > options=3 > inet 127.0.0.1 netmask 0xff000000 > $ ifconfig -l > usbus0 usbus1 usbus2 usbus3 msk0 usbus4 usbus5 usbus6 usbus7 lo0 > > šššI don't have any USB ethernet devices, so I would expect usbus, et > all to be blank, but this would break a few (dumb) scenarios we have > at my work where it goes and looks at ifconfig -l (of course I've > tried convincing others to use ifconfig -l inet instead, but that was > to no avail). > šššThis could potentially break other dumb scripts as well. > šššSo the question is: what are we gaining with this additional, terse output? > Thanks, > -Garrett > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > Log: Don't print usbus[0-9] interfaces that it's not the interesting interface type for ifconfig(8). svn commit: r216089