From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Sat, 03 Jan 2004 05:58:47 +0000 Subject: Re: removable media revalidation - udev vs. devfs or static /dev Message-Id: <20040103055847.GC5306@kroah.com> List-Id: References: <200401012333.04930.arvidjaar@mail.ru> In-Reply-To: <200401012333.04930.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 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 ------------------------------------------------------- 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