From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Sat, 03 Jan 2004 20:51:20 +0000 Subject: Re: removable media revalidation - udev vs. devfs or static /dev Message-Id: <20040103205119.GA10802@kroah.com> List-Id: References: <200401012333.04930.arvidjaar@mail.ru> <20040103055847.GC5306@kroah.com> <200401031151.02001.arvidjaar@mail.ru> In-Reply-To: <200401031151.02001.arvidjaar@mail.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Andrey Borzenkov Cc: linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org On Sat, Jan 03, 2004 at 11:51:33AM +0300, Andrey Borzenkov wrote: > > You could make a script that just creates > > the device node in /tmp, runs dd on it, and then cleans it all up to > > force partition scanning. > > > > You miss the point. When should this script be run? There is no event when you > just insert Jaz disk; nor is there any way to trigger revalidation on access > to non-existing device like is the case without udev. > > what I aim at - udev needs to provide some extension mechanism to allow > arbitrarily scripts to be run. It does provide that mechanism. See the CALLOUT rule. It can run any program or script when a new device is seen by the kernel. thanks, greg k-h ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263963AbUACUvR (ORCPT ); Sat, 3 Jan 2004 15:51:17 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263983AbUACUvR (ORCPT ); Sat, 3 Jan 2004 15:51:17 -0500 Received: from mail.kroah.org ([65.200.24.183]:62948 "EHLO perch.kroah.org") by vger.kernel.org with ESMTP id S263963AbUACUvQ (ORCPT ); Sat, 3 Jan 2004 15:51:16 -0500 Date: Sat, 3 Jan 2004 12:51:20 -0800 From: Greg KH To: Andrey Borzenkov Cc: linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org Subject: Re: removable media revalidation - udev vs. devfs or static /dev Message-ID: <20040103205119.GA10802@kroah.com> References: <200401012333.04930.arvidjaar@mail.ru> <20040103055847.GC5306@kroah.com> <200401031151.02001.arvidjaar@mail.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200401031151.02001.arvidjaar@mail.ru> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Jan 03, 2004 at 11:51:33AM +0300, Andrey Borzenkov wrote: > > You could make a script that just creates > > the device node in /tmp, runs dd on it, and then cleans it all up to > > force partition scanning. > > > > You miss the point. When should this script be run? There is no event when you > just insert Jaz disk; nor is there any way to trigger revalidation on access > to non-existing device like is the case without udev. > > what I aim at - udev needs to provide some extension mechanism to allow > arbitrarily scripts to be run. It does provide that mechanism. See the CALLOUT rule. It can run any program or script when a new device is seen by the kernel. thanks, greg k-h