From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick Mansfield Date: Wed, 18 Jan 2006 21:05:28 +0000 Subject: Re: scsi.agent trouble: load more than module per TYPE Message-Id: <20060118210528.GA22783@us.ibm.com> List-Id: References: <20060118182519.4c7bd4b5@lounge.fly.net> In-Reply-To: <20060118182519.4c7bd4b5@lounge.fly.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Wed, Jan 18, 2006 at 09:16:50PM +0100, Marco d'Itri wrote: > On Jan 18, Patrick Mansfield wrote: > > > IMHO, sg should still be loaded for all scsi devices, especially for > > ones that have an odd (such as enclousre or raid) or unknown type. Looks > > like only SUSE does it this way. > Nobody ever opened a bug suggesting to do it differently, so I did not > bother changing the rules used by Debian. If you don't want to always load sg, at least load sg if no other driver is loaded for the scsi device. That might even be better than always loading it (sort of force SG_IO users to use /dev/sd ...). I don't know why sr_mod is loaded for type 3 (processor), unless you have patched sr.c sr_probe(), sr only attaches to 5 (TYPE_ROM) and 4 (TYPE_WORM). So use (for debian at least, not tested at all): SUBSYSTEM="scsi_device", SYSFS{type}!="[0|1|4|5|7|14]", RUN+="/sbin/modprobe sg" -- Patrick Mansfield ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ 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