Jean Delvare wrote:
Hi Andrey, Jeff,
Le Wednesday 05 June 2013 à 21:33 +0400, Andrey Borzenkov a écrit :
В Wed, 05 Jun 2013 13:21:09 -0400 Jeff Mahoney
пишет: On 6/5/13 12:41 PM, Andrey Borzenkov wrote:
В Wed, 05 Jun 2013 18:29:53 +0200 Jean Delvare
пишет: * I have no idea why/how sg is being loaded, it has no modalias and no other module depend on it. But /dev/sd* nodes are created so it is certainly useful. Hannes?
/usr/lib/udev/rules.d/80-drivers.rules:SUBSYSTEM=="scsi", ENV{DEVTYPE}=="scsi_device", TEST!="[module/sg]", IMPORT{builtin}="kmod load sg"
Thanks for the pointer.
I do not think it is needed much; the practical problem is to make sure it is loaded *when* it is needed (like remote SCSI enclosure monitoring via SES or jukebox control).
This is the SCSI generic interface. You've identified the practical problem perfectly - there's no way to tell when a user will need it. It's not just for jukebox and SES. Optical media writers use it as well.
Are you sure? I thought sr was extended with necessary functionality ages ago. At least cdrecord dev=/dev/sr0 worked for me for years.
The sg driver has been creating a sysfs symlink from each SCSI device to its sg interface for at least 8 years. So applications do no longer need the user to point them to that sg interface.
Whether optical media writers or other applications actually need the sg interface today or not, I can't say. I see that the wodim binary still has references to /dev/sg%d and the sg driver, but I don't know if it is for current or older kernels.
Last I checked, I still needed /dev/sgX to work with media changers. (see man mtx) -- Per Jessen, Zürich (16.6°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org