linux-kernel - Re: ENOENT creating /dev/root on MTD RAM partition

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 03 Apr 2007 12:15:22 +1000
From:	John Williams <jwilliams@...e.uq.edu.au>
To:	Olaf Hering <olaf@...fle.de>
CC:	linux-kernel@...r.kernel.org
Subject: Re: ENOENT creating /dev/root on MTD RAM partition

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/