Hey thanks for the report.

I missed to change 2.8/3.0 in our rc init script. Also setup stuff contained need a version bump, etc.

In other words; our initrd need some work.

- fix problem with job control[1]
- fix version numbers
- review setup stuff (setup, setup.dependencies, etc.)
- add more doc about to create the CRUX media (file crux.media)
- etc.

[1] http://www.busybox.net/FAQ.html#job_control

there is no job control in the shell but note about the message you got:

* The CRUX media was not properly mounted!
Spawning a shell for you to attempt to fix this problem. If
you are able to find the correct device, mount it at
/media and then log out of this shell to continue.
If you are NOT able to fix the problem, installation will
not be possible.

/bin/sh: can't access tty; job control turned off

you need to have the CRUX media, so you missed to add a file called 'crux-media' at topdir of your media installation device

you can select between:

a) mount the CRUX media

1. you should look for you media installation device and mount it at /media
2. then log out (type 'exit' or press Control-D)

b) avoid this message and continue

1. log out (type 'exit' or press Control-D)

after that the init script will continue and you'll have a complete shell with job control

NOTES

- the CRUX media is required to complete some parts for the installation

if you just booted the initrd/initramfs for debug, test or rescue purposses you don't need it

- if you failed to mount the proper media then you can safely log out and continue with a complete shell

so later after you mounted the media properly you can try it again by running /etc/rc script

it was a problem with mdev -s command in order to create mmc devices correctly

see this changeset related: https://crux-arm.nu/gitweb?p=initramfs.git;a=commitdiff;h=47138301d00f8fe2805bc43168adec3931b421e8