/linuxrc link to /bin/busybox causes booting to fail (sysvinit should be used instead)

[David Huggins-Daines <dhuggins@cs.cmu.edu>]

Hi,

When booting base-image or minimal-image from a ramdisk, I get errors 
like the following:

RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem) on device 1:0.
init started: BusyBox v1.13.2 (2009-04-03 15:54:42 EDT)
Bad inittab entry at line 5
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/z6: No such file or directory
can't open /dev/S: No such file or directory
process '/sbin/sulogin' (pid 167) exited. Scheduling for restart.
process '/sbin/getty 57600 ttyAM0' (pid 168) exited. Scheduling for restart.

This is because, even though /sbin/init points to /sbin/init.sysvinit, 
there is also a /linuxrc -> /bin/busybox link, which the kernel uses in 
preference, causing busybox to run as 'init'.  The problem is that  
busybox init uses a different syntax from sysvinit.

I think this problem might have started when inittab support was added 
to busybox...

Is there a good reason for that /linuxrc link?  And if not, where is it 
coming from, so that I can remove it?

Thanks!