On Fri, 2015-04-03 at 14:01 +0200, Lennart Poettering wrote:
On Thu, 02.04.15 15:04, Simon McVittie (simon.mcvit...@collabora.co.uk) wrote:
On 02/04/15 14:31, Lennart Poettering wrote:
Hmm? I really don't see how the NFS vs wpa_supplicant issue has
anything to do with dbus? NFS doesn't
Am Freitag, den 03.04.2015, 16:47 +0200 schrieb Lennart Poettering:
On Thu, 02.04.15 13:11, Paul Menzel wrote:
some network cards with certain cables and devices take up to five
seconds so that the link is up [1].
$ sudo journalctl -u systemd-networkd
-- Logs begin at
[CC’ing coreboot, GRUB, SeaBIOS, Syslinux project and Linux kernel]
Am Montag, den 16.03.2015, 11:38 +0100 schrieb Kay Sievers:
On Mon, Mar 16, 2015 at 11:29 AM, Umut Tezduyar Lindskog wrote:
I would like to pass the time it was spent in bootloader to systemd.
Is there a kernel command line
On Fri, Mar 27, 2015 at 12:54:50PM +0100, Martin Pitt wrote:
Hey Peter,
thanks for these! Patches 1 to 4 look good to me, but I have some
questions/comments on this one.
Peter Hutterer [2015-03-23 11:30 +1000]:
--- /dev/null
+++ b/rules/60-evdev.rules
@@ -0,0 +1,14 @@
+# do not
udev uses inotify to implement a scheme where when the user closes
a writable device node, a change uevent is forcefully generated.
In the case of block devices, it actually requests a partition rescan.
This currently can't be synchronized with udevadm settle, i.e. this
is not reliable in a
Separate patch for ease of review, will be merged into
udev: builtin-keyboard: add support for EV_ABS_OVERRIDE
Replace the hwdb keyboard: prefix with evdev: and drop the separate
60-keyboard.rules file. The new 60-evdev.rules is called for all event nodes
anyway, we don't need a separate rules
On Sat, Apr 04, 2015 at 02:07:27PM +0200, David Herrmann wrote:
Hi
On Fri, Apr 3, 2015 at 8:55 PM, Hans de Goede hdego...@redhat.com wrote:
[...]
I don't think we should return when we see INPUT_PROP_ACCEL. If a
keyboard embeds an accelerometer, we will miss it. I think I went too
deep
On Fri, Apr 03, 2015 at 04:12:00PM +0200, Hans de Goede wrote:
The pointingstick of the Dell Latitude E6400 is somewhat slow by default,
where as the pointingstick of the Dell Latitude D620 is much too fast by
s/where as/whereas/
ACK otherwise.
Cheers,
Peter
default, set
On Fri, Apr 03, 2015 at 04:11:59PM +0200, Hans de Goede wrote:
Lenovo has changed the sensitity of the trackpoint on the x240 / T440s / T540
s/sensitity/sensitivity/
generation of Thinkpads, making them somewhat unsensitive by default, add a
I think it's insensitive, not unsensitive.
hwdb
On Fri, Apr 03, 2015 at 04:11:57PM +0200, Hans de Goede wrote:
There is quite a wide spread in the delta events generated by pointingsticks,
some generate deltas of 1-2 under normal use, while others generate deltas
from 1-20.
This commit adds a set of rules + a hwdb file which allows
On Fri, Apr 03, 2015 at 04:11:58PM +0200, Hans de Goede wrote:
The IBM / Lenovo trackpoints are special, they allow specifying a sensitivity
s/are special, they//
setting through a ps/2 command, which changes the range of the deltas send
when
s/send/sent/
using the trackpoint. One some
On Mon, 06.04.15 06:17, 임창근 (ck21...@samsung.com) wrote:
Hello EveryOne.
I wonder that If I use kernel v3.4 with systemd v219, systemd-run function is
work or not.
Because My target have kernel v3.4 and systemd v216.
Please check the README shipped in the tarball, it always lists the
Am 06.04.2015 um 08:17 schrieb 임창근:
Hello EveryOne.
I wonder that If I use kernel v3.4 with systemd v219, systemd-run function is
work or not.
Because My target have kernel v3.4 and systemd v216.
So, If possible, I want apply just minor upgrade at kernel side.
Which Kernel Feature needed?
Hello EveryOne.
I wonder that If I use kernel v3.4 with systemd v219, systemd-run function is
work or not.
Because My target have kernel v3.4 and systemd v216.
So, If possible, I want apply just minor upgrade at kernel side.
Which Kernel Feature needed? or impossible?
Thanks.
Hello Lennart, all,
Lennart Poettering [2015-04-03 14:58 +0200]:
To start with, the code is really wrong, it should never have been
merged in its current state, the read/write logic for the sockets is
completely borked (I cannot even boot my own machine reliably with
it!).
This is surprising
Hello all,
Lennart Poettering [2015-04-03 16:34 +0200]:
Well, I had a brief look at this patch, but it still doesn't get the
socket IO stuff right. It uses synchronous fgets() to read things of
the sockets, that's still not OK, and is a major thing that is
wrong.
fsckd kicks malicious/broken
On Sun, Apr 05, 2015 at 09:56:14AM +0200, sdrb wrote:
Hello,
I've got a few very basic questions regarding configuration of systemd.
I'm trying to setup some minimal configuration for qemu running linux.
The qemu runs linux kernel which mounts nfs-root as root directory.
I've made
17 matches
Mail list logo
