hello, i'm trying to switch to simpleinit but can't find clear (and updated) information. my problem is that i don't understand how simpleinit interacts with shutdown and how it carries the information further to the scripts. the common way would be to switch the runlevel and start the scripts in the apropriate subfolder with "stop" or "reboot" in the commandline. however, because simpleinit only rolls back what is already registered by need, the reboot and the halt script-parts must already be considered in the boot script(s). am i right here? otherwise i don't understand how to trigger an extra reboot or halt script - and how to cover these from being executed with the others at startup? this leads me to the question if initctl really starts every registered script to ask it for a halt or a reboot service? this takes a lot of time, i think. wouldn't it be better if need could register a script for services like: "need -s start -s stop -s reboot script"? best is when every script re-registers itself appropriately. because need doesn't start scripts twice, this should work out. i also don't understand the need for both the fileprefix and the INIT_PATH variable in inittab. IMHO the inittab file could be made obsolete by: 1. expecting a default bootscript or boot directory (as found) 2. sending commandlines like for the ttys and finalprog (the names of the variables are strange too!) to initctl via another prog (like execute) and from the scripts. this would also gain more flexibility. last but not least: is there a restart option? many thanks, dennis heuer -- To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
