> On Jan 13, 2015, at 4:25 PM, Sascha Hauer <s.hauer@xxxxxxxxxxxxxx> wrote: > > On Tue, Jan 13, 2015 at 07:21:09AM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote: >> as we now will use symlink on /env/rc.d to specify init order >> >> the script will be store in /env/init >> >> so any board can overwrite them or add script that need to run before a >> default one > > Boards can overwrite scripts without links. Numbering the files seems > good because it makes the execution order more predictable and easier to > put a script between two other scripts. > > But why links? On Linux PCs this allows to separate distribution > provided scripts from their actual (site specific) execution. Also > the same scripts can be executed from different runlevels. > On barebox I see no good reason for links. There is only one runlevel > in barebox and if I don't want to execute a script I can just remove it. > Runtime change I’ve a board where I need to change the init order based on the board revision so the symlink allow this and this will allow also to have the same script at different order based on the board requirement. Best Regards, J. > 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
