From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 10 21:23:12 2006 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2758B16A401 for ; Mon, 10 Apr 2006 21:23:12 +0000 (UTC) (envelope-from darren.pilgrim@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D28843D66 for ; Mon, 10 Apr 2006 21:23:04 +0000 (GMT) (envelope-from darren.pilgrim@bitfreak.org) Received: from [127.0.0.1] (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id 9DFE919F2C; Mon, 10 Apr 2006 14:23:03 -0700 (PDT) Message-ID: <443ACCB6.8080306@bitfreak.org> Date: Mon, 10 Apr 2006 14:23:02 -0700 From: Darren Pilgrim User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: "M. Warner Losh" References: <20060409090757.GW80492@spc.org> <20060409.184825.99254285.imp@bsdimp.com> <20060410194746.GY80492@spc.org> <20060410.141042.25162164.imp@bsdimp.com> In-Reply-To: <20060410.141042.25162164.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: mwm-keyword-freebsdhackers.102a7e@mired.org, scottl@samsco.org, ceri@submonkey.net, hackers@FreeBSD.org Subject: Re: Using any network interface whatsoever X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 21:23:12 -0000 I think at this point it's been pretty well established that: - Device naming and unit numbering is not stable enough to avoid breakage across hardware changes. - There is a need for generic and/or descriptive interface naming independent of driver- and probe-order-based naming. - There are static bits of information available about each device in the system that can be used to locate a specific device that would be sufficient to allow assignment of a network configuration to a physical device, not it's attached name. If I were to write an rc.d script to use descriptive network interface names and wire configs to static hardware identification, would there be support for such a feature?