From: Richard Yao <ryao@gentoo.org>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-api@vger.kernel.org
Subject: Re: Why not make kdbus use CUSE?
Date: Mon, 01 Dec 2014 23:31:27 -0500 [thread overview]
Message-ID: <547D409F.7090004@gentoo.org> (raw)
In-Reply-To: <20141201142311.37c81ff1@lxorguk.ukuu.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]
On 12/01/2014 09:23 AM, One Thousand Gnomes wrote:
>> 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).
If the shim were in glibc, then that would be reasonable, but the shim
is in systemd. That would make the systemd developers the gate keepers
ta kernel interface. If we are going to enforce Linus' stable API
policy, then the shim should be in a repository that has a track record
for interface stability, which the systemd developers simply do not
have. It was not that long ago that firmware loading was moved into the
kernel because they had caused problems. I do not think that the systemd
developers are the correct ones to assume stewardship over such code. If
kdbus is merged, I think the best situation would be to move it into
Linus' tree.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]
prev parent reply other threads:[~2014-12-02 4:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-29 6:34 Why not make kdbus use CUSE? Richard Yao
2014-11-29 17:59 ` Greg Kroah-Hartman
2014-12-02 5:40 ` Richard Yao
2014-12-02 5:48 ` Greg Kroah-Hartman
2014-12-02 7:59 ` Richard Yao
2014-12-02 12:22 ` Richard Yao
2014-12-02 17:26 ` Greg Kroah-Hartman
2014-12-03 9:22 ` Richard Yao
2014-12-03 21:15 ` Greg Kroah-Hartman
2014-12-02 17:12 ` Greg Kroah-Hartman
2014-12-01 14:23 ` One Thousand Gnomes
2014-12-02 4:31 ` Richard Yao [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=547D409F.7090004@gentoo.org \
--to=ryao@gentoo.org \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox