Re: [systemd-devel] [PATCH] SMACK: assign * label to /tmp when using SMACK.

2013-11-01 Thread Karel Zak
On Thu, Oct 31, 2013 at 01:20:18PM -0700, Kok, Auke-jan H wrote: BTW, for SELinux we remove selinux specific mount options in userspace (in mount(8)) if the kernel does not support selinux. It help us to make command line or fstab setting independent on the current kernel features.

Re: [systemd-devel] .libs/test-sched-prio failed

2013-11-01 Thread Rongqing Li
On 10/31/2013 11:44 AM, Zbigniew Jędrzejewski-Szmek wrote: On Thu, Oct 31, 2013 at 08:05:18AM +0800, Rongqing Li wrote: On 10/30/2013 07:10 PM, Zbigniew Jędrzejewski-Szmek wrote: On Wed, Oct 30, 2013 at 10:02:33AM +0800, Rongqing Li wrote: Hi: I am running the systemd test cases, but

Re: [systemd-devel] [PATCH] fix compiler warnings

2013-11-01 Thread Markus Mayer
On 10/31/2013 07:26 PM, Ronny Chevalier wrote: multiple warnings like src/socket-proxy/socket-proxyd.c: In function ‘transfer_data_cb’: src/socket-proxy/socket-proxyd.c:237:25: warning: format ‘%ld’ expects argument of type ‘long int’, but argument 6 has type ‘size_t’ [-Wformat=]

Re: [systemd-devel] [PATCH] fix compiler warnings

2013-11-01 Thread Ronny Chevalier
Yes, already fixed by David 2013/11/1 Markus Mayer lotharl...@gmx.de: On 10/31/2013 07:26 PM, Ronny Chevalier wrote: multiple warnings like src/socket-proxy/socket-proxyd.c: In function ‘transfer_data_cb’: src/socket-proxy/socket-proxyd.c:237:25: warning: format ‘%ld’ expects argument of

Re: [systemd-devel] Xorg+logind+DM issue: inactive graphical session for seat0

2013-11-01 Thread David Herrmann
Hi On Tue, Oct 29, 2013 at 4:44 PM, Laércio de Sousa lbsous...@gmail.com wrote: I would append another approach to the list: * For non-seat0 seats, X server should open no VT at all. Currently, even with -sharevts option, it seems Xorg does open a VT, although it can't control this. Yes,

Re: [systemd-devel] tree-wide conversion from libdbus to libsystemd-bus

2013-11-01 Thread Lennart Poettering
On Wed, 30.10.13 23:08, Kay Sievers (k...@vrfy.org) wrote: On Wed, Oct 30, 2013 at 3:48 AM, Kay Sievers k...@vrfy.org wrote: [update] To avoid any duplication of work, here are the tools which still need conversion. Please reply to this mail, in case you decide to work on anything

Re: [systemd-devel] tree-wide conversion from libdbus to libsystemd-bus

