T

Zbigniew Jędrzejewski-Szmek edb4843fbd man: show output in example systemd-resolve commands

I think example output allows the reader of the man page to
see what functionlity is provided without running the commands
themselves. Specific values in the examples are bound to get out
of date but this is not a problem.

2016-02-16 19:10:25 -05:00

catalog

editors: only extend line width to 119 for C and XML files

2016-02-10 12:29:32 +01: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

build-sys: run "make hwdb-update"

2016-02-11 13:11:02 +01:00

build-sys: Perform flag tests in context to existing flags

2016-02-06 14:57:46 +01:00

man

man: show output in example systemd-resolve commands

2016-02-16 19:10:25 -05:00

network

networkd: emit DNS/NTP/Timezone info via DHCP server by default

2015-08-27 16:47:26 +02:00

Update zh_TW translation.

2016-02-12 11:52:02 +08:00

rules

rfkill: rework and make it listen on /dev/rfkill

2015-10-01 16:21:09 +02:00

shell-completion

cgroup: remove support for NetClass= directive

2016-02-10 16:38:56 +01:00

src

resolved: make sure to normalize all domain names returned via the bus

2016-02-16 15:30:04 +01:00

sysctl.d

coredump: honour RLIMIT_CORE when saving/processing coredumps

2016-02-10 16:08:32 +01:00

system-preset

preset: enable machines.target by default

2014-12-29 17:36:57 +01:00

sysusers.d

remove bus-proxyd

2016-02-12 19:10:01 +01:00

test

tests: add test for https://github.com/systemd/systemd/issues/1981

2016-02-10 18:19:08 +00: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

remove bus-proxyd

2016-02-12 19:10:01 +01:00

xorg

2015-08-31 18:12:37 +02:00

.dir-locals.el

editors: only extend line width to 119 for C and XML files

2016-02-10 12:29:32 +01:00

.editorconfig

editors: only extend line width to 119 for C and XML files

2016-02-10 12:29:32 +01:00

.gitattributes

…

.gitignore

Merge pull request #2618 from zonque/busproxy-removal

2016-02-15 14:54:09 +01: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: only extend line width to 119 for C and XML files

2016-02-10 12:29:32 +01:00

.ycm_extra_conf.py

…

autogen.sh

build-sys: drop libsystemd-{id128,daemon,login,journal}.so compat libs

2016-02-13 11:57:14 +01:00

CODING_STYLE

CODING_STYLE: make sure line break recommendation matches edit configuration

2016-01-25 17:19:19 +01:00

configure.ac

build-sys: fix type detection

2016-02-16 15:22:06 +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

…

LICENSE.LGPL2.1

…

Makefile-man.am

Merge pull request #2618 from zonque/busproxy-removal

2016-02-15 14:54:09 +01:00

Makefile.am

resolved: turn on DNSSEC by default, unless configured otherwise

2016-02-16 15:22:05 +01:00

NEWS

resolved: turn on DNSSEC by default, unless configured otherwise

2016-02-16 15:22:05 +01:00

README

remove bus-proxyd

2016-02-12 19:10:01 +01:00

README.md

github: extend README.md a bit

2016-01-25 17:19:19 +01:00

TODO

Merge pull request #2618 from zonque/busproxy-removal

2016-02-15 14:54:09 +01:00

README.md

systemd - System and Service Manager

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.