[BusyBox] can't seem to get "minit" working as an init replacement

[Robert P. J. Day]

  i just finished replacing the standard init with "minit", and the boot
fails at the point where init should be invoked.

  currently, here's my setup:

* /sbin/minit -> ../bin/busybox, so the symlink for minit seems fine
* /etc/minit has a fairly simple structure -- i'm following an example
  setup from the www.fefe.de site

when i boot, i use the boot line:

  load: console=ttyS0,9600 rw root=/dev/ram0 init=/sbin/minit


what i get is
==========================================================
...

VFS: Mounted root (ext2 filesystem).
Mounted devfs on /dev
Freeing unused kernel memory: 60k init         <-- so far, so good ...
BusyBox v1.00-pre8 (2004.03.19-12:46+0000) multi-call binary

Usage: busybox [function] [arguments]...
   or: [function] [arguments]...

        BusyBox is a multi-call binary that combines many common Unix
        utilities into a single executable.  Most people will create a
        link to busybox for each function they wish to use, and BusyBox
        will act like whatever it was invoked as.

Currently defined functions:

... (big snip here) ...

Kernel panic: Attempted to kill init!
 <0>Rebooting in 180 seconds..

==========================================================

  this would suggest that the initial invocation of minit is what's
failing, and that it has nothing to do with my actual minit configuration;
it doesn't seem that minit is even being started.

  thoughts? 

rday