All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vyacheslav Yurkov <uvv.mail@gmail.com>
To: Quentin Schulz <foss@0leil.net>, docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH 1/2] ref-manual: add overlayfs-etc class
Date: Fri, 17 Dec 2021 07:05:04 +0100	[thread overview]
Message-ID: <768e04dc-feb7-89f6-9465-b1ba61753e01@gmail.com> (raw)
In-Reply-To: <C97BA46D-92DD-4A26-871C-D0991A67E1E8@0leil.net>

Hi Quentin,
Thanks for the review

On 16.12.2021 18:37, Quentin Schulz wrote:
>
>> +
>> +  OVERLAYFS_ETC_MOUNT_OPTIONS = "wsync"
>> +
>> +The class provides two options for ``/sbin/init`` generation:
>> +
>> +* Default option is to rename original ``/sbin/init`` to ``/sbin/init.orig`` and
>> +  place generated init under original name, i.e. ``/sbin/init``. It has an advantage
>> +  that you won't need to change any kernel parameters in order to make it work,
>> +  but it poses a restriction that package-management can't be used, becaause updating
>> +  init manager would remove generated script
> What is the default value? This needs to be explicit otherwise it cannot be "undone" in a bbappends for example.
>
> Thanks for the patch,
> Cheers,
> Quentin

Could you please elaborate on default value of what we are talking here? 
For mandatory variables there are no default values, for two optional 
variables the default values are set with ??=.

Cheers,
Slava


      reply	other threads:[~2021-12-17  6:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15 17:11 [PATCH 1/2] ref-manual: add overlayfs-etc class Vyacheslav Yurkov
2021-12-15 17:11 ` [PATCH 2/2] ref-manual: document overlayfs-etc image feature Vyacheslav Yurkov
2021-12-15 20:54   ` [docs] " Michael Opdenacker
2021-12-15 18:54 ` [docs] [PATCH 1/2] ref-manual: add overlayfs-etc class Michael Opdenacker
2021-12-16 17:37 ` Quentin Schulz
2021-12-17  6:05   ` Vyacheslav Yurkov [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=768e04dc-feb7-89f6-9465-b1ba61753e01@gmail.com \
    --to=uvv.mail@gmail.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=foss@0leil.net \
    /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.