]>
Commit | Line | Data |
---|---|---|
1 | Porting systemd To New Distributions | |
2 | ||
3 | HOWTO: | |
4 | You need to make the follow changes to adapt systemd to your | |
5 | distribution: | |
6 | ||
7 | 1) Find the right configure parameters for: | |
8 | ||
9 | --with-rootprefix= | |
10 | --with-sysvinit-path= | |
11 | --with-sysvrcnd-path= | |
12 | --with-rc-local-script-path-start= | |
13 | --with-rc-local-script-path-stop= | |
14 | --with-kbd-loadkeys= | |
15 | --with-kbd-setfont= | |
16 | --with-tty-gid= | |
17 | --with-ntp-servers= | |
18 | ||
19 | 2) Try it out. Play around (as an ordinary user) with | |
20 | '/usr/lib/systemd/systemd --test --system' for a test run | |
21 | of systemd without booting. This will read the unit files and | |
22 | print the initial transaction it would execute during boot-up. | |
23 | This will also inform you about ordering loops and suchlike | |
24 | ||
25 | NTP POOL: | |
26 | ||
27 | By default, timesyncd uses the Google NTP servers | |
28 | time[1-4].google.com. They serve time that is not standards | |
29 | compliant, and can be up to .5s off. Google does not | |
30 | officially support these servers for the broader | |
31 | audience. Distributions and vendors really should not ship | |
32 | OSes or devices with these NTP servers configured. Instead, | |
33 | please register your own vendor pool at ntp.org and make it | |
34 | the built-in default by passing --with-ntp-servers= to | |
35 | configure. Registering vendor pools is free: | |
36 | ||
37 | http://www.pool.ntp.org/en/vendors.html | |
38 | ||
39 | Again, if you ship your software or device with the default | |
40 | NTP servers, then you will get served wrong time, and will | |
41 | rely on services that might not be supported for long. | |
42 | ||
43 | CONTRIBUTING UPSTREAM: | |
44 | ||
45 | We generally do no longer accept distribution-specific | |
46 | patches to systemd upstream. If you have to make changes to | |
47 | systemd's source code to make it work on your distribution, | |
48 | unless your code is generic enough to be generally useful, we | |
49 | are unlikely to merge it. Please always consider adopting the | |
50 | upstream defaults. If that is not possible, please maintain | |
51 | the relevant patches downstream. | |
52 | ||
53 | Thank you for understanding. |