JianyuWang0623 commented on PR #17216: URL: https://github.com/apache/nuttx/pull/17216#issuecomment-3454700683
@anchao > Nuttx already supports init scripts, which follow shell syntax. The shell is initialized after the script is initialized. If you believe that init should be separated from nsh, the correct approach would be to improve nsh into 2-stage init/shell system while still providing support for legacy scripts within init. Splitting the initialization function from NSH is a good idea. From what I understand of `nsh_consolemain()`, it can be assumed that NSH includes the shell (sh) and additionally incorporates system initialization functionality. However, expanding the shell syntax while ensuring its stability may not be a straightforward task—for instance, how to configure the restart interval of the daemon process? If you already have ideas and are willing to share them, that would be fantastic. > However, the Nuttx kernel now uses 2 different startup script syntaxes: Android init and Nuttx init. Do you think this is a good design? Regarding the perspective of having multiple Init Languages coexist, could we maintain an open attitude toward their coexistence? For system initialization components that are relatively universal, independent, and optional, can we offer users an extra choice? I don’t see any downside to this. If there is anything wrong with what I’ve said, please feel free to correct me. Thank you. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
