From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gary_Lerhaupt@Dell.com Date: Fri, 13 Sep 2002 19:40:45 +0000 Subject: RE: Did you try devlabel Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org Yeah, a generic disk.agent would probably be a good idea to handle the devlabel calls and the rest of the agents could funnel through that or whatever. As for scsi_unique_id, its only good for SCSI devices. I think the man page should call this out clearly. For IDE things, you get the serial number from words 10-19 of /proc/ide/hd[a-z]/identify. So, in the meantime, to get devlabel officially working through hotplug, what direction should be taken? Gary -----Original Message----- From: David Brownell [mailto:david-b@pacbell.net] Sent: Friday, September 13, 2002 2:19 PM To: Gary_Lerhaupt@exchange.dell.com Cc: greg@kroah.com; Linux-hotplug-devel@lists.sourceforge.net Subject: Re: Did you try devlabel 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. ------------------------------------------------------- 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