From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752151AbbIQRrI (ORCPT ); Thu, 17 Sep 2015 13:47:08 -0400 Received: from mail-ob0-f169.google.com ([209.85.214.169]:36414 "EHLO mail-ob0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751371AbbIQRrG convert rfc822-to-8bit (ORCPT ); Thu, 17 Sep 2015 13:47:06 -0400 MIME-Version: 1.0 In-Reply-To: <20150917114955.GA2600@homura> References: <55FAA6BB.3060008@odi.ch> <20150917114955.GA2600@homura> Date: Thu, 17 Sep 2015 19:47:04 +0200 Message-ID: Subject: Re: Failover root devices From: Richard Weinberger To: Drew DeVault Cc: =?UTF-8?Q?Ortwin_Gl=C3=BCck?= , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Sep 17, 2015 at 1:49 PM, Drew DeVault wrote: > On 2015-09-17 1:40 PM, Ortwin Glück wrote: >> You can do that completely in user space from an initramfs. > > Yep, I'm aware of that. I think it would still be useful for the kernel > to support it. Bonus - if the kernel supports it, there's a standard way > of doing it that would propegate down to the various initramfs designs > of the distros without having me write patches against all of them. > Right? I really don't see why we need this feature in-kernel as it can be done perfectly fine in userspace. Every non-trivial system needs an initramfs anyway these days. -- Thanks, //richard