From: Khem Raj <raj.khem@gmail.com>
To: Stefan Agner <stefan@agner.ch>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] busybox: avoid circular dependency when using initramfs
Date: Tue, 6 Sep 2016 09:35:43 -0700 [thread overview]
Message-ID: <D66BCC92-E85B-4BCA-AB12-2517146B91C9@gmail.com> (raw)
In-Reply-To: <20160904202555.30636-1-stefan@agner.ch>
[-- Attachment #1: Type: text/plain, Size: 2724 bytes --]
> On Sep 4, 2016, at 1:25 PM, Stefan Agner <stefan@agner.ch> wrote:
>
> The kernel does not automatically mount devtmpfs when using initramfs
> based booting (even when using CONFIG_DEVTMPFS_MOUNT). If the rootfs
> is built with USE_DEVFS=1 (which is the default), the system ends up
> with a completely empty /dev to begin with.
>
> Busybox uses the first entry in inittab slightly different than
> other init systems:
> <id>: WARNING: This field has a non-traditional meaning for BusyBox init!
>
> The id field is used by BusyBox init to specify the controlling tty for
> the specified process to run on. The contents of this field are
> appended to "/dev/" and used as-is.
>
> Since /dev/null is not there yet, Busybox throws errors instead of
> executing the commands, and hence never mounts devtmpfs:
> init started: BusyBox v1.24.1 (2016-09-04 11:53:14 PDT)
> can't open /dev/null: No such file or directory
> can't open /dev/null: No such file or directory
> can't open /dev/null: No such file or directory
> can't open /dev/null: No such file or directory
> can't open /dev/null: No such file or directory
> can't open /dev/null: No such file or directory
> can't open /dev/null: No such file or directory
>
> Avoid this circular dependency by not specifing <id>. With that
> Busybox ends up using the stdio of the init process and executes
> the inittab just fine.
This looks good. Have you also tested it when using busybox/mdev as main
init system just not in initramfs
>
> Signed-off-by: Stefan Agner <stefan@agner.ch>
> ---
> meta/recipes-core/busybox/files/inittab | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/meta/recipes-core/busybox/files/inittab b/meta/recipes-core/busybox/files/inittab
> index bfec4a7..2bc831c 100644
> --- a/meta/recipes-core/busybox/files/inittab
> +++ b/meta/recipes-core/busybox/files/inittab
> @@ -1,13 +1,13 @@
> # This is run first except when booting in single-user mode.
>
> # Startup the system
> -null::sysinit:/bin/mount -t proc proc /proc
> -null::sysinit:/bin/mount -t sysfs sysfs /sys
> -null::sysinit:/bin/mount -t devtmpfs devtmpfs /dev
> -null::sysinit:/bin/mount -o remount,rw /
> -null::sysinit:/bin/mkdir -p /dev/pts
> -null::sysinit:/bin/mount -t devpts devpts /dev/pts
> -null::sysinit:/bin/mount -a
> +::sysinit:/bin/mount -t proc proc /proc
> +::sysinit:/bin/mount -t sysfs sysfs /sys
> +::sysinit:/bin/mount -t devtmpfs devtmpfs /dev
> +::sysinit:/bin/mount -o remount,rw /
> +::sysinit:/bin/mkdir -p /dev/pts
> +::sysinit:/bin/mount -t devpts devpts /dev/pts
> +::sysinit:/bin/mount -a
>
> ::sysinit:/etc/init.d/rcS
>
> --
> 2.9.0
>
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]
next prev parent reply other threads:[~2016-09-06 16:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-04 20:25 [PATCH] busybox: avoid circular dependency when using initramfs Stefan Agner
2016-09-06 16:35 ` Khem Raj [this message]
2016-09-06 17:51 ` Stefan Agner
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=D66BCC92-E85B-4BCA-AB12-2517146B91C9@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=stefan@agner.ch \
/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