Matt Lawrence wrote:
There is a "firstboot" init script (e.g., /etc/init.d/firstboot) that looks for select files (e.g., /etc/sysconfig/firstboot). Depending whether it exists or doesn't exist, the firstboot init script -- if set to start for the run-level -- does or doesn't do something. It will then create/delete the file at the end of the run, as appropriate, to prevent it from running next time.
The firstboot package has various dependencies that I don't really want. But it could be a good model.
You might also want to keep in mind that firstboot is run only when the /etc/reconfigSys file exists. The /etc/sysconfig/firstboot file is only checked by firstboot itself....
and you need something like :
firstboot --reconfig
in the ks.cfg to get that setup properly.