---
The patch by Umut did miss at least hybrid-sleep -- it involves hibernation
as well (hybrid sleep is a hibernation followed by S3 rather than S4 powerdown).
Also, it messed up indentation a bit (Makefile.am seems to use tabs), which I
fixed as well.
And I wonder, maybe it makes sense to condi
Applied. Thanks!
Tom
On Mon, Sep 8, 2014 at 9:53 PM, Mantas Mikulėnas wrote:
> If not backslash-escaped, it splits the rule in two.
> ---
> rules/80-net-setup-link.rules | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/rules/80-net-setup-link.rules b/rules/80-net-setup
If not backslash-escaped, it splits the rule in two.
---
rules/80-net-setup-link.rules | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/rules/80-net-setup-link.rules b/rules/80-net-setup-link.rules
index 27c43b9..4207694 100644
--- a/rules/80-net-setup-link.rules
+++ b/rules/8
On Mon, Sep 8, 2014 at 10:32 PM, Dale R. Worley wrote:
>> From: Simon McVittie
>
>> > In my "Store.mount" file, I see no indication of an executable which
>> > implements the unit.
>>
>> I think it's always mount(8), which has its own extension mechanism to
>> dispatch per-filesystem if necessary
On Mon, Sep 8, 2014 at 3:30 PM, Mantas Mikulėnas wrote:
> On Mon, Sep 8, 2014 at 9:27 PM, Chris Morgan wrote:
>> Hello.
>>
>> We have a build environment that we use to build our software for
>> desktop Linux and we are currently using Yocto to build for an
>> embedded target.
>>
>> I'm looking f
> From: Simon McVittie
> > In my "Store.mount" file, I see no indication of an executable which
> > implements the unit.
>
> I think it's always mount(8), which has its own extension mechanism to
> dispatch per-filesystem if necessary (e.g. mount.cifs).
What I was thinking of is, what is the pr
On Mon, Sep 8, 2014 at 9:27 PM, Chris Morgan wrote:
> Hello.
>
> We have a build environment that we use to build our software for
> desktop Linux and we are currently using Yocto to build for an
> embedded target.
>
> I'm looking for a way for developers to use the systemd unit files for
> our se
Hello.
We have a build environment that we use to build our software for
desktop Linux and we are currently using Yocto to build for an
embedded target.
I'm looking for a way for developers to use the systemd unit files for
our services out of their user owned build directory during
development s
On Mon, Sep 08, 2014 at 03:32:21PM +0200, Daniel Mack wrote:
> On 09/08/2014 03:18 PM, Djalal Harouni wrote:
> > Upstream kernels allow unprivileged users to create user namespaces
> > and change their uid/gid.
> >
> > These patches update kdbus policy logic to handle this case and
> > improve our
On Mon, Sep 08, 2014 at 03:27:42PM +0200, Daniel Mack wrote:
> On 09/08/2014 03:18 PM, Djalal Harouni wrote:
> > * This is the internal version of struct kdbus_policy_db_access.
> > @@ -51,7 +52,8 @@ struct kdbus_policy_db_cache_entry {
> > struct kdbus_policy_db_entry_access {
> > u8 type;
This makes possible to spawn service instances triggered by socket with
MLS/MCS SELinux labels which are created based on information provided by
connected peer.
Implementation of label_get_child_mls_label derived from xinetd.
Reviewed-by: Paul Moore
---
Changes in v5:
* removed unneede
On 09/08/2014 03:18 PM, Djalal Harouni wrote:
> Upstream kernels allow unprivileged users to create user namespaces
> and change their uid/gid.
>
> These patches update kdbus policy logic to handle this case and
> improve our current checks across user namespaces.
>
> So this patch adds:
>
> * k
On 09/08/2014 03:18 PM, Djalal Harouni wrote:
> * This is the internal version of struct kdbus_policy_db_access.
> @@ -51,7 +52,8 @@ struct kdbus_policy_db_cache_entry {
> struct kdbus_policy_db_entry_access {
> u8 type;/* USER, GROUP, WORLD */
> u8 access; /* OWN, TALK,
Use the global kuid_t and kgid_t to store uid/gid values, this way we
our policy checks will work across user namespaces.
Note that currently we ignore that the user is privileged in its own
namespaces and the policy access kuid_t and kgid_t were mapped into that
namespace. If this is requested we
Upstream kernels allow unprivileged users to create user namespaces
and change their uid/gid.
These patches update kdbus policy logic to handle this case and
improve our current checks across user namespaces.
So this patch adds:
* kdbus_test_waitpid() to get exit code of childs.
* kdbus_clone_us
Applied. Thanks!
Tom
On Mon, Sep 8, 2014 at 12:26 PM, Angus Gibson wrote:
> This lets the routing metric for links to be specified per-network,
> still defaulting to DHCP_ROUTE_METRIC (1024) if unspecified. Hopefully
> this helps with multiple interfaces configured via DHCP.
>
> ---
> man/syste
Applied. Thanks!
Tom
On Fri, Sep 5, 2014 at 11:56 AM, Emil Renner Berthing wrote:
> This makes DHCPv4 and IPv4LL coexist peacefully.
> ---
> src/network/networkd-dhcp4.c | 11 +++
> src/network/networkd-route.c | 22 ++
> src/network/networkd.h | 2 ++
> 3 fil
On 05/09/14 18:22, Jakub Klinkovský wrote:
> What is the reason behind logging unit's description? Consider the
> following journal message (from `journalctl -b`):
>
> systemd[1]: Starting A secure, fast, compliant and very flexible
> web-server...
As a data point, Debian's init scripts have trad
This lets the routing metric for links to be specified per-network,
still defaulting to DHCP_ROUTE_METRIC (1024) if unspecified. Hopefully
this helps with multiple interfaces configured via DHCP.
---
man/systemd.network.xml | 6 ++
src/network/networkd-dhcp4.c | 6
Hi Alison, thanks to this hidden gem of reference, and with your pointers i was
able to a pretty nice job of reordering the units and dependencies to pull
ahead the early boot target. I agree after spending a few hours, i could bring
up my functional ui with significant improvements. I have some
Am 08.09.2014 um 11:21 schrieb Colin Guthrie:
> Reindl Harald wrote on 06/09/14 00:59:
>>
>> Am 05.09.2014 um 19:30 schrieb Mantas Mikulėnas:
>>> On Fri, Sep 5, 2014 at 8:22 PM, Jakub Klinkovský wrote:
What is the reason behind logging unit's description? Consider the
following
>
Reindl Harald wrote on 06/09/14 00:59:
>
> Am 05.09.2014 um 19:30 schrieb Mantas Mikulėnas:
>> On Fri, Sep 5, 2014 at 8:22 PM, Jakub Klinkovský wrote:
>>>
>>> What is the reason behind logging unit's description? Consider the following
>>> journal message (from `journalctl -b`):
>>>
>>> systemd
On Sun, Sep 7, 2014 at 11:32 PM, Ivan Shapovalov wrote:
> On Tuesday 02 September 2014 at 12:31:49, Umut Tezduyar Lindskog wrote:
>> ---
>> Makefile.am | 52
>> configure.ac |6 ++
>> 2 files changed, 38 insertions(+), 20 deletions(-
23 matches
Mail list logo
