I've written a program in Qt that should load automatically when the root fs has been initialized. I'm using ptxdist for the rootfs. The rootfs also requires a login. 1.) How do I a disable thr login such that my program can execute without having to logon to the system? 2.) How do I execute my Qt program automatically once the rootfs has been initialized Thank you MC
Think you could put something into profile.environment I noticed that Pengutronix have put a few export variables for tslib in there, so I was going to try putting them all in there plus: /usr/bin/./arora -qws
Just create a small script that starts your application and store it at /etc/init.d/<my_script_name>. After that create a simple symbolic link to this file in directory "/etc/rc.d/S99_<my_script_name>" pointing to the script in "/etc/init.d/<my_script_name>". The S99* means these jobs are started in the order of these numbers. And S99* is the last one. So it will be started if the others things booting up the system are already done.
Thank you guys. Do you have any advice for q1. more specific to ptx? 1.) How do I a disable thr login such that my program can execute without having to logon to the system? MC
So, profile.environment is not called during bootup? Dave
I also used profile.environment and it works. But I first have to login before it is called.
bluscape I just send you offline an example how to do it with the help of PTXdist.
Hi Juergen, I've implemented the startup script procedure that you have provided and it is working fine. Only problem is that my fonts are not the same anymore and the touch screen is also not working anymore. Its seems as if the startup script prevent other scripts from being executed even though it is a S99. Do you have any ideas where this coudl go wrong? Thank you MC
Ok, found the problem. Copied the tslib exports from /etc/profile.environment to the startup script.
Ups, sorry. Yes, the "/etc/profile.environment" is used from the shell interpreter only. And your application is now started from "init". BTW: You should not copy its content, just source it into your script with: . /etc/profile.environment
This is working fine, ut I think the fact that I bypass the login screen, the fs is not enabled for file access. The program is running fine but I've added some setting files which I can't read and write when I bypass the login screen. When I boot normal with the login prompt activated everything works fine and I can read and write the setting files. How can I enable file access even when the login screen is bypassed?
I have no idea what your problem is. Can you show us the error messages you see?