keymaps: replace dir tokens in keyboard-force-release

Use the correct udev libexec dir as well, not systemd's.
systemd-detect-virt: fix "option '--quiet' requires an argument"

https://bugs.freedesktop.org/show_bug.cgi?id=50671
keymaps: keyboard-force-release - fix shebang

This script will still run without the shebang, but we won't get the
intended effect of the errexit flag in the interpreter line.
fstab-generator: avoid mangling of non-path mount source and dest

This can invalidate otherwise valid source paths with trailing slashes,
such as "host:/" in the case of a network mount.

Based on a patch from Dave Reisner <dreisner@archlinux.org>, which
removed the slash mangling entirely.

Changed it to match on the leading slash to exclude non-path values.
logind: punt duplicate definition of InhibitWhat

Trivial fix for:
  src/login/logind-inhibit.h:37:3: error: redefinition of typedef 'InhibitWhat'
  src/login/logind-inhibit.h:26:26: note: previous declaration of 'InhibitWhat' was here
unit-name: never create a unit name with a leading '.'

Supposed to prevent creating unit files like:
  ├── dev-sda1.device.wants
  │   └── .dot.mount -> /run/systemd/generator/.dot.mount
  ├── .dot.mount
from:
  # cat /etc/fstab
  /dev/sda1    /.dot           vfat ro           1 3

which we later skip reading because of the leading '.'.
fstab-generator: avoid mangling of mount source string

This is a valid source entry in /etc/fstab:
  //192.168.6.10/data /data cifs noperm,auto

On Mon, Jun 4, 2012 at 2:04 PM, Dave Reisner <d@falconindy.com> wrote:
> On Mon, Jun 04, 2012 at 12:57:47PM +0200, Kay Sievers wrote:
>>
>> Changed it to use:
>>   path_is_absolute()
>> instead of:
>>   is_path(),
>> so that we still sanitize the input we might match against.
>>
>> Let me know, if you think that could still cause any problems?

> Yes, this will still break CIFS shares.
udev: lower the starting children_max -> drop the minimum required RAM from 23mb to 5mb

Udev was the limiting factor for us on low-RAM systems.
Given an average RSS of 180kb, 128 workers would require ~23mb of RAM.

Now, please consider what happens when there is only, say, 15mb free.
Udev protects itself from OOM, and the kernel can do nothing but panic.

28 workers * 0.18mb = ~5mb. This change should not affect more powerful
systems much, given that they still get the addition from the amount of RAM.
update TODO
udev: limit minimum worker count to 16
remove support for deprecated /proc/self/oom_adj
udev: reset /proc/self/oom_score_adj in worker processes

Only the main daemon process should be excluded from OOM handling,
not the worker processes or their child processes.
systemctl: rename "man" to "help"
build-sys: release 185
silence gcc warning on 32 bit
udev: kernel cmdline - accept rd.* parameters
udev: remove remaining selinux labeling for file in /run
readahead: Add tool to analyze the contents of the pack file. v3.

This patch adds code to compile 'systemd-readahead-analyze' and install
it into $bindir.

Use this program to parse the contents of the readahead pack file, or
an arbitrary pack file and display which files are listed in it, and
how much of the files are requested to be readahead.

This code is not new - it's partially taken from sreadahead (formerly
maintained by Arjan van der Ven and me, and was originally written
by me), and adapted with the right bits to parse the systemd
readahead pack files, which are slightly different in format.

v2 adds a common READAHEAD_PACK_FILE_VERSION used in all the code
to provide a quick way to assure all these programs are always
synchronized. v3 fixes the integer math.
units: avoid redundant VT clearing by agetty

TTYVTDisallocate=yes already clears the VT. agetty does not need to do
it again. Run it with --noclear.

Felix Miata found the double clearing confusing in this bugreport:
https://bugzilla.redhat.com/show_bug.cgi?id=828007
Add a comment explaining what clears the VT.
udev: systemd-udev-settle.service fix After=

https://bugs.freedesktop.org/show_bug.cgi?id=50779