init_exec precedence, before or after init_script?
A recent change to init, has introduced the welcome init_exec kenv. Unfortunately "man init" indicates ambiguity as both: init_script and init_exec are run as "the very first action". So that needs a change. Due to this ambiguity I referred to the source, and init_exec is performed first. As init_script has been around for awhile, may I suggest that it be first and init_exec then take over the PID 1 position? It also suits my use case, where I have a script that does some file system work before transferring to init_exec, something I look forward to taking advantage of (rather than my current init hack) ;) Regards, Dewayne ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: virtualbox crash
On 20.09.20 16:29, xto...@hotmail.com wrote: Volodymyr Kostyrko wrote: Hello. I'm currently using 12.2-STABLE r365916. After update the host started crashing immediately after loading VirtualBox modules. Does anyone else experience similar behavior? Tried rebuilding vbox kernel modules? Was the first thing to try. No candy. It was working for me on the build from ~ Sep 9 or so. Bisecting to find the issue. -- Sphinx of black quartz judge my vow. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: virtualbox crash
Volodymyr Kostyrko wrote: Hello. I'm currently using 12.2-STABLE r365916. After update the host started crashing immediately after loading VirtualBox modules. Does anyone else experience similar behavior? Tried rebuilding vbox kernel modules? ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
virtualbox crash
Hello. I'm currently using 12.2-STABLE r365916. After update the host started crashing immediately after loading VirtualBox modules. Does anyone else experience similar behavior? Thanks in advance. -- Sphinx of black quartz judge my vow. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
