From: Greg KH <greg@kroah.com>
To: James Bottomley <James.Bottomley@suse.de>
Cc: Hannes Reinecke <hare@suse.de>,
Nao Nishijima <nao.nishijima.xt@hitachi.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-hotplug@vger.kernel.org, Kay Sievers <kay.sievers@vrfy.org>,
Jon Masters <jcm@redhat.com>,
2nddept-manager@sdl.hitachi.co.jp
Subject: Re: [PATCH 1/2] SCSI: Add a SCSI option for persistent device names
Date: Fri, 08 Apr 2011 16:14:20 +0000 [thread overview]
Message-ID: <20110408161420.GB12111@kroah.com> (raw)
In-Reply-To: <1302275652.4090.10.camel@mulgrave.site>
On Fri, Apr 08, 2011 at 08:14:12AM -0700, James Bottomley wrote:
> So, while I agree totally with the above: udev and userspace is the way
> to go, I'm not totally opposed to having a non-invasive mechanism for
> indicating a user's preferred name for a device. I think there are a
> couple of ways to do this:
>
> 1. Entirely in userspace: just have udev consult a preferred name
> file and create say /dev/disk/by-preferred. Then have all the
> tools that normally output device information do the same (i.e.
> since real name to preferred name is 1:1, they could all do a
> reverse lookup).
> 2. have a writeable sysfs preferred_name field, either in the
> generic device or just in SCSI. The preferred name would be
> used by outbound only (i.e. kernel dev_printk messages and
> possibly /proc/partitions). All inbound uses of the device
> would come via the standard udev mechanisms
> (i.e. /dev/disk/by-preferred would be the usual symlink). This
> means from the kernel point of view, no renaming has happened.
> We'd just try to print out the preferred name in certain
> circumstances, which should solve most of the described problem.
Either, or both, of those options are fine with me as well.
thanks,
greg k-h
next prev parent reply other threads:[~2011-04-08 16:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 12:49 [PATCH 1/2] SCSI: Add a SCSI option for persistent device names in Nao Nishijima
2011-04-05 12:50 ` [PATCH 2/2] SCSI: modify SCSI subsystem Nao Nishijima
2011-04-05 16:14 ` [PATCH 1/2] SCSI: Add a SCSI option for persistent device names Greg KH
2011-04-08 14:12 ` Nao Nishijima
2011-04-08 14:33 ` Hannes Reinecke
2011-04-08 15:14 ` [PATCH 1/2] SCSI: Add a SCSI option for persistent device James Bottomley
2011-04-08 16:14 ` Greg KH [this message]
2011-04-08 16:43 ` [PATCH 1/2] SCSI: Add a SCSI option for persistent device names Kay Sievers
2011-04-12 13:23 ` Nao Nishijima
2011-04-12 13:29 ` [PATCH 1/2] SCSI: Add a SCSI option for persistent device James Bottomley
2011-04-14 2:06 ` [PATCH 1/2] SCSI: Add a SCSI option for persistent device names Nao Nishijima
2011-04-14 2:18 ` Greg KH
2011-04-08 17:21 ` Stefan Richter
2011-04-05 16:14 ` Greg KH
2011-04-08 14:07 ` Nao Nishijima
2011-04-08 16:12 ` Greg KH
2011-04-14 8:15 ` Nao Nishijima
2011-04-14 20:07 ` Greg KH
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=20110408161420.GB12111@kroah.com \
--to=greg@kroah.com \
--cc=2nddept-manager@sdl.hitachi.co.jp \
--cc=James.Bottomley@suse.de \
--cc=hare@suse.de \
--cc=jcm@redhat.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nao.nishijima.xt@hitachi.com \
/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).