Am 13.01.2014 02:47, schrieb Kay Sievers:
On Mon, Jan 13, 2014 at 8:07 AM, Greg KH gre...@linuxfoundation.org wrote:
On Sun, Jan 12, 2014 at 11:48:56PM +0100, Dominique Michel wrote:
I need that pc for production, so I rapidly installed another
distribution without systemd. So this problem is
Hi,
.device units stopped showing up for me in git systemd since somewhere around
mid-december. I have noticed that udevd and even udevadm monitor receives the
kernel events but systemd itself never receives them.
Further debugging, I have found out device_dispatch_io() (src/core/device.c) is
At Sun, 12 Jan 2014 11:39:29 -0500,
Dave Reisner wrote:
On Sun, Jan 12, 2014 at 11:15:52AM -0500, Dave Reisner wrote:
$attr{number} in the RUN rule is an empty expansion. This makes sense,
because the path doesn't exist -- i.e., it refers to the path:
Hi,
I've just been debugging a weird problem in my 208 build (which is quite
similar to Fedora's - a lot of the same patches).
So far I've noticed two problems:
1. If I do systemctl enable sysvinitscript it will print me a warning
about how the units do not carry [Install] sections. This is
'Twas brillig, and Colin Guthrie at 13/01/14 11:16 did gyre and gimble:
2. This is the much odder part of the problem I'm seeing. The call to
daemon_reload() at the end of the enable_unit() seems to trigger some
kind of broken daemon reload that puts things into a bad state,
including a stale
On Mon, Jan 13, 2014 at 8:56 AM, Daniel Buch boogiewasth...@gmail.com wrote:
Okay, guess thats right? Second opinion, lennart? Kay?
Yeah, wait a bit with the rename until we have some more feedback,
just heard a suggestion from Kay of calling it sd-resolv instead
(which sounds good to me).
-t
On Mon, Jan 13, 2014 at 10:37:58AM +0100, Umut Tezduyar Lindskog wrote:
Hi,
.device units stopped showing up for me in git systemd since somewhere around
mid-december. I have noticed that udevd and even udevadm monitor receives the
kernel events but systemd itself never receives them.
Ohh.. that sounds reasonable, i can do the git mv and renameig (And squash
to a single commit) when the decision is set :)
2014/1/13 Tom Gundersen t...@jklm.no
On Mon, Jan 13, 2014 at 8:56 AM, Daniel Buch boogiewasth...@gmail.com
wrote:
Okay, guess thats right? Second opinion, lennart? Kay?
'Twas brillig, and Tom Gundersen at 13/01/14 13:36 did gyre and gimble:
On Mon, Jan 13, 2014 at 8:56 AM, Daniel Buch boogiewasth...@gmail.com wrote:
Okay, guess thats right? Second opinion, lennart? Kay?
Yeah, wait a bit with the rename until we have some more feedback,
just heard a
On Mon, Jan 13, 2014 at 5:35 PM, Thomas Bächler tho...@archlinux.org wrote:
Am 13.01.2014 02:47, schrieb Kay Sievers:
On Mon, Jan 13, 2014 at 8:07 AM, Greg KH gre...@linuxfoundation.org wrote:
On Sun, Jan 12, 2014 at 11:48:56PM +0100, Dominique Michel wrote:
I need that pc for production, so I
'Twas brillig, and Colin Guthrie at 13/01/14 11:30 did gyre and gimble:
'Twas brillig, and Colin Guthrie at 13/01/14 11:16 did gyre and gimble:
2. This is the much odder part of the problem I'm seeing. The call to
daemon_reload() at the end of the enable_unit() seems to trigger some
kind of
'Twas brillig, and Colin Guthrie at 13/01/14 15:08 did gyre and gimble:
'Twas brillig, and Colin Guthrie at 13/01/14 11:30 did gyre and gimble:
'Twas brillig, and Colin Guthrie at 13/01/14 11:16 did gyre and gimble:
2. This is the much odder part of the problem I'm seeing. The call to
Le Sun, 12 Jan 2014 16:07:45 -0800,
Greg KH gre...@linuxfoundation.org a écrit :
On Sun, Jan 12, 2014 at 11:48:56PM +0100, Dominique Michel wrote:
I need that pc for production, so I rapidly installed another
distribution without systemd. So this problem is solved for me, but
that doesn't
Hello,
You're approaching this whole thread from a fixed position and therefore
seem to be seeing *everything* as negative and problematic.
Rather than coming here with problem and looking for a solution, you've
arrived with a solution already designed and seem to be complaining that
it won't
'Twas brillig, and Colin Guthrie at 13/01/14 15:33 did gyre and gimble:
'Twas brillig, and Colin Guthrie at 13/01/14 15:08 did gyre and gimble:
'Twas brillig, and Colin Guthrie at 13/01/14 11:30 did gyre and gimble:
'Twas brillig, and Colin Guthrie at 13/01/14 11:16 did gyre and gimble:
2.
On Mon, Jan 13, 2014 at 2:43 PM, Daniel Buch boogiewasth...@gmail.com wrote:
Ohh.. that sounds reasonable, i can do the git mv and renameig (And squash
to a single commit) when the decision is set :)
I was doing a lot of git mv anyway now, so I went ahead and moved
the files to sd-resolv. If
For gudev - gudevdevice:
- Add support for get_sysfs_attr_keys()
- Add support for has_sysfs_attr()
Note: Only tested against systemd-204 on Ubuntu 13.10's patch-set...
RFC1: For some reason libudev cosiders every link or file as sysfs
attribute (opposed to udevadm). Is this intended ?
RFC2:
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
openSuSE-13.1 dist and a 3.4.74 kernel. The back trace indicates an out
of kernel driver I have to maintain. Yet this also indicates Pid: 361,
comm: systemd-udevd caused the
On Mon, Jan 13, 2014 at 04:20:05PM -0500, Mark Hounschell wrote:
Basically, I don't think this problem is the driver. I think the problem
is systemd/udev related so I'm posting this here hoping the get some
input on what the problem is.
If the kernel crashes, then it's kernel's fault (usually).
On Mon, Jan 13, 2014 at 12:10:20PM -0800, Tom Gundersen wrote:
commit 5681d7fb8be37771c152d21ea6e95597d664e3f1
Author: Tom Gundersen t...@jklm.no
Date: Mon Jan 13 21:03:28 2014 +0100
libsystemd-dns: merge into libsystemd
Also rename sd-dns - sd-resolv.
Looks good.
commit
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
openSuSE-13.1 dist and a 3.4.74 kernel.
3.4? That's an incompatible thing right there with openSUSE 13.1,
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 rather reading sysfs files that your driver
is
Le Mon, 13 Jan 2014 19:39:57 +,
Colin Guthrie gm...@colin.guthr.ie a écrit :
Hello,
You're approaching this whole thread from a fixed position and
therefore seem to be seeing *everything* as negative and
problematic.
Hi,
You are partly right on this. In the mean time, I read other
On Tue, Jan 14, 2014 at 5:58 AM, Zbigniew Jędrzejewski-Szmek
libsystemd-bus: rename to libsystemd
Documentation was updated to refer to either 'libsystemd' or 'sd-bus' in
place
of libsystemd-bus.
Eeeh, why? This new name suggests that this libary is for systemd
functionality.
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
openSuSE-13.1 dist and a 3.4.74 kernel.
3.4? That's an incompatible
El 13/01/14 19:42, Dominique Michel escribió:
Or I am wrong and systemd will not work without the
kernel cgroups?
systemd *requires* cgroups, what you can disable are certain controllers.
I do not know to which extent this ability to disable controllers will
remain in place. Whatever is
On Mon, Jan 13, 2014 at 10:58 PM, Zbigniew Jędrzejewski-Szmek
zbys...@in.waw.pl wrote:
On Mon, Jan 13, 2014 at 12:10:20PM -0800, Tom Gundersen wrote:
commit 5681d7fb8be37771c152d21ea6e95597d664e3f1
Author: Tom Gundersen t...@jklm.no
Date: Mon Jan 13 21:03:28 2014 +0100
libsystemd-dns:
27 matches
Mail list logo
