Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH buildroot] fs/common: Create initial console device
Date: Wed, 31 Oct 2012 23:46:33 +0100	[thread overview]
Message-ID: <5091AA49.6070300@mind.be> (raw)
In-Reply-To: <1351677232-14959-1-git-send-email-markos.chandras@gmail.com>

On 10/31/12 10:53, Markos Chandras wrote:
> From: Markos Chandras<markos.chandras@imgtec.com>
>
> A /dev/console node must be present in rootfs when the Linux kernel
> boots otherwise the kernel will print the following warning:
> "Warning: unable to open an initial console"
>
> This is because when we use an initramfs along with devtmpfs, the /dev
> directory is not populated at this point. This can cause problems when a
> program (e.g ldso with early debugging enabled) opens a standard file
> descriptor for read/write before these descriptors are actually created by
> the init process later on.
>
> Signed-off-by: Markos Chandras<markos.chandras@imgtec.com>

  Good point.  However:

- this is also true for mdev/udev;
- it is only relevant in a cpio/initramfs rootfs;
- it's cleaner to use the device table.

So I'd add a device table line to PACKAGES_PERMISSIONS_TABLE in
fs/cpio/cpio.mk, where the init script is also installed.

  Regards,
  Arnout

> ---
>   fs/common.mk |    6 ++++++
>   1 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/fs/common.mk b/fs/common.mk
> index debf7db..d7383d1 100644
> --- a/fs/common.mk
> +++ b/fs/common.mk
> @@ -55,6 +55,12 @@ endif
>   	echo "$(HOST_DIR)/usr/bin/makedevs -d $(FULL_DEVICE_TABLE) $(TARGET_DIR)">>  $(FAKEROOT_SCRIPT)
>   endif
>   	echo "$(ROOTFS_$(2)_CMD)">>  $(FAKEROOT_SCRIPT)
> +	# create initial console if devtmpfs is used
> +ifeq ($(BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_DEVTMPFS),y)
> +	echo -e 'pushd $(TARGET_DIR)/dev/>  /dev/null 2>&1'>>  $(FAKEROOT_SCRIPT)
> +	echo -e '/bin/mknod -m 622 console c 5 1'>>  $(FAKEROOT_SCRIPT)
> +	echo -e 'popd>  /dev/null 2>&1'>>  $(FAKEROOT_SCRIPT)
> +endif
>   	chmod a+x $(FAKEROOT_SCRIPT)
>   	$(HOST_DIR)/usr/bin/fakeroot -- $(FAKEROOT_SCRIPT)
>   	- at rm -f $(FAKEROOT_SCRIPT) $(FULL_DEVICE_TABLE)

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2012-10-31 22:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-31  9:53 [Buildroot] [PATCH buildroot] fs/common: Create initial console device Markos Chandras
2012-10-31 22:46 ` Arnout Vandecappelle [this message]
2012-11-01  9:22   ` Markos Chandras

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=5091AA49.6070300@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox