3 ms·
I know I shouldn't feed the trolls... But init(8) != System V init scripts https://www.freebsd.org/cgi/man.cgi?query=init&apropos=0&sektion=0&manpath=FreeBS
by AdieuToLogic 11y ago
I know I shouldn't feed the trolls... But
init(8) != System V init scripts
https://www.freebsd.org/cgi/man.cgi?query=init&apropos=0&sektion=0&manpath=FreeBSD+10.2-RELEASE&arch=default&format=html https://www.freebsd.org/cgi/man.cgi?query=init&apropos=0&sek...
- tyingq 11y agoNot sure what you're trying to say. Launchd may not be a 100% function for function equivalent for init(8), but it does replace it, along with the rc subsystem. "launchd(8) replaces: init, rc, the init.d and rc.d scripts" (source: https://wiki.freebsd.org/launchd https://wiki.freebsd.org/launchd)
- AdieuToLogic 11y ago> Launchd may not be a 100% function for function equivalent for init(8), but it does replace it, along with the rc subsystem. You are right. I was drawing on quite old knowledge regarding the OS-X boot process in thinking launchd worked in collaboration with init(8) and friends. Apparently, it has been this way for some time[1]. I have been aware of launchd replacing rc.d since its introduction. What I did not realize is that it supplanted init as PID 1. Knowing that this is the case, I am less likely to support its adoption FWIW. 1 - http://aplawrence.com/Words2005/2005_05_15.html http://aplawrence.com/Words2005/2005_05_15.html