From: Douglas Gilbert <dougg@torque.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: SCSI Patches - mostly on/off-line stuff
Date: Thu, 18 Jan 2001 21:08:36 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-97985278930021@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-97925037703688@msgid-missing>
David Brownell wrote:
>
> It seemed to me that something was missing in that stack though;
> the layers above (4), specifically filesystems, that would also need
> to know about new devices that were added. When everything is
> working smoothly, users need to see filesystems get mounted as
> a direct consequence of hotplugging such storage units.
>
> One way to look at that issue is to ask what user mode notifications
> will be used to address that part of the hotplug problem. Devfsd
> is what some folk like, but it's not universally accepted. GUI
> driven solutions don't seem right in all cases either.
> [snip]
Devfs has the useful property that only devices that are
present and have their drivers ready appear in the /dev
hierarchy. In the case of SCSI devices, devfs maintains
this dynamically via calls in the _attach() and _detach()
functions within the upper level drivers. The new
directory notification capability in lk 2.4 (see
Documentation/dnotify.txt) could then be used to detect
changes in the /dev directory (or below).
A user mode notification daemon could read /proc/scsi/scsi
periodically to detect the arrival and departure of SCSI
(pseudo) devices. To this end, the output read from
/proc/scsi/sg/devices would be easier to parse.
If a cdrom drive has just be introduced, it would relatively
easy to work out which /dev/sr<n> device name it was. I guess
existing cdrom applications would then be smart enough to
work out whether the drive was empty, had a music cd, or a
data cdrom (which fs type, etc).
Currently there is a boolean flag: 'emulated' that sg can
yield via an ioctl and is available in /proc/scsi/sg/hosts .
I assume it was introduced for the first pseudo scsi driver:
ide-scsi. Seems to me that this flag could be expanded to
be the major device number of the primary protocol stack
that a pseudo SCSI device belongs to (e.g. IDE, USB,
IEEE1394 etc). This would allow a user mode notification
daemon to cross reference the primary protocol stack.
Doug Gilbert
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-01-18 21:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-11 21:56 SCSI Patches - mostly on/off-line stuff Douglas Gilbert
2001-01-11 22:43 ` Oliver.Neukum
2001-01-17 20:32 ` David Brownell
2001-01-18 0:08 ` Douglas Gilbert
2001-01-18 9:03 ` Oliver Neukum
2001-01-18 9:25 ` Miles Lane
2001-01-18 15:37 ` Eric Youngdale
2001-01-18 16:20 ` Venkatesh Ramamurthy
2001-01-18 16:49 ` Prasenjit Sarkar
2001-01-18 16:50 ` Venkatesh Ramamurthy
2001-01-18 17:03 ` Venkatesh Ramamurthy
2001-01-18 18:14 ` David Brownell
2001-01-18 19:12 ` Oliver Neukum
2001-01-18 19:20 ` Prasenjit Sarkar
2001-01-18 19:45 ` Miles Lane
2001-01-18 21:08 ` Douglas Gilbert [this message]
2001-01-18 21:41 ` Miles Lane
2001-01-18 22:07 ` David Brownell
2001-01-18 22:15 ` David Brownell
2001-01-18 22:45 ` Oliver Neukum
2001-01-18 23:10 ` Oliver Neukum
2001-01-18 23:25 ` Miles Lane
2001-01-18 23:37 ` Oliver Neukum
2001-01-19 2:08 ` David Brownell
2001-01-19 2:10 ` Bob Frey
2001-01-19 2:16 ` Venkatesh Ramamurthy
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-97985278930021@msgid-missing \
--to=dougg@torque.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.