All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ulrich Ölmann" <u.oelmann@pengutronix.de>
To: michael.opdenacker@bootlin.com
Cc: Paul Eggleton <bluelightning@bluelightning.org>,
	"Michael Opdenacker via lists.yoctoproject.org"
	<michael.opdenacker=bootlin.com@lists.yoctoproject.org>,
	docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] manuals: expand init manager documentation
Date: Fri, 28 Apr 2023 09:11:26 +0200	[thread overview]
Message-ID: <6redo4bhk0.fsf@pengutronix.de> (raw)
In-Reply-To: <20230427155308.56744-1-michael.opdenacker@bootlin.com>

Hi Michael,

On Thu, Apr 27 2023 at 17:53 +0200, "Michael Opdenacker via lists.yoctoproject.org" <michael.opdenacker=bootlin.com@lists.yoctoproject.org> wrote:
> From: Michael Opdenacker <michael.opdenacker@bootlin.com>
>
> - Add details about INIT_MANAGER
>   Correct the fact that "none" currently generates
>   an image with "sysvinit", at least on Poky.
>   This behaviour should probably be changed.
>
> - Expand the "Selecting an Initialization Manager" section.
>
> - Stop mentioning "rescue image" generation, as this
>   is not detailed anywhere else.
>
> Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
> CC: Paul Eggleton <bluelightning@bluelightning.org>
> ---
>  documentation/dev-manual/device-manager.rst |   2 +
>  documentation/dev-manual/init-manager.rst   | 108 +++++++++++++-------
>  documentation/ref-manual/variables.rst      |  31 ++++--
>  3 files changed, 98 insertions(+), 43 deletions(-)
>

[...]

>  
> diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
> index 01b710199d..acfdd7a544 100644
> --- a/documentation/ref-manual/variables.rst
> +++ b/documentation/ref-manual/variables.rst
> @@ -3959,16 +3959,33 @@ system and gives an overview of their function and contents.
>     :term:`INIT_MANAGER`
>        Specifies the system init manager to use. Available options are:
>  
> -      -  ``sysvinit`` - System V init (default for poky)
> -      -  ``systemd`` - systemd
> -      -  ``mdev-busybox`` - mdev provided by busybox
> -      -  ``none`` - no init manager
> +      -  ``sysvinit``
> +      -  ``systemd``
> +      -  ``mdev-busybox``
> +      -  ``none``
> +
> +      With ``sysvinit``, the init manager is set to
> +      :wikipedia:`SysVinit <Init#SysV-style>`, the traditional UNIX init
> +      system. This is the default choice in the Poky distribution, together with
> +      the Udev device manager (see the ":ref:`device-manager`" section).
> +
> +      With ``systemd``, the init manager becomes :wikipedia:`systemd <Systemd>`,
> +      which comes with the :wikipedia:`udev <Udev>` device manager.
> +
> +      With ``mdev-busybox``, the init manager becomes the must simpler BusyBox

here a typo probably slipped in:

  s/becomes the must simpler/becomes the much simpler/

> +      init, together with the BusyBox mdev device manager. This is the simplest
> +      and lightest solution, and probably the best choice for low-end systems
> +      with a rather slow CPU and a limited amount of RAM.
> +
> +      With ``none``, the init manager is also set to ``sysvinit``. This is the
> +      default setting in OpenEmbedded-Core. This option also selects the
> +      :wikipedia:`udev <Udev>` device manager.
>  
>        More concretely, this is used to include
>        ``conf/distro/include/init-manager-${INIT_MANAGER}.inc`` into the global
> -      configuration. You can have a look at the ``conf/distro/include/init-manager-*.inc``
> -      files for more information, and also the
> -      ":ref:`dev-manual/init-manager:selecting an initialization manager`"
> +      configuration. You can have a look at the
> +      :yocto_git:`meta/conf/distro/include/init-manager-*.inc </poky/tree/meta/conf/distro/include>`
> +      files for more information, and also the ":ref:`init-manager`"
>        section in the Yocto Project Development Tasks Manual.
>  
>     :term:`INITRAMFS_DEPLOY_DIR_IMAGE`

A nice refinement for the documentation - thanks!

Best regards
Ulrich
-- 
Pengutronix e.K.                           | Ulrich Ölmann               |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |


  reply	other threads:[~2023-04-28  7:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-27 15:53 [PATCH] manuals: expand init manager documentation michael.opdenacker
2023-04-28  7:11 ` Ulrich Ölmann [this message]
2023-04-28  8:26   ` [docs] " Michael Opdenacker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6redo4bhk0.fsf@pengutronix.de \
    --to=u.oelmann@pengutronix.de \
    --cc=bluelightning@bluelightning.org \
    --cc=docs@lists.yoctoproject.org \
    --cc=michael.opdenacker=bootlin.com@lists.yoctoproject.org \
    --cc=michael.opdenacker@bootlin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.