All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes.sorensen@gmail.com>
To: NeilBrown <neilb@suse.com>
Cc: linux-raid <linux-raid@vger.kernel.org>,
	Hannes Reinecke <hare@suse.de>,
	kernel-team@fb.com
Subject: Re: Can we deprecate ioctl(RAID_VERSION)?
Date: Tue, 11 Apr 2017 10:46:06 -0400	[thread overview]
Message-ID: <fad96876-017b-ae43-a11d-6c0ea42fdbcf@gmail.com> (raw)
In-Reply-To: <878tn9yymi.fsf@notabene.neil.brown.name>

On 04/09/2017 07:01 PM, NeilBrown wrote:
> On Fri, Apr 07 2017, jes.sorensen@gmail.com wrote:
>
>>
>> Next question since I am wearing my 'what is this old stuff doing' hat.
>> mdassemble? Does anything still use this? The reason is a lot of the
>> newer features are explicitly included, and switching to sysfs is
>> effectively going to kill it, unless it gets a major upgrade.
>>
>
> I was never a big fan, of mdassemble, but it is smaller than mdadm and
> some people apparently have (or had) space-constrained boot
> environments.
> Maybe post to the linux-raid list with a subject "mdassemble is going
> way, do you care?". ??

Makes sense - looking at the code it wasn't clear if it is even usable 
in modern times since it ignores sysfs access.

I'll post another message and get out the big hammer!

Cheers,
Jes



      parent reply	other threads:[~2017-04-11 14:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-05 17:55 Can we deprecate ioctl(RAID_VERSION)? jes.sorensen
2017-04-05 19:02 ` jes.sorensen
2017-04-05 22:32   ` NeilBrown
2017-04-06 15:31     ` Jes Sorensen
2017-04-06 18:10       ` Coly Li
2017-04-06 18:14         ` Jes Sorensen
2017-04-07  3:54           ` Coly Li
2017-04-07 14:54             ` Jes Sorensen
2017-04-06 22:44       ` NeilBrown
2017-04-07 15:55         ` jes.sorensen
2017-04-09 23:01           ` NeilBrown
2017-04-10  9:26             ` Nix
2017-04-11 14:46             ` Jes Sorensen [this message]

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=fad96876-017b-ae43-a11d-6c0ea42fdbcf@gmail.com \
    --to=jes.sorensen@gmail.com \
    --cc=hare@suse.de \
    --cc=kernel-team@fb.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.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.