From: Martin Wilck <mwilck-l3A5Bk7waGM@public.gmane.org>
To: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RFC/PATCH] Give --persistent_policy precedence over /dev/mapper names
Date: Mon, 17 Oct 2016 11:18:31 +0200 [thread overview]
Message-ID: <1476695911.4871.2.camel@suse.de> (raw)
In-Reply-To: <20161005121303.31582-1-mwilck-l3A5Bk7waGM@public.gmane.org>
On Wed, 2016-10-05 at 14:13 +0200, Martin Wilck wrote:
> There is currently no way to override dracut's preference for
> /dev/mapper device names. But using these is problematic in
> different scenarios: For example, if a user has a multipath-
> enabled system but wants to disable multipath, or if the
> names of multipath maps change because of configuration changes
> (e.g. toggling user_friendly_names in /etc/multipath.conf).
>
> This patch makes dracut prefer the user-specified
> --persistent_policy names over /dev/mapper names.
>
> It might be worthwhile to discuss why dracut prefers /dev/mapper
> of /dev/disk/by-uuid at all. This preference was introduced
> in 9037b63e with the argument "dm devices maintain /dev/mapper/* as
> persistent names", but that's wrong for the scenarios mentioned
> above, and is not a compelling reason for preferring /dev/mapper
> over /dev/disk/by-uuid.
Ping - does nobody have an opinion on this suggestion?
Regards
Martin
next prev parent reply other threads:[~2016-10-17 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 12:13 [RFC/PATCH] Give --persistent_policy precedence over /dev/mapper names Martin Wilck
[not found] ` <20161005121303.31582-1-mwilck-l3A5Bk7waGM@public.gmane.org>
2016-10-17 9:18 ` Martin Wilck [this message]
2016-10-26 11:45 ` Harald Hoyer
[not found] ` <e8384369-a93f-63b1-9422-21c9d5bce657-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-10-27 7:18 ` Martin Wilck
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=1476695911.4871.2.camel@suse.de \
--to=mwilck-l3a5bk7wagm@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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.