From: Hannes Reinecke <hare@suse.de>
To: Benjamin Marzinski <bmarzins@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>,
Harald Hoyer <harald@redhat.com>
Subject: root on multipath and dracut
Date: Mon, 10 Feb 2014 14:30:56 +0100 [thread overview]
Message-ID: <52F8D490.8000500@suse.de> (raw)
Hi Ben,
as we're switching to dracut/systemd nowadays I've tried to setup
and enable root on multipath for this, too.
As you might've seen, I've already added proper systemd support for
multipath-tools, so it should be easy to plug it into dracut.
Or so I thought.
As it turns out, dracut is trying to add some RH-specific rules files:
40-multipath.rules
62-multipath.rules
65-multipath.rules
which have only _very_ sparse documentation.
Wouldn't it be a good idea to settle on a default set on scripts
here and include those into the multipath-tools repository?
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)
next reply other threads:[~2014-02-10 13:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 13:30 Hannes Reinecke [this message]
2014-02-10 14:34 ` root on multipath and dracut Harald Hoyer
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=52F8D490.8000500@suse.de \
--to=hare@suse.de \
--cc=bmarzins@redhat.com \
--cc=dm-devel@redhat.com \
--cc=harald@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.