Re: [systemd-devel] Second (erroneous) check of rootfs?

2015-01-11 Thread Nikolai Zhubr
Hi, 11.01.2015 1:31, Chris Murphy: Yeah it's a bit messy and I really think to some degree this should be bounced back to the ext developers and say how do you envision this working because doing the right thing for ext4 really burdens multiple other processes: systemd of course, but also

Re: [systemd-devel] Second (erroneous) check of rootfs?

2015-01-11 Thread Chris Murphy
On Sun, Jan 11, 2015 at 4:11 AM, Andrei Borzenkov arvidj...@gmail.com wrote: В Sun, 11 Jan 2015 13:43:34 +0300 Nikolai Zhubr n-a-zh...@yandex.ru пишет: Uh. Why not simply mount rootfs rw in initrd then? I'm not against generally. But it'd mean that this first mount is actually a real

Re: [systemd-devel] Second (erroneous) check of rootfs?

2015-01-11 Thread Andrei Borzenkov
В Sun, 11 Jan 2015 13:43:34 +0300 Nikolai Zhubr n-a-zh...@yandex.ru пишет: Uh. Why not simply mount rootfs rw in initrd then? I'm not against generally. But it'd mean that this first mount is actually a real mount, the fs will start up in full. Then I'd suppose it is definitely a must

Re: [systemd-devel] Second (erroneous) check of rootfs?

2015-01-11 Thread Nikolai Zhubr
Hi, 11.01.2015 10:09, Andrei Borzenkov: Ok. I've invented a quick-and-dirty fix. I'll modify systemd-fsck so that when run with no argument it does nothing and exit successfully. This way I'll still have rootfs fsck'ed every boot, but never twice. Uh. Why not simply mount rootfs rw in initrd

Re: [systemd-devel] Second (erroneous) check of rootfs?

2015-01-11 Thread Chris Murphy
On Sun, Jan 11, 2015 at 3:43 AM, Nikolai Zhubr n-a-zh...@yandex.ru wrote: Hi, 11.01.2015 10:09, Andrei Borzenkov: Ok. I've invented a quick-and-dirty fix. I'll modify systemd-fsck so that when run with no argument it does nothing and exit successfully. This way I'll still have rootfs fsck'ed

Re: [systemd-devel] Second (erroneous) check of rootfs?

2015-01-11 Thread Andrei Borzenkov
В Sun, 11 Jan 2015 04:15:41 -0700 Chris Murphy li...@colorremedies.com пишет: On Sun, Jan 11, 2015 at 4:11 AM, Andrei Borzenkov arvidj...@gmail.com wrote: В Sun, 11 Jan 2015 13:43:34 +0300 Nikolai Zhubr n-a-zh...@yandex.ru пишет: Uh. Why not simply mount rootfs rw in initrd then?

Re: [systemd-devel] Second (erroneous) check of rootfs?

2015-01-11 Thread Chris Murphy
On Sun, Jan 11, 2015 at 4:57 AM, Andrei Borzenkov arvidj...@gmail.com wrote: Does it using systemd *inside* of initrd? I don't know how to find the answer to this. There is an initramfs and systemd-journald is the first thing (other than kernel) to be found in dmesg after the initramfs is

Re: [systemd-devel] Second (erroneous) check of rootfs?

2015-01-11 Thread Nikolai Zhubr
Hi, 11.01.2015 14:11, Andrei Borzenkov: [...] By adding all needed options to rootflags=... (modify GRUB_CMDLINE_LINUX_DEFAULT and possibly GRUB_CMDLINE_LINUX_RECOVERY in /etc/default/grub; you can use yast for it). Ah, indeed. Although it feels a bit ugly because the consistency between fstab

Re: [systemd-devel] [PATCH udev v4] udev: Add builtin/rule to export touchscreen/tablet size as udev properties

2015-01-11 Thread David Herrmann
Hi On Mon, Dec 22, 2014 at 5:04 PM, Carlos Garnacho carl...@gnome.org wrote: This rule is only run on tablet/touchscreen devices, and extracts their size in millimeters, as it can be found out through their struct input_absinfo. This may be useful to separate policy and application at the

