From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 22 21:32:58 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 25A6C1065675 for ; Tue, 22 Apr 2008 21:32:58 +0000 (UTC) (envelope-from jille@quis.cx) Received: from smtp4.versatel.nl (smtp4.versatel.nl [62.58.50.91]) by mx1.freebsd.org (Postfix) with ESMTP id 8D58A8FC1B for ; Tue, 22 Apr 2008 21:32:57 +0000 (UTC) (envelope-from jille@quis.cx) Received: (qmail 25969 invoked by uid 0); 22 Apr 2008 21:06:16 -0000 Received: from ip83-113-174-82.adsl2.versatel.nl (HELO istud.quis.cx) ([82.174.113.83]) (envelope-sender ) by smtp4.versatel.nl (qmail-ldap-1.03) with SMTP for < >; 22 Apr 2008 21:06:16 -0000 Received: by istud.quis.cx (Postfix, from userid 100) id 98B0D39864; Tue, 22 Apr 2008 23:06:14 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on istud.quis.cx X-Spam-Level: X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.4 Received: from [192.168.1.4] (ille [192.168.1.4]) by istud.quis.cx (Postfix) with ESMTP id 6EBBC39860; Tue, 22 Apr 2008 23:06:08 +0200 (CEST) Message-ID: <480E533C.60301@quis.cx> Date: Tue, 22 Apr 2008 23:06:04 +0200 From: Jille User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: Andriy Gapon References: <480E4269.2090604@icyb.net.ua> In-Reply-To: <480E4269.2090604@icyb.net.ua> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: devctl (alike?) for devfs 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: Tue, 22 Apr 2008 21:32:58 -0000 Andriy Gapon wrote: > Maybe this is a crazy idea or maybe we already have something like this. > Is it possible to get notifications about changes in devfs - appearance > and disappearance of devices (in devfs sense of the word)? > devctl currently notifies about real (hardware) devices handled by > device drivers and some notifications about hardware/driver events. > But what if I want to automatically run some action if > /dev/ufs/magic-label appears? > Or if I want to monitor appearance and disappearance of ad* and da* > devices (without having to monitor low level drivers like umass)? > I don't know whether it is what you are looking for, but take a look at devd(8). -- Jille