Ninjatrappeur's systemd working tree
Go to file
Phillip Sz e3ceb75be3 test: remove exit 0 at the end
We don't need that at the end, as it will always exit with 0 if
everything is okey.
2016-02-05 11:38:58 +01:00
catalog catalog: updated Russian translation 2016-02-02 21:15:44 +03:00
coccinelle tree-wide: use xsprintf() where applicable 2016-01-12 15:36:32 +01:00
docs docs: add .gitignore 2015-07-06 17:47:38 +02:00
factory/etc factory: remove broken pam_limits 2014-07-30 15:21:54 +02:00
hwdb hwdb: add HP Pavilion dm4 axis corrections 2016-02-05 09:26:27 +10:00
m4 build-sys: Check behavior of -Werror=shadow before deciding to use it 2015-09-22 09:54:33 -07:00
man core: when a service's ExecStartPre= times out, skip ExecStop= 2016-02-03 23:58:47 +01:00
network networkd: emit DNS/NTP/Timezone info via DHCP server by default 2015-08-27 16:47:26 +02:00
po po: updated Russian translation 2016-02-02 21:15:12 +03:00
rules rfkill: rework and make it listen on /dev/rfkill 2015-10-01 16:21:09 +02:00
shell-completion systemctl: rename "reload-or-try-restart" verb to "try-reload-or-restart" 2016-01-28 18:57:04 +01:00
src resolved: correctly store interface index of RRs in cache 2016-02-04 01:10:36 +01:00
sysctl.d sysctl: use %P instead of %p in core pattern 2015-11-17 17:32:49 +01:00
system-preset preset: enable machines.target by default 2014-12-29 17:36:57 +01:00
sysusers.d tmpfiles: drop /run/lock/lockdev 2016-02-01 12:16:24 +01:00
test test: remove exit 0 at the end 2016-02-05 11:38:58 +01:00
tmpfiles.d tmpfiles: drop /run/lock/lockdev 2016-02-01 12:16:24 +01:00
tools man: include the target name when linking to man pages in html output 2015-11-22 23:54:29 -05:00
units Merge pull request #2331 from yuwata/journal-remote-unit-v2 2016-01-22 09:56:54 +01:00
xorg login: support user-bus on dbus1 2015-08-31 18:12:37 +02:00
.dir-locals.el emacs: also configure nxml parameters in .dir-locals.el 2016-01-25 16:00:28 +01:00
.editorconfig add editorconfig configuration 2015-11-23 12:32:59 +01:00
.gitattributes git: indicate that tabs are never OK in the systemd tree 2013-10-30 02:25:38 +01:00
.gitignore test-resolve-tables: new "test", useful to print mappings 2016-01-29 12:13:08 -05:00
.mailmap NEWS: add more stuff, and reorder things a bit 2015-11-13 13:59:50 +01:00
.travis.yml remove gudev and gtk-doc 2015-06-03 00:22:53 +02:00
.vimrc editors: specify fill column 2016-01-11 19:39:59 +01:00
.ycm_extra_conf.py ycm: update flag blacklist 2014-06-04 15:41:10 -04:00
autogen.sh terminal: drop unfinished code 2015-07-27 20:15:34 +02:00
CODING_STYLE CODING_STYLE: make sure line break recommendation matches edit configuration 2016-01-25 17:19:19 +01:00
configure.ac utf8.[ch] et al: use char32_t and char16_t instead of int, int32_t, int16_t 2016-01-27 14:10:02 +01:00
CONTRIBUTING.md CONTRIBUTING.md: Minor typo fix 2016-01-27 16:53:11 +01:00
DISTRO_PORTING build-sys: warn if people don't change the default NTP servers when building systemd 2015-07-11 14:24:29 -03:00
LICENSE.GPL2 relicense to LGPLv2.1 (with exceptions) 2012-04-12 00:24:39 +02:00
LICENSE.LGPL2.1 licence: remove references to old FSF address 2012-12-17 11:41:31 +01:00
Makefile-man.am sd-journal: add an API to enumerate known field names of the journal 2016-02-01 22:42:33 +01:00
Makefile.am nspawn: optionally run a stub init process as PID 1 2016-02-03 23:58:24 +01:00
NEWS tmpfiles: drop /run/lock/lockdev 2016-02-01 12:16:24 +01:00
README README: drop link to systemd-commits ML 2016-01-25 17:19:19 +01:00
README.md github: extend README.md a bit 2016-01-25 17:19:19 +01:00
TODO update TODO 2016-02-01 22:18:16 +01:00

systemd - System and Service Manager

Build Status
Coverity Scan Status

Details

General information about systemd can be found in the systemd Wiki.

Information about build requirements are provided in the README file.

Consult our NEWS file for information about what's new in the most recent systemd versions.

Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.

When preparing patches for systemd, please follow our Coding Style Guidelines.

If you are looking for support, please contact our mailing list or join our IRC channel.