Hi,
I was trying to enable tests in the %check part of systemd rpm.
Something strange happens which causes test-dhcp-client when building
in mock:
FAIL: test-dhcp-client
==
Assertion 'client' failed at ../src/libsystemd-network/sd-dhcp-client.c:141,
function
On 30/01/15 22:53, Elias Probst wrote:
IMHO, env variables are something we should get rid of in the long term.
It might be fine for now to provide some legacy-compatibility mechanisms
(like your not-yet-written tool), but to me environment variables are
something straight out of the dark
On 30/01/15 09:30, Simon McVittie wrote:
user-session
I don't think there is a standard term for this so I'm making one up.
Notes from the hackfest: A few people called these super-sessions when
we discussed them. I preferred user-session tbh, but if people want to
standardize
On 01/29/15 00:09, Lennart Poettering wrote:
On Wed, 28.01.15 23:51, Topi Miettinen (toiwo...@gmail.com) wrote:
diff --git a/src/backlight/backlight.c b/src/backlight/backlight.c
index 1271a66..df53b75 100644
--- a/src/backlight/backlight.c
+++ b/src/backlight/backlight.c
@@ -373,6 +373,7
I asked:
I don't know of any use case for one unit to start another directly.
Is there one?
Marko responds:
1.) Coming up with a small tree first reduces the loading time of the unit
set (not so much important in my case)
2.) If you wanna create some dynamics between target A and target B
From: Naveen Kumar nku...@redhat.com
This map will be used to provide a fallback for translations.
For example, a Niederdeutsch (nds) speaker prefers to fall back to
German (de) translations rather then the English (C) ones.
https://bugzilla.redhat.com/show_bug.cgi?id=624158#c9
---
For the entries listed in the first column of language-fallback-map,
the entry from the second column will be used for LANGUAGE=, if
LANGUAGE= is not explicitly specified.
https://bugzilla.redhat.com/show_bug.cgi?id=624158
---
This fixes a long-standing bug where users of a dialect locale would
Kay, Lennart,
comments?
Zbyszek
On Thu, Jan 29, 2015 at 09:27:38AM +0100, Philipp Reinkemeier wrote:
Hi.
Since it has bothered me that systemd-timesyncd unconditionally writes
the current clock value to disk everytime it got an NTP fix i filed a
BUG report
On Sat, Jan 31, 2015 at 04:16:12PM -0800, Brian Redbeard wrote:
In the systemd documentation for systemd.network units the
[Network] section notes that for the option DHCP=:
DHCP=
Enables DHCPv4 and/or DHCPv6 support. Accepts yes, no, ipv4
or ipv6.
In testing the options ipv4 and ipv6
In the systemd documentation for systemd.network units the
[Network] section notes that for the option DHCP=:
DHCP=
Enables DHCPv4 and/or DHCPv6 support. Accepts yes, no, ipv4
or ipv6.
In testing the options ipv4 and ipv6 are actually implemented as
v4 and v6. Additionally on the same page in
On my computer, the minimum brightness enforced by clamping in
backlight is too bright.
Let udev property ID_BACKLIGHT_CLAMP control whether the brightness
is clamped or not.
---
man/systemd-backli...@.service.xml | 9 -
src/backlight/backlight.c | 5 -
2 files changed, 12
On Wed, Jan 28, 2015 at 11:51:47PM +0200, Topi Miettinen wrote:
On my computer, the minimum brightness enforced by clamping in
backlight is too bright.
Let udev property ID_BACKLIGHT_CLAMP control whether the brightness
is clamped or not.
---
man/systemd-backli...@.service.xml | 11
On 30/01/15 09:49, Jan Janssen wrote:
But really: why not use automounting logic in fstab?:
/dev/mapper/data /home/myuser/data ext4 noauto,x-systemd.automount 0 0
No need to manually trigger a mount. And you can even use noauto in
crypttab so that the encrypted device is only opened once
On 31/01/15 10:25, John Lane wrote:
On 30/01/15 09:49, Jan Janssen wrote:
But really: why not use automounting logic in fstab?:
/dev/mapper/data /home/myuser/data ext4 noauto,x-systemd.automount 0 0
No need to manually trigger a mount. And you can even use noauto in
crypttab so that the
14 matches
Mail list logo
