From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Bottomley Subject: Re: scsi "target1:0:0" Date: 16 Nov 2004 11:25:23 -0600 Message-ID: <1100625933.2770.45.camel@mulgrave> References: <1100622096.8606.104.camel@localhost.localdomain> <1100622800.2574.41.camel@mulgrave> <1100624154.8606.122.camel@localhost.localdomain> <20041116171018.GK26623@parcelfarce.linux.theplanet.co.uk> <1100625783.4546.4.camel@davidz> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from stat16.steeleye.com ([209.192.50.48]:57819 "EHLO hancock.sc.steeleye.com") by vger.kernel.org with ESMTP id S262059AbUKPRZn (ORCPT ); Tue, 16 Nov 2004 12:25:43 -0500 In-Reply-To: <1100625783.4546.4.camel@davidz> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: David Zeuthen Cc: Matthew Wilcox , Kay Sievers , SCSI Mailing List On Tue, 2004-11-16 at 11:23, David Zeuthen wrote: > Please explain how you expect userspace to keep track of the device tree > and enforce policy if we don't get hotplug events for things in the > middle of the tree? The full path to the device is part of the environment of the event. Can't you simply parse this? I'm already getting complaints in the other direction (too many SCSI hotplug events) from the large system people. I'm really loth to introduce more simply as a convenience for a user space daemon. Really, I think there should only be hot plug events from real entities (which, more often than not are only the leaf nodes of the sysfs trees). James