2013-11-01 Thread Kay Sievers
On Fri, Nov 1, 2013 at 4:44 PM, Lennart Poettering lenn...@poettering.net wrote: [update] - systemd-logind Lennart: I am knee-deep in converting logind now. - loginctl Peeters Simon: I'll take ... (probably loginctl afterwards) - hostnamectl Peeters Simon's (patch on the list, needs

Re: [systemd-devel] [PATCH] SMACK: assign * label to /tmp when using SMACK.

2013-11-01 Thread Kok, Auke-jan H
On Fri, Nov 1, 2013 at 12:57 AM, Karel Zak k...@redhat.com wrote: On Thu, Oct 31, 2013 at 01:20:18PM -0700, Kok, Auke-jan H wrote: BTW, for SELinux we remove selinux specific mount options in userspace (in mount(8)) if the kernel does not support selinux. It help us to make command

[systemd-devel] Linux kernel API

2013-11-01 Thread ScotXW
Hi, systemd is written exclusively for the Linux kernel because this offers advantages over the POSIX API. To illustrate the difference between Linux kernel API and POSIX API I created a diagram, see [1]. On topic: It could be used to illustrate the reasons for this decision. 1. Could you

Re: [systemd-devel] Linux kernel API

2013-11-01 Thread Greg KH
On Fri, Nov 01, 2013 at 06:47:00PM +0100, ScotXW wrote: Hi, systemd is written exclusively for the Linux kernel because this offers advantages over the POSIX API. To illustrate the difference between Linux kernel API and POSIX API I created a diagram, see [1]. Linux doesn't implement all of

Re: [systemd-devel] Linux kernel API

2013-11-01 Thread ScotXW
On 11/01/2013 06:51 PM, Greg KH wrote: On Fri, Nov 01, 2013 at 06:47:00PM +0100, ScotXW wrote: Hi, systemd is written exclusively for the Linux kernel because this offers advantages over the POSIX API. To illustrate the difference between Linux kernel API and POSIX API I created a diagram, see

[systemd-devel] Help on Automatic Symlink XDG_DATA_HOME

2013-11-01 Thread systemdkiosk
Might some expert address: https://bbs.archlinux.org/viewtopic.php?id=172220 It seems systemd pushes hard-wired paths irrespective of XDG vars, a possible bug. On this box XDG_DATA_HOME and XDG_CACHE_HOME point outside $HOME, while XDG_CONFIG_HOME is the default ~/.config folder. XDG_DATA_DIRS

Re: [systemd-devel] Linux kernel API

2013-11-01 Thread Greg KH
On Sat, Nov 02, 2013 at 12:05:23AM +0100, ScotXW wrote: On 11/01/2013 06:51 PM, Greg KH wrote: On Fri, Nov 01, 2013 at 06:47:00PM +0100, ScotXW wrote: Hi, systemd is written exclusively for the Linux kernel because this offers advantages over the POSIX API. To illustrate the difference

Re: [systemd-devel] [PATCH 2/2] hostnamectl: port to sd-bus

2013-11-01 Thread Kay Sievers
On Wed, Oct 30, 2013 at 6:55 AM, Simon Peeters peeters.si...@gmail.com wrote: +#define foreach_dbus_property(r, bus, dest, object, error, reply, name, contents) \ +for (int _i = 0; _i 3; _i++) \ +if (_i == 0) { \ +r = sd_bus_call_method(bus,

Re: [systemd-devel] Help on Automatic Symlink XDG_DATA_HOME

2013-11-01 Thread Zbigniew Jędrzejewski-Szmek
On Fri, Nov 01, 2013 at 11:02:30PM +, systemdki...@yopmail.com wrote: Might some expert address: https://bbs.archlinux.org/viewtopic.php?id=172220 It seems systemd pushes hard-wired paths irrespective of XDG vars, a possible bug. On this box XDG_DATA_HOME and XDG_CACHE_HOME point

Re: [systemd-devel] Help on Automatic Symlink XDG_DATA_HOME

2013-11-01 Thread Mantas Mikulėnas
On Sat, Nov 2, 2013 at 1:37 AM, Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl wrote: On Fri, Nov 01, 2013 at 11:02:30PM +, systemdki...@yopmail.com wrote: Might some expert address: https://bbs.archlinux.org/viewtopic.php?id=172220 It seems systemd pushes hard-wired paths irrespective of

Re: [systemd-devel] Help on Automatic Symlink XDG_DATA_HOME

2013-11-01 Thread systemdkiosk
Zbigniew Jędrzejewski-Szmek wrote: Are you sure that systemd is actually running with this variable set? Excellent question, and no, I'm not sure. If you can tell me how to determine the answer, please do. What I can say is that 1) XDG_DATA_HOME is set in /etc/profile.d on Arch Linux, the

Re: [systemd-devel] Help on Automatic Symlink XDG_DATA_HOME

2013-11-01 Thread systemdkiosk
Zbigniew Jędrzejewski-Szmek wrote: I guess that systemd should not create the link if the destination doesn't exist. +1 Mantas Mikulėnas wrote: I'm curious why the symlink is created at all... I know not why, but I do know that: If a symlink is made, the C code should use $XDG_CONFIG_HOME to

[systemd-devel] [PATCH 0/1] systemd will fail to compile if libgcrypt is missing

2013-11-01 Thread Djalal Harouni
Hi list, I'm doing some systemd testing on clean machines. I'm building from git tree, and I've noticed that systemd autogen.sh will fail if the libgcrypt and its headers are missing, this will produce a buggy configure script. The error messages were not clear, I did lost time debugging... :-/

[systemd-devel] [PATCH 1/1] configure.ac: make libgcrypt dependency optional

2013-11-01 Thread Djalal Harouni
Currently systemd will fail to build if libgcrypt headers are not installed: autoge.sh output: ... libtoolize: linking file `m4/lt~obsolete.m4' configure.ac:547: warning: macro 'AM_PATH_LIBGCRYPT' not found in library configure.ac:47: error: possibly undefined macro: AC_MSG_ERROR If this token

Re: [systemd-devel] [PATCH 0/1] systemd will fail to compile if libgcrypt is missing

2013-11-01 Thread Djalal Harouni
List please hold on these patch! It seems that AM_PATH_LIBGCRYPT will also define LIBGCRYPT_LIBS which is used to link again libgcrypt and other libraries related to libgcrypt. My bad, this current patch will not fix the problem! I guess that we are stuck with this :-/ until gcrypt converts to

Re: [systemd-devel] Help on Automatic Symlink XDG_DATA_HOME

2013-11-01 Thread systemdkiosk
Zbigniew Jędrzejewski-Szmek wrote: 'systemctl --user show-environment' will show what's set I get errors as normal user and root. $ systemctl --user show-environment Failed to issue method call: Process /bin/false exited with status 1 $ su - Password: # systemctl --user show-environment