From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15151] New: Busybox /etc/init.d scripts are not executable
Date: Sun, 27 Nov 2022 21:42:37 +0000 [thread overview]
Message-ID: <bug-15151-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15151
Bug ID: 15151
Summary: Busybox /etc/init.d scripts are not executable
Product: buildroot
Version: 2022.02.7
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: mek101-dev.inv@slmail.me
CC: buildroot@uclibc.org
Target Milestone: ---
I've been trying to build a compact qemu VM with buildroot (commit
d036dc6ec873f50a24e73d8dbdafecb3b4098909) with a readonly filesystem.
At boot, the following error is displayed after the kernel messages:
> can't run '/etc/init.d/rcS': Permission denied
After a small investigation, it appears that busybox's init scripts aren't
marked with the executable bit permission, and as such aren't run.
> # ls -l /etc/init.d/
> total 9
> -rw-r--r-- 1 root root 1012 Nov 24 17:24 S01syslogd
> -rw-r--r-- 1 root root 1004 Nov 24 17:24 S02klogd
> -rw-r--r-- 1 root root 2804 Nov 24 17:24 S02sysctl
> -rw-r--r-- 1 root root 1620 Nov 24 17:24 S20urandom
> -rw-r--r-- 1 root root 438 Nov 24 17:24 S40network
> -rw-r--r-- 1 root root 423 Nov 24 17:24 rcK
> -rw-r--r-- 1 root root 408 Nov 24 17:24 rcS
This is while all the symlinks in /bin and /sbin are correctly set as
executable.
Perhaps a packaging error?
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-11-27 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-27 21:42 bugzilla [this message]
2022-11-27 22:45 ` [Buildroot] [Bug 15151] Busybox /etc/init.d scripts are not executable bugzilla
2022-11-28 15:10 ` bugzilla
2022-11-28 15:25 ` bugzilla
2022-11-28 15:26 ` bugzilla
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=bug-15151-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/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