Re: modules.devfsd needs /dev/scsi/*/part* handling

[Thierry Vignaud <tvignaud@xxxxxxxxxxxxxxxx>]

Richard Gooch <rgooch@xxxxxxxxxxxxxxx> writes:

>> Attached patch is against current Mandrake devfsd.conf. It works just
>> fine here for SCSI; I'd appreciate anybody testing it for IDE. It is
>> great because it means we can continue to use compatibility names by
>> default without endless "hey, why it says no such device!"=20
>> 
>> blockdev is garanteed to exist on Mandrake that is currently my concern
>> :-)
>> 
>> many thanks for idea (yes, sometimes you must really read TFM).
>
> Well, thanks, but since blockdev isn't available everywhere, I can't
> really use it in a generic configuration file. However, I wonder if
> blockdev is actually required. IIRC, merely opening the block device
> should suffice to trigger media revalidation. Is this not the case?
> What is blockdev doing that is special?
>
> Can you please try to use dd instead in your devfsd.conf file and tell
> me if that works? An action like this:
>       EXECUTE dd if=$mntpnt/\1 of=/dev/null count=1

this would add a dependancy on fileutils. as for mandrake, it's required by
basesystem package, so it's ok for us. should be the same for rh & debian, but a
check wouldn't hurt.

> should suffice. It will probably generate some messages about 1+0
> blocks read and so forth, but ignore that for now.