All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Williams <jwilliams@itee.uq.edu.au>
To: Olaf Hering <olaf@aepfle.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ENOENT creating /dev/root on MTD RAM partition
Date: Tue, 03 Apr 2007 12:15:22 +1000	[thread overview]
Message-ID: <4611B8BA.6000406@itee.uq.edu.au> (raw)
In-Reply-To: <20070402125212.GA11522@aepfle.de>

Olaf Hering wrote:
> On Mon, Apr 02, John Williams wrote:
> 
>>Any comments or suggestions on a possible cause or approach to track it
>>down would be greatly appreciated.
> 
> Just a guess:
> Check if '/dev' exists. I think it is now possible to not add the built-in
> cpio archive with the mandatory /dev, /dev/console and /root entries.

Thanks Olaf - you got me on the right track.  Turned out to be an arch 
link script error whereby the "rootfs" initcalls were not placed in the 
initcall table - thus the init ramfs wasn't yet mounted, and /dev wasn't 
there.

Cheers,

John

  reply	other threads:[~2007-04-03  2:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-02  6:41 ENOENT creating /dev/root on MTD RAM partition John Williams
2007-04-02 12:52 ` Olaf Hering
2007-04-03  2:15   ` John Williams [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-04-02  1:09 John Williams

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=4611B8BA.6000406@itee.uq.edu.au \
    --to=jwilliams@itee.uq.edu.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olaf@aepfle.de \
    /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.