From: Michal Soltys <soltys-R61QfzASbfY@public.gmane.org>
To: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RFC 0/6] Update 90mdraid
Date: Sun, 11 Sep 2011 01:33:04 +0200 [thread overview]
Message-ID: <4E6BF3B0.6040505@ziu.info> (raw)
In-Reply-To: <1315261048-19544-1-git-send-email-soltys-R61QfzASbfY@public.gmane.org>
Either way, I'll be doing v2 with quite a bit different approach - a
clean split for mdadm 2.x (pre-udev/pre-container) and 3.x - as things
are a little bit different with both of those.
Also, 2.x path is better with -As and conf file telling what to do,
while 3.x with -I and conf telling what not to do (trivially allowing
the same behaviour as with old -As). Some details about conf file are
also different, so this approach should be cleaner than trying to throw
everything into one big bag.
From other changes I'm thinking about adding few potentially useful
options - assembly by name (storing one is supported by 1.x and ddf),
controlling force-run, allowing partitionable raid on <2.6.28 kernels,
and few other lesser details.
next prev parent reply other threads:[~2011-09-10 23:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 22:17 [RFC 0/6] Update 90mdraid Michal Soltys
[not found] ` <1315261048-19544-1-git-send-email-soltys-R61QfzASbfY@public.gmane.org>
2011-09-05 22:17 ` [RFC 1/6] 90mdraid: adjust stock mdadm udev rules Michal Soltys
2011-09-05 22:17 ` [RFC 2/6] 90(md|dm)raid: recognize ddf container Michal Soltys
2011-09-05 22:17 ` [RFC 3/6] 90mdraid: containers are not runnable Michal Soltys
2011-09-05 22:17 ` [RFC 4/6] 90mdraid: fix/adjust mdraid-cleanup Michal Soltys
2011-09-05 22:17 ` [RFC 5/6] 90mdraid: fix/adjust force-run script Michal Soltys
2011-09-05 22:17 ` [RFC 6/6] 90mdraid: fix/adjust 65-md* rules and related scripts Michal Soltys
2011-09-09 20:02 ` question - minimal mdadm version Michal Soltys
2011-09-10 23:33 ` Michal Soltys [this message]
2011-09-22 13:45 ` [RFC 0/6] Update 90mdraid 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=4E6BF3B0.6040505@ziu.info \
--to=soltys-r61qfzasbfy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox