projects / thirdparty / systemd.git / blame
| Commit | Line | Data |
|---|---|---|
| eb10a764 LP |
1 | Porting systemd To New Distributions |
| 2 | ||
| 1486dbe1 | 3 | HOWTO: |
| eb10a764 LP |
4 | You need to make the follow changes to adapt systemd to your |
| 5 | distribution: | |
| 6 | ||
| bc270841 LP |
7 | 1) Find the right configure parameters for: |
| 8 | ||
| 72cdb3e7 ZJS |
9 | -D rootprefix= |
| 10 | -D sysvinit-path= | |
| 11 | -D sysvrcnd-path= | |
| 12 | -D rc-local= | |
| 13 | -D halt-local= | |
| 14 | -D loadkeys-path= | |
| 15 | -D setfont-path= | |
| 16 | -D tty-gid= | |
| 17 | -D ntp-servers= | |
| 0629976f | 18 | -D dns-servers= |
| 72cdb3e7 | 19 | -D support-url= |
| bc270841 | 20 | |
| 45548321 CA |
21 | 2) Try it out. Play around (as an ordinary user) with |
| 22 | '/usr/lib/systemd/systemd --test --system' for a test run | |
| 23 | of systemd without booting. This will read the unit files and | |
| 24 | print the initial transaction it would execute during boot-up. | |
| 72cdb3e7 | 25 | This will also inform you about ordering loops and suchlike. |
| eb10a764 | 26 | |
| 2ed3de9c | 27 | NTP POOL: |
| 0629976f LP |
28 | By default, systemd-timesyncd uses the Google Public NTP servers |
| 29 | time[1-4].google.com, if no other NTP configuration is available. They | |
| 30 | serve time that uses a leap second smear, and can be up to .5s off from | |
| 31 | servers that use stepped leap seconds. | |
| 2ed3de9c | 32 | |
| 501bf2d5 MS |
33 | https://developers.google.com/time/smear |
| 34 | ||
| 35 | If you prefer to use leap second steps, please register your own | |
| 36 | vendor pool at ntp.org and make it the built-in default by | |
| 37 | passing --with-ntp-servers= to configure. Registering vendor | |
| 38 | pools is free: | |
| 2ed3de9c | 39 | |
| 501bf2d5 | 40 | http://www.pool.ntp.org/en/vendors.html |
| 2ed3de9c | 41 | |
| 0629976f LP |
42 | Use -D ntp-servers= to direct systemd-timesyncd to different fallback |
| 43 | NTP servers. | |
| 44 | ||
| 45 | DNS SERVERS: | |
| 46 | By default, systemd-resolved uses the Google Public DNS servers | |
| 47 | 8.8.8.8, 8.8.4.4, 2001:4860:4860::8888, 2001:4860:4860::8844 as | |
| 48 | fallback, if no other DNS configuration is available. | |
| 49 | ||
| 50 | Use -D dns-servers= to direct systemd-resolved to different fallback | |
| 51 | DNS servers. | |
| 52 | ||
| baed1fed FS |
53 | PAM: |
| 54 | The default PAM config shipped by systemd is really bare bones. | |
| 55 | It does not include many modules your distro might want to enable | |
| 56 | to provide a more seamless experience. For example, limits set in | |
| 57 | /etc/security/limits.conf will not be read unless you load pam_limits. | |
| 58 | Make sure you add modules your distro expects from user services. | |
| 59 | ||
| 72cdb3e7 ZJS |
60 | Pass -D pamconfdir=no to meson to avoid installing this file and |
| 61 | instead install your own. | |
| 651742d8 | 62 | |
| eb10a764 | 63 | CONTRIBUTING UPSTREAM: |
| 72cdb3e7 ZJS |
64 | We generally do no longer accept distribution-specific patches to |
| 65 | systemd upstream. If you have to make changes to systemd's source code | |
| 66 | to make it work on your distribution, unless your code is generic | |
| 67 | enough to be generally useful, we are unlikely to merge it. Please | |
| 68 | always consider adopting the upstream defaults. If that is not | |
| 69 | possible, please maintain the relevant patches downstream. | |
| 1486dbe1 | 70 | |
| bc270841 | 71 | Thank you for understanding. |