summaryrefslogtreecommitdiff
path: root/README
blob: a183cb364f7eb3958eede5d4cca09e28438ef0e7 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
systemd System and Session Manager

DETAILS:
        http://0pointer.de/blog/projects/systemd.html

WEB SITE:
        http://www.freedesktop.org/wiki/Software/systemd

GIT:
        git://anongit.freedesktop.org/systemd
        ssh://git.freedesktop.org/git/systemd

GITWEB:
        http://cgit.freedesktop.org/systemd/

MAILING LIST:
        http://lists.freedesktop.org/mailman/listinfo/systemd-devel
        http://lists.freedesktop.org/mailman/listinfo/systemd-commits

IRC:
        #systemd on irc.freenode.org

BUG REPORTS:
        https://bugs.freedesktop.org/enter_bug.cgi?product=systemd

AUTHOR:
        Lennart Poettering with major support from Kay Sievers

REQUIREMENTS:
        Linux kernel >= 2.6.30 (with devtmpfs, cgroups; optional but strongly recommended: autofs4, ipv6)
        libudev >= 163
        dbus >= 1.4.0
        libcap
        gtk+ >= 2.20 (optional)
        PAM >= 1.1.2 (optional)
        libcryptsetup (optional)
        libaudit (optional)
        libselinux (optional)
        tcpwrappers (optional)
        libnotify (optional)

        When you build from git you need the following additional dependencies:

        vala >= 0.10
        docbook-xsl
        xsltproc
        automake
        autoconf
        libtool
        make, gcc, and similar tools

        During runtime you need the following dependencies:

        util-linux > v2.18 (requires fsck -l, agetty -s)
        sulogin (from sysvinit-tools, optional but recommended)
        plymouth (optional)
        dracut (optional)

WARNINGS:
        systemd will warn you during boot if /etc/mtab is not a
        symlink to /proc/mounts. Please ensure that /etc/mtab is a
        proper symlink.

        systemd will warn you during boot if /usr is on a different
        file system than /. While in systemd itself very little will
        break if /usr is on a seperate partition many of its
        dependencies very likely will break sooner or later in one
        form or another. For example udev rules tend to refer to
        binaries in /usr, binaries that link to libraries in /usr or
        binaries that refer to data files in /usr. Since these
        breakages are not always directly visible systemd will warn
        about this, since this kind of file system setup is not really
        supported anymore by the basic set of Linux OS components.