linux-kernel - Re: [GIT PULL] kdbus for 4.1-rc1

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: <20150429150341.GA12374@thunk.org>
Date:	Wed, 29 Apr 2015 11:03:41 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Harald Hoyer <harald@...hat.com>
Cc:	Richard Weinberger <richard@....at>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] kdbus for 4.1-rc1

On Wed, Apr 29, 2015 at 04:53:53PM +0200, Harald Hoyer wrote:
> Sure, I can write one binary to rule them all, pull out all the code from all
> tools I need, but for me an IPC mechanism sounds a lot better. And it should be
> _one_ common IPC mechanism and not a plethora of them. It should feel like an
> operating system and not like a bunch of thrown together software, which is
> glued together with some magic shell scripts.

And so requiring wireshark (and X?) in initramfs to debug problems
once dbus is introduced is better?

I would think shell scripts are *easier* to debug when things go
wrong, especially in a minimal environment such as an initial ram
disk.  Having had to debug problems in a distro initramfs when trying
to help a customer bring up a FC boot disk long ago in another life,
I'm certain I would rather debug problems while on site at a
classified machine room[1] using shell scripts, and trying to debug
dbus is something that would be infinitely worse.

						- Ted

[1] So no laptop, no google, no access to sources to figure out random
dbus messages, etc.
--
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/