2010-05-17 01:39:51 +02:00
|
|
|
Porting systemd To New Distributions
|
|
|
|
|
2010-05-17 19:35:36 +02:00
|
|
|
HOWTO:
|
2010-05-17 01:39:51 +02:00
|
|
|
You need to make the follow changes to adapt systemd to your
|
|
|
|
distribution:
|
|
|
|
|
2013-01-04 23:24:38 +01:00
|
|
|
1) Find the right configure parameters for:
|
|
|
|
|
2017-07-03 02:21:34 +02:00
|
|
|
-D rootprefix=
|
|
|
|
-D sysvinit-path=
|
|
|
|
-D sysvrcnd-path=
|
|
|
|
-D rc-local=
|
|
|
|
-D halt-local=
|
|
|
|
-D loadkeys-path=
|
|
|
|
-D setfont-path=
|
|
|
|
-D tty-gid=
|
|
|
|
-D ntp-servers=
|
2017-07-24 11:26:54 +02:00
|
|
|
-D dns-servers=
|
2017-07-03 02:21:34 +02:00
|
|
|
-D support-url=
|
2013-01-04 23:24:38 +01:00
|
|
|
|
2014-12-02 14:30:59 +01:00
|
|
|
2) Try it out. Play around (as an ordinary user) with
|
|
|
|
'/usr/lib/systemd/systemd --test --system' for a test run
|
|
|
|
of systemd without booting. This will read the unit files and
|
|
|
|
print the initial transaction it would execute during boot-up.
|
2017-07-03 02:21:34 +02:00
|
|
|
This will also inform you about ordering loops and suchlike.
|
2010-05-17 01:39:51 +02:00
|
|
|
|
2015-07-11 19:16:40 +02:00
|
|
|
NTP POOL:
|
2017-07-24 11:26:54 +02:00
|
|
|
By default, systemd-timesyncd uses the Google Public NTP servers
|
|
|
|
time[1-4].google.com, if no other NTP configuration is available. They
|
|
|
|
serve time that uses a leap second smear, and can be up to .5s off from
|
|
|
|
servers that use stepped leap seconds.
|
2015-07-11 19:16:40 +02:00
|
|
|
|
2017-02-12 06:30:40 +01:00
|
|
|
https://developers.google.com/time/smear
|
|
|
|
|
|
|
|
If you prefer to use leap second steps, please register your own
|
|
|
|
vendor pool at ntp.org and make it the built-in default by
|
|
|
|
passing --with-ntp-servers= to configure. Registering vendor
|
|
|
|
pools is free:
|
2015-07-11 19:16:40 +02:00
|
|
|
|
2017-02-12 06:30:40 +01:00
|
|
|
http://www.pool.ntp.org/en/vendors.html
|
2015-07-11 19:16:40 +02:00
|
|
|
|
2017-07-24 11:26:54 +02:00
|
|
|
Use -D ntp-servers= to direct systemd-timesyncd to different fallback
|
|
|
|
NTP servers.
|
|
|
|
|
|
|
|
DNS SERVERS:
|
|
|
|
By default, systemd-resolved uses the Google Public DNS servers
|
|
|
|
8.8.8.8, 8.8.4.4, 2001:4860:4860::8888, 2001:4860:4860::8844 as
|
|
|
|
fallback, if no other DNS configuration is available.
|
|
|
|
|
|
|
|
Use -D dns-servers= to direct systemd-resolved to different fallback
|
|
|
|
DNS servers.
|
|
|
|
|
2016-10-10 15:40:05 +02:00
|
|
|
PAM:
|
|
|
|
The default PAM config shipped by systemd is really bare bones.
|
|
|
|
It does not include many modules your distro might want to enable
|
|
|
|
to provide a more seamless experience. For example, limits set in
|
|
|
|
/etc/security/limits.conf will not be read unless you load pam_limits.
|
|
|
|
Make sure you add modules your distro expects from user services.
|
|
|
|
|
2017-07-03 02:21:34 +02:00
|
|
|
Pass -D pamconfdir=no to meson to avoid installing this file and
|
|
|
|
instead install your own.
|
2016-10-12 16:56:27 +02:00
|
|
|
|
2010-05-17 01:39:51 +02:00
|
|
|
CONTRIBUTING UPSTREAM:
|
2017-07-03 02:21:34 +02:00
|
|
|
We generally do no longer accept distribution-specific patches to
|
|
|
|
systemd upstream. If you have to make changes to systemd's source code
|
|
|
|
to make it work on your distribution, unless your code is generic
|
|
|
|
enough to be generally useful, we are unlikely to merge it. Please
|
|
|
|
always consider adopting the upstream defaults. If that is not
|
|
|
|
possible, please maintain the relevant patches downstream.
|
2010-05-17 19:35:36 +02:00
|
|
|
|
2013-01-04 23:24:38 +01:00
|
|
|
Thank you for understanding.
|