buildroot.busybox.net archive mirror
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: Norbert Lange <nolange79@gmail.com>, buildroot@buildroot.org
Cc: "Michał Łyszczek" <michal.lyszczek@bofc.pl>
Subject: Re: [Buildroot] [PATCH v2] package/openrc: add patch to create /run/lock/subsys
Date: Sun, 9 Jan 2022 14:12:16 +0100	[thread overview]
Message-ID: <f78e9576-5626-dbe4-b61b-7cd8f4a6b779@mind.be> (raw)
In-Reply-To: <20220109110555.3789-1-nolange79@gmail.com>



On 09/01/2022 12:05, Norbert Lange wrote:
> Together with changes to sysv/busybox init, this directory
> will already exist on all init systems before any service
> scripts are run.
> 
> Signed-off-by: Norbert Lange <nolange79@gmail.com>

  Applied to master, thanks.

  Normally we require patches to be upstreamed first, but there are already 
plenty of other patches that haven't been sent upstream. It could also be a bit 
buildroot-specific (though I think the subsys is there because some packages 
actually use that directory).

  Still, Michał, do you think this patch would be acceptable upstream? Obviously 
not in its current form since upstream has group uucp rather than daemon.

  Regards,
  Arnout

> ---
> v1->v2:
> *   refresh patch
> ---
>   ...lso-create-run-lock-subsys-directory.patch | 29 +++++++++++++++++++
>   1 file changed, 29 insertions(+)
>   create mode 100644 package/openrc/0006-Also-create-run-lock-subsys-directory.patch
> 
> diff --git a/package/openrc/0006-Also-create-run-lock-subsys-directory.patch b/package/openrc/0006-Also-create-run-lock-subsys-directory.patch
> new file mode 100644
> index 0000000000..cf592a88b0
> --- /dev/null
> +++ b/package/openrc/0006-Also-create-run-lock-subsys-directory.patch
> @@ -0,0 +1,29 @@
> +From 49e5929b468f604d80a0c04a6ce78eb96ca36090 Mon Sep 17 00:00:00 2001
> +From: Norbert Lange <nolange79@gmail.com>
> +Date: Sun, 9 Jan 2022 00:22:40 +0100
> +Subject: [PATCH] Also create /run/lock/subsys directory
> +
> +Buildroot service scripts regularly use this directory, so
> +create it in the most appropriate spot.
> +
> +Signed-off-by: Norbert Lange <nolange79@gmail.com>
> +---
> + sh/init.sh.Linux.in | 2 +-
> + 1 file changed, 1 insertion(+), 1 deletion(-)
> +
> +diff --git a/sh/init.sh.Linux.in b/sh/init.sh.Linux.in
> +index e8afc1fb..662ab223 100644
> +--- a/sh/init.sh.Linux.in
> ++++ b/sh/init.sh.Linux.in
> +@@ -82,7 +82,7 @@ elif ! mountinfo -q /run; then
> + fi
> +
> + checkpath -d "$RC_SVCDIR"
> +-checkpath -d -m 0775 -o root:daemon /run/lock
> ++checkpath -d -m 0775 -o root:daemon /run/lock /run/lock/subsys
> +
> + # Try to mount xenfs as early as possible, otherwise rc_sys() will always
> + # return RC_SYS_XENU and will think that we are in a domU while it's not.
> +--
> +2.34.1
> +
> 
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-01-09 13:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-09 11:05 [Buildroot] [PATCH v2] package/openrc: add patch to create /run/lock/subsys Norbert Lange
2022-01-09 13:12 ` Arnout Vandecappelle [this message]
2022-01-09 23:52   ` michal.lyszczek
2022-01-09 14:49 ` Arnout Vandecappelle

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=f78e9576-5626-dbe4-b61b-7cd8f4a6b779@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@buildroot.org \
    --cc=michal.lyszczek@bofc.pl \
    --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;
as well as URLs for NNTP newsgroup(s).