linux-kernel - Re: Failover root devices

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <55FB087C.1050105@gmail.com>
Date:	Thu, 17 Sep 2015 14:37:48 -0400
From:	Austin S Hemmelgarn <ahferroin7@...il.com>
To:	Richard Weinberger <richard.weinberger@...il.com>,
	Drew DeVault <sir@...wn.com>
Cc:	Ortwin Glück <odi@....ch>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Failover root devices

On 2015-09-17 13:47, Richard Weinberger wrote:
> On Thu, Sep 17, 2015 at 1:49 PM, Drew DeVault <sir@...wn.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.


Download attachment "smime.p7s" of type "application/pkcs7-signature" (3019 bytes)