Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: "Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be>
Cc: Norbert Lange <nolange79@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] docs/manual: introduce "Integration topics" chapter
Date: Fri, 29 Jul 2022 22:50:33 +0200	[thread overview]
Message-ID: <20220729205033.GC1554632@scaer> (raw)
In-Reply-To: <20220727221217.1072588-1-arnout@mind.be>

Arnout, All,

On 2022-07-28 00:12 +0200, Arnout Vandecappelle (Essensium/Mind) spake thusly:
> We want to add more information in the manual about how a system created
> with buildroot works overall. We currently already have a chapter about
> SELinux, but we want to add more information like that, e.g. details
> about how systemd in Buildroot works.
> 
> Create a new chapter "Integration topics" with an introductory blurb,
> and move the SELinux topic under it (as a section rather than a
> chapter).
> 
> "Integration topics" is not the best title, but we couldn't find
> anything better.
> 
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>

Applied to master with the fix spotted by Edgard, thanks.

Regards,
Yann E. MORIN.

> ---
>  ...x-support.txt => integration-selinux-support.txt} |  6 +++---
>  docs/manual/integration.txt                          | 12 ++++++++++++
>  docs/manual/manual.txt                               |  2 ++
>  3 files changed, 17 insertions(+), 3 deletions(-)
>  rename docs/manual/{selinux-support.txt => integration-selinux-support.txt} (96%)
>  create mode 100644 docs/manual/integration.txt
> 
> diff --git a/docs/manual/selinux-support.txt b/docs/manual/integration-selinux-support.txt
> similarity index 96%
> rename from docs/manual/selinux-support.txt
> rename to docs/manual/integration-selinux-support.txt
> index 21137ae6c3..1f6bcf47eb 100644
> --- a/docs/manual/selinux-support.txt
> +++ b/docs/manual/integration-selinux-support.txt
> @@ -2,7 +2,7 @@
>  // vim: set syntax=asciidoc:
>  
>  [[selinux]]
> -== Using SELinux in Buildroot
> +=== Using SELinux in Buildroot
>  
>  https://selinuxproject.org[SELinux] is a Linux kernel security module
>  enforcing access control policies. In addition to the traditional file
> @@ -30,7 +30,7 @@ upstream https://github.com/SELinuxProject/refpolicy[refpolicy]
>  project, enabled with +BR2_PACKAGE_REFPOLICY+.
>  
>  [[enabling-selinux]]
> -=== Enabling SELinux support
> +==== Enabling SELinux support
>  
>  To have proper support for +SELinux+ in a Buildroot generated system,
>  the following configuration options must be enabled:
> @@ -42,7 +42,7 @@ In addition, your filesystem image format must support extended
>  attributes.
>  
>  [[selinux-policy-tweaking]]
> -=== SELinux policy tweaking
> +==== SELinux policy tweaking
>  
>  The +SELinux refpolicy+ contains modules that can be enabled or
>  disabled when being built. Each module provide a number of +SELinux+
> diff --git a/docs/manual/integration.txt b/docs/manual/integration.txt
> new file mode 100644
> index 0000000000..bdfbfa59de
> --- /dev/null
> +++ b/docs/manual/integration.txt
> @@ -0,0 +1,12 @@
> +// -*- mode:doc; -*-
> +// vim: set syntax=asciidoc:
> +
> +[[integration]]
> +== Integration topics
> +
> +This chapter discusses how various things are integrated at system
> +level. Buildroot is highly configurable, almost everything discussed
> +here can be changed or overridden by xref:rootfs-custom[rootfs overlay
> +or custom skeleton] configuration.
> +
> +include::integration-selinux-support.txt[]
> diff --git a/docs/manual/manual.txt b/docs/manual/manual.txt
> index b5cc044805..8ba0c76d32 100644
> --- a/docs/manual/manual.txt
> +++ b/docs/manual/manual.txt
> @@ -38,6 +38,8 @@ include::common-usage.txt[]
>  
>  include::customize.txt[]
>  
> +include::integration.txt[]
> +
>  include::selinux-support.txt[]
>  
>  include::faq-troubleshooting.txt[]
> -- 
> 2.35.3
> 

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2022-07-29 20:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27 22:12 [Buildroot] [PATCH 1/2] docs/manual: introduce "Integration topics" chapter Arnout Vandecappelle (Essensium/Mind)
2022-07-27 22:12 ` [Buildroot] [PATCH 2/2] docs/manual: add integration section for systemd with dbus Arnout Vandecappelle (Essensium/Mind)
2022-07-29 20:51   ` Yann E. MORIN
2022-07-28  7:54 ` [Buildroot] [PATCH 1/2] docs/manual: introduce "Integration topics" chapter Edgar Bonet
2022-07-29 20:49   ` Yann E. MORIN
2022-07-29 20:50 ` Yann E. MORIN [this message]

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=20220729205033.GC1554632@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=arnout@mind.be \
    --cc=buildroot@buildroot.org \
    --cc=nolange79@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox