All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>,
	Christophe Varoqui <christophe.varoqui@opensvc.com>,
	Zdenek Kabelac <zkabelac@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>,
	Peter Volkov <peter.volkov@gmail.com>
Subject: Re: multipath-0.5.0 still provides broken udev rules
Date: Tue, 26 Apr 2016 07:53:48 +0200	[thread overview]
Message-ID: <571F026C.5040102@suse.de> (raw)
In-Reply-To: <1986ca6b-d281-4faf-2b50-11c3dc132463@gmail.com>

On 04/25/2016 10:14 PM, Xose Vazquez Perez wrote:
> On 04/25/2016 02:56 PM, Christophe Varoqui wrote:
> 
>> Those example udev rules are indeed unmaintained and should be
>> removed not to confuse distributors.
>>
>> Distributors can't be asked to agree on a common udev ruleset.
>> Ben, Hannes, Xosé, Peter are you ok with my deleting the udev rules example ?
> 
> Fine with me.
> 
> Btw, are these relevant ?
> 
> getuid/usb_id
Huh? What is that doing there?
It should really have been moved to the udev package ...

> kpartx/kpartx_id
> kpartx/kpartx.rules
See above. Yes, they are relevant (at least for us)

> multipath/01_udev
> multipath/02_multipath
Not used anymore with systemd/dracut

> multipath/11-dm-mpath.rules
Yep. Absolutely required.

> multipath.conf.annotated
> multipath.conf.defaults
> multipath.conf.synthetic
Actually, I never saw the need for those.
Can we at least have them merged?

> multipathd/multipathd.init.debian
> multipathd/multipathd.init.redhat
> multipathd/multipathd.init.suse
Old init scripts; doubtful value.

> multipathd/multipathd.service
> multipathd/multipathd.socket
systemd service definitions. Yes, required.

> multipath/multipath.init.suse
Old init script; not used anymore.

> multipath/multipath.rules
Yep. used for udev.

> multipath-tools.spec.in
> 
Well; due to our buildservice we have to keep a separate spec file
anyway. So ATM we don't use it.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		   Teamlead Storage & Networking
hare@suse.de			               +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

  reply	other threads:[~2016-04-26  5:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-25 10:52 multipath-0.5.0 still provides broken udev rules Peter Volkov
2016-04-25 10:58 ` Zdenek Kabelac
2016-04-25 12:10   ` Peter Volkov
2016-04-25 12:32     ` Zdenek Kabelac
2016-04-25 12:52       ` Peter Volkov
2016-04-25 12:56       ` Christophe Varoqui
2016-04-25 14:15         ` Peter Volkov
2016-04-25 17:38         ` Benjamin Marzinski
2016-04-26  5:43           ` Hannes Reinecke
2016-04-26  8:39             ` Zdenek Kabelac
2016-04-26  8:47               ` Hannes Reinecke
2016-04-26  9:19                 ` Zdenek Kabelac
2016-04-25 20:14         ` Xose Vazquez Perez
2016-04-26  5:53           ` Hannes Reinecke [this message]
2016-04-27 22:46             ` Benjamin Marzinski
2016-04-28  6:23               ` Hannes Reinecke
2016-04-28 22:10                 ` Benjamin Marzinski
2016-05-11 18:46                   ` Distributions mpt code Xose Vazquez Perez
2016-04-28 22:45                 ` multipath-0.5.0 still provides broken udev rules Benjamin Marzinski
2016-05-19 15:24               ` multipath-tools: irrelevant files Xose Vazquez Perez
2016-06-01 15:05                 ` Christophe Varoqui
2016-06-04  0:14                   ` multipath-tools: web Xose Vazquez Perez
2016-04-25 15:04 ` multipath-0.5.0 still provides broken udev rules Hannes Reinecke

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=571F026C.5040102@suse.de \
    --to=hare@suse.de \
    --cc=christophe.varoqui@opensvc.com \
    --cc=dm-devel@redhat.com \
    --cc=peter.volkov@gmail.com \
    --cc=xose.vazquez@gmail.com \
    --cc=zkabelac@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.