2008/5/20 Alessandro Rubini <[EMAIL PROTECTED]>: > >> I use busybox on embedded system: PowerPC 405GP Walnut board >> which only has a serial port for debugging. > > So you have no display, and no text console on the display. > >> My busybox is built with default menuconfig settings and make it >> into Ramdisk form. > > So, it looks like your inittab includes entries to run getty on the > text terminals. > >> Can't open /dev/tty4: No such file or directory >> Can't open /dev/tty2: No such device or address >> Can't open /dev/tty3: No such device or address > > /dev/tty2 and /dev/tty3 exist on the filesystem but there is no associated > driver (no display, no text terminal). /dev/tty4 is not existing in the > filesystem. > >> The error message will show again and again. > > You should fix your inittab so init won't try to run the getty process > on those devices. >
I am not sure about him but mine /etc/inittab does not carry any tty[2-5] but it showed the same messages and linking /dev/tty[2-5] against /dev/null was the first workaround which shut up the busybox. If it could be of any help my system is a UMLinux but before launching it I unset the DISPLAY environment variable: http://lugge.wikidot.com/tar2loop and the used busybox is the last version 1.10.2, config could be retrieved here: http://lugge.wikidot.com/local--files/tar2loop/busybox.config here the /etc/inittab: # This is run first except when booting in single-user mode # ::sysinit:/etc/rc.sh # /bin/sh invocations on selected ttys # # Start an "askfirst" shell on the console (whatever that may be) ::askfirst:-/bin/sh # Start an "askfirst" shell on /dev/tty2-4 #tty2::askfirst:-/bin/sh #tty3::askfirst:-/bin/sh #tty4::askfirst:-/bin/sh # Stuff to do when restarting the init process ::restart:/sbin/init # Stuff to do before rebooting ::ctrlaltdel:/sbin/reboot ::shutdown:/etc/shutdown Cheers, -- /roberto _______________________________________________ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
