Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966131AbbD2Qhj (ORCPT ); Wed, 29 Apr 2015 12:37:39 -0400 Received: from mail.lang.hm ([64.81.33.126]:59568 "EHLO bifrost.lang.hm" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964905AbbD2Qhf (ORCPT ); Wed, 29 Apr 2015 12:37:35 -0400 Date: Wed, 29 Apr 2015 09:36:46 -0700 (PDT) From: David Lang X-X-Sender: dlang@asgard.lang.hm To: Martin Steigerwald cc: Harald Hoyer , John Stoffel , Havoc Pennington , "Theodore Ts'o" , Linus Torvalds , Andy Lutomirski , Lukasz Skalski , Greg Kroah-Hartman , Andrew Morton , Arnd Bergmann , "Eric W. Biederman" , One Thousand Gnomes , Tom Gundersen , Jiri Kosina , "linux-kernel@vger.kernel.org" , Daniel Mack , David Herrmann , Djalal Harouni Subject: Re: [GIT PULL] kdbus for 4.1-rc1 In-Reply-To: <1608909.Hzt9NDh2yO@merkaba> Message-ID: References: <20150423163616.GA10874@kroah.com> <21824.5086.446831.189915@quad.stoffel.home> <5540D2F9.2010704@redhat.com> <1608909.Hzt9NDh2yO@merkaba> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1443 Lines: 31 On Wed, 29 Apr 2015, Martin Steigerwald wrote: > Am Mittwoch, 29. April 2015, 14:47:53 schrieb Harald Hoyer: >> We really don't want the IPC mechanism to be in a flux state. All tools >> have to fallback to a non-standard mechanism in that case. >> >> If I have to pull in a dbus daemon in the initramfs, we still have the >> chicken and egg problem for PID 1 talking to the logging daemon and >> starting dbus. >> systemd cannot talk to journald via dbus unless dbus-daemon is started, >> dbus cannot log anything on startup, if journald is not running, etc... > > Do I get this right that it is basically a userspace *design* decision > that you use as a reason to have kdbus inside the kernel? > > Is it really necessary to use DBUS for talking to journald? And does it > really matter that much if any message before starting up dbus do not > appear in the log? /proc/kmsg is a ring buffer, it can still be copied over > later. I've been getting the early boot messages in my logs for decades (assuming the system doesn't fail before the syslog daemon is started). It sometimes has required setting a larger than default ringbuffer in the kernel, but that's easy enough to do. David Lang -- 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/