[systemd-devel] dmsetup or cryptsetup hangs in the initrd

[Sean MacLennan]

In RedHat 7 I am trying to setup a partition with dmsetup. I have attached
a tarball that includes three files:

* go.sh is a simple script to install everything
* install is the dracut module install
* 95dmcrypt.sh is the file I want to run at boot time

The module is 99securevm.

Obviously, this has all been stripped down to make it as simple as
possible. Sorry for the hard coding. If you want to test it, you need to
provide a /dev/sdb1 partition that is at least 2G. If you comment out the
`exit 0' in go.sh it will setup the partition for you.

Note that if 95dmcrypt.sh has either the dmsetup or the 2 cryptsetup lines
commented in, it will hang the machine.

I am hoping I have just put something in the wrong place. pre-mount is
where we previously ran the script from.

Cheers,
Sean


dmtest.tar.gz
Description: GNU Zip compressed data
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Overriding WantedBy and Alias directives

[Chris Bell]

On 2015-10-16 18:30, Andrei Borzenkov wrote:

16.10.2015 17:41, Chris Bell пишет:

[Install]
WantedBy=   # To clear out previous wantedby 
params,
though this doesn't seem to work like that. Documentation doesn't say 
it

should, so I'm not surprised.


Only selected directives can be cleared this way.


Is there a way I can have it only enable the alias of the unit? Or do
both have to be enabled?


The problem is that Alias is just a symlink to "primary" unit file.
But in case of instantiated template no primary unit file exists at
all. So there would really be nothing to link to.

But it seems that even if I create link foo@bar.service to
foo@.service it still wants to enable template, not instantiated unit.

Also, is there any way to specify a unit alias within an 
override.conf?




Seems to be ignored, at least [Install] section.


So, in short, systemd doesn't provide quite the functionality I am 
looking for here. I am able to enable only the alias by using:


[Install]
Alias=machines.target.wants/gitlab.service

and not using 'WantedBy.' This achieves part of what I'd like to 
accomplish. However, it doesn't end up being any more convenient from 
most points of view. I was hoping that, if I aliased 
'systemd-nspawn@gitlab.service' to 'gitlab.service' that I could then 
use:


# systemctl  gitlab.service

and have it know that I'm talking about gitlab.service. And I would 
really like to be able to do this with overrides. Why? Because I'd like 
to be able to have conveniently-named service identifiers that point to 
pre-defined services/templates/etc. I would like to manage 
'systemd-nspawn@gitlab.service' as 'gitlab.service' without having to 
copy the systemd-nspawn template to a brand new gitlab.service. If I 
create one-off copies, then if the template is updated those changes 
don't propagate to the one-off copy. I guess I could accomplish this 
with symlinks in the /etc/systemd dir (gitlab.service -> 
systemd-nspawn@gitlab.service) but that's not a nice, clean, or good way 
to do it. Are there any other solutions/workarounds? Or is systemd just 
not intended to be used like this?


Thanks again!

Chris
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Overriding WantedBy and Alias directives

[Andrei Borzenkov]

16.10.2015 17:41, Chris Bell пишет:

Hello,

I currently have a systemd unit that I have to reference a lot which has
a rather long name. I would prefer to be able to reference this unit as
a short alias.

Example: I have a container unit called 'systemd-nspawn@gitlab.service'
and I would like to be able to refer to it as simply 'sd-gitlab.service'
I've added an override.conf with the following:

[Install]
WantedBy=   # To clear out previous wantedby params,
though this doesn't seem to work like that. Documentation doesn't say it
should, so I'm not surprised.


Only selected directives can be cleared this way.


Alias=sd-gitlab.service # I've also tried
Alias=machines.target.wants/gitlab.service and omitted the following
WantedBy decl.
WantedBy=machines.target

When I run enable, it does not make the symlinks:

#systemctl enable systemd-nspawn@gitlab.service
Created symlink from
/etc/systemd/system/machines.target.wants/systemd-nspawn@gitlab.service
to /etc/systemd/system/systemd-nspawn@gitlab.service


However, if I edit the systemd-nspawn@gitlab.service base unit file
(systemctl edit --full systemd-nspawn@gitlab.service) and change the
Install section to:

[Install]
Alias=gitlab.service  # Only added this one line
WantedBy=machines.target

and enable the service:

#systemctl enable systemd-nspawn@gitlab.service
Created symlink from /etc/systemd/system/gitlab.service to
/etc/systemd/system/systemd-nspawn@gitlab.service.
Created symlink from
/etc/systemd/system/machines.target.wants/systemd-nspawn@gitlab.service
to /etc/systemd/system/systemd-nspawn@gitlab.service.

Is there a way I can have it only enable the alias of the unit? Or do
both have to be enabled?


The problem is that Alias is just a symlink to "primary" unit file. But 
in case of instantiated template no primary unit file exists at all. So 
there would really be nothing to link to.


But it seems that even if I create link foo@bar.service to foo@.service 
it still wants to enable template, not instantiated unit.



Also, is there any way to specify a unit alias within an override.conf?



Seems to be ignored, at least [Install] section.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] A few GitHub team changes

[David Timothy Strauss]

On Wed, Oct 14, 2015 at 9:35 AM Jóhann B. Guðmundsson 
wrote:

> What makes up that members list [1] in the first place?
>

I think it includes anyone on any team associated with the organization. It
also provides organization-level permissions for things like making new
projects (but not being an admin on existing ones).
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Block device shutdown "hook"

[Ian Pilcher]

On 10/16/2015 05:25 AM, Kay Sievers wrote:

Systemd, as the very last step at system reboot/shutdown tries to
stop/disassemle/unmount all active mounts/mapper/loop/... devices, but
that works only for simple storage setups and has no hooks for other
tools.


This is the DM_DEV_REMOVE ioctl call in delete_dm() (in
src/core/umount.c), right?

If that's good enough for an LVM cache device, it's hard to see how it
wouldn't be good enough for a dm-cache device created in some other way.

So I think I need to go ask the device mapper folks ...

Thanks!

--

Ian Pilcher arequip...@gmail.com
 "I grew up before Mark Zuckerberg invented friendship" 

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Machinectl shell/login do not attach to console

[Chris Bell]

On 2015-10-16 14:01, Chris Bell wrote:

On 2015-10-16 13:55, Chris Bell wrote:

On 2015-10-14 15:58, Lennart Poettering wrote:

On Mon, 05.10.15 12:30, Chris Bell (cwb...@narmos.org) wrote:


Hi all,

I have an Arch machine with systemd 226, running an Arch container, 
also
with systemd 226. For whatever reason in 225, `machinectl login` 
stopped
working correctly, and in 226 `machinectl login` does not work 
properly. It
attaches to the machine, but does not seem to redirect stdin and 
stdout to
the machine. When I attempt to use login, the login prompt is never 
printed

to the command line:


There were some races when machinectl was too fast and the systemd
inside the container too slow. This should be fixed in systemd git,
specifically commit 40e1f4ea7458a0a80eaf1ef356e52bfe0835412e and 
related.


I've recompiled from git, and the problem has, indeed, been solved! 
Thank you!


Sorry, I was wrong. I was running 'machinectl shell' without a machine
name, and it spawned a shell for my host machine. Guest machine still
cannot be accessed with 'shell' or 'login' and stdin/out are still
redirected to the journal.

I compiled commit 7a1e5abbc6e741e5b6995288c607522faa69c8b4 (Master)
from the github repo.


So... Downgrading back to 226 on both the host and container... seems to 
have fixed the issue? No idea why, but now both 'machinectl shell' and 
'machinectl login' works. I have no idea why.

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] systemctl edit via polkit results in access denied

[Chris Bell]

On 2015-10-16 15:41, Mantas Mikulėnas wrote:

On Fri, Oct 16, 2015 at 5:44 PM, Chris Bell  wrote:

Is there a way for polkit to correct or temporarily override these
permissions? Or should I use ACLs to grant write permission to my
user for those directories?


The problem is that `systemctl edit` only uses D-Bus calls for
reloading systemd; it still manages the unit files directly. For now,
use directory ACLs.


Thanks, that's what I ended up doing. I created a new group, 
sd-managers, and gave the group rwX access to the systemd directories 
via ACLs. Now it works as expected, thanks!


--Chris
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] systemctl edit via polkit results in access denied

[Mantas Mikulėnas]

On Fri, Oct 16, 2015 at 5:44 PM, Chris Bell  wrote:

> Hello,
>
> I have configured polkit to allow my user to manage basically everything
> in systemd without requiring sudo or root. Enabling, disabling, reloading,
> etc all work as expected. However, 'systemctl edit' does not. It does not
> deny permission for me to use the function, but it fails when trying to
> copy the file to a temporary directory:
>
> $ systemctl edit rngd.service
> Failed to create directories for
> "/etc/systemd/system/rngd.service.d/override.conf": Permission denied
>
>
> Is there a way for polkit to correct or temporarily override these
> permissions? Or should I use ACLs to grant write permission to my user for
> those directories?
>

The problem is that `systemctl edit` only uses D-Bus calls for reloading
systemd; it still manages the unit files directly. For now, use directory
ACLs.

(Wonder if this could somehow make use of GNOME's new admin:/// vfs...)

-- 
Mantas Mikulėnas 
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] network interface names flipping

[Kay Sievers]

On Fri, Oct 16, 2015 at 4:44 PM, Olaf Hering  wrote:
> Since the introducion of the (un)predictable network interface names the
> name of the single onboard interface on my Shuttle changes if I boot my
> own .config or the kernel.rpm provided by openSUSE. I just threw up
> hands and continue to boot with netnames=0 (or whatever).
>
> Now that same thing starts to happen on my Probook, and that makes me
> wonder if the whole code should just be dropped from udev because it
> obviously fails to work. Unless of course the goal is "UNpredictable"
>
> So, with my own kernel "eth0" becomes "enp2s0". And as I noticed just
> now, with kernel.rpm its always named "ens1".
>
> What is udev doing wrong?
> See http://pastebin.com/raw.php?i=Y5NJWJGF for some data.

Your own kernel might not support PCI hotplug? The slot names might
not be available if the support for them is missing.

Btw, predictable means it will not change between reboots, that names
will not depend on enumeration order within the same setup. It does
not mean or promise, that added kernel/driver/firmware features will
not result in different names. That is expected behavior.

Kay
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] network interface names flipping

[Tomasz Torcz]

On Fri, Oct 16, 2015 at 04:44:34PM +0200, Olaf Hering wrote:
> Since the introducion of the (un)predictable network interface names the
> name of the single onboard interface on my Shuttle changes if I boot my
> own .config or the kernel.rpm provided by openSUSE. I just threw up
> hands and continue to boot with netnames=0 (or whatever).
> 
> 
> So, with my own kernel "eth0" becomes "enp2s0". And as I noticed just
> now, with kernel.rpm its always named "ens1".
> 
> What is udev doing wrong?
> See http://pastebin.com/raw.php?i=Y5NJWJGF for some data.

  udev takes info from firmware.  Does openSUSE kernel package
carry any patches fixing/changing what firmware reports?

-- 
Tomasz   .. oo o.   oo o. .o   .o o. o. oo o.   ..
Torcz.. .o .o   .o .o oo   oo .o .. .. oo   oo
o.o.o.   .o .. o.   o. o. o.   o. o. oo .. ..   o.

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] network interface names flipping

[Olaf Hering]

Since the introducion of the (un)predictable network interface names the
name of the single onboard interface on my Shuttle changes if I boot my
own .config or the kernel.rpm provided by openSUSE. I just threw up
hands and continue to boot with netnames=0 (or whatever).


Now that same thing starts to happen on my Probook, and that makes me
wonder if the whole code should just be dropped from udev because it
obviously fails to work. Unless of course the goal is "UNpredictable"

So, with my own kernel "eth0" becomes "enp2s0". And as I noticed just
now, with kernel.rpm its always named "ens1".

What is udev doing wrong?
See http://pastebin.com/raw.php?i=Y5NJWJGF for some data.


Olaf
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] systemctl edit via polkit results in access denied

[Chris Bell]

Hello,

I have configured polkit to allow my user to manage basically everything 
in systemd without requiring sudo or root. Enabling, disabling, 
reloading, etc all work as expected. However, 'systemctl edit' does not. 
It does not deny permission for me to use the function, but it fails 
when trying to copy the file to a temporary directory:


$ systemctl edit rngd.service
Failed to create directories for 
"/etc/systemd/system/rngd.service.d/override.conf": Permission denied



Is there a way for polkit to correct or temporarily override these 
permissions? Or should I use ACLs to grant write permission to my user 
for those directories?


Thanks!

Chris
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] Overriding WantedBy and Alias directives

[Chris Bell]

Hello,

I currently have a systemd unit that I have to reference a lot which has 
a rather long name. I would prefer to be able to reference this unit as 
a short alias.


Example: I have a container unit called 'systemd-nspawn@gitlab.service' 
and I would like to be able to refer to it as simply 'sd-gitlab.service' 
I've added an override.conf with the following:


[Install]
WantedBy=   # To clear out previous wantedby params, 
though this doesn't seem to work like that. Documentation doesn't say it 
should, so I'm not surprised.
Alias=sd-gitlab.service # I've also tried 
Alias=machines.target.wants/gitlab.service and omitted the following 
WantedBy decl.

WantedBy=machines.target

When I run enable, it does not make the symlinks:

#systemctl enable systemd-nspawn@gitlab.service
Created symlink from 
/etc/systemd/system/machines.target.wants/systemd-nspawn@gitlab.service 
to /etc/systemd/system/systemd-nspawn@gitlab.service



However, if I edit the systemd-nspawn@gitlab.service base unit file 
(systemctl edit --full systemd-nspawn@gitlab.service) and change the 
Install section to:


[Install]
Alias=gitlab.service  # Only added this one line
WantedBy=machines.target

and enable the service:

#systemctl enable systemd-nspawn@gitlab.service
Created symlink from /etc/systemd/system/gitlab.service to 
/etc/systemd/system/systemd-nspawn@gitlab.service.
Created symlink from 
/etc/systemd/system/machines.target.wants/systemd-nspawn@gitlab.service 
to /etc/systemd/system/systemd-nspawn@gitlab.service.


Is there a way I can have it only enable the alias of the unit? Or do 
both have to be enabled?

Also, is there any way to specify a unit alias within an override.conf?

Thanks in advance!


___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] add new entry for HP ProBook 6555b to keyboard.hwdb

[Martin Pitt]

Olaf Hering [2015-10-16 16:21 +0200]:
> root@probook:~ # udevadm test-builtin keyboard
> /devices/platform/i8042/serio0/input/input4/event5
> calling: test-builtin
> === trie on-disk ===
> tool version:  224
> file size: 7049404 bytes
> header size 80 bytes
> strings1762740 bytes
> nodes  5286584 bytes
> Load module index
> timestamp of '/usr/lib/systemd/network' changed
> Parsed configuration file /usr/lib/systemd/network/99-default.link
> Created link configuration context.
> Unload module index
> Unloaded link configuration context.

That didn't work -- so apparently the device path has changed over a
reboot.

> My entry from the initial mail works, no worries.

Oh! I misunderstood you that it did *not* work, and you asked for
debugging why. I submitted a pull request:

  https://github.com/systemd/systemd/pull/1586

> # If your changes are generally applicable, open a bug report on
> #   http://bugs.freedesktop.org/enter_bug.cgi?product=systemd

This was already updated a while ago.

I didn't change the trigger comment, as the manpage also indicates
that triggering multiple path arguments is supposed to work. So let's
rather fix that.

Thanks,

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] add new entry for HP ProBook 6555b to keyboard.hwdb

[Olaf Hering]

Am 16.10.2015 um 15:42 schrieb Martin Pitt:
> Hello Olaf,
> 
> Olaf Hering [2015-10-16 15:22 +0200]:
>> I just noticed that there is a catch al, which looks very odd:
>>
>> evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pn*:pvr*
> 
> How does it look odd?

Wildcard for all of HP?!

>> Why would such a wildcard be correct?
> 
> As inconsistent as scan code assignments are between different
> vendors, the big ones at least sem to have some internal consistency,
> like HP, the "ThinkPad Extra Buttons", or the "Acer WMI hotkeys". We
> just found over time that a large number of different HP models all
> have the same keymap and it seems logical to factor out the common
> keys and then just add a few model specific adjustments.
> 
> The common map does not set b2 BTW, so disabling it won't change
> anything.

I disabled everything, and the result when doing the Fn+something is
like shown below. This means that at least the entries for 81, 89, 92,
97 and ee are already correct via wildcard. The other wildcards may not
hurt.

However b7 and 1d should be handled somehow. Not sure what the correct
entries for this model would be to handle print and interrupt (Its
labeled Untbr in german) keys. Right now both send wrong keys. Not sure
what sysrq is supposed to do anyway, at least GNOME does a screenshot.

Olaf

icon
sleep:Fn+F3  == value df, KEY_SLEEP
display:  Fn+F4  == value ee, unhandled

no label: Fn+ESC == value 81, unhandled
no label: Fn+F6  == value 8a, unhandled
battery:  Fn+F8  == value 89, unhandled
bright-:  Fn+F9  == value 92, unhandled
bright+:  Fn+F10 == value 97, unhandled
no label: Fn+F11 == value b3, unhandled

print:Fn+pos1== value b7, sysrq?
sysrq:Fn+ende== value 54, sysrq
pause:Fn+pgup== value c5, pause
intr: Fn+pgdn== value 1d, left ctrl?

Olaf
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] add new entry for HP ProBook 6555b to keyboard.hwdb

[Olaf Hering]

Am 16.10.2015 um 15:45 schrieb Martin Pitt:

>   udevadm test-builtin keyboard 
> /devices/platform/i8042/serio0/input/input4/event5
> 
> ? Does that give any error message wrt. assigning the www key? Can you
> please double-check in evtest that you really still get KEY_HOMEPAGE
> after that?

root@probook:~ # udevadm test-builtin keyboard
/devices/platform/i8042/serio0/input/input4/event5
calling: test-builtin
=== trie on-disk ===
tool version:  224
file size: 7049404 bytes
header size 80 bytes
strings1762740 bytes
nodes  5286584 bytes
Load module index
timestamp of '/usr/lib/systemd/network' changed
Parsed configuration file /usr/lib/systemd/network/99-default.link
Created link configuration context.
Unload module index
Unloaded link configuration context.
root@probook:~ #

My entry from the initial mail works, no worries.

Olaf
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Machinectl shell/login do not attach to console

[Chris Bell]

On 2015-10-16 13:55, Chris Bell wrote:

On 2015-10-14 15:58, Lennart Poettering wrote:

On Mon, 05.10.15 12:30, Chris Bell (cwb...@narmos.org) wrote:


Hi all,

I have an Arch machine with systemd 226, running an Arch container, 
also
with systemd 226. For whatever reason in 225, `machinectl login` 
stopped
working correctly, and in 226 `machinectl login` does not work 
properly. It
attaches to the machine, but does not seem to redirect stdin and 
stdout to
the machine. When I attempt to use login, the login prompt is never 
printed

to the command line:


There were some races when machinectl was too fast and the systemd
inside the container too slow. This should be fixed in systemd git,
specifically commit 40e1f4ea7458a0a80eaf1ef356e52bfe0835412e and 
related.


I've recompiled from git, and the problem has, indeed, been solved! 
Thank you!


Sorry, I was wrong. I was running 'machinectl shell' without a machine 
name, and it spawned a shell for my host machine. Guest machine still 
cannot be accessed with 'shell' or 'login' and stdin/out are still 
redirected to the journal.


I compiled commit 7a1e5abbc6e741e5b6995288c607522faa69c8b4 (Master) from 
the github repo.

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Machinectl shell/login do not attach to console

[Chris Bell]

On 2015-10-14 15:58, Lennart Poettering wrote:

On Mon, 05.10.15 12:30, Chris Bell (cwb...@narmos.org) wrote:


Hi all,

I have an Arch machine with systemd 226, running an Arch container, 
also
with systemd 226. For whatever reason in 225, `machinectl login` 
stopped
working correctly, and in 226 `machinectl login` does not work 
properly. It
attaches to the machine, but does not seem to redirect stdin and 
stdout to
the machine. When I attempt to use login, the login prompt is never 
printed

to the command line:


There were some races when machinectl was too fast and the systemd
inside the container too slow. This should be fixed in systemd git,
specifically commit 40e1f4ea7458a0a80eaf1ef356e52bfe0835412e and 
related.


I've recompiled from git, and the problem has, indeed, been solved! 
Thank you!


___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] add new entry for HP ProBook 6555b to keyboard.hwdb

[Martin Pitt]

Olaf Hering [2015-10-16 15:14 +0200]:
> > As for the new entry being ignored, is that still the case after "udevadm
> > control --reload", or just rebooting? (I've heard that this sometimes is
> > necessary). If so, can you please pastebin "udevadm info --export-db"
> > somewhere, so that we can verify the DMI names and whether the hwdb
> > entry actually matches?
> 
> http://pastebin.com/raw.php?i=Y5NJWJGF

OK, so that has

P: /devices/platform/i8042/serio0/input/input4/event5
[...]
E: KEYBOARD_KEY_b2=www

which means that your hwdb match worked. Can you please copy&paste the
output of

  udevadm test-builtin keyboard 
/devices/platform/i8042/serio0/input/input4/event5

? Does that give any error message wrt. assigning the www key? Can you
please double-check in evtest that you really still get KEY_HOMEPAGE
after that?

Martin

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] add new entry for HP ProBook 6555b to keyboard.hwdb

[Martin Pitt]

Hello Olaf,

Olaf Hering [2015-10-16 15:22 +0200]:
> I just noticed that there is a catch al, which looks very odd:
> 
> evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pn*:pvr*

How does it look odd?

> Why would such a wildcard be correct?

As inconsistent as scan code assignments are between different
vendors, the big ones at least sem to have some internal consistency,
like HP, the "ThinkPad Extra Buttons", or the "Acer WMI hotkeys". We
just found over time that a large number of different HP models all
have the same keymap and it seems logical to factor out the common
keys and then just add a few model specific adjustments.

The common map does not set b2 BTW, so disabling it won't change
anything.

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] add new entry for HP ProBook 6555b to keyboard.hwdb

[Olaf Hering]

Am 16.10.2015 um 14:56 schrieb Martin Pitt:
> This looks similar to this already existing rule for this model:

I just noticed that there is a catch al, which looks very odd:


evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pn*:pvr*

Why would such a wildcard be correct? Guess I will disable that part
and see what the hardware actually provides...

Olaf
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] add new entry for HP ProBook 6555b to keyboard.hwdb

[Olaf Hering]

Am 16.10.2015 um 14:56 schrieb Martin Pitt:
>> # HP ProBook 6555b, icon earth, sends home, should send www
>> evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard:pnHPProBook6555b:*
>>  KEYBOARD_KEY_b2=www
> 
> This looks similar to this already existing rule for this model:
> # HDX9494nr
> evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pnHDX9494NR:pvr*
>  KEYBOARD_KEY_b2=www# Fn+F3
>  KEYBOARD_KEY_d8=!f23   # touchpad off
>  KEYBOARD_KEY_d9=!f22   # touchpad on
> 
> Do you have touchpad on/off keys? Do they already work?

No, there are no such keys.

> As for the new entry being ignored, is that still the case after "udevadm
> control --reload", or just rebooting? (I've heard that this sometimes is
> necessary). If so, can you please pastebin "udevadm info --export-db"
> somewhere, so that we can verify the DMI names and whether the hwdb
> entry actually matches?

http://pastebin.com/raw.php?i=Y5NJWJGF

Ignored means the desktop does nothing with XF86HomePage.

> Finally, which systemd version are you running? (The 60-keyboard.hwdb
> syntax changed in 220).

openSUSE Tumbleweed, currently at 224.

Olaf
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] add new entry for HP ProBook 6555b to keyboard.hwdb

[Martin Pitt]

Hey Olaf,

Olaf Hering [2015-10-16 14:21 +0200]:
> My copy of /usr/lib/udev/hwdb.d/60-keyboard.hwdb has (at least) three
> issues:
> 
> This advice fails, bugreporting is disabled, perhaps just for me?
> # If your changes are generally applicable, open a bug report on
> #   http://bugs.freedesktop.org/enter_bug.cgi?product=systemd

Thanks for pointing out! This should point to github issues now, I'll
adjust this with my next keymap PR (presumably one to fix your key).

> The wildcard does not work for me, but using /dev/input/event5 works.
> #   udevadm hwdb --update
> #   udevadm trigger /dev/input/eventXX
> # where /dev/input/eventXX is the keyboard in question. If in
> # doubt, simply use /dev/input/event* to reload all input rules.

Kay, is this supposed to work (and udevadm fixed for that)? If not,
this certainly does work:

  udevadm trigger --sysname-match=event*

> And finally, this new entry to let th 'Earth' icon start the web browser
> instead of sending XF86HomePage, which is ignored.
> 
> # HP ProBook 6555b, icon earth, sends home, should send www
> evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard:pnHPProBook6555b:*
>  KEYBOARD_KEY_b2=www

This looks similar to this already existing rule for this model:
# HDX9494nr
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard*:pnHDX9494NR:pvr*
 KEYBOARD_KEY_b2=www# Fn+F3
 KEYBOARD_KEY_d8=!f23   # touchpad off
 KEYBOARD_KEY_d9=!f22   # touchpad on

Do you have touchpad on/off keys? Do they already work?

As for the new entry being ignored, is that still the case after "udevadm
control --reload", or just rebooting? (I've heard that this sometimes is
necessary). If so, can you please pastebin "udevadm info --export-db"
somewhere, so that we can verify the DMI names and whether the hwdb
entry actually matches?

Finally, which systemd version are you running? (The 60-keyboard.hwdb
syntax changed in 220).

Thanks,

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)


signature.asc
Description: Digital signature
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] add new entry for HP ProBook 6555b to keyboard.hwdb

[Olaf Hering]

My copy of /usr/lib/udev/hwdb.d/60-keyboard.hwdb has (at least) three
issues:

This advice fails, bugreporting is disabled, perhaps just for me?
# If your changes are generally applicable, open a bug report on
#   http://bugs.freedesktop.org/enter_bug.cgi?product=systemd


The wildcard does not work for me, but using /dev/input/event5 works.
#   udevadm hwdb --update
#   udevadm trigger /dev/input/eventXX
# where /dev/input/eventXX is the keyboard in question. If in
# doubt, simply use /dev/input/event* to reload all input rules.


And finally, this new entry to let th 'Earth' icon start the web browser
instead of sending XF86HomePage, which is ignored.

# HP ProBook 6555b, icon earth, sends home, should send www
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHewlett-Packard:pnHPProBook6555b:*
 KEYBOARD_KEY_b2=www


This is the output from evtest:
...
Testing ... (interrupt to exit)
Event: time 1444997900.742080, type 4 (EV_MSC), code 4 (MSC_SCAN), value 1c
Event: time 1444997900.742080, type 1 (EV_KEY), code 28 (KEY_ENTER), value 0
Event: time 1444997900.742080, -- SYN_REPORT 
Event: time 1444997901.811896, type 4 (EV_MSC), code 4 (MSC_SCAN), value b2
Event: time 1444997901.811896, type 1 (EV_KEY), code 172 (KEY_HOMEPAGE), value 1
Event: time 1444997901.811896, -- SYN_REPORT 
Event: time 1444997901.818859, type 4 (EV_MSC), code 4 (MSC_SCAN), value b2
Event: time 1444997901.818859, type 1 (EV_KEY), code 172 (KEY_HOMEPAGE), value 0
Event: time 1444997901.818859, -- SYN_REPORT 
Event: time 1444997902.143888, type 4 (EV_MSC), code 4 (MSC_SCAN), value b2
Event: time 1444997902.143888, type 1 (EV_KEY), code 172 (KEY_HOMEPAGE), value 1
Event: time 1444997902.143888, -- SYN_REPORT 
Event: time 1444997902.150824, type 4 (EV_MSC), code 4 (MSC_SCAN), value b2
Event: time 1444997902.150824, type 1 (EV_KEY), code 172 (KEY_HOMEPAGE), value 0
Event: time 1444997902.150824, -- SYN_REPORT 
Event: time 1444997903.703173, type 4 (EV_MSC), code 4 (MSC_SCAN), value 1d
Event: time 1444997903.703173, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 1
Event: time 1444997903.703173, -- SYN_REPORT 
Event: time 1444997905.50, type 4 (EV_MSC), code 4 (MSC_SCAN), value 2e
Event: time 1444997905.50, type 1 (EV_KEY), code 46 (KEY_C), value 1
Event: time 1444997905.50, -- SYN_REPORT 
...

Olaf
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Block device shutdown "hook"

[Kay Sievers]

On Fri, Oct 16, 2015 at 1:55 AM, Ian Pilcher  wrote:
> Does systemd provide any sort of "hook" mechanism to call a script
> program when a block device is unmounted (or otherwise no longer being
> used) on shutdown?
>
> I'm toying with the idea of creating an alternative way of managing
> dm-cache devices -- something that will operate a bit more like bcache,
> rather than LVM cache.  It seems to be pretty straightforward, except
> for the need to properly shutdown the dm-cache once any filesystems,
> VGs, etc., on it are no longer in use.
>
> Is there a way to tell systemd how to "shut down" a block device?

There is no facility to watch individual block devices, and there will
probably never be such a thing in systemd.

Systemd, as the very last step at system reboot/shutdown tries to
stop/disassemle/unmount all active mounts/mapper/loop/... devices, but
that works only for simple storage setups and has no hooks for other
tools.

Kay
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] How does systemd discover template instances?

[Ansgar Burchardt]

Michael Chapman  writes:
> On Thu, 15 Oct 2015, Stuart Longland wrote:
>> Assuming I have a few files distributed in the base package:
>>  /lib/systemd/system/comms-drivers.service
>>  /lib/systemd/system/comms-drivers@.service
>>
>> Ordinarily, one would tell systemd about template instances by creating
>> symbolic links.
>>
>> Suppose however I wanted to not do this, but instead, provide some
>> automatic discovery mechanism for systemd, so it could run a script that
>> would tell it what instances exist.
>>
>> Is there a mechanism for doing this in systemd?
>
> One approach you might want to consider is using a systemd generator
> [1] to create the instance symlinks automatically at boot, e.g.:

This was done for OpenVPN in Debian. As Stuart said he based his
sysvinit script on Debian's openvpn script, the systemd integration
might also help him.

The generator can be found at [2], the .service files at [3] and [4].

Ansgar

  [2] 

  [3] 

  [4] 

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] quota-support in systemd-nspawn

[Andreas Matthus]

Hallo,

systemd ist a great solution! ;-)

My question is using xfs-quotas inside a systemd-nspawn-container.

I mount a xfs-filesystem in the host with usrquota,grpquota and can working
with quotas in it. The mountpoint is in a folder down of the startfolder
from the systemd-nspawn-container. So i can use this filesystem inside the
machine. Thats well. But I cant use quota-support. /dev/mapper/... don't
exist and so all tools failed.

Can you help me to get access to quotas?

with regards
Andreas Matthus 

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel