All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Bultel <thierry.bultel@wanadoo.fr>
To: buildroot@busybox.net
Subject: [Buildroot] no /dev/console; /dev/null when booting with initrd of type 'ext2'
Date: Tue, 16 Oct 2012 18:15:36 +0200	[thread overview]
Message-ID: <507D8828.4020007@wanadoo.fr> (raw)
In-Reply-To: <20121016142342.GA2131@mail.sceen.net>

Le 16/10/2012 16:23, Richard Braun a ?crit :
> On Tue, Oct 16, 2012 at 04:16:48PM +0200, Thierry Bultel wrote:
>> Would the solution be to always have these inodes created in
>> 'device_table.txt' ?
>> (Works in my case, I do not plan to use the static table)
> The devtmpfs "file system" is usually a better approach.
>
I have CONFIG_TMPFS and , and CONFIG_DEVTMPFS_MOUNT, and it works with 
everything but initrd of type "ext2"

I am thus asking 2 questions to myself
1) Why does the ISO image imply an ext2 initrd , instead of a cpio ?
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) ?

Regards
Thierry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121016/e479d661/attachment.html>

  reply	other threads:[~2012-10-16 16:15 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 [this message]
2012-10-16 16:28     ` Richard Braun
2012-10-16 17:27       ` Thomas Petazzoni
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=507D8828.4020007@wanadoo.fr \
    --to=thierry.bultel@wanadoo.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.