mirror of
https://git.busybox.net/buildroot.git
synced 2024-12-03 18:33:48 +08:00
98a6f1fc02
When booting with 'console=<empty>' in the kernel command line (as e.g. U-Boot does with silent flags in effect), opening /dev/console fails. As per POSIX [0], when iany redirection fails, the shell running exec shal exit in error. So, when 'console=<empty>' is specified. /dev/console can't be opened, and the redirection fails, and /init is killed. That behaviour was fixed on the kernel side with commit 2bd3a997befc2 (Open /dev/console from rootfs), present since 2.6.34, released in May 2010, so any [dr]ecent kernel will have that fix. Furthermore, busybox will fix things up anyway (in bb_sanitize_stdio()), falling back to opening /dev/null if no console is availble. systemd does a similar thing (in make_console_stdio()), and sysvinit again has a similar approach (in console_init()). The archealogy search turned up those relevant commits: 2011-08-04 |
||
---|---|---|
.. | ||
axfs | ||
btrfs | ||
cloop | ||
cpio | ||
cramfs | ||
erofs | ||
ext2 | ||
f2fs | ||
initramfs | ||
iso9660 | ||
jffs2 | ||
romfs | ||
squashfs | ||
tar | ||
ubi | ||
ubifs | ||
yaffs2 | ||
common.mk | ||
Config.in |