| 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
| ||
|
Message-ID: <5540E821.8050204@nod.at> Date: Wed, 29 Apr 2015 16:18:09 +0200 From: Richard Weinberger <richard@....at> To: Harald Hoyer <harald@...hat.com> CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [GIT PULL] kdbus for 4.1-rc1 Am 29.04.2015 um 16:11 schrieb Harald Hoyer: >>> 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. Why/how do you need to connect them? Sorry for being persistent but as I use most of these tools too (also in initramfs) I'm very curious. Many of us grumpy kernel devs simply don't know all the use case of you have to cover. So, please explain. :-) Thanks, //richard -- 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