Mailinglist Archive: opensuse-bugs (4283 mails)

< Previous Next >
[Bug 1036463] Please take over /usr/lib/modules-load.d/sg.conf
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 02 May 2017 19:46:04 +0000
  • Message-id: <bug-1036463-21960-Vhk7yMxbpv@http.bugzilla.suse.com/>
http://bugzilla.suse.com/show_bug.cgi?id=1036463
http://bugzilla.suse.com/show_bug.cgi?id=1036463#c6

Lee Duncan <lduncan@xxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |IN_PROGRESS
Flags|needinfo?(lduncan@xxxxxxxx) |

--- Comment #6 from Lee Duncan <lduncan@xxxxxxxx> ---
(In reply to Franck Bui from comment #4)
(In reply to Lee Duncan from comment #3)
Yes, the sg driver still needs to be loaded, by default, since it is used by
udev as well as the sg3_utils package, which also seems to be installed by
default.

Could you explain why the sg driver is special here and needs to be loaded
manually unlike most other drivers ?

The sg driver creates generic SCSI device access points for SCSI devices when
they are attached, if and only if it is loaded at that time.

So either the burden must be on each and every SCSI device added to ensure that
the "sg" driver is loaded before it probes a new device, or the sg driver must
be pre-loaded. It has always been pre-loaded.


Also how does exactly udev rely on it ?

Thanks.

Actually it's udev rules that rely on it:

zsh# grep -rl sg /usr/lib/udev/rules.d
/usr/lib/udev/rules.d/55-scsi-sg3_id.rules
/usr/lib/udev/rules.d/58-scsi-sg3_symlink.rules
/usr/lib/udev/rules.d/60-persistent-storage-tape.rules
/usr/lib/udev/rules.d/40-libgphoto2.rules

Out of those, it looks like perhaps the only rules depending on SG devices
these days is the libgphoto2 library? So perhaps I misspoke. But certainly
customers expect the sg device to be present when they plug in devices, as
shown in the original bug (see bsc#761109).

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >