On Fri, Apr 26, 2019 at 02:37:05PM +0200, Roland Hieber wrote: > Hi Sascha, > > small note: one might want to interrupt long-running processes during > the init sequence, e.g. if an init script contains a "dhcp" call or does > some NFS mount, but the board is currently not connected to the network. Do you have a better example? You shouldn't run dhcp in an init script. > Now it is no longer possible to interrupt such processes, even when > global.autoboot_abort_key is set to anything else than "ctrl-c". Was > this use case considered? You can't abort the init sequence, but you can prevent it from being executed at all. So when you are in such a situation, reset the board and use ctrl-c or 'q' to not run the init sequence. Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
