From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 17:21:24 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 DCADD106566C; Tue, 30 Nov 2010 17:21:24 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 1EA578FC12; Tue, 30 Nov 2010 17:21:23 +0000 (UTC) Received: by ewy24 with SMTP id 24so2990174ewy.13 for ; Tue, 30 Nov 2010 09:21:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:cc:content-type; bh=JLc1cVNZWOyafavzfkiVPrN14i/5VDivQAuZxex9SZc=; b=q1lGQcKglAFVd0VzzQf72KcqA+mCEJjOmTh0e62ImO9JvtOAzcrY7X2TpPvwBkfRrQ qOw9gCRWO81a4uLlHXotq5FiSkk295mBWYsrvk1IFDC9rJO1wPNnPlxnBi/BV9pM1sYV bvJS6Ly87WHIi0EiIocUW7LqKBULEfT5Vf/nc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=TmNli7VcxzxUkfvZHACQfr2qDuRZYtKoVh2IDbUenMBDQyuP27jOHBV9EHHy6wEeqn y7ob/2sG0yxn1HXUPt+7rcTWMA4JOVIkRxEOd8x1YRK1ZZTr2DBUsDxk7ljNVyDMDSPj 4Ho1tTSQ2GxSQ3eoHe97Vx6hjvPDrUHHWf6EM= MIME-Version: 1.0 Received: by 10.216.175.18 with SMTP id y18mr7683406wel.30.1291137682284; Tue, 30 Nov 2010 09:21:22 -0800 (PST) Received: by 10.216.198.27 with HTTP; Tue, 30 Nov 2010 09:21:22 -0800 (PST) Date: Tue, 30 Nov 2010 09:21:22 -0800 Message-ID: From: Garrett Cooper To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1 Cc: weongyo@freebsd.org, Hans Petter Selasky Subject: 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: Tue, 30 Nov 2010 17:21:24 -0000 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