From owner-freebsd-net  Fri Jun  4 18:58:12 1999
Delivered-To: freebsd-net@freebsd.org
Received: from databus.databus.com (databus.databus.com [198.186.154.34])
	by hub.freebsd.org (Postfix) with SMTP id 329CE14C01
	for <freebsd-net@FreeBSD.ORG>; Fri,  4 Jun 1999 18:57:59 -0700 (PDT)
	(envelope-from barney@databus.databus.com)
From: Barney Wolff <barney@databus.com>
To: freebsd-net@FreeBSD.ORG
Date: Fri, 4 Jun 1999 21:19 EDT
Subject: Re: subtle SIOCGIFCONF bug
Content-Length: 668
Content-Type: text/plain
Message-ID: <375884220.6584@databus.databus.com>
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

You have not said specifically what about SIOCGIFCONF is bad, that
could possibly justify the incredible statement that one should
use a non-portable technique when a portable technique is available.
SIOGIFCONF works on Unixware, Solaris, HP-UX, Irix and FreeBSD, just
to list systems I can access right now.  sysctl excludes all of them
except FreeBSD.  Please explain!

Barney Wolff  <barney@databus.com>

> Date: Fri, 4 Jun 1999 20:43:40 -0400 (EDT)
> From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
> 
> Use an interface which provides clients with enough information to
> know when they have retrieved all of the relevant information.  Here's
> an example.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message