From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752392AbbIQRtU (ORCPT ); Thu, 17 Sep 2015 13:49:20 -0400 Received: from mail.cmpwn.com ([45.56.77.53]:37287 "EHLO mail.cmpwn.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751979AbbIQRtT (ORCPT ); Thu, 17 Sep 2015 13:49:19 -0400 Subject: Re: Failover root devices To: Richard Weinberger References: <55FAA6BB.3060008@odi.ch> <20150917114955.GA2600@homura> Cc: =?UTF-8?Q?Ortwin_Gl=c3=bcck?= , "linux-kernel@vger.kernel.org" From: Drew DeVault Message-ID: <55FAFD1D.8030305@cmpwn.com> Date: Thu, 17 Sep 2015 13:49:17 -0400 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > 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. Most initramfs systems will parse the root= line of your kernel command line and use it to remount root. The kernel seems like the best place to establish this, since the various initramfs solutions will implement the same format just to support parsing the kernel command line correctly. I mean, maybe that's not enough to justify putting it in the kernel, but that's why I see the kernel as the appropriate place to implement this feature. -- Drew DeVault