Douglas Gilbert wrote: > Mark, > In the lk 2.6 series you can open a disk directly > (e.g. /dev/sda) and send it SCSI commands using the > SG_IO ioctl. The situation is the same if you open > the corresponding sg device and send SCSI commands. > > What is important is which SCSI commands are sent. There > is some crude filtering based on file permissions and > the SCSI command opcode. Other than that, the onus is > on the person sending the SCSI commands. Mounted file > systems can be seen in /proc/mounts ** . > > The sg driver is a pass through. The SG_GET_ACCESS_COUNT > ioctl was a window to a variable which someone else removed > around 18 months ago. There is little I can do other > than try to explain ... > Understood and thanks for the info. I know about being having a limited set of CDB opcodes available for the sd devices however it is much to limited for me. It just doesn't make sense to me that the "window to the variable" was closed without offerring a simple alternative. An application that has been in use for years using a documented and supported API now eats my root device if I run it???? I think sombody wasn't thinking too clearly or took an easy way out to a problem they didn't care to address. Thanks again Mark - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
