From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Did you try devlabel
Date: Fri, 13 Sep 2002 19:18:47 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-103194488806159@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-103185682023240@msgid-missing>
I'd kind of thought that this stuff should happen through some
kind of "disk" hotplug event. And maybe the natural spot for
such calls is driverfs: for devices in the "disk" class; but it
could also be called directly from each of the bus-specific disk
drivers (IDE, SCSI-over-{SCSI,USB,IDE,Firewire,...}, Flash, etc).
Given such a hotplug event, I think this package would simplify
a bit -- "/etc/hotplug/disk.agent" would replace patches for all
current (and future) bus agents. I'd prefer such a structure;
it could still handle SCSI of course.
I'd see SCSI hotplug as responsible for loading the SCSI disk or
cdrom driver ... and when those drivers found a device, they'd
trigger a "disk" hotplug event. Which would have the benefit of
whatever smarts the bus-specific disk driver could share.
There've been a lot of discussions about how to identify disks,
multipathing and so on. I think the conclusion was that some
user mode policy input was needed. Your scsi_unique_id program
seems like it'd be important for a number of SCSI configs, and
could grow to handle the bigger ones.
- Dave
p.s. Was /dev/hda supposed to work as input to 'scsi_unique_id'?
the man page implied it should, but that didn't work.
And I'd expect /usr/sbin for such sysadin tools.
Gary_Lerhaupt@Dell.com wrote:
> I haven't written the scsi hotplug patch but it should be trivial. On all
> storage hotplugs, at the very bottom of the add & remove calls, there should
> be:
>
> if [ -x /sbin/devlabel ]; then
> devlabel restart
> fi
>
> If you can think of a less intrusive method to get this kicked off on all
> add/remove events, I am game.
>
> gary
>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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:[~2002-09-13 19:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 18:46 Did you try devlabel Gary_Lerhaupt
2002-09-12 21:20 ` Gary_Lerhaupt
2002-09-12 22:15 ` Greg KH
2002-09-12 23:21 ` Gary_Lerhaupt
2002-09-12 23:26 ` Greg KH
2002-09-12 23:38 ` Gary_Lerhaupt
2002-09-13 5:50 ` Greg KH
2002-09-13 14:41 ` Gary_Lerhaupt
2002-09-13 19:18 ` David Brownell [this message]
2002-09-13 19:40 ` Gary_Lerhaupt
2002-09-13 19:52 ` Greg KH
2002-09-13 20:18 ` David Brownell
2002-09-13 20:39 ` Greg KH
2002-09-13 20:52 ` Gary_Lerhaupt
2002-09-13 21:02 ` Greg KH
2002-09-15 23:51 ` David Brownell
2002-09-16 22:54 ` Gary_Lerhaupt
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-103194488806159@msgid-missing \
--to=david-b@pacbell.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 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).