The situation is: by default, we get a "auto" value for kmod compiling
option, so if we found required kmod files, then we build it with kmod
enabled, otherwise, just build without kmod and do not complain to user.
However, currently, if kmod version < 15 available in machine, and build
with defau
The incorrect shell code of AS_IF always get false value, so it always
build without dbus though build with "--enable-dbus" explicitely.
Signed-off-by: Chengwei Yang
---
configure.ac |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure.ac b/configure.ac
index 7140627.
Am 15.01.2014 03:57, schrieb Andrey Borzenkov:
> В Wed, 15 Jan 2014 02:54:16 +0100
> Reindl Harald пишет:
>
>> can someone please have a look why starting with Fedora 20/RHEL7
>> and systemd-208 after typing "systemctl reboot" no longer waits
>> until sshd is closing the client connection resul
В Wed, 15 Jan 2014 02:54:16 +0100
Reindl Harald пишет:
> can someone please have a look why starting with Fedora 20/RHEL7
> and systemd-208 after typing "systemctl reboot" no longer waits
> until sshd is closing the client connection resulting in a completly
> frozen VT ignoring CTRL+C and waitin
can someone please have a look why starting with Fedora 20/RHEL7
and systemd-208 after typing "systemctl reboot" no longer waits
until sshd is closing the client connection resulting in a completly
frozen VT ignoring CTRL+C and waiting for KeepAlive timeout
https://bugzilla.redhat.com/show_bug.cgi
Hi,
I'm perfectly fine if we skip this patch, and to my understanding there is
no benefits and only corresponds to external linkage.
2014/1/14 Tom Gundersen
> Hi Daniel,
>
> I guess we should only do this once we decide to export the API. I
> guess we won't be doing that for a few releases (we
Hi Daniel,
I guess we should only do this once we decide to export the API. I
guess we won't be doing that for a few releases (we'll use it
internally first to make sure it is the way we want it).
Or are there any benefits to these annotations even when the symbols
are not exported?
-t
On Tue,
On Tue, Jan 14, 2014 at 10:17:36AM -0500, Mark Hounschell wrote:
> On 01/13/2014 05:00 PM, Greg KH wrote:
> > On Mon, Jan 13, 2014 at 01:59:39PM -0800, Greg KH wrote:
> >> That really sounds like a driver problem, especially given your trace
> >> shows it is failing somewhere. The udevd PID is pro
On 01/11/2014 11:48 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Thu, Jan 02, 2014 at 10:52:44AM +0100, Lukasz Skalski wrote:
As you can see above, path name, interface name and others string
are in the same place. Problem is with signature positions. Any
ideas on what could be causing the problem?
On 01/13/2014 05:00 PM, Greg KH wrote:
> On Mon, Jan 13, 2014 at 01:59:39PM -0800, Greg KH wrote:
>> That really sounds like a driver problem, especially given your trace
>> shows it is failing somewhere. The udevd PID is probably because udev
>> loaded your driver.
>
> Sorry, not loading it, but
On Tue, Jan 14, 2014 at 10:26 PM, Umut Tezduyar Lindskog
wrote:
> From: Umut Tezduyar Lindskog
Applied.
Thanks,
Kay
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
El 14/01/14 11:10, Reindl Harald escribió:
which application should this be?
please state a real-world example - the Kernel usually does not break userland
Fedora 18 as example was released with Kernel 3.6 and is now at EOL on 3.11.10
Fedora 17 as example was released with Kernel 3.3 and at EO
From: Umut Tezduyar Lindskog
---
README |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/README b/README
index a1058c5..6fcab4f 100644
--- a/README
+++ b/README
@@ -63,7 +63,7 @@ REQUIREMENTS:
Some udev rules and virtualization detection relies on it:
On Tue, Jan 14, 2014 at 07:52:31AM -0500, Mark Hounschell wrote:
> On 01/13/2014 10:20 PM, Cristian RodrÌguez wrote:
> > El 13/01/14 18:59, Greg KH escribiÛ:
> >> On Mon, Jan 13, 2014 at 04:20:05PM -0500, Mark Hounschell wrote:
> >>> I'll have to admit, I don't have a very good understanding of
> >
On Tue, Jan 14, 2014 at 2:15 PM, Joonas Lahtinen
wrote:
>> I've implemented very basic BMP support and commited it.
>
>
> The custom format was there for best possible speed to be achieved when
> displaying the splash, as the original use case is extremely time critical.
> I will look into the spe
systemd-208-9.fc20.x86_64
We have been porting a working configuration from fedora 19 to fedora 20.
After systemd prints the Welcome message it then hangs.
We found that changing the LogLevel from debug to info fixes the
hang. As does setting LogTarget=console.
It would seem that the default Log
Am 14.01.2014 15:03, schrieb Cristian Rodríguez:
> El 14/01/14 09:52, Mark Hounschell escribió:
>
>> Well, the systemd/udev README file from 208-15.1:
>
> yeah, one thing is what systemd upstream requires and a completely different
> one is what openSUSE can/will support
> or allow.
>
> It is n
---
src/libsystemd/sd-resolv.c | 38 +++---
1 file changed, 19 insertions(+), 19 deletions(-)
diff --git a/src/libsystemd/sd-resolv.c b/src/libsystemd/sd-resolv.c
index b8288ba..cd79a6c 100644
--- a/src/libsystemd/sd-resolv.c
+++ b/src/libsystemd/sd-resolv.c
@@ -41
El 14/01/14 09:52, Mark Hounschell escribió:
Well, the systemd/udev README file from 208-15.1:
yeah, one thing is what systemd upstream requires and a completely
different one is what openSUSE can/will support or allow.
It is not just systemd really, other applications or libraries may
r
Hi,
I have figured it out. e8a3b2dc (Dec 18) changed the behavior for me by making
containers subscribe to NETLINK_KOBJECT_UEVENT with UDEV_MONITOR_NONE. We also
introduced a function udev_has_devtmpfs which makes a system call
name_to_handle_at.
Our kernel doesn't support system call name_to_
'Twas brillig, and Colin Guthrie at 14/01/14 12:57 did gyre and gimble:
> Looking again, it seems as if "systemctl daemon-reexec; systemctl
> daemon-reexec" can also trigger the problem...
OK, so from the last couple days of debugging, I can see two problems
where this problem occurs.
1. If syste
Hi,
Sorry for quite a delay in replying, I've was backpacking in Southeast
Asia for a month, now back working.
On 16.12.2013 00:54, Kay Sievers wrote:
On Sun, Dec 15, 2013 at 2:54 PM, Kay Sievers wrote:
On Tue, Dec 10, 2013 at 10:23 AM, Joonas Lahtinen
wrote:
Add support for two new confi
'Twas brillig, and Colin Guthrie at 14/01/14 12:10 did gyre and gimble:
> Hi,
>
> OK, so following on from my posts yesterday about "systemctl
> [en|dis]able weirdness + reload (writes /run/nologin)", I do still seem
> to be getting problems.
>
> It seems that I got bitten again by this today (th
On 01/13/2014 10:20 PM, Cristian RodrÌguez wrote:
> El 13/01/14 18:59, Greg KH escribiÛ:
>> On Mon, Jan 13, 2014 at 04:20:05PM -0500, Mark Hounschell wrote:
>>> I'll have to admit, I don't have a very good understanding of
>>> systemd/udev. I am using systemd/udev version 208-15.1 on an
>>> openSuS
On Tue, Jan 14, 2014 at 11:46 AM, Daniel Buch wrote:
> ---
> src/libsystemd/resolv-util.h | 12 +++---
> src/libsystemd/sd-resolv.c | 100
> +--
> src/libsystemd/test-resolv.c | 38
> src/systemd/sd-resolv.h | 80
---
src/libsystemd/sd-resolv.c | 282 +--
src/libsystemd/test-resolv.c | 26 ++--
src/systemd/sd-resolv.h | 48
3 files changed, 178 insertions(+), 178 deletions(-)
diff --git a/src/libsystemd/sd-resolv.c b/src/libsystemd/sd-resolv.c
index
---
src/libsystemd/resolv-util.h | 12 +++---
src/libsystemd/sd-resolv.c | 100 +--
src/libsystemd/test-resolv.c | 38
src/systemd/sd-resolv.h | 80 +-
4 files changed, 115 insertions(+), 115 deletio
On Tue, Jan 14, 2014 at 5:58 AM, Zbigniew Jędrzejewski-Szmek
wrote:
>> commit c813ca40c859ff8abc8bc6aabc3f1e896623eb67
>> Author: Tom Gundersen
>> Date: Mon Jan 13 19:12:16 2014 +0100
>>
>> libsystemd-dhcp: merge into libsystemd
> OK.
Hmm, maybe DHCP should stay as a separate lib? We shou
28 matches
Mail list logo
