UPDATED: init will not execute inittab lines that start with null::

[Thompson Harmon [US], Stanley W.]

> 
> Rob,
> 
>    I tried rw as a kernel option... no change in results.  
> Furthermore, I used my new kernel (2.6.11) and boot loader 
> (syslinux) with my old buildroot/busybox filesystem from a 
> year ago and it works fine.  Please note that both 
> filesystems (new one is based on busybox 1.1.3) have the rw 
> equivalent as the first executable "null::/bin/mount..." line 
> in the /etc/inittab file.  You can find this code in the 
> example inittab for busybox.  Oh, and I also made sure I had 
> switch_root available for my 2.6 kernel in case pivot_root 
> (for kernel 2.4) was not used by busybox init.
> 
> On another note, I will check with the linux sites too.
> 
> Stan
> 
> P.S. Sorry for the top post - it's an evil blackberry thing.
> 
> On Friday 28 July 2006 7:29 am, Thompson Harmon [US], Stanley 
> W. wrote:
> > Dave,
> > 
> >    The /dev/null file does exist in my filesystem.  I have 
> even tried to
> > move the null::sysinit:... lines to a file called
> > /etc/init.d/S01inittab.  The file did execute; but, the / filesystem
> > remained read-only.  My current thought is this must be a simple
> > configuration error somewhere.
> 
> Add "rw" to your kernel command line.
> 
> I don't suppose that kernelnewbies.org has a mailing list for 
> these sort of 
> questions?  (Or perhaps Linux From Scratch?)
> 
> Rob
> -- 
> Never bet against the cheap plastic solution.
> _______________________________________________

Rob,

   After many hours of configuration switch research, build attempts,
and a retry of your "rw" request, we discovered that our syslinux boot
loader was NEVER added to configuration control.  Thus, as our
development environments were upgraded, so were our boot loaders.  The
old boot loader with the new kernel and file system works well.
However, the new boot loader with the new kernel and file system
requires the "rw" to work correctly.  In sort, it was always broken.  As
I often say, there is a difference between having an error and KNOWING
that you have an error.

   As for the busybox inittab example, our busybox inittab was derived
from the 2001 busybox inittab example.  The 2004 busybox inittab example
does NOT contain the "null::sysinit:/bin/mount ..." lines.  Hmmm, if
memory serves, I think this is 2006?!?

Thanks for the help,
Stan