From owner-freebsd-current  Sun May  4 16:11:31 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id QAA22227
          for current-outgoing; Sun, 4 May 1997 16:11:31 -0700 (PDT)
Received: from nyx.pr.mcs.net (nyx.pr.mcs.net [204.95.55.81])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA22218
          for <current@freebsd.org>; Sun, 4 May 1997 16:11:25 -0700 (PDT)
Received: from nyx.pr.mcs.net (localhost [127.0.0.1])
	by nyx.pr.mcs.net (8.8.5/8.8.5) with ESMTP id SAA00518
	for <current@freebsd.org>; Sun, 4 May 1997 18:10:58 -0500 (CDT)
Message-Id: <199705042310.SAA00518@nyx.pr.mcs.net>
X-Mailer: exmh version 1.6.9 8/22/96
To: current@freebsd.org
Subject: new ifconfig quirk...
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 04 May 1997 18:10:58 -0500
From: Chris Csanady <ccsanady@nyx.pr.mcs.net>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

It seems that ifconfig now requires an address family.  If not
specified, it just spits out the usage.  You can no longer do
the following..

ifconfig ep0 down
ifconfig ep0 -link0 link1
etc..

If you ask me, things dealing with the media and interface being
up or down dont have much to do with an address family.  Or am
I missing something?  The code in ifconfig.c is not ambiguous as
to what it does..

--Chris Csanady