On Thu, Nov 20, 2003 at 06:27:31AM +1100, Bruce Evans wrote: > > set init_path=/rescue/init > > If dynamic root were ready to be turned on, then /rescue/init would be > in the default init_path. I had that explained to me too. :-) There is a loop in sys/kern/init_main.c that "probes" for an init to run. But it only does what you want for cases of the files not existing or otherwise just totally not executable. It won't handle the "started but then dumped core" case the way it would need to if /sbin/init were to fail because of shared library problems. So if just relying on this mechanism it would either not work right (/sbin/init in the path before /rescue/init) or it would always start /rescue/init (/rescue/init before /sbin/init in the path). -- Ken Smith - From there to here, from here to | kensmith_at_cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel |Received on Wed Nov 19 2003 - 10:43:25 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:30 UTC