From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751659AbbIQLt7 (ORCPT ); Thu, 17 Sep 2015 07:49:59 -0400 Received: from mail.cmpwn.com ([45.56.77.53]:37211 "EHLO mail.cmpwn.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751059AbbIQLt6 (ORCPT ); Thu, 17 Sep 2015 07:49:58 -0400 Date: Thu, 17 Sep 2015 07:49:55 -0400 From: Drew DeVault To: Ortwin =?iso-8859-1?Q?Gl=FCck?= Cc: "linux-kernel@vger.kernel.org" Subject: Re: Failover root devices Message-ID: <20150917114955.GA2600@homura> References: <55FAA6BB.3060008@odi.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <55FAA6BB.3060008@odi.ch> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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'm working on an initramfs-based solution that meets my own needs, for what it's worth. > Above script actually makes it easy by supporting disk labels: > root=LABEL=ROOT will boot the first available partition that is labelled > ROOT. It is independent of the device name and works nice when you switch > hardware vs. virtual machines for instance. This is a neat idea, I'll check it out. -- Drew DeVault