Re: removable media revalidation - udev vs. devfs or static /dev

[Greg KH]

On Thu, Jan 01, 2004 at 11:33:04PM +0300, Andrey Borzenkov wrote:
> udev names are created when kernel detects corr. device. Unfortunately for 
> removable media kernel rescans for partitions only when I try to access 
> device. Meaning - because kernel does not know partition table it did not 
> send hotplug event so udev did not create device nodes. But without device 
> nodes I have no way to access device in Unix :(
> 
> specifically I have now my Jaz and I have no (reasonable) way to access 
> partition 4 assuming device nodes are managed by udev.
> 
> devfs solved this problem by
> 
> - always exporting at least handle to the whole disk (sda as example)

Doesn't the kernel always create the main block device for this device?
If so, udev will catch that.  If not, there's no way udev will work for
this kind of device, sorry.  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.

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/