From owner-freebsd-current@FreeBSD.ORG Fri Jul 26 14:40:26 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 19323FF9; Fri, 26 Jul 2013 14:40:26 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id F052B2EC0; Fri, 26 Jul 2013 14:40:24 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id RAA27064; Fri, 26 Jul 2013 17:40:23 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1V2jBu-000IA3-So; Fri, 26 Jul 2013 17:40:22 +0300 Message-ID: <51F28A33.7040209@FreeBSD.org> Date: Fri, 26 Jul 2013 17:39:47 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130708 Thunderbird/17.0.7 MIME-Version: 1.0 To: FreeBSD Current , freebsd-stable List Subject: [HEADS UP] change in devfs path matching logic X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=X-VIET-VPS Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Fri, 26 Jul 2013 14:40:26 -0000 I have just committed a significant change to devfs path matching logic http://svnweb.freebsd.org/changeset/base/253677 Jaakko Heinonen (jh@) has full credit for the code while I have full responsibility for any consequences of the commit. Before this change the logic of matching the devfs paths to the patterns in devfs rules was quite arcane. Now this logic should be much simpler and logical (sorry for tautology). Please note that nothing changes with respect to matching simple paths like /dev/something. It is the complex paths that involve subdirectories that are affected. I think that if you knew how the old logic worked and were able to devise rules for it, then you will have no problem to change those rules for the new logic. Just please don't forget to do it when you upgrade! I hope that overall you will find this change to be an improvement. P.S. I notify stable@ because I currently plan to MFC this change after 1 month period. If you know a reason why the MFC should not be done, please alert me to it. -- Andriy Gapon