Around about 19/12/2002 14:11, Derrik Pates typed ...
I had a look at this over XMas; apart from not yet being able to rpmbuild the kernel from the src-rpm (can 'make' from 'sources' rpm - need to investigate), I found the following: sd.c (no where near where you pointed - what kernel vn. were you ref.ing?) says:On line 1376 (in fop_relatidate_scsidisk()) in drivers/scsi/sd.c, change the second parameter of the call to revalidate_scsidisk() from a 0 to a 1. Then rebuild the kernel modules (or the kernel, if you have SCSI disk support built statically into your kernel).
/* This routine is called to flush all partitions and partition tables
* for a changed scsi disk, and then re-read the new partition table.
* If we are revalidating a disk because of a media change, then we
* enter with usage == 0. If we are using an ioctl, we automatically have
* usage == 1 (we need an open channel to use an ioctl :-), so this
* is our limit.
*/
int revalidate_scsidisk(kdev_t dev, int maxusage)
So we /want/ '0' in this case, don't we? Is passing '1' correct here?
--
[neil@fnx ~]# rm -f .signature
[neil@fnx ~]# ls -l .signature
ls: .signature: No such file or directory
[neil@fnx ~]# exit
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
