Age | Commit message (Collapse) | Author |
|
|
|
|
|
This way we can include documentation about minor macros/inline function
within the introducionary man page in a sane way.
|
|
|
|
This makes sure we are OK in outputting all valid, non-control UTF-8
characters, instead of just printable 7bit ASCII.
|
|
|
|
we now can take multiple matches, and they will apply as AND if they
apply to different fields and OR if they apply to the same fields. Also,
terms of this kind can be combined with an overreaching OR.
|
|
|
|
|
|
|
|
|
|
|
|
Before: shared code such as log.c was linked once into the public
libraries (where it is entirely hidden) and once into the various tools
which might use those libraries. This is suboptimal, as this way static
variables such as the maximum log level are instantiated twice in all
tools.
After: our build the public libraries a second time, as a convenience
libary, and link our tools against those. Hence all tools use only a
single instance of everything.
|
|
|
|
|
|
The old automatism that the flushing of the journal from /run to /var
was triggered by the appearance of /var/log/journal is broken if that
directory is mounted from another host and hence always available to be
useful as mount point. To avoid probelsm with this, introduce a new unit
that is explicitly orderer after all mounte files systems and triggers
the flushing.
|
|
With this we'll print a marker "----- Reboot -----" between two
subsequent lines with different boot IDs.
|
|
There's now sd_journal_new_directory() for watching specific journal
directories. This is exposed in journalctl -D.
sd_journal_wait() and sd_journal_process() now return whether changes in
the journal are invalidating or just appending.
We now create inotify kernel watches only when we actually need them
|
|
|
|
|
|
"permanent" is simply the wrong term and we use "persistant" in most
other contexts to correct this.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
initrds can only be on tmpfs or ramfs, so check for that
|
|
If accessing an automount point triggers more changes to
/proc/self/mountinfo than just to add the directly wanted mount, these
changes can lead to spurious -ENODEV notifications on the automount unit
causing the request to fail when in fact the mount will be setup right
afterwards.
|
|
|
|
E.g. systemctl --all -t masked gives the list of masked units.
The -t/--type option is reused. This is possible because unit types
and unit load states are called differently, so it is possible to
distinguish what the user meant. Using the same option also means that
the interface is user for the user: less options to remember.
|
|
This makes it possible to use them from systemctl without linking
against the core.
|
|
|
|
to unit-name.h
|
|
|
|
Systemctl accepted anything as the argument for -t, and simply said '0
units found'. It is better to catch this user error early.
|
|
This makes it possible to use them from systemctl without linking
against the core. A string->enum lookup table is added.
|
|
|
|
|
|
|
|
|
|
This is useful if your keyfile is a block device, and you want to
use a specific part of it, such as an area between the MBR and the
first partition.
This feature is documented in the Arch wiki[0], and has been supported
by the Arch initscripts, so would be nice to get this into systemd.
This requires libcryptsetup >= 1.4.2 (released 12.4.2012).
Acked-by: Paul Menzel <paulepanter@users.sourceforge.net>
[0]:
<https://wiki.archlinux.org/index.php/System_Encryption_with_LUKS#
Storing_the_key_between_MBR_and_1st_partition>
|
|
|
|
|
|
The MeeGo distribution is still a supported distribution, but
will probably not see an updated version of systemd anymore.
Most of the development is focussing on Tizen now, and the
generic support for building --with-distro=other is more than
adequate enough.
This patch removes the support as a custom configuration build
target in systemd. People who are still building this for
the MeeGo distribution should build as "other" distro.
|
|
|
|
At least Wikipedia writes it that way [1].
[1] https://en.wikipedia.org/wiki/Endianness
|
|
• 2 was replaced by »two« in one place to avoid some ambiguity.
|
|
|
|
|