I posit that starting svscan by init script, and not DJB's suggested inittab method, is dangerous. Example: new to the Gentoo system, I've tripped on a few changes to outlying network interface confs (i.e. not primary & therefore not critical) that caused the 'net' init dependency to fail. Thus, on next boot, failing to run svscan. Thus failing to start critical services, like ssh. Thus making a remote box dead in the water. Svscan should always be given a chance to run. (Of course, this also protects from svscan failure -- init will restart it.)
Mike, can you make this an option and add some postinst() info about how to do it? init monitors for dead processes and then will respawn them, which is why DJB uses it. currently, gentoo initscripts do not do this.
*** This bug has been marked as a duplicate of 28294 ***
