On Mon, Sep 29, 2014 at 06:52:12PM +0200, Zbigniew Jędrzejewski-Szmek wrote:
> On Mon, Sep 29, 2014 at 08:35:04PM +0400, Andrei Borzenkov wrote:
> > В Mon, 29 Sep 2014 17:16:25 +0200
> > Zbigniew Jędrzejewski-Szmek пишет:
> >
> > >
> > > The problem with reading but back discards settings remain
Ronny Chevalier wrote on 30/09/14 20:28:
> Hi,
>
> 2014-09-30 21:18 GMT+02:00 Tobias Hunger :
>> Any feedback at all? Please?
>>
>> Am I doing something wrong in posting my patch here?
> No you just need to wait that someone review your patch. It rarely
> takes more than 2 weeks.
Also note that L
(Cc'd to the systemd mailing list because sd-bus is the reference
implementation of the user-space side of kdbus, but please join the dbus
list and follow-up there if you are interested in D-Bus.)
I've recently been looking at kdbus as a transport for D-Bus messages,
and how compatible or otherwis
Hi Simon,
On 10/01/2014 03:33 PM, Simon McVittie wrote:
> (Cc'd to the systemd mailing list because sd-bus is the reference
> implementation of the user-space side of kdbus, but please join the dbus
> list and follow-up there if you are interested in D-Bus.)
>
> I've recently been looking at kdbu
On Wed, 01.10.14 14:33, Simon McVittie (simon.mcvit...@collabora.co.uk) wrote:
Thanks a ton for reviewing kdbus and its concepts!
(Also, sorry for not responding earlier to all the dbus/kdbus traffic
in the last month, I was travelling.)
> System bus access-control policy
> =
On Sun, 21.09.14 15:31, Martin Steigerwald (mar...@lichtvoll.de) wrote:
> I just have one question. In the light of
[...]
>
> in the light of the ongoing discussions on linux-kernel, debian-devel, debian-
> user and other mailing lists more than some dozens threads meanwhile:
>
> Did you ever a
On Mon, 22.09.14 10:16, Dale R. Worley (wor...@alum.mit.edu) wrote:
> 1. Systemd has some very large binaries, each of which implements many
> aspects of the system. Conversely, the typical Un*x approach is to
> separate functions into many executablels, many of which are scripts.
> The latter ap
On Tue, 23.09.14 15:13, Dale R. Worley (wor...@alum.mit.edu) wrote:
> > Again, this seems rather ignorant of the status quo. Between the blog
> > posts and wiki documentation and the 164 man pages, systemd is rather
> > copiously documented. Not to say that things can't be improved, but
> > by Lin
On Sat, 27.09.14 09:55, Koen Kooi (k...@dominion.thruhere.net) wrote:
> diff --git a/src/login/70-power-switch.rules b/src/login/70-power-switch.rules
> index a6997f7..695d246 100644
> --- a/src/login/70-power-switch.rules
> +++ b/src/login/70-power-switch.rules
> @@ -10,5 +10,6 @@ ACTION=="remove
On Fri, 26.09.14 12:23, Simon Peeters (peeters.si...@gmail.com) wrote:
> hej,
>
> In the light of my linux classes i was looking into hooking up vagrant
> with machined in order to be able to use nss-mymachines to resolve the
> ip address on the host-only adaptor. Unfortunatly the network side of
On Tue, Sep 30, 2014 at 9:24 PM, Günther J. wrote:
> Hello,
>
> Am Dienstag, 30. September 2014, 20:38:10 schrieb Andrei Borzenkov:
>> В Tue, 30 Sep 2014 13:24:13 +0200
>>
>> Günther J. Niederwimmer пишет:
>> > Hello,
>> >
>> > I have a problem to run this correct, it is working on a reboot but n
Thanks for the reply :) The libvirt-guests.service was the very first thing
I had tried. It, however, did absolutely nothing and I believe it to be
broken in arch linux. I have given up on trying to get a shutdown/reboot
script to run for now.
On Tue, Sep 23, 2014 at 5:44 AM, Daniel P. Berrange
w
---
src/libsystemd/sd-bus/PORTING-DBUS1 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/libsystemd/sd-bus/PORTING-DBUS1
b/src/libsystemd/sd-bus/PORTING-DBUS1
index 958e7b6..81e9413 100644
--- a/src/libsystemd/sd-bus/PORTING-DBUS1
+++ b/src/libsystemd/sd-bus/PORTING-DBUS1
@
D-Bus' type hierarchy as described in the spec is:
\- basic
\- fixed type (u, i, etc.)
\- string-like type (s, o, g)
\- container
Someone seems to have referred to basic types as "simple types" at
some point, but that term isn't defined in the D-Bus Specification,
and seems redundant.
So f
On Thu, Oct 2, 2014 at 12:58 AM, Lennart Poettering
wrote:
> On Fri, 26.09.14 12:23, Simon Peeters (peeters.si...@gmail.com) wrote:
>
>> hej,
>>
>> In the light of my linux classes i was looking into hooking up vagrant
>> with machined in order to be able to use nss-mymachines to resolve the
>> ip
Hello,
ifupdown [1], NetworkManager, and WICD all support hooks for when a
network interface is configured or deconfigured (before and after
these actions).
Are there any plans to support something along these lines? If so,
what will that look like?
If there are no plans, how do networkd's devel
Hi Cameron,
On Thu, Oct 2, 2014 at 6:36 AM, Cameron Norman wrote:
> ifupdown [1], NetworkManager, and WICD all support hooks for when a
> network interface is configured or deconfigured (before and after
> these actions).
>
> Are there any plans to support something along these lines? If so,
> wh
Thanks for the information, I am not in a hurry and am no longer
feeling ignored.
It is also reassuring to hear that I did not do something obviously
wrong like sending the patch here without also requesting a review on
some website or whatever. Some projects are rather imaginative when it
comes t
I agree, it makes sense to use the D-Bus terms in the porting doc. Applied.
Thanks!
Tom
On Wed, Oct 1, 2014 at 5:11 PM, Simon McVittie
wrote:
> D-Bus' type hierarchy as described in the spec is:
>
> \- basic
>\- fixed type (u, i, etc.)
>\- string-like type (s, o, g)
> \- container
>
> S
On Wed, 01.10.14 21:36, Cameron Norman (camerontnor...@gmail.com) wrote:
> Hello,
>
> ifupdown [1], NetworkManager, and WICD all support hooks for when a
> network interface is configured or deconfigured (before and after
> these actions).
>
> Are there any plans to support something along these
20 matches
Mail list logo
