From owner-freebsd-current@FreeBSD.ORG Tue Jul 15 03:04:02 2014 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 ESMTPS id 04CC440A for ; Tue, 15 Jul 2014 03:04:02 +0000 (UTC) Received: from BLU004-OMC2S17.hotmail.com (blu004-omc2s17.hotmail.com [65.55.111.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B143D2055 for ; Tue, 15 Jul 2014 03:04:01 +0000 (UTC) Received: from BLU179-W85 ([65.55.111.72]) by BLU004-OMC2S17.hotmail.com with Microsoft SMTPSVC(7.5.7601.22712); Mon, 14 Jul 2014 20:02:54 -0700 X-TMN: [QXC6X4Uh/feUR6K3/UVwnYjWmEK391xI] X-Originating-Email: [brunolauze@msn.com] Message-ID: From: =?iso-8859-1?B?QnJ1bm8gTGF1euk=?= To: "freebsd-current@freebsd.org" Subject: libdevattr Date: Mon, 14 Jul 2014 23:02:54 -0400 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 15 Jul 2014 03:02:54.0464 (UTC) FILETIME=[45CA5000:01CF9FD9] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 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: Tue, 15 Jul 2014 03:04:02 -0000 I was looking at dragonfly and why they have libdevattr and we don'tI reall= y think having udev compatible api would open the door to a lot of software= =2C imho.I feel it wouldn't be so complicated to port dragonfly kern_udev= =2C libprop and libdevattr from dragonfly bsd. Am i missing a point or is this in contradiction witch any of freebsd objec= tives? Let me know your thoughts... =