Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753760AbaLAOXo (ORCPT ); Mon, 1 Dec 2014 09:23:44 -0500 Received: from 251.110.2.81.in-addr.arpa ([81.2.110.251]:53232 "EHLO lxorguk.ukuu.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753355AbaLAOXn (ORCPT ); Mon, 1 Dec 2014 09:23:43 -0500 Date: Mon, 1 Dec 2014 14:23:11 +0000 From: One Thousand Gnomes To: Richard Yao Cc: linux-kernel@vger.kernel.org, Greg Kroah-Hartman , linux-api@vger.kernel.org Subject: Re: Why not make kdbus use CUSE? Message-ID: <20141201142311.37c81ff1@lxorguk.ukuu.org.uk> In-Reply-To: <20141129063416.GE32286@woodpecker.gentoo.org> References: <20141129063416.GE32286@woodpecker.gentoo.org> Organization: Intel Corporation X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.24; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > told quite plainly that such distributions are not worth consideration. If kdbus > is merged despite concerns about security and backward compatibility, could we > at least have the shim moved to libc netural place, like Linus' tree? I would expect any other libc would fork the shim anyway (or just not bother with systemd in most cases). Alan -- 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/