From: One Thousand Gnomes <gnomes-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>
To: Richard Yao <ryao-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Greg Kroah-Hartman
<gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>,
linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Why not make kdbus use CUSE?
Date: Mon, 1 Dec 2014 14:23:11 +0000 [thread overview]
Message-ID: <20141201142311.37c81ff1@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20141129063416.GE32286-WkJ4KB730YtOk+SH+krGketnjj8NnB7F@public.gmane.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
next prev parent reply other threads:[~2014-12-01 14:23 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
[not found] ` <20141129063416.GE32286-WkJ4KB730YtOk+SH+krGketnjj8NnB7F@public.gmane.org>
2014-11-29 17:59 ` Greg Kroah-Hartman
[not found] ` <20141129175947.GB32510-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2014-12-02 5:40 ` Richard Yao
[not found] ` <547D50B9.9040909-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2014-12-02 5:48 ` Greg Kroah-Hartman
2014-12-02 7:59 ` Richard Yao
2014-12-02 12:22 ` Richard Yao
[not found] ` <547DAEF3.1090106-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2014-12-02 17:26 ` Greg Kroah-Hartman
[not found] ` <20141202172612.GA8958-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2014-12-03 9:22 ` Richard Yao
[not found] ` <547ED659.2040106-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2014-12-03 21:15 ` Greg Kroah-Hartman
[not found] ` <547D7159.2040900-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2014-12-02 17:12 ` Greg Kroah-Hartman
2014-12-01 14:23 ` One Thousand Gnomes [this message]
[not found] ` <20141201142311.37c81ff1-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>
2014-12-02 4:31 ` Richard Yao
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=20141201142311.37c81ff1@lxorguk.ukuu.org.uk \
--to=gnomes-qbu/x9rampvanceybjwyrvxrex20p6io@public.gmane.org \
--cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ryao-aBrp7R+bbdUdnm+yROfE0A@public.gmane.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