[thirdparty/systemd.git] / DISTRO_PORTING

Porting systemd To New Distributions

HOWTO:
        You need to make the follow changes to adapt systemd to your
        distribution:

        1) Find the right configure parameters for:

            --with-rootprefix=
            --with-sysvinit-path=
            --with-sysvrcnd-path=
            --with-rc-local-script-path-start=
            --with-rc-local-script-path-stop=
            --with-kbd-loadkeys=
            --with-kbd-setfont=
            --with-tty-gid=
            --with-ntp-servers=
            --with-support-url=

        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.
        This will also inform you about ordering loops and suchlike

NTP POOL:

        By default, timesyncd uses the Google NTP servers
        time[1-4].google.com. They serve time that is not standards
        compliant, and can be up to .5s off. Google does not
        officially support these servers for the broader
        audience. Distributions and vendors really should not ship
        OSes or devices with these NTP servers configured. Instead,
        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:

        http://www.pool.ntp.org/en/vendors.html

        Again, if you ship your software or device with the default
        NTP servers, then you will get served wrong time, and will
        rely on services that might not be supported for long.

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.

        Pass --with-pamconfdir=no to ./configure to avoid installing this file
        and instead install your own.

CONTRIBUTING UPSTREAM:

        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.

        Thank you for understanding.
Commit	Line	Data
eb10a764 LP	1	Porting systemd To New Distributions
eb10a764 LP	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
	9	--with-rootprefix=
	10	--with-sysvinit-path=
dee4c244	11	--with-sysvrcnd-path=
bc270841 LP	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=
2ed3de9c	17	--with-ntp-servers=
b74d0fdf	18	--with-support-url=
bc270841	19
45548321 CA	20	2) Try it out. Play around (as an ordinary user) with
	21	'/usr/lib/systemd/systemd --test --system' for a test run
	22	of systemd without booting. This will read the unit files and
	23	print the initial transaction it would execute during boot-up.
	24	This will also inform you about ordering loops and suchlike
eb10a764	25
2ed3de9c LP	26	NTP POOL:
	27
	28	By default, timesyncd uses the Google NTP servers
	29	time[1-4].google.com. They serve time that is not standards
	30	compliant, and can be up to .5s off. Google does not
	31	officially support these servers for the broader
	32	audience. Distributions and vendors really should not ship
	33	OSes or devices with these NTP servers configured. Instead,
	34	please register your own vendor pool at ntp.org and make it
	35	the built-in default by passing --with-ntp-servers= to
	36	configure. Registering vendor pools is free:
	37
	38	http://www.pool.ntp.org/en/vendors.html
	39
	40	Again, if you ship your software or device with the default
	41	NTP servers, then you will get served wrong time, and will
	42	rely on services that might not be supported for long.
	43
baed1fed FS	44	PAM:
	45	The default PAM config shipped by systemd is really bare bones.
	46	It does not include many modules your distro might want to enable
	47	to provide a more seamless experience. For example, limits set in
	48	/etc/security/limits.conf will not be read unless you load pam_limits.
	49	Make sure you add modules your distro expects from user services.
	50
651742d8 FS	51	Pass --with-pamconfdir=no to ./configure to avoid installing this file
	52	and instead install your own.
	53
eb10a764	54	CONTRIBUTING UPSTREAM:
eb10a764	55
45548321	56	We generally do no longer accept distribution-specific
bc270841	57	patches to systemd upstream. If you have to make changes to
45548321	58	systemd's source code to make it work on your distribution,
19aadacf	59	unless your code is generic enough to be generally useful, we
bc270841	60	are unlikely to merge it. Please always consider adopting the
19aadacf JE	61	upstream defaults. If that is not possible, please maintain
19aadacf JE	62	the relevant patches downstream.
1486dbe1	63
bc270841	64	Thank you for understanding.