content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Subject: RE: removable media revalidation - udev vs. devfs or static /dev
Date: Mon, 12 Jan 2004 17:09:35 +0800
Message-ID: <3ACA40606221794F80A5670F0AF15F8402D4EED7@PDSMSX403.ccr.corp.intel.com>
Thread-Topic: removable media revalidation - udev vs. devfs or static /dev
Thread-Index: AcPWYhFjgmNie2tFQuGkoWRjzBNGOACiA8Rg
From: "Ling, Xiaofeng" <xiaofeng.ling@intel.com>
To: "Joel Becker" <Joel.Becker@oracle.com>, "Greg KH" <greg@kroah.com>
Cc: <linux-hotplug-devel@lists.sourceforge.net>,
       <linux-kernel@vger.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1219
Lines: 24

> 
> On Wed, Jan 07, 2004 at 10:57:00AM -0800, Greg KH wrote:
 to create  16 partitions for every block device, if they need them or not.
> 
> 	Um, adding all 16 partitions for a block device that 
> has 5 defined is opposite of the intention of udev, no?  
> While I'd prefer the partition code in-kernel provide hotplug 
> events for each partition, if it is instead scanned by udev, 
> udev should indeed scan the partition table.  Remember, udev 
> should be able to give the appropriate system-defined names 
> for the partition, not just 'sda1'.
> 
> Joel
  I think current kernel do provide hotplug events for each partition, the
key problem is as Linus said, the most hardware will not give a event when
media changes.  So I just use a stupid way(just like "use a big button"),
pull out first and then plug in the flashdriver when changing the media 
or inserting a media to an empty driver. Then udev can remove the old 
node for and create new node for new media. 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/