From: Patrick Mansfield <patmans@us.ibm.com>
To: Roman Kagan <rkagan@mail.ru>, Willem Riede <osst@riede.org>,
linux-scsi@vger.kernel.org,
linux-hotplug-devel@lists.sourceforge.net
Subject: Re: [ANNOUNCE] hotplug-ng 001 release
Date: Fri, 18 Feb 2005 10:33:50 -0800 [thread overview]
Message-ID: <20050218183350.GA21954@us.ibm.com> (raw)
In-Reply-To: <20050218181106.GC4424@katya>
On Fri, Feb 18, 2005 at 09:11:06PM +0300, Roman Kagan wrote:
> On Fri, Feb 18, 2005 at 09:17:37AM -0800, Patrick Mansfield wrote:
> > You could also append the sdev->vendor and sdev->model, and use alias wild
> > cards.
>
> String values haven't been used in the aliases so far, and I think for a
> reason: with all the unpredictable weird characters and string lengths
> they would make maintainance harder, not easier.
Yes, but modprobe should just work with them, even if scripts or other
usage has problems. I haven't seen any really odd strings for vendor or
model, ususally just spaces and alphanumeric, I don't remember (or even
remember where to look) for the allowed characters; there are always
devices that behave badly.
> > Also, sg loading would want (along with modprobe load all feature):
> >
> > MODULE_ALIAS("scsi-type-*");
>
> Is it certain that it can live together with s[dtr]? I thought these
> guys now handled all the ioctls sg was supposed to themselves...
Yes.
The block SG_IO handles the ioctls, but not devices without a SCSI upper
level driver (i.e. not tape, disk or cdrom).
For example, media changers (though a driver has just been submitted),
scanners, enclosure devices, or printers (I've never seen any scsi
printers).
In my experience, there are always applications that want to use the
standard device driver (/dev/sda etc.) and others that want to use a
generic driver.
-- Patrick Mansfield
next prev parent reply other threads:[~2005-02-18 18:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050211193627.GB20015@suse.de>
[not found] ` <20050211204626.GC2568@katya>
[not found] ` <20050211211028.GB21512@suse.de>
[not found] ` <20050212003458.GI2568@katya>
[not found] ` <20050214224208.GC13110@suse.de>
[not found] ` <20050216105117.GB2360@katya>
[not found] ` <20050216110752.GC2360@katya>
[not found] ` <1108594961l.5056l.5l@serve.riede.org>
[not found] ` <20050216231741.GD2870@katya>
[not found] ` <1108596771l.5056l.6l@serve.riede.org>
2005-02-18 17:17 ` [ANNOUNCE] hotplug-ng 001 release Patrick Mansfield
2005-02-18 18:11 ` Roman Kagan
2005-02-18 18:33 ` Patrick Mansfield [this message]
2005-02-18 19:41 ` Roman Kagan
2005-02-18 20:17 ` Patrick Mansfield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050218183350.GA21954@us.ibm.com \
--to=patmans@us.ibm.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-scsi@vger.kernel.org \
--cc=osst@riede.org \
--cc=rkagan@mail.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox