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>] [day] [month] [year] [list]
Date:	Thu, 22 Apr 2010 10:19:21 -0400
From:	Rishi Dhupar <rishid@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: initramfs issue with console missing

I am trying to use initramfs to run an embedded linux device.  I am
getting a kern warning printed during bootup that the kernel is unable
to open an initial console.  My rootfs does not contain a /dev/console
node; I was expecting to be able to create the /dev/console node in my
init script before the kernel tries to access the /dev tree.

Why does the kernel expect /dev/console to exist prior to running the
ramdisk init process?  I thought one of the benefits of initramfs was
it could run earlier in the init process, thus allowing me to create
devs and build the proc, sys directories at run-time. I know I could
do a mknod console on my host machine before building the rootfs but I
want my device to be able to get itself up and running with a minimal
file system.

For reference: init/main.c:init_post()
it checks if /dev/console exists (and prints warning) prior to calling
run_init_process(ramdisk_execute_command)
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