On Thu, 4 Sep 2014 12:06:29 -0300
Henrique de Moraes Holschuh wrote:
> https://lwn.net/Articles/405346/
> https://lwn.net/Articles/484203/
> https://lwn.net/Articles/580194/
> https://lwn.net/Articles/537017/
> https://lwn.net/Articles/551969/
Thanks for these very interesting links.
> Be sure
On Thu, 4 Sep 2014 02:42:33 +0200
B wrote:
> On Thu, 4 Sep 2014 09:26:48 +0900
> Joel Rees wrote:
>
> [SNIP]
>
> So, where is the solution then?
Bzzz, what I'm about to say is a genuine question, not a snide remark:
What's the problem needing a solution?
I would guess the problem is pro
On Wed, 3 Sep 2014 21:38:47 +0100
Jonathan Dowland wrote:
> On Wed, Sep 03, 2014 at 03:54:06AM +0200, B wrote:
> > Hehe, because it sinks his claws deep and everywhere (it also
> > plans to implant dbus _into_ the kernel (WTF? A kernel is
> > here to kernelling and nothing else AFAIK),
>
>
On Thu, 04 Sep 2014, Joel Rees wrote:
> dbus/kdbus is actually another case of re-inventing bad solutions, and
> getting things more wrong the second time.
>
> Admitted, it's often better to do something not-quite-right than do nothing
> at all, but forgetting that there is a better way is not a g
On Thu, Sep 4, 2014 at 9:46 PM, Jonathan Dowland wrote:
> On Thu, Sep 04, 2014 at 08:03:29PM +0900, Joel Rees wrote:
>> Where? indeed.
>> What problem are we trying to solve with dbus and kdbus?
>
> I think Bzzz interpreted your assurance that dbus and kdbus were bad fits for
> 'the problem' as im
On Thu, Sep 04, 2014 at 08:03:29PM +0900, Joel Rees wrote:
> Where? indeed.
> What problem are we trying to solve with dbus and kdbus?
I think Bzzz interpreted your assurance that dbus and kdbus were bad fits for
'the problem' as implying you were aware of what was a better fit. He's clearly
quite
2014/09/04 9:43 "B" :
>
> On Thu, 4 Sep 2014 09:26:48 +0900
> Joel Rees wrote:
>
> [SNIP]
>
> So, where is the solution then?
Where? indeed.
What problem are we trying to solve with dbus and kdbus?
Joel Rees
Computer memory is just fancy paper,
CPUs just fancy pens.
All is a stream of text
On Thu, 4 Sep 2014 09:26:48 +0900
Joel Rees wrote:
[SNIP]
So, where is the solution then?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140904024233.58e4f8f7@m
2014/09/04 6:02 "B" :
>
> On Wed, 3 Sep 2014 21:38:47 +0100
> Jonathan Dowland wrote:
>
> Thanks for your very clear explanation, Jonathan.
>
> > kernel support is pretty much essential to improve the performance of
> > dbus. Lots of data is being passed over dbus by apps nowadays, and
> > bec
On Wed, 3 Sep 2014 21:38:47 +0100
Jonathan Dowland wrote:
Thanks for your very clear explanation, Jonathan.
> kernel support is pretty much essential to improve the performance of
> dbus. Lots of data is being passed over dbus by apps nowadays, and
> because it's an entirely userspace solution t
On Wed, Sep 03, 2014 at 03:54:06AM +0200, B wrote:
> Hehe, because it sinks his claws deep and everywhere (it also
> plans to implant dbus _into_ the kernel (WTF? A kernel is
> here to kernelling and nothing else AFAIK),
Plans to move bits of dbus into the kernel predate systemd. The first s
11 matches
Mail list logo
