busybox 컴파일 문제 질문 드립니다.
정상 적으로 작동하는 램디스크에 busybox를 컴파일해서 적용을 해보았습니다.
램디스크를 올리고 나서 문제가 발생하는데 왜 이런 문제가 생기는지.??
여러 방법으로 테스트를 했는데도..??
busybox컴파일시 컴파일을 잘못해서 생기는 문제인지..??
윗 부분을 보면 init에서 문제가 발생한는데 정상적으로 작동하는 램디크였는데
init busybox와 관련되서 문제가 되는듯한데..
혹 init는 기존에 오리지날 init를 사용 해보려고도 해보았지는 그것도 여의치 안네요..
혹시 어떤 방식으로 해결해야 할지 아시는분..조언좀 부탁드립니다.
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 120K
init started: BusyBox v1.9.1 (2008-02-22 14:20:05 KST)
Bad inittab entry: id:3:initdefault:
Bad inittab entry: pf::powerwait:/etc/init.d/powerfail start
Bad inittab entry: pn::powerfailnow:/etc/init.d/powerfail now
Bad inittab entry: po::powerokwait:/etc/init.d/powerfail stop
Can't open /dev/si: No such file or directory
Can't open /dev/~~: No such file or directory
Can't open /dev/l0: No such file or directory
Can't open /dev/l1: No such file or directory
Can't open /dev/l2: No such file or directory
Can't open /dev/l3: No such file or directory
Can't open /dev/l4: No such file or directory
Can't open /dev/l5: No such file or directory
Can't open /dev/l6: No such file or directory
Can't open /dev/1: No such file or directory
Can't open /dev/T0: No such file or directory
Can't open /dev/z6: No such file or directory
process '/sbin/sulogin' (pid 800) exited. Scheduling it for restart.
process '/sbin/getty 115200 tty1' (pid 801) exited. Scheduling it for restart.
process '/sbin/getty -L ttyS0 115200 vt100' (pid 802) exited. Scheduling it for restart.
Can't open /dev/1: No such file or directory
Can't open /dev/T0: No such file or directory
Can't open /dev/z6: No such file or directory
process '/sbin/sulogin' (pid 803) exited. Scheduling it for restart.
process '/sbin/getty 115200 tty1' (pid 804) exited. Scheduling it for restart.
process '/sbin/getty -L ttyS0 115200 vt100' (pid 805) exited. Scheduling it for restart.
Can't open /dev/1: No such file or directory
Can't open /dev/T0: No such file or directory
Can't open /dev/z6: No such file or directory
process '/sbin/sulogin' (pid 806) exited. Scheduling it for restart.
process '/sbin/getty 115200 tty1' (pid 807) exited. Scheduling it for restart.
process '/sbin/getty -L ttyS0 115200 vt100' (pid 808) exited. Scheduling it for restart.
Can't open /dev/1: No such file or directory
Can't open /dev/T0: No such file or directory
Can't open /dev/z6: No such file or directory
process '/sbin/sulogin' (pid 809) exited. Scheduling it for restart.
process '/sbin/getty 115200 tty1' (pid 810) exited. Scheduling it for restart.
process '/sbin/getty -L ttyS0 115200 vt100' (pid 811) exited. Scheduling it for restart.
Can't open /dev/1: No such file or directory
Can't open /dev/T0: No such file or directory
Can't open /dev/z6: No such file or directory
process '/sbin/sulogin' (pid 812) exited. Scheduling it for restart.
process '/sbin/getty 115200 tty1' (pid 813) exited. Scheduling it for restart.
process '/sbin/getty -L ttyS0 115200 vt100' (pid 814) exited. Scheduling it for restart.
Can't open /dev/1: No such file or directory
Can't open /dev/T0: No such file or directory
Can't open /dev/z6: No such file or directory
process '/sbin/sulogin' (pid 815) exited. Scheduling it for restart.
process '/sbin/getty 115200 tty1' (pid 816) exited. Scheduling it for restart.
process '/sbin/getty -L ttyS0 115200 vt100' (pid 817) exited. Scheduling it for restart.
Can't open /dev/1: No such file or directory
Can't open /dev/T0: No such file or directory
Can't open /dev/z6: No such file or directory
process '/sbin/sulogin' (pid 818) exited. Scheduling it for restart.
process '/sbin/getty 115200 tty1' (pid 819) exited. Scheduling it for restart.
process '/sbin/getty -L ttyS0 115200 vt100' (pid 820) exited. Scheduling it for restart.
Can't open /dev/1: No such file or directory
Can't open /dev/T0: No such file or directory
Can't open /dev/z6: No such file or directory
비지박스 Doc를 보시면 답...
모 시간이 무지 무지 지난 질문이만..그래도..
비지박스 Docs 보시면 init 설명란에...
WARNING: This field has a non-traditional meaning for BusyBox init!
The id field is used by BusyBox init to specify the controlling tty for
the specified process to run on. The contents of this field are
appended to "/dev/" and used as-is. There is no need for this field to
be unique, although if it isn't you may have strange results. If this
field is left blank, the controlling tty is set to the console. Also
note that if BusyBox detects that a serial console is in use, then only
entries whose controlling tty is either the serial console or /dev/null
will be run. BusyBox init does nothing with utmp. We don't need no
stinkin' utmp.
예전의 inittab 하고는 달라졌습니다.
지금 님께서는 아래와 같이 예전의 inittab 를 사용 하시는것 같군여
1:2345:respawn:/sbin/getty 38400 tty1
2:23:respawn:/sbin/getty 38400 tty2
3:23:respawn:/sbin/getty 38400 tty3
4:23:respawn:/sbin/getty 38400 tty4
5:23:respawn:/sbin/getty 38400 tty5
6:23:respawn:/sbin/getty 38400 tty6
# Example how to put a getty on a serial line (for a terminal)
T0:23:respawn:/sbin/getty -L ttyS0 115200 vt100
설명을 보시면 아시겠지만 맨앞의 1,2,3,4,5,6, T0는 dev의 이름이 되었습니다.
그래서 아래와 같은 에러 메세지가 나온거구요.
Can't open /dev/1: No such file or directory
Can't open /dev/T0: No such file or directory
Busybox 내의 examples 에 보시면 sample inittab가 있으니 참조 하셔요.
댓글 달기