public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Harald Hoyer <harald.hoyer@gmail.com>, Drew DeVault <sir@cmpwn.com>
Cc: "Ortwin Glück" <odi@odi.ch>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Failover root devices
Date: Thu, 17 Sep 2015 20:29:34 +0200	[thread overview]
Message-ID: <55FB068E.1080000@nod.at> (raw)
In-Reply-To: <55FB060E.6080503@gmail.com>

Am 17.09.2015 um 20:27 schrieb Harald Hoyer:
> On 17.09.2015 20:17, Richard Weinberger wrote:
>> Am 17.09.2015 um 20:05 schrieb Drew DeVault:
>>>> Better send a patch to dracut folks. :-)
>>>> Major distros use it and if the feature is nice other initramfs implementations will adopt it too.
>>>
>>> dracut is the common one sure, but I'm still not confident that it's the right place to put this. How would that feature look? Would we have the root= parameter use a format that's
>>> specific to dracut and no longer a sane kernel parameter? Would we use a second parameter and discard the root= parameter? I think all of these are suboptimal solutions. No, the
>>> right way, I think, is to implement this in the kernel and let the init systems take it from there themselves.
>>
>> I'd patch dracut to support kernel command lines like "root=/dev/diskX root=/dev/diskY". initramfs is allowed to parse/use the command line.
>> So, you can do what you want.
>>
>> Thanks,
>> //richard
> 
> 
> https://github.com/haraldh/dracut/blob/master/modules.d/95rootfs-block/rootfallback.sh

Awesome! :-)

Thanks,
//richard

  parent reply	other threads:[~2015-09-17 18:29 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17 11:40 Failover root devices Ortwin Glück
2015-09-17 11:49 ` Drew DeVault
2015-09-17 17:47   ` Richard Weinberger
2015-09-17 17:49     ` Drew DeVault
2015-09-17 17:52       ` Richard Weinberger
2015-09-17 18:05         ` Drew DeVault
2015-09-17 18:17           ` Richard Weinberger
2015-09-17 18:18             ` Drew DeVault
2015-09-17 18:19               ` Richard Weinberger
2015-09-17 18:21                 ` Drew DeVault
2015-09-17 18:23                   ` Richard Weinberger
2015-09-17 18:28                     ` Drew DeVault
2015-09-18 14:59                       ` Ortwin Glück
2015-09-18 15:00                         ` Drew DeVault
2015-09-18 15:04                           ` Ortwin Glück
2015-09-18 15:36                             ` Austin S Hemmelgarn
2015-09-17 18:27             ` Harald Hoyer
2015-09-17 18:29               ` Drew DeVault
2015-09-17 18:33                 ` Richard Weinberger
2015-09-17 18:35                   ` Drew DeVault
2015-09-17 18:42                     ` Richard Weinberger
2015-09-17 18:29               ` Richard Weinberger [this message]
2015-09-17 18:37     ` Austin S Hemmelgarn
2015-09-17 18:40       ` Richard Weinberger
2015-09-18 14:40         ` Austin S Hemmelgarn
  -- strict thread matches above, loose matches on Subject: below --
2015-09-17  0:16 Drew DeVault
2015-09-17 16:02 ` Austin S Hemmelgarn
2015-09-17 17:30   ` Drew DeVault
2015-09-18 14:34     ` Austin S Hemmelgarn
2015-09-18 14:43       ` Drew DeVault

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=55FB068E.1080000@nod.at \
    --to=richard@nod.at \
    --cc=harald.hoyer@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=odi@odi.ch \
    --cc=sir@cmpwn.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox