cederom commented on PR #3192: URL: https://github.com/apache/nuttx-apps/pull/3192#issuecomment-3455980760
> > @cederom: I still think it would be good to refactor `init_*` to `nxinit_*` or at least have self-explanatory `nxinit_main` in the configs since application is called nxinit. What do you think guys? :-) > > ``` > > CONFIG_INIT_ENTRYPOINT="nxinit_main" > > ``` > > @JianyuWang0623: @cederom Thank you. **_This is my view_**: whether it is the current NxInit, or SystemV Init (which may be added later), or other versions, from a functional perspective, the default value of PROGNAME should be "init". For example, in some Linux distributions, even systemd uses the widely recognized name "init": > > ```shell > $ cat /etc/lsb-release > DISTRIB_ID=Ubuntu > DISTRIB_RELEASE=22.04 > DISTRIB_CODENAME=jammy > DISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS" > > $ ls /usr/sbin/init -l > lrwxrwxrwx 1 root root 20 Jun 4 22:17 /usr/sbin/init -> /lib/systemd/systemd > ``` > > ``` > SYSTEMD(1) > NAME > systemd, init - systemd system and service manager > ``` > > If there is anything wrong with what I said, please feel free to correct me, thanks. Okay @JianyuWang0623 as discussed in different PR now I get your point - there may be different init applications and all of them will provide the same `init_main` entry point, the kconfig file will use the same entry point for all of them, there will be no conflict because only one can be selected at time - this is more versatile approach 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]
