[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5540E432.9020606@redhat.com>
Date: Wed, 29 Apr 2015 16:01:22 +0200
From: Harald Hoyer <harald@...hat.com>
To: Richard Weinberger <richard@....at>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] kdbus for 4.1-rc1
On 29.04.2015 15:46, Richard Weinberger wrote:
> Am 29.04.2015 um 15:38 schrieb Harald Hoyer:
>> On 29.04.2015 15:33, Richard Weinberger wrote:
>>> It depends how you define "beginning". To me an initramfs is a *very* minimal
>>> tool to prepare the rootfs and nothing more (no udev, no systemd, no
>>> "mini distro").
>>> If the initramfs fails to do its job it can print to the console like
>>> the kernel does if it fails
>>> at a very early stage.
>>>
>>
>> Your solution might work for your small personal needs, but not for our customers.
>
> Correct, I don't know your customers, all I know are my customers. :-)
>
> What feature do your customers need?
> I mean, I fully agree with you that an initramfs must not fail silently
> but how does dbus help there? If it fails to mount the rootfs there is not
> much it can do.
>
> Thanks,
> //richard
>
We don't handcraft the initramfs script for every our customers, therefore we
have to generically support hotplug, persistent device names, persistent
interface names, network connectivity in the initramfs, user input handling for
passwords, fonts, keyboard layouts, fips, fsck, repair tools for file systems,
raid assembly, LVM assembly, multipath, crypto devices, live images, iSCSI,
FCoE, all kinds of filesystems with their quirks, IBM z-series support, resume
from hibernation, […]
And no, this is not a simple minimal tool.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists