From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: class_device/udev support for tapes?
Date: Tue, 02 Dec 2003 18:00:41 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107038837701891@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107038690632125@msgid-missing>
On Tue, Dec 02, 2003 at 06:35:18PM +0100, Arnd Bergmann wrote:
> Has anyone come up with a solution for using udev for tape devices?
The scsi people need to add support for this into the st driver. They
also need to add it to their sg driver for scsi generic devices. They
know about this, and hopefully are working on it...
> Unlike block devices, there is no master device with anything
> similar to partitions, but all the interfaces are equal. One way
> to represent them would be to create a class device without a
> dev entry and have the chardev interfaces as child kobjects of that:
>
> /sys/class/tape/st0/st0/dev
> /sys/class/tape/st0/st0a/dev
> /sys/class/tape/st0/nst0/dev
> /sys/class/tape/st0/device -> ../../...
> /sys/class/tape/rtibm0/ntibm0/dev
What is "st0" here? Why not just:
/sys/class/scsi_tape/st0/dev
/sys/class/scsi_tape/st0a/dev
/sys/class/scsi_tape/nst0/dev
/sys/class/scsi_tape/ntibm0/dev
> This would of course be inconsistant with all the other classes.
> The second option I see is naming the 'dev' attribute differently:
>
> /sys/class/tape/st0/dev-st
> /sys/class/tape/st0/dev-sta
> /sys/class/tape/st0/dev-nst
Hm, I probably don't understand tapes. What's the difference between
st, sta, and nst? Are they all different char devices for the same tape
device? Doing different things?
> This is also somewhat inconsistant from udev's point of view, but not
> so much from the kernel.
True, but we can always work around that in udev, if it's necessary.
> The third option is to simply register one class device for each logical
> device:
>
> /sys/class/tape/st0/dev
> /sys/class/tape/st0/device -> ../../...
> /sys/class/tape/st0a/dev
> /sys/class/tape/st0a/device -> ../../...
> /sys/class/tape/nst0/dev
> /sys/class/tape/nst0/device -> ../../...
> /sys/class/tape/rtibm0/dev
>
> This is at least possible with the least number of changes to udev
> and the view of class devices, but not as intuitive for the user.
>
> I am totally unsure which option should be used or if there is maybe
> a better way that I failed to see.
>
> The other question is how to best design the kernel interface for
> registering a tape class device with a variable number of chardev nodes.
You might want to take this to the linux-scsi list, as the people there
should know how to do this.
thanks,
greg k-h
-------------------------------------------------------
This SF.net email is sponsored by OSDN's Audience Survey.
Help shape OSDN's sites and tell us what you think. Take this
five minute survey and you could win a $250 Gift Certificate.
http://www.wrgsurveys.com/2003/osdntech03.php?site=8
_______________________________________________
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
next prev parent reply other threads:[~2003-12-02 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 17:35 class_device/udev support for tapes? Arnd Bergmann
2003-12-02 18:00 ` Greg KH [this message]
2003-12-02 20:09 ` Arnd Bergmann
2003-12-10 1:14 ` Greg KH
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=marc-linux-hotplug-107038837701891@msgid-missing \
--to=greg@kroah.com \
--cc=linux-hotplug@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).