Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] no /dev/console; /dev/null when booting with initrd of type 'ext2'
Date: Tue, 16 Oct 2012 19:27:00 +0200	[thread overview]
Message-ID: <20121016192700.01faa4e8@skate> (raw)
In-Reply-To: <20121016162825.GA26334@mail.sceen.net>

Dear Richard Braun,

On Tue, 16 Oct 2012 18:28:25 +0200, Richard Braun wrote:
> On Tue, Oct 16, 2012 at 06:15:36PM +0200, Thierry Bultel wrote:
> > 2) Why does ext2 not work with devtmpfs (the answer is likely
> > somewhere in the kernel sources and I will take a look as well) ?
> 
> A common mistake is forgetting to select the "mount devtmpfs at boot
> time" option (CONFIG_DEVTMPFS_MOUNT).

Yes, but Thierry explicitly said he enabled this option, re-read the
e-mail you're replying to :)

Maybe the devtmpfs mounting done by CONFIG_DEVTMPFS_MOUNT does not take
place when an initrd is used? I honestly don't know, I don't use initrd
personally.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-10-16 17:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-16 14:16 [Buildroot] no /dev/console; /dev/null when booting with initrd of type 'ext2' Thierry Bultel
2012-10-16 14:23 ` Richard Braun
2012-10-16 16:15   ` Thierry Bultel
2012-10-16 16:28     ` Richard Braun
2012-10-16 17:27       ` Thomas Petazzoni [this message]
2012-10-16 17:30         ` Richard Braun
2012-10-16 21:20         ` Peter Korsgaard
2012-10-16 16:09 ` Arnout Vandecappelle
2012-10-17 12:04   ` Thierry Bultel
2012-10-17 21:10     ` Thomas Petazzoni

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=20121016192700.01faa4e8@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --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