From owner-freebsd-current@FreeBSD.ORG Wed Nov 12 01:01:29 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B74F16A4CF for ; Wed, 12 Nov 2003 01:01:29 -0800 (PST) Received: from mailhub.fokus.fraunhofer.de (mailhub.fokus.fraunhofer.de [193.174.154.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9605943F93 for ; Wed, 12 Nov 2003 01:01:27 -0800 (PST) (envelope-from brandt@fokus.fraunhofer.de) Received: from beagle (beagle [193.175.132.100])hAC91PU12900 for ; Wed, 12 Nov 2003 10:01:25 +0100 (MET) Date: Wed, 12 Nov 2003 10:01:25 +0100 (CET) From: Harti Brandt To: current@freebsd.org Message-ID: <20031112095711.A33680@beagle.fokus.fraunhofer.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: HEADSUP: netgraph constants changing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 12 Nov 2003 09:01:29 -0000 Hi all, as I've written a couple of days ago I'm going to bump some constants in the netgraph code that defined various name lengths in the next minutes. I've not received any negative feedback and have the ok from re. If you use netgraph make sure that the kernel, any externally maintained netgraph modules and any user space netgraph stuff (mainly ngctl and nghook) are in sync otherwise they'll not be able to communicate. This is especially important if you use netgraph for booting purposes. No correctly written code should break by this change :-) harti -- harti brandt, http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.fraunhofer.de, harti@freebsd.org