From: Hannes Reinecke <hare@suse.de>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Priozier for remote port on fibre channel devices
Date: Fri, 11 Jan 2013 09:42:49 +0100 [thread overview]
Message-ID: <50EFD089.9050606@suse.de> (raw)
In-Reply-To: <OFE9A4507F.3E574BF0-ONC1257AF0.002D3A81-C1257AF0.002DAC1C@continental-corporation.com>
On 01/11/2013 09:18 AM,
Andreas.Bleischwitz@continental-corporation.com wrote:
> Thanks for the hint, that will at least work for RHEL6+. For RHEL5 I
> will use the scripted version.
>
> The only downside on that is, that I will have a long line for the
> weightedpath regex definition as this has to be for each VPLEX-port.
> At least I will have reduced the need to write something on my own ;)
>
Or write you own udev rules to generate shorter names ...
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
prev parent reply other threads:[~2013-01-11 8:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 7:11 Priozier for remote port on fibre channel devices Andreas.Bleischwitz
2013-01-11 7:22 ` Hannes Reinecke
2013-01-11 7:47 ` Andreas.Bleischwitz
2013-01-11 8:06 ` Hannes Reinecke
2013-01-11 8:18 ` Andreas.Bleischwitz
2013-01-11 8:42 ` Hannes Reinecke [this message]
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=50EFD089.9050606@suse.de \
--to=hare@suse.de \
--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.