Hi , Excuse me for the jumbled mail problem and I will fix it.
Yes, I am clear that busybox "init" doesn't support run levels. /etc/inittab says use sysvinit for runlevels and to use run level, in the Buildroot ( using gcc 4.1.2 , binuitls 2.17 and uClibc 0.9.29 version) busybox package selection, I have enabled "Hide application that are provided by busybox" to select "sysvinit" which builts and installs sysVinit version 2.86 in the final rootfs. In the rootfs, I have modified a bit in /etc/inittab and created rc2.d in /etc to test the run level 2 . Finally, the bootup message ..... Looking up port of RPC 100003/2 on 192.168.6.1 Looking up port of RPC 100005/1 on 192.168.6.1 VFS: Mounted root (nfs filesystem). Freeing init memory: 108K INIT: version 2.86 booting INIT: Entering runlevel: 2 uClibc login: shows that init doesn't execute /etc/init.d/rcS or /etc/init.d/rc. If there is a syntax error or missing run level in the inittab then "init" throws the respective error message. Here is my /etc/inittab and rc2.d for further analysis # /etc/inittab # # Copyright (C) 2001 Erik Andersen # # Note: BusyBox init doesn't support runlevels. The runlevels field is # completely ignored by BusyBox init. If you want runlevels, use # sysvinit. # The default runlevel. id:2:initdefault: # Startup the system l1::sysinit:/bin/mount -o remount,rw / l2::sysinit:/bin/mount -t proc proc /proc l3::sysinit:/bin/mount -a # now run any rc scripts si::sysinit:/etc/init.d/rcS ( this is not invoked ) # /etc/init.d executes the S and K scripts upon change # of runlevel. l4:2:wait:/etc/init.d/rc 2 ( this is not called after entering runlevel 2) # Set up a couple of getty's #tty1::respawn:/sbin/getty 38400 tty1 #tty2::respawn:/sbin/getty 38400 tty2 # Put a getty on the serial port T1::respawn:/sbin/getty -L ttySA0 38400 vt100 ( respawn getty for login prompt) I went through the http://busybox.net/bugs/view.php?id=1244 bug tracking and seems to be bit similar. I have also performed some test discussed like echo TEST >/dev/tty echo TEST >/dev/console and i got TEST msg printed out on the console. Executing the scripts individually inside the prompt works well. I use the rootfs built by buildroot using . Its strange that init desn't execute the /etc/initd.rcS and /etc/init.d/rc ? At the least it should execute /etc/init.d/rcS. Did I missed something very important to make init work? Sara ----- Original Message ----- From: "Denys Vlasenko" <[EMAIL PROTECTED]> To: "saravanan chanemouganandam" <[EMAIL PROTECTED]> Cc: "Saravanan Chanemouganandam" <[EMAIL PROTECTED]>; "Brian Austin" <[EMAIL PROTECTED]>; <[email protected]> Sent: Tuesday, December 04, 2007 7:05 PM Subject: Re: init hangs > On Monday 03 December 2007 09:01, saravanan chanemouganandam wrote: >> Hi, >> >> I have finally built the toolchain and rootfs using buildroot for the arm >> target. Using init=/bin/ash I endup with the prompt. Now, I have a small >> problem in using "sysvinit" built with the busybox package to use run >> level >> configurations. > > Sidenote: busybox init doesn't support runlevels. > It's not my idea to make it so, but I agree with it. > SysV init's runlevels was a wrong design decision in the first place. > >> The init starts well and uses /etc/inittab but doesn't run >> the /etc/init.d/rcS script. > > Is it similar to http://busybox.net/bugs/view.php?id=1244 ? > >> I have replaced buildoot /etc with existing >> /etc to incude run levels. > > Just replacing /etc scripts cannot make runlevels work. > You need different init (not busybox's one). > >> IP-Config: Complete:device=eth0, addr=192.168.6.243, mask=255.255.255.0, >> gw=192.168.6.1,host=cm-x270, domain=, >> nis-domain=(none),bootserver=192.168.6.1, rootserver=192.168.6.1, >> rootpath=Looking up port of RPC 100003/2 on 192.168.6.1Looking up port of >> RPC 100005/1 on 192.168.6.1VFS: Mounted root (nfs filesystem).Freeing >> init >> memory: 108KINIT: version 2.86 bootingINIT: Entering runlevel: 2 Debian >> GNU/Linux 3.1 ttySA0 login: rootPassword: any idea why init doesn't >> starts the rcS script. > > (Something is wrong with mail program you are using. > It all looksjumbledtogether.) > > If you will show your /etc/inittab and /etc/*rc_scripts_you_are_using*, > somebody on the list may have easier time trying to reproduce it. > -- > vda > _______________________________________________ busybox mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/busybox
