[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#992034: installation-guide: Include a note on how to change init system during install



On Fri, Aug 27, 2021 at 12:19:11PM +0200, Holger Wansing wrote:
> Hi,
> 
> Justin Rye <justin.byam.rye@gmail.com> wrote (Fri, 27 Aug 2021 07:38:17 +0100):
> > Holger Wansing <hwansing@mailbox.org> wrote:
> > > I wonder if "the easiest time to select an alternative init system is during the
> > > installation process" is correct English.
> > >
> > > Maybe better "the best time ... " ?
> > >
> > > Asking debian-l10n-english for advise.
> > >
> > > @debian-l10n-english:
> > > Hi all, could someone please comment on the merge request
> > > mentioned above?
> > 
> > There's nothing wrong with the English of "the easiest time to do X is
> > during Y"; "best" is also okay but asserts something different (which
> > is slightly more a matter of subjective opinion).
> 
> Ok.
> 
Rather than easiest / best, maybe use "most appropriate" or 
"most straightforward" since it can be quite hard afterwards.

All best, as ever,

Andy Cater

> 
> Moreover, when thinking about this implementation, I'm quite uncomfortable with 
> adding such paragraph into the "Using individual components" section, since this 
> "change-init-system part" is no "installer component" like the others in this 
> section (say: there is no 'change-init-system udeb').
> 
> Therefore, I would be in favor of adding a separate section for such things as
> section 6.5 after the "Loading missing firmware" section, like this:
> 
> 
> 
> ====snip==================================
> diff --git a/build/templates/docstruct.ent b/build/templates/docstruct.ent
> index dd3e8d273..81702c32d 100644
> --- a/build/templates/docstruct.ent
> +++ b/build/templates/docstruct.ent
> @@ -126,6 +126,8 @@
>    <!ENTITY module-pkgsel.xml             SYSTEM "##SRCPATH##/using-d-i/modules/pkgsel.xml">
>    <!ENTITY loading-firmware.xml          SYSTEM "##SRCPATH##/using-d-i/loading-firmware.xml">
>  
> +  <!ENTITY misc-adaptions.xml            SYSTEM "##SRCPATH##/using-d-i/misc-adaptions.xml">
> +
>    <!-- No longer used; should be removed after translation updates -->
>    <!ENTITY module-mips-arcboot-installer.xml  SYSTEM "##SRCPATH##/using-d-i/modules/mips/arcboot-installer.xml">
>    <!ENTITY module-mipsel-colo-installer.xml  SYSTEM "##SRCPATH##/using-d-i/modules/mipsel/colo-installer.xml">
> diff --git a/en/using-d-i/using-d-i.xml b/en/using-d-i/using-d-i.xml
> index 3561ced2d..fe9c4628e 100644
> --- a/en/using-d-i/using-d-i.xml
> +++ b/en/using-d-i/using-d-i.xml
> @@ -446,6 +446,7 @@ report installer software problems to &debian; developers later.
>  
>  &using-d-i-components.xml;
>  &loading-firmware.xml;
> +&misc-adaptions.xml;
>  
>  </chapter>
> 
> ====snap==================================
> 
> 
> Plus adding a new file en/using-d-i/misc-adaptions.xml:
> 
> +<!-- retain these comments for translator revision tracking -->
> +<!-- $Id$ -->
> +
> + <sect1 id="misc-adaptions">
> + <title>Miscellaneous adaptions</title>
> +<para>
> +You may make custom adaptions of the installation process, to make it fit 
> +your needs:
> +</para>
> +
> +  <sect2><title>Installing an alternative init system</title>
> +<para>
> +&debian; uses systemd as its default init system. However, other init
> +systems (such as sysvinit and OpenRC) are supported, and the
> +easiest time to select an alternative init system is during the
> +installation process. For detailed instructions on how to do so,
> +please see the <ulink
> +url="https://wiki.debian.org/Init#Changing_the_init_system_-_at_installation_time";>Init
> +page on the Debian wiki</ulink>.
> +</para>
> +
> +  </sect2>
> + </sect1>
> 
> 
> 
> 
> @debian-l10n-english: How does this look like for you (especially the first 
> part, since review for the second part has already been done) ?
> 
> @debian-boot: any objections against this solution?
> 
> 
> 
> Holger
> 
> 
> 
> 
> -- 
> Holger Wansing <hwansing@mailbox.org>
> PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076
> 


Reply to: