summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2012-05-21cryptsetup: support discards (TRIM)Matthew Monaco
2012-05-21main: try a bit harder to find an init process to execute after ↵Lennart Poettering
reexec/switch-root
2012-05-21service: make the fsck pass no configurableLennart Poettering
2012-05-21cryptsetup: a few simplificationsLennart Poettering
2012-05-21hostname-setup: also consider (ńone) an unset hostnameLennart Poettering
2012-05-21update TODOLennart Poettering
2012-05-21update TODOLennart Poettering
2012-05-21unit: introduce RequiredBy= setting in [Install], to complement WantedBy=Lennart Poettering
2012-05-21login: minor typo fixLennart Poettering
2012-05-21units: introduce new Documentation= field and make use of it everywhereLennart Poettering
This should help making the boot process a bit easier to explore and understand for the administrator. The simple idea is that "systemctl status" now shows a link to documentation alongside the other status and decriptionary information of a service. This patch adds the necessary fields to all our shipped units if we have proper documentation for them.
2012-05-21systemctl: drop useless DBus calls from 'systemctl show foo.service'Michal Schmidt
systemctl called LoadUnit, GetUnit, GetAll in this order to get the properties. It is useless to load units explicitly, because it won't ensure anything. The unit may be freed immediately by the garbage collector. It is unnecessary to call GetUnit, because systemctl can easily translate the unit name to DBus path by itself. GetAll will load the unit if necessary.
2012-05-21dbus-unit: always load the unit before handling a message for itMichal Schmidt
We need to be able to show the properties even of inactive units. systemctl loads the unit before getting its properties, but this is racy as the garbage collector may kick in right after the loading. Fix it by always loading the unit before handling a message for it. https://bugzilla.redhat.com/show_bug.cgi?id=814966#c6
2012-05-21delta: drop PHP'ismLennart Poettering
2012-05-21delta: don't highlight unchanged filesLennart Poettering
2012-05-21update TODOLennart Poettering
2012-05-21delta: introduce arg_flags field, to follow our usual schemeLennart Poettering
2012-05-16delta: use same nomenclature for equivalent and redirected everywhereLennart Poettering
2012-05-16delta: enums are much cooler than definesLennart Poettering
2012-05-16delta: Support filtering what type of deltas to showGergely Nagy
Not everyone is interested in every kind of deltas (and some might even be interested knowing which files do not have overrides), so this here is an implementation of a --type=LIST... option for systemd-delta, that makes it possible to filter what subset of deltas we want. The available modifiers are masked, equivalent, redirected, overriden, and unchanged - they should be self explanatory, and the man page explains them in a little more detail anyway. As a side effect, in case of overriden files, the diff output was made optional. By default, everything is shown (with a diff, if appropriate) except for completely unchanged files. Signed-off-by: Gergely Nagy <algernon@balabit.hu>
2012-05-16delta: add preset dirsLennart Poettering
2012-05-16delta: add missing filesLennart Poettering
2012-05-16switch-root: check for absolute pathsLennart Poettering
2012-05-16delta: add systemd-delta tool to find overriden configuration and unit filesLennart Poettering
2012-05-15udev: update docs, NEWSKay Sievers
2012-05-15udev: libudev - bump soname, remove deprecated functions, introduce symbol ↵Kay Sievers
versions
2012-05-15build-sys: support build-from-git without gobject-introspectionKay Sievers
2012-05-15build-sys: fix distcheckKay Sievers
2012-05-15tmpfiles: if we are supposed to write a string to a file, it's OK if we ↵Lennart Poettering
can't write the trailing newline
2012-05-15build-sys: fix buildLennart Poettering
2012-05-15build-sys: fix build for folks without gtk-doc installedLennart Poettering
2012-05-15git: update gitignoreLennart Poettering
2012-05-15build-sys: move gtk-doc stuff into its own subdir and reindent autogen.shLennart Poettering
We moved most other build noise files into their own subdirs, so let's do this for gtk-doc too
2012-05-15man: overwrite vs. overrideMichal Schmidt
'overwrite' conveys the idea of the old text being destroyed. 'override' does not. It is more similar to 'overrule'.
2012-05-15install: fix inverted meaning of '--force' in systemctl enableMichal Schmidt
2012-05-14missing: Fix broken syscall(__NR_fanotify_mark... on ppc32Andreas Schwab
The same situation as on o32 mips.
2012-05-14sd-login: update header docs a bitLennart Poettering
2012-05-14namespace: make PrivateTmp= apply to both /tmp and /var/tmpLennart Poettering
2012-05-14update TODOLennart Poettering
2012-05-14systemctl: add switch-root verbLennart Poettering
2012-05-14core: add extra safety check before switching rootLennart Poettering
2012-05-14job: info message if JOB_VERIFY_ACTIVE detects an inactive unitMichal Schmidt
2012-05-14job: report the status of first half of JOB_RESTART the same as JOB_STOPMichal Schmidt
2012-05-14unit: unit type dependent status messagesMichal Schmidt
Instead of generic "Starting..." and "Started" messages for all unit use type-dependent messages. For example, mounts will announce "Mounting..." and "Mounted". Add status messages to units of types that used to be entirely silent (automounts, sockets, targets, devices). For unit types whose jobs are instantaneous, report only the job completion, not the starting event. Socket units with non-instantaneous jobs are rare (Exec*= is not used often in socket units), so I chose not to print the starting messages for them either. This will hopefully give people better understanding of the boot.
2012-05-14unit: print the color status marks on the leftMichal Schmidt
The alignment of the "[ OK ]" and "[FAILED]" status marks to the right side of the terminal makes it difficult to link them with the messages on the left if your console is wide. I considered the options: 1. Align them to the 80th column regardless of the console width. Disadvantage - either: - truncating messages needlessly, not using available space; or - If the message is long, write the mark over it. => ugly 2. Write them to the 80th column for short messages, and further to the right for longer ones. Disadvantage: - jagged look 3. Write the marks on the left, before the message. Disadvantage: - Breaks tradition from RHL. Advantages: + slightly simpler code + Will annoy holy-traditionalists. I chose option 3. BTW, Debian now uses similar marks on the left with its makefile-style boot. Special values of the "status" argument to status_vprintf are: NULL - no status mark, no message indentation "" - no status mark, message indented as if the mark was there
2012-05-14job: change red [ABORT] status to yellow [DEPEND]Michal Schmidt
The red "[ABORT]" for a dependency failure is too scary. It suggests a crash. And it suggests a problem with the unit itself. Change it to a yellow "[DEPEND]" message. The color communicates the level of seriousness better.
2012-05-14job: only jobs on the runqueue can be runMichal Schmidt
2012-05-14units: do not quit plymouth too earlyMichal Schmidt
2012-05-14keymap: Add Mio N890Martin Pitt
https://launchpad.net/bugs/998621
2012-05-14update mailmap for Martin PittMartin Pitt
2012-05-10udev: path_id - cciss - set "we have a bus" flagKay Sievers