Do you have a question? Post it now! No Registration Necessary
Subject
- Posted on
Loading application after init
- 07-30-2007
- Himanshu Chauhan
July 30, 2007, 3:34 pm

Hello all,
I am doing an embedded project based on the AT91RM9200 board. I am using
2.6.22 vanilla kernel with patches from maxim. Till now the system boots
fine and init loads the sulogin followed by busy box shell, after
booting. I have a program. That is the only program that will ever run
on the board. How can start that automatically after init. I don't want
any login prompt. Board can drop into single user mode, no problem. But
it should be all by itself. Which is the way to go?
--Himanshu
I am doing an embedded project based on the AT91RM9200 board. I am using
2.6.22 vanilla kernel with patches from maxim. Till now the system boots
fine and init loads the sulogin followed by busy box shell, after
booting. I have a program. That is the only program that will ever run
on the board. How can start that automatically after init. I don't want
any login prompt. Board can drop into single user mode, no problem. But
it should be all by itself. Which is the way to go?
--Himanshu

Re: Loading application after init

Simply:
Just run your program instead of sulogin in init
tty1::respawn:/bin/yourprog
You really should have read the manual.
You want to be confident that the program you are running is solid -
especially if you are still developing.
Having a crashing program that continually respawns just makes things
more difficult.
The other option is to launch a script from init. I guess it depends
how complex your system is and how physically secure you want it to
be.
Cheers
Marc

Re: Loading application after init

Before posting here I had already tried the above initab thing. Didn't
work. For some reasons busybox's sulogin was being run. Sorry didn't
reply to any of the earlier posts, because all other posts were
preaching. I am used to usenet now. I understand when to post and I also
understand 10% people will try to preach. You can avoid them :) Anyways,
replacing sulogin didn't seem to work. I will have to figure out why it
happens. Because I had a similar problem. The tftp program in busybox
wasn't good enough. So I wrote a small tftp program and am using it now.
I copied that in /usr/local/bin where the symlink to tftp of busybox was
lysing in the board. But still when I simply type tftp the busybox's
tftp starts. To run my binary I have to give full path.
--Himanshu
Site Timeline
- » Porting u-boot and uClinux to SAmsung S3C33B0x
- — Next thread in » Embedded Linux
-
- » Setting up Board
- — Previous thread in » Embedded Linux
-
- » Addressing on I2C
- — Newest thread in » Embedded Linux
-
- » PCA9957 defektes SPI
- — The site's Newest Thread. Posted in » Electronics (German)
-