Re: [systemd-devel] Second (erroneous) check of rootfs?

2015-01-11 Thread Chris Murphy
On Sun, Jan 11, 2015 at 4:48 AM, Nikolai Zhubr n-a-zh...@yandex.ru wrote: Hi, 11.01.2015 1:31, Chris Murphy: Yeah it's a bit messy and I really think to some degree this should be bounced back to the ext developers and say how do you envision this working because doing the right thing for

Re: [systemd-devel] Second (erroneous) check of rootfs?

2015-01-11 Thread Andrei Borzenkov
В Sun, 11 Jan 2015 15:22:54 +0300 Nikolai Zhubr n-a-zh...@yandex.ru пишет: Hi, 11.01.2015 14:11, Andrei Borzenkov: [...] By adding all needed options to rootflags=... (modify GRUB_CMDLINE_LINUX_DEFAULT and possibly GRUB_CMDLINE_LINUX_RECOVERY in /etc/default/grub; you can use yast for

Re: [systemd-devel] Second (erroneous) check of rootfs?

2015-01-11 Thread Nikolai Zhubr
Hi, 11.01.2015 15:54, Andrei Borzenkov: It's no more ugly than using privately patched distribution package. I did not suggest it as long term generic solution. Yes, absolutely. Therefore I'm reading all the answers to find a reasonable workaround and avoid whatever ugly patching.

Re: [systemd-devel] Second (erroneous) check of rootfs?

2015-01-11 Thread Nikolai Zhubr
Hi, 11.01.2015 15:04, Chris Murphy: That's all I meant by bouncing back to ext devs. I don't mean there's anything wrong with ext4. It's pretty clear the XFS and Btrfs devs expect that if a normal rw mount fails, that boot fails and we're dropped to a dracut shell with an unmounted root. And

Re: [systemd-devel] Second (erroneous) check of rootfs?

2015-01-11 Thread Nikolai Zhubr
11.01.2015 15:22, Nikolai Zhubr: By adding all needed options to rootflags=... (modify GRUB_CMDLINE_LINUX_DEFAULT and possibly GRUB_CMDLINE_LINUX_RECOVERY in /etc/default/grub; you can use yast for it). Ah, indeed. Although it feels a bit ugly because the consistency between fstab and

Re: [systemd-devel] Second (erroneous) check of rootfs?

2015-01-11 Thread Dave Reisner
On Sun, Jan 11, 2015 at 10:09:08AM +0300, Andrei Borzenkov wrote: В Sat, 10 Jan 2015 16:51:24 +0300 Nikolai Zhubr n-a-zh...@yandex.ru пишет: Hi, 09.01.2015 23:48, Chris Murphy: [...] I might be missing something, but what's wrong with the existing root=... rootfstype=...

Re: [systemd-devel] Second (erroneous) check of rootfs?

2015-01-11 Thread Andrei Borzenkov
В Thu, 08 Jan 2015 21:32:08 +0100 Harald Hoyer harald.ho...@gmail.com пишет: In case of systemd in the initrd, the fstab-generator ensures that fsck is done on root and /usr and any other partition marked with x-initrd.mount. How is it supposed to work? In native systemd mode

Re: [systemd-devel] Second (erroneous) check of rootfs?

2015-01-11 Thread Chris Murphy
On Sun, Jan 11, 2015 at 4:57 AM, Andrei Borzenkov arvidj...@gmail.com wrote: В Sun, 11 Jan 2015 04:15:41 -0700 Does it using systemd *inside* of initrd? From upstream dracut: if ! dracut_module_included systemd; then inst_hook cmdline 95 $moddir/parse-block.sh inst_hook

Re: [systemd-devel] [PATCH udev v4] udev: Add builtin/rule to export touchscreen/tablet size as udev properties

2015-01-11 Thread Carlos Garnacho
Hey David, On dom, 2015-01-11 at 14:37 +0100, David Herrmann wrote: snip Otherwise, looks all good. I was about to push it, but could you rename it to something more generic? udev_builtin_evdev_id for example. I don't want a different builtin for each evdev property we add, so lets be

[systemd-devel] [PATCH udev v5] udev: Add builtin/rule to export evdev information as udev properties

2015-01-11 Thread Carlos Garnacho
This rule is only run on tablet/touchscreen devices, and extracts their size in millimeters, as it can be found out through their struct input_absinfo. The first usecase is exporting device size from tablets/touchscreens. This may be useful to separate policy and application at the time of

Re: [systemd-devel] Second (erroneous) check of rootfs?

2015-01-11 Thread Reindl Harald
Am 11.01.2015 um 12:48 schrieb Nikolai Zhubr: I suppose this traditional (historical) technique of maintaining mount-count, running fsck at boot time before remount r/w, etc, should not be so much attributed specifically to ext filesystem. Most probably it existed long before even ext2

[systemd-devel] [PATCH 1/2] machinectl: use GNU basename, not the XPG version

2015-01-11 Thread Cristian Rodríguez
--- src/machine/machinectl.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/machine/machinectl.c b/src/machine/machinectl.c index 749170e..980fba1 100644 --- a/src/machine/machinectl.c +++ b/src/machine/machinectl.c @@ -32,7 +32,7 @@ #include net/if.h #include

[systemd-devel] [PATCH] Break JobNew signal dbus signature by adding JobType.

2015-01-11 Thread Dimitri John Ledkov
At the moment JobNew and JobRemoved signals are not useful for tracking streams of events. JobType is missing from both of them, and thus one can only track that something is happening and to which units (And whether something is about to happen, finished, failed, got aborted etc.). To get the

[systemd-devel] [TOOL] Check-undocumented arguments and bash autocompletions

2015-01-11 Thread Carlos Morata Castillo
Hi, I've updated the tool today to work with verbs and some cache issues. ./check-undocumented.sh -p hostnamectl Not standar hostnamectl.Update please. Updates needed in ../shell-completion/bash/hostnamectl ...Option not found: --machine ...Verb not found: set-location --

Re: [systemd-devel] Second (erroneous) check of rootfs?

2015-01-11 Thread Nikolai Zhubr
Hi, 11.01.2015 23:03, Reindl Harald: Am 11.01.2015 um 12:48 schrieb Nikolai Zhubr: I suppose this traditional (historical) technique of maintaining mount-count, running fsck at boot time before remount r/w, etc, should not be so much attributed specifically to ext filesystem. Most probably it

Re: [systemd-devel] systemd networking : problems with bridges

2015-01-11 Thread Charles Devereaux
(oops, accidentally replied off-list. Reposting) Hello On Sat, Jan 3, 2015 at 6:58 AM, Andrei Borzenkov arvidj...@gmail.com wrote: So if I understand it correctly you want - configure one interface - start some program that establishes what you call uplink. I presume it results in one

[systemd-devel] [RFC] hwdb: add MOUSE_WHEEL_CLICK_ANGLE as property

2015-01-11 Thread Peter Hutterer
Most mice have a wheel click angle of 15 degrees, i.e. 24 clicks per full wheel rotation. Some mice, like the Logitech M325 have a larger angle. To allow userspace to make use of that knowledge, add a property to the hwdb. --- libinput patches to read this are here:

Re: [systemd-devel] Second (erroneous) check of rootfs?

2015-01-11 Thread Chris Murphy
On Sun, Jan 11, 2015 at 2:14 PM, Nikolai Zhubr n-a-zh...@yandex.ru wrote: Hi, 11.01.2015 23:03, Reindl Harald: Am 11.01.2015 um 12:48 schrieb Nikolai Zhubr: I suppose this traditional (historical) technique of maintaining mount-count, running fsck at boot time before remount r/w, etc,

[systemd-devel] networkd-218 seems to ignore .link files

2015-01-11 Thread Jan Engelhardt
In systemd-218, I have configured the following testcase: /etc/systemd/network# ls -al total 20 drwxr-xr-x 2 root root 4096 Jan 11 18:14 . drwxr-xr-x 5 root root 4096 Jan 11 16:23 .. -rw-r--r-- 1 root root 96 Jan 11 18:14 99a-ether.link -rw-r--r-- 1 root root 241 Jan 11 18:12 brd0.network

[systemd-devel] slow systemd-networkd DHCP client on wlan0 with systemd v217

2015-01-11 Thread Charles Devereaux
Hello With dhcpcd5 and the following options, once wpa_supplicant is done, I have a connection within the same second if I ignore ARP. With systemd-network, it's much much slower. $ systemd-analyze blame 3.923s systemd-networkd-wait-online.service (...) I tried to measure the time

Re: [systemd-devel] Second (erroneous) check of rootfs?

2015-01-11 Thread Nikolai Zhubr
Hi, 12.01.2015 0:47, Chris Murphy: [...] - man tune2fs uses very strong language to set either interval-between-checks or max-mount-counts. However, mke2fs 1.42.11 (09-Jul-2014) sets neither by default. I'm not sure when this changed, it used to set check interval to 180, but a new file system

Re: [systemd-devel] [PATCH udev v5] udev: Add builtin/rule to export evdev information as udev properties

2015-01-11 Thread Zbigniew Jędrzejewski-Szmek
On Sun, Jan 11, 2015 at 08:47:19PM +0100, Carlos Garnacho wrote: This rule is only run on tablet/touchscreen devices, and extracts their size in millimeters, as it can be found out through their struct input_absinfo. The first usecase is exporting device size from tablets/touchscreens. This

[systemd-devel] networkd-218 won't set bridge l2addr to slave device

2015-01-11 Thread Jan Engelhardt
When using the old-fashioned brctl to set up a bridge, it would give the bridge the L2 address of the first slave when the slave is added. networkd does not do that, which leads to a setup like this: 2: enp0s3: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast master brg0 state UP

Re: [systemd-devel] Second (erroneous) check of rootfs?

2015-01-11 Thread Andrei Borzenkov
В Sun, 11 Jan 2015 12:45:17 -0700 Chris Murphy li...@colorremedies.com пишет: On Sun, Jan 11, 2015 at 4:57 AM, Andrei Borzenkov arvidj...@gmail.com wrote: В Sun, 11 Jan 2015 04:15:41 -0700 Does it using systemd *inside* of initrd? From upstream dracut: if ! dracut_module_included

Re: [systemd-devel] Second (erroneous) check of rootfs?

2015-01-11 Thread Chris Murphy
On Sun, Jan 11, 2015 at 8:29 PM, Andrei Borzenkov arvidj...@gmail.com wrote: В Sun, 11 Jan 2015 12:45:17 -0700 Chris Murphy li...@colorremedies.com пишет: On Sun, Jan 11, 2015 at 4:57 AM, Andrei Borzenkov arvidj...@gmail.com wrote: В Sun, 11 Jan 2015 04:15:41 -0700 Does it using systemd

Re: [systemd-devel] Second (erroneous) check of rootfs?

2015-01-11 Thread Chris Murphy
On Sun, Jan 11, 2015 at 10:13 PM, Chris Murphy li...@colorremedies.com wrote: On Sun, Jan 11, 2015 at 8:29 PM, Andrei Borzenkov arvidj...@gmail.com wrote: В Sun, 11 Jan 2015 12:45:17 -0700 Chris Murphy li...@colorremedies.com пишет: On Sun, Jan 11, 2015 at 4:57 AM, Andrei Borzenkov

[systemd-devel] LLDP from Zyxel – Operation not supported

2015-01-11 Thread Mantas Mikulėnas
I enabled LLDP receive for eth* in networkd. It recognizes outgoing packets sent by lldpd (on the computer itself) and by ladvd (on pfSense), but chokes on incoming packets sent by a Zyxel switch: LLDP: Receive frame failed: Operation not supported Attaching the actual packet. (By the way,