public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: Olaf Hering <olh@suse.de>,
	linux-hotplug-devel@lists.sourceforge.net,
	linux-scsi@vger.kernel.org
Subject: Re: devices with more than one node
Date: Tue, 13 Jan 2004 15:18:13 -0800	[thread overview]
Message-ID: <20040113231813.GA7409@kroah.com> (raw)
In-Reply-To: <20040113150147.A9902@beaverton.ibm.com>

On Tue, Jan 13, 2004 at 03:01:47PM -0800, Patrick Mansfield wrote:
> Don't forget to let the scsi people know ;-) cc-ing linux-scsi

Ok, here goes:

linux-scsi, DO NOT USE THE cdev sysfs directory.  It will be going away
as soon as I get around to writing the patch for it.  Putting the sg
symlink in there is not the proper place.

For scsi generic you should create a scsi generic class (scsi_generic?)
and create the individual sg devices in that directory (feel free to use
the simple_class.c code that is currently in the -mm tree if you want,
it makes it much simpler)

> st also needs changes.

I agree.

> Did anyone figure out how udev should handle the one tape device requiring
> multiple minors (for open/close with/without rewind)? It really is a
> single device requiring multiple dev entries.

Create multiple class_device items for every tape device and have the
device symlink point to the same scsi device.  The simple_class code
should make life a lot easier for you.

> For scsi_id support with udev, st needs to support SG_IO, AFAIUI it can
> use similiar code as found in sd.c and sr.c.

That's a scsi core issue, not a udev issue :)

thanks,

greg k-h


-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html

  reply	other threads:[~2004-01-13 23:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040113193842.GA29887@suse.de>
     [not found] ` <20040113194631.GA3818@kroah.com>
     [not found]   ` <20040113211122.GA28100@suse.de>
     [not found]     ` <20040113212058.GA2595@kroah.com>
2004-01-13 23:01       ` devices with more than one node Patrick Mansfield
2004-01-13 23:18         ` Greg KH [this message]
2004-01-14  1:12           ` dougg
2004-01-14  1:26             ` Greg KH
2004-01-14  3:08             ` Willem Riede
2004-01-15  8:04               ` Douglas Gilbert
2004-01-15 23:21                 ` Greg KH
2004-01-16  9:59                   ` Mike Anderson
2004-01-18 22:08                 ` Willem Riede

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=20040113231813.GA7409@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-scsi@vger.kernel.org \
    --cc=olh@suse.de \
    --cc=patmans@us.ibm.com \
    /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