[BusyBox] init script and umount

[David Boyes]

Hi all,

I have been having a problem with shutdown, or rather restart after shutdown, 
on a busybox system using a conventional hard disk as the root device.  After 
looking at the sources, the CVS and newsgroups, I am not sure if this is a 
bug, a feature or just a result of the combination I am using.  The problem 
is that for recent versions disk is always "unclean" and needs to be fsck'ed.

The problem seems to be in init.c.  Apparently the decision was made between 
60.3 and 60.5 to put the run_actions() before the kill() calls which pull 
down all but the shutdown processes, in order that users can invoke scripts 
from inittab in a normal environment.  The problem on my system is that this 
does not permit "umount -a -r" given by a user to unmount and remount the 
root disk, so the next start sees the disk as badly unmounted.  When I move 
the run_actions() call back to after the kill()'s all is well.  I hesitate to 
shout "bug", as while there is from time to time mention of similar problems 
they are pretty rare, so it's maybe also related to the combination of 
chipset, compiler and kernel.  This is a 2.4.20 kernel patched for RTAI, and 
the compiler is gcc 3.2.2 with libc 2.3.1, and I've tried this on 60.3, 60.5 
and the two 1.0 pre's.

I attach the Config.h which can be used with either 60.3 and 60.5.  As you can 
see I compiled for mount, but I have also tried the distro umount with the 
same results.

Anyone else seen this or thinks it's a problem?

Regards
David Boyes


-------------- next part --------------
A non-text attachment was scrubbed...
Name: Config.h
Type: text/x-chdr
Size: 14313 bytes
Desc: not available
Url : http://lists.busybox.net/pipermail/busybox/attachments/20030730/f50a53bd/attachment.h