[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrVRkO-KRTtnX69ku5DkVLmFLbMqK22B1xyEpWt-o-xK9Q@mail.gmail.com>
Date: Tue, 21 Oct 2014 12:47:47 -0700
From: Andy Lutomirski <luto@...capital.net>
To: Al Viro <viro@...iv.linux.org.uk>
Cc: Bastien Nocera <hadess@...ess.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: A desktop environment[1] kernel wishlist
On Tue, Oct 21, 2014 at 12:43 PM, Al Viro <viro@...iv.linux.org.uk> wrote:
> On Tue, Oct 21, 2014 at 12:28:12PM -0700, Andy Lutomirski wrote:
>
>> Why is kdbus needed?
>
> Presumably because freedesktop crowd has made an architectural mistake and
> pushed dbus as solution to all problems. And ran into limitations of
> that, er, solution. Then, instead of perhaps reconsidering the wisdom of
> their inspired decision, went for "let's push it kernelwards, it might
> somewhat reduce the overhead and problems will be easier to chalk up to
> something wrong being done by the kernel".
Well, yes, but the question I was actually trying to ask is: why does
a containerized app need any kernel help at all for communication with
the rest of the system (using dbus or anything else)? Passing socket
fds into a container works just fine.
--Andy
--
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