Yes but i already have an flag from kernel arguments. So and have created rc.d init script which looks for this but what i wanted is to bring that script into the foreground.
On Tue, Jan 17, 2012 at 2:15 PM, Jonathan Bither <[email protected]>wrote: > You can probably have a hook similar to the failsafe hook that does "echo > 1 > /tmp/pawelhook" and have your init script read it and do whatever you > want. > > > On 01/17/2012 02:10 PM, Pawel Pastuszak wrote: > >> Need dhcp up first and everything mounted. >> >> So if there is an easy flag for that then i think pre-init would solve >> my issue. >> >> Pawel >> >> On Tue, Jan 17, 2012 at 2:05 PM, Jonathan Bither <[email protected] >> <mailto:[email protected]>> wrote: >> >> Why not add a pre-init hook? >> >> >> On 01/17/2012 02:02 PM, Pawel Pastuszak wrote: >> >> Ok, but i am looking for it to go into the foreground and i want >> to lock >> the console access till it finished running it then reboot. >> >> Pawel >> >> On Tue, Jan 17, 2012 at 1:52 PM, Luka Perkov >> <[email protected] <mailto:[email protected]**> >> <mailto:[email protected] >> >> <mailto:[email protected]**>__>> wrote: >> >> On Tue, Jan 17, 2012 at 01:42:13PM -0500, Pawel Pastuszak >> wrote: >> > Hello everybody, >> > >> > I have an odd question i am trying to find an way to have my >> init >> script on >> > power up to take over the console so the process can be >> interrupted. It's >> > pretty much if an flag is set to x in kernel arguments then do y >> but i want >> > y to be the foreground process. What i notice all Init script >> are >> executed >> > in background. >> > >> > Any thoughts for any one? >> >> If your script is in the foreground and does not finish your >> openwrt >> will not boot completely. That is especialy the case when >> you boot >> openwrt for the first time after flashing it on the device. >> >> Luka >> ______________________________**___________________ >> openwrt-devel mailing list >> [email protected].__**org >> >> <mailto:openwrt-devel@lists.**openwrt.org<[email protected]> >> > >> <mailto:openwrt-devel@lists.__**openwrt.org <http://openwrt.org> >> >> <mailto:openwrt-devel@lists.**openwrt.org<[email protected]> >> >> >> >> https://lists.openwrt.org/__**mailman/listinfo/openwrt-devel<https://lists.openwrt.org/__mailman/listinfo/openwrt-devel> >> >> <https://lists.openwrt.org/**mailman/listinfo/openwrt-devel<https://lists.openwrt.org/mailman/listinfo/openwrt-devel> >> **> >> >> >> >> >> >> ______________________________**___________________ >> openwrt-devel mailing list >> [email protected].__**org >> >> <mailto:openwrt-devel@lists.**openwrt.org<[email protected]> >> > >> >> https://lists.openwrt.org/__**mailman/listinfo/openwrt-devel<https://lists.openwrt.org/__mailman/listinfo/openwrt-devel> >> >> <https://lists.openwrt.org/**mailman/listinfo/openwrt-devel<https://lists.openwrt.org/mailman/listinfo/openwrt-devel> >> **> >> >> ______________________________**___________________ >> openwrt-devel mailing list >> [email protected].__**org >> <mailto:openwrt-devel@lists.**openwrt.org<[email protected]> >> > >> >> https://lists.openwrt.org/__**mailman/listinfo/openwrt-devel<https://lists.openwrt.org/__mailman/listinfo/openwrt-devel> >> >> >> <https://lists.openwrt.org/**mailman/listinfo/openwrt-devel<https://lists.openwrt.org/mailman/listinfo/openwrt-devel> >> **> >> >> >> >> >> ______________________________**_________________ >> openwrt-devel mailing list >> [email protected].**org <[email protected]> >> https://lists.openwrt.org/**mailman/listinfo/openwrt-devel<https://lists.openwrt.org/mailman/listinfo/openwrt-devel> >> > ______________________________**_________________ > openwrt-devel mailing list > [email protected].**org <[email protected]> > https://lists.openwrt.org/**mailman/listinfo/openwrt-devel<https://lists.openwrt.org/mailman/listinfo/openwrt-devel> >
_______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
