Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966250AbbD2OLX (ORCPT ); Wed, 29 Apr 2015 10:11:23 -0400 Received: from mx1.redhat.com ([209.132.183.28]:36614 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966088AbbD2OLV (ORCPT ); Wed, 29 Apr 2015 10:11:21 -0400 Message-ID: <5540E684.4070606@redhat.com> Date: Wed, 29 Apr 2015 16:11:16 +0200 From: Harald Hoyer User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Richard Weinberger CC: "linux-kernel@vger.kernel.org" Subject: Re: [GIT PULL] kdbus for 4.1-rc1 References: <20150423163616.GA10874@kroah.com> <20150423171640.GA11227@kroah.com> <553A4A2F.5090406@samsung.com> <20150428171840.GB11351@thunk.org> <21824.5086.446831.189915@quad.stoffel.home> <5540D2F9.2010704@redhat.com> <5540DEEB.2060405@redhat.com> <5540E0C7.3050106@nod.at> <5540E432.9020606@redhat.com> <5540E4D9.6000007@nod.at> In-Reply-To: <5540E4D9.6000007@nod.at> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2027 Lines: 45 On 29.04.2015 16:04, Richard Weinberger wrote: > Am 29.04.2015 um 16:01 schrieb Harald Hoyer: >> 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, […] > > This is correct. But which of these tools/features depend on dbus? I would love to add dbus support to all of them and use it, so I can connect them all more easily. No need for them to invent their own version of IPC, which can only be used by their own tool set. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/