From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: [PATCH 1/3] [RFC] genhd: add a new attribute in device structure Date: Thu, 16 Jun 2011 19:02:33 +0100 Message-ID: <20110616180233.GN11521@ZenIV.linux.org.uk> References: <20110615081610.2237.44767.stgit@ltc233.sdl.hitachi.co.jp> <20110615081627.2237.9620.stgit@ltc233.sdl.hitachi.co.jp> <20110615153337.GA10160@kroah.com> <4DF9F11F.705@hitachi.com> <20110616154129.GA31498@kroah.com> <1308239454.2436.34.camel@mulgrave> <4DFA3E1A.9050207@interlog.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4DFA3E1A.9050207@interlog.com> Sender: linux-kernel-owner@vger.kernel.org To: Douglas Gilbert Cc: James Bottomley , Greg KH , Nao Nishijima , linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org, kay.sievers@vrfy.org, jcm@redhat.com, hare@suse.de, stefanr@s5r6.in-berlin.de, yrl.pp-manager.tt@hitachi.com List-Id: linux-scsi@vger.kernel.org On Thu, Jun 16, 2011 at 01:32:10PM -0400, Douglas Gilbert wrote: > As James' notes each storage device can only have one > "preferred name" at a time. But how can that preferred name > be represented in sysfs ? If /sys/block/ > suddenly changed to /sys/block/ that would > be very disruptive. I would prefer something like > /sys/class/block_preferred_name/ was introduced > as a symlink to /sys/block/ but that would require > that all s were unique. [Not a bad restriction > IMO]. If the was only placed in the > /sys/block/ directory that would be ugly from > the user space tool point of view. Oh, rapture... so now we can expect the container crowd to introduce yet *another* "namespace" ;-/