2010/7/21 Andy Green <andy@xxxxxxxxxxx>
On 07/21/10 14:23, Somebody in the thread at some point said:If /bin/bash is working you're mostly there.
How can I achiev the behavior of the default debian system to show me a
log in prompt? I know the basics about vinit system. Thanks for any help
You can run the default /sbin/init as "init" which runs the standard init sequence. However, this is really inefficient for typical embedded device, it can be 30s or more before it's done on an otherwise fast system.
I did a lot of work on the txtr device init scripts based on Fedora to finish boot into its GUI in ~7s from power on.
In there, I run agetty directly like this (you will need to adjust the serial device to match your serial console device ) -->
agetty /dev/ttymxc0 115200 vt100-nav
You can so this by making "init" a shell script, mount goodies like proc / sys / dev/pts and so on in there and then spawn agetty.
It's enough to just have
#!/bin/sh
at the start (and chmod the script +x !) and the kernel can understand it's a shell script for init. If you made that shell script as /sbin/myinit, you would need init=/sbin/myinit on the kernel commandline to get it working.
Once you have your init "script" you can pile all the boot tasks in there until / unless you're ready to migrate them to systemd or whatever.
-Andy
Some weeks ago I allready used the fedora rootfs in combination with the factory kernel / uboot, which did not use the init boot option. How did they achiev it to get a login prompt? What did they do, I am really curious and would like to recreate that behaviour
Regards
Bernhard
_______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm
