From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Richard Weinberger <richard@nod.at>,
Richard Weinberger <richard.weinberger@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: Fri, 18 Sep 2015 10:40:00 -0400 [thread overview]
Message-ID: <55FC2240.8000309@gmail.com> (raw)
In-Reply-To: <55FB0923.30505@nod.at>
[-- Attachment #1: Type: text/plain, Size: 1527 bytes --]
On 2015-09-17 14:40, Richard Weinberger wrote:
> Am 17.09.2015 um 20:37 schrieb Austin S Hemmelgarn:
>> On 2015-09-17 13:47, Richard Weinberger wrote:
>>> On Thu, Sep 17, 2015 at 1:49 PM, Drew DeVault <sir@cmpwn.com> 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.
>>>
>> Ha, not unless you're using systemd. I have more than 2 dozen servers with complex setups that boot just fine without an initramfs. Yes there is more setup done in initramfs
>> these days, but it's still not actually needed in most cases except complicated storage setups.
>
> I really don't count root=UUID... or root=LABEL... as complicated storage setup...
>
> Thanks,
> //richard
>
That's not what I mean, I mean stuff like /usr and /var on separate
filesystems, in a couple of cases self-assembling MD arrays, and in a
couple of cases ATAoE or iSCSI backed root filesystems on hardware that
doesn't natively support booting such devices.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
next prev parent reply other threads:[~2015-09-18 14:40 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
2015-09-17 18:37 ` Austin S Hemmelgarn
2015-09-17 18:40 ` Richard Weinberger
2015-09-18 14:40 ` Austin S Hemmelgarn [this message]
-- 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=55FC2240.8000309@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=odi@odi.ch \
--cc=richard.weinberger@gmail.com \
--cc=richard@nod.at \
--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