From: Ritesh Raj Sarraf <rsarraf@netapp.com>
To: Alasdair G Kergon <agk@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH] Rename prio callout program mpath_prio_netapp to mpath_prio_ontap
Date: Thu, 4 Oct 2007 22:05:16 +0530 [thread overview]
Message-ID: <200710042205.23145.rsarraf@netapp.com> (raw)
In-Reply-To: <20071004110157.GR18444@agk.fab.redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 1077 bytes --]
Hi,
On Thursday 04 October 2007, Alasdair G Kergon wrote:
> On Thu, Oct 04, 2007 at 02:55:19PM +0530, Ritesh Raj Sarraf wrote:
> > Attached are 2 patches to rename the callout program from
> > mpath_prio_netapp to mpath_prio_ontap.
>
> We're unable to take such a patch into RHEL directly because it is removing
> a program that was there before and that breaks backwards compatibility,
> but how about maintaining a symlink from the old location?
>
We've been shipping the mpath_prio_ontap callout program for more than a year
with our software kit (which is supposed to be installed on top of our
supported Linux operating systems). So customers who'd have followed our
setup guides should not be hit by any compatibility issues.
We're looking forward to using "mpath_prio_ontap" as the name because it is
more generic and serves our additional needs.
For RHEL5/4 series, is it okay to have "mpath_prio_netapp" as a link pointing
to "mpath_prio_ontap" ?
As for RHEL6 and ahead, we could just remove "mpath_prio_netapp".
Thanks,
Ritesh
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2007-10-04 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 9:25 [PATCH] Rename prio callout program mpath_prio_netapp to mpath_prio_ontap Ritesh Raj Sarraf
2007-10-04 11:01 ` Alasdair G Kergon
2007-10-04 16:35 ` Ritesh Raj Sarraf [this message]
2007-10-04 16:51 ` Alasdair G Kergon
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=200710042205.23145.rsarraf@netapp.com \
--to=rsarraf@netapp.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.