[systemd-devel] udev-rules not applied to device

2014-03-27 Thread Satz Klauer
So...hopefully this is really the udev mailing list... I use CentoOS 6.5, an embedded device that is connected via USB and shows up as /dev/ttyACMx (in my case it is always /dev/ttyACM0). To have it read/writable for everybody and to avoid the modem-manager is accessing it I created following

Re: [systemd-devel] udev-rules not applied to device

2014-03-27 Thread Mantas Mikulėnas
On Mar 27, 2014 8:48 AM, Satz Klauer satzkla...@googlemail.com wrote: So...hopefully this is really the udev mailing list... I use CentoOS 6.5, an embedded device that is connected via USB and shows up as /dev/ttyACMx (in my case it is always /dev/ttyACM0). To have it read/writable for

[systemd-devel] [PATCH 1/2] hostnamed: expose OperatingSystemName and OperatingSystemRelease on the bus

2014-03-27 Thread Djalal Harouni
--- src/hostname/hostnamed.c | 12 1 file changed, 12 insertions(+) diff --git a/src/hostname/hostnamed.c b/src/hostname/hostnamed.c index 3b19d43..abafa62 100644 --- a/src/hostname/hostnamed.c +++ b/src/hostname/hostnamed.c @@ -23,6 +23,7 @@ #include string.h #include unistd.h

[systemd-devel] [PATCH 2/2] hostnamectl: read OS name and release from remote

2014-03-27 Thread Djalal Harouni
--- src/hostname/hostnamectl.c | 11 --- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/src/hostname/hostnamectl.c b/src/hostname/hostnamectl.c index 326f371..12ab8e2 100644 --- a/src/hostname/hostnamectl.c +++ b/src/hostname/hostnamectl.c @@ -67,6 +67,8 @@ typedef struct

[systemd-devel] [PATCH] backlight: do nothing if max_brightness is 0

2014-03-27 Thread Thomas Bächler
On virtually any newer Asus mainboard, the eeepc-wmi driver is loaded. It exposes a backlight device despite the lack of any physical backlight devices. This fake backlight device has max_brightness set to 0. Since the introduction of the clamp_brightness function, systemd-backlight tries to write

[systemd-devel] failed to store sound card state

2014-03-27 Thread Felix Miata
I see this repeated often during reboot attempts that do not proceed as expected to swiftly do the deed. It seems to be prerequisite to shutdown/reboot. I can't recall ever seeing anything like it when sysvinit was employed. Why does rebooting require the storing of a sound card state,

Re: [systemd-devel] failed to store sound card state

2014-03-27 Thread Cristian Rodríguez
El 27/03/14 20:21, Felix Miata escribió: I see this repeated often during reboot attempts that do not proceed as expected to swiftly do the deed. It seems to be prerequisite to shutdown/reboot. I can't recall ever seeing anything like it when sysvinit was employed. Why does rebooting require the

Re: [systemd-devel] failed to store sound card state

2014-03-27 Thread Felix Miata
On 2014-03-27 21:46 (GMT-0300) Cristian Rodríguez composed: Felix Miata composed: I see this repeated often during reboot attempts that do not proceed as expected to swiftly do the deed. It seems to be prerequisite to shutdown/reboot. I can't recall ever seeing anything like it when sysvinit