From owner-freebsd-net@FreeBSD.ORG  Thu Aug 13 19:20:49 2009
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
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 23BFE10656AE
	for <freebsd-net@freebsd.org>; Thu, 13 Aug 2009 19:20:49 +0000 (UTC)
	(envelope-from sthaug@nethelp.no)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33])
	by mx1.freebsd.org (Postfix) with SMTP id 6A9138FC52
	for <freebsd-net@freebsd.org>; Thu, 13 Aug 2009 19:20:47 +0000 (UTC)
Received: (qmail 5734 invoked from network); 13 Aug 2009 19:20:46 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33)
	by bizet.nethelp.no with SMTP; 13 Aug 2009 19:20:46 -0000
Date: Thu, 13 Aug 2009 21:20:46 +0200 (CEST)
Message-Id: <20090813.212046.78768090.sthaug@nethelp.no>
To: bzeeb-lists@lists.zabbadoz.net
From: sthaug@nethelp.no
In-Reply-To: <20090813182918.S93661@maildrop.int.zabbadoz.net>
References: <4A840DA1.600@yandex.ru> <4A844FF2.9000307@elischer.org>
	<20090813182918.S93661@maildrop.int.zabbadoz.net>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: freebsd-net@freebsd.org, bu7cher@yandex.ru, d@delphij.net,
	julian@elischer.org
Subject: Re: RFC: interface description
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Aug 2009 19:20:49 -0000

> My point has always been - if I have to add/do an ioctl I can always also
> use a library call that will read it from a .txt, .xml, .db file
> or whatever and I don't have to go to the kernel, handle all the
> string length problems there, ... especially as the kernel cannot do
> anything with that string.

Personally, I couldn't care less if an interface description is stored
in the kernel or in a file. I *do* care about being able to set and
show the description via ifconfig.

Steinar Haug, Nethelp consulting, sthaug@nethelp.no