Ssh not waiting on network?

[dmtc1]

I downloaded the multicore iso and I can boot it fine in virtual box.  Out of the gate the ssh client is loaded, problem is when I write that iso to a usb key and boot ssh is not? 

The only conclusion, I could draw was that one of two things is happening:
1 Network active faster when booting iso in vbox without network ssh does not load properly.
2. My usb key creation process is flawed and ssh is not getting setup?

I was thinking is there a way I can verify the network is active prior to loading extensions?  I know on my Gentoo box I had a similiar issue, I put a sleep 5 and echo 'ip to screen' in my network init file, this was enough to let the dhcp server respond.  Not sure the exact time needed I picked 5 and it worked with 400day uptimes it didnt matter, once it worked I quit.

[gerald_clark]

When booting a USB key you need to use the waitusb boot code.
This will allow the USB key to be ready before TC starts scanning for the tce directory.
You should be using the ApplicationBrowser to install needed extensions to the USB key.

[dmtc1]

Here is what I am seeing.  I tried waitusb, but that was not the issue.  The top caption is virtual box booting the .iso, the bottom is booting usbkey in virtual box.  You can see one shot loads dropbear, apache, openssh vs the other which does not.

**************Good news, once I removed my head from my rear, I realized the virtual machine that was loading my extensions had them installed on the hard drive.  I don't know what I was thinking.  I got confused because it was loading extensions that where not in the ISO and I didnt realize where they were getting loaded.