We simply keep open copies of the dbus connections across the
reexecution and close them as last step of it. A client can thus simply
wait until its connection is dropped to know when the reexecution is
finished.
https://bugzilla.redhat.com/show_bug.cgi?id=698198
/etc/crypttab uses "size" argument only for plain crypt mapping
(and input is limited to volume key size)
For LUKS it always read whole keyfile (no arguments except "luks"
should be in crypttab).
Because of bug in cryptsetup 1.2.0 (fixed in 1.3.0) library
did not enforced keyfile size argument, so this bug was
hidden for some time.
Patch also converts size in bits to bytes like excepted
by libcryptsetup api.
Fixes https://bugs.freedesktop.org/show_bug.cgi?id=36264
Since strv_* functions handle null arguments, this warning is actually
valid.
src/strv.c: In function ‘strv_copy’:
src/strv.c:68:21: warning: ‘k’ may be used uninitialized in this function [-Wuninitialized]
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=%23618562
MIPS o32 ABI enforces that 64bit arguments should be 64bit-aligned, and
the third argument of syscall(__NR_fanotify_mark, ...) is 64bit and not
64bit-aligned on o32 mips platform, thus extra padding is inserted
before it. The syscall function doesn't know the prototype of
fanotify_mark, so the padding will be passed into kernel as valid
argument.
Mounting /var/lib/nfs/rpc_pipefs and /proc/fs/nfsd is required by rpcbind
and the NFS server respectively. To depend on them being mounted, systemd
needs to be allowed to create mount units for both in order to avoid having
to implement hacks (mounting in ExecStartPre or using shell scripts).
This commit consists of the initial work to include MeeGo as a ported
distribution for systemd.
The majority of the changes are small configuration additions to auto
tools, so that MeeGo is identified as a valid distribution option.
Some small deviations will be noticed between the configuration of MeeGo
and other distributions. As MeeGo is a distribution striving for
compliancy to support its near embedded attributes and target users,
there is less user configuration options available by default. Most
services will be enabled by systemd as part of the distribution
requirements, and as such most links and service files will be pre-setup
for the MeeGo distribution. As much of this is going to be done within
the MeeGo distribution packaging this is still noteworthy to mention, as
it explains why in systemd you will observe configuration differences
where the MeeGo distribution removes all links in the pkgsysconfdir for
instance. MeeGo will be user configurable if there is desire, but most
services will be enabled by the distribution as designated by the MeeGo
compliancy standards.
Other changes are in source to add such areas as meego-release defined
in utils, and hostname in hostname-setup, defining vconsole-setup,
localizations and rescue additions as needed.
As this is all ground work, MeeGo will continue to strive for complete
compatibility.
