Hi, Niels and Javi said well for release-notes and translation time-line of installation-guide against the freeze.
If you are thinking of submitting a patch to installation-guide for the following part, I reminds you few things to get it accepted. > 196 <caution> > 197 <para> > 198 Be advised that some packages may have degraded behaviour or > @@ -33,3 +43,43 @@ > 207 role="package">systemd-sysv</systemitem> package must be > 208 installed first. > 209 </para> > + > + <!-- New installations of Jessie --> > + <title>How to avoid the default init system for Jessie</title> > + <para> > + For new installations of Jessie the default init system > + systemd-sysvinit will be installed. In order to run a > + traditional init system, such as sysvinit-core, two > + workarounds are available: > + > + <para> > + 1) Go through the installation, selecting the minimum number > + of packages, maybe do only select standard (or use > + netinst.iso). After the installation and first reboot, > + install sysvinit-core and remove systemd-sysv (and maybe > + other *systemd* packages). If a desktop is to be > + installed install systemd-shim first before choosing other > + components. > + </para> > + > + <para> > + 2) Use a preseed command to finish the install with > + sysvinit-core instead of systemd-core. (again choosing a > + minimum installation) > + <screen> > + Choose #### Advanced options > + Choose ### Running custom commands during the installation > + </screen> > + Issue > + <screen> > + preseed/late_command="in-target apt-get install -y sysvinit-core" > + </screen> > + and continue with the installation. > + For further info see > + https://wiki.debian.org/systemd#Installing_without_systemd > + and > + <screen> > + http://d-i.debian.org/manual/en.i386/apbs05.html > + http://d-i.debian.org/manual/example-preseed.txt > + </screen> > + </para> This is too long and the tone of text is not right. Although you may not like it, the rule is that the non-default install guide should not interfere with the guide for the default install process. Also, you should avoid writing long "workaround instructions" in the way which cause translation problems (There will be the last minutes changes which obsolete such workarounds.) I would suggest the following: 1. A short pointer text in appropriate main manual text pointing to the appendix containing workaround. For example, right before "6.3.4. Installing the Base System" propose to add "*.*.*. Setting the init system" and you state there simply as: | The default init system on the Debian <arch> system is <init-program>. | | You can override it using the preseeding (see B.2 Using the alternative | init system). (I am too lazy to gigure out how to set up <arch> and <init-program> in XML and entity references.) 2. Add new section "B.2.6. Using the alternative init system" | === Using the alternative init system === | | You can specify the alternative init system, e.g. the classic sysvinit, | to the debian-installer by passing preseed/late_command at the boot | prompt: | | <screen> | preseed/late_command="in-target apt-get install -y sysvinit-core" | </screen> | | Please note some desktop environment may not be fully compatible with | such non-standard init systems. If you feel like adding some other workarounds, please make them as the independent paragraph or list item. So each removal with some bug fix should not cause translation updates. (Dropped English text will be nicely synched via po4a.) You may ask a patch to example-preseed.txt, too. Quite frankly, HOWTO for switching already installed init system is off topic and should not be included in installation-guide. You should consider creating well organized text somewhere in wiki.debian.org if it does not exist. Good luck, Osamu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
