In article <firstname.lastname@example.org>, email@example.com says…
The “right build script” is the question. What we wanted to do was add some
boot-up capability that would auto-launch our app and make sure it stayed
I probably took the wrong approach.
Not at all. You might want to rid of a lot of unnecessary stuff for
target system (like pkg fs, compiller, enumerators etc.). .boot and
…altboot images on compact disk were designed to boot almost any PC for
installing selfhosted development tools (or playing non-commercially if
you got free distribution).
I’m glad to hear you solved the problem.
I don’t know enough about the scripts in
RC.D, or wherever, to know where to turn Photon off, to force bootup without
a password, and how to auto-launch our app. Instead, I initialized the
harddrive using “fdisk”, added a boot partition, started the disk driver,
mounted the harddrive to a given name, then created /bin, /sbin, /lib
directories where I coppied in the QNX files we needed. Then I built simple
.boot and .altboot files that includes a KSH script which is an infinite
loop and makes sure our app is launched and running. If it crashes, the
script simply restarts it.
Which direction to take…What would have been nice is to modify the
default “project”, or whatever it is, that builds the default .boot and
.altboot images, and add in some custom controls.
It depends on what you want to achieve. You can slightly modify the base
installation (like I did for my tight h/w) - you should read all those
scripts starting form /etc/system/sysinit and couple of good articles
“Making Buildfiles…” at
Or you can build custom system:
Thanks for taking a look,
Did you choose the right build script (there are quite a few scripts in
/boot/build, but they are real :^)). Did you rid of “diskboot” from the