0N/APorting systemd To New Distributions
0N/A You need to make the follow changes to adapt systemd to your
2362N/A 0) Make your distribution recognized via the autoconf checks
2362N/A insensitively) and you should be able to find the places where
0N/A read your host name from. You might also want to update
0N/A 2) Check the unit files in units/ if they match your
0N/A distribution. Most likely you will have to make additions to
2362N/A step 2. Also you might need to update the m4 invocation in
0N/A and you should be able to find the places where you need to
0N/A 4) Try it out. Play around with 'systemd --test --system' for
0N/A a test run of systemd without booting. This will read the unit
0N/A files and print the initial transaction it would execute
0N/A during boot-up. This will also inform you about ordering loops
0N/ACONTRIBUTING UPSTREAM:
0N/A We are interested in merging your changes upstream, if they
2080N/A are for a big, and well-known distribution. Unfortunately we
0N/A don't have the time and resources to maintain
2080N/A distribution-specific patches for all distributions on the
2080N/A planet, hence please do not send us patches that add systemd
0N/A support for non-mainstream or niche distributions.
2080N/A Thank you for understanding.
0N/A We'd like to keep differences between the distributions
0N/A minimal. This both simplifies our maintenance work, as well
0N/A as it helps administrators to move from one distribution to
0N/A Hence we'd like to ask you to keep your changes minimal, and
0N/A not rename any units without a very good reason (if you need a
0N/A particular name for compatibility reasons, consider using
0N/A alias names via symlinks). Before you make changes that change
0N/A semantics from upstream, please talk to us!
0N/A In SysV almost every distribution uses a different
0N/A nomenclature and different locations for the boot-up
1263N/A scripts. We'd like to avoid chaos like that with systemd right
0N/A from the beginning. So please, be considerate!