All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francis Moreau <francis.moro-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: dracut: qestions about mdraid module
Date: Sat, 27 Sep 2014 17:21:42 +0200	[thread overview]
Message-ID: <5426D606.6020300@gmail.com> (raw)

Hello,

I'm looking at the module 'mdraid' of dracut (0.38) and was wondering
the purpose of rd.md.uuid= parameter.

I understand it can be used to selectively activate the array matching
the UUID passed through the parameter but I'm wondering in which cases
it can be useful...

Also I don't really understand why dracut try to do its own mechanism to
achieve that (by providing its own udev rules which are modified at boot
time) whereas mdadm already provide the infrastructure (through
mdadm.conf) in a cleaner way (IMHO).

Another question, hopefully you don't mind: dracut provide an udev set
of rules in a file named 59-persistent-storage-md.rules. I still don't
really see the point since most of the stuff in it seems to already be
done by the rule fileudev-md-raid-arrays.rules, shipped by mdadm (3.3.2).

Ah my last question not related to mdraid: why dracut uses stderr to
print out all its messages: info, debug, error. Stderr is usually used
for error/warning messages only.

Thanks !

             reply	other threads:[~2014-09-27 15:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-27 15:21 Francis Moreau [this message]
     [not found] ` <5426D606.6020300-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-10-20 11:02   ` dracut: qestions about mdraid module Harald Hoyer
     [not found]     ` <5444EBDF.7090004-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-10-21 12:35       ` Francis Moreau
     [not found]         ` <5446532E.3050304-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-10-21 15:06           ` Andrei Borzenkov

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=5426D606.6020300@gmail.com \
    --to=francis.moro-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=harald-H+wXaHxf7aLQT0dZR+AlfA@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.