Le mardi 26 janvier 2016 21:55:11 UTC+1, Adam Farden a écrit :
> recovery init.rc is actually really simple, you probably don't need a custom
> init.rc
> you can add what you need in init.recovery.[platform].rc and it will be
> picked up automatically.
>
> https://android.googlesource.com/platform/bootable/recovery/+/android-4.3_r1/etc/init.rc#1
Well, I've tried this approach before for custom init.rc in boot.img but don't
know if it's really working. All I can say is, if I don't add
init.[platform].rc to PRODUCT_COPY_FILES too, I'm not getting custom init.rc in
boot.img, but the default one (yep, TARGET_PROVIDES_INIT_RC flag was set).
So I fear this will be the same for recovery.img.
BTW, how do you deal with priorities? I mean, if you have directives in "on
early-init" section of how both init.recovery.[platform].rc and recovery's
default init.rc, are the ones from init.recovery.[platform].rc parsed before
the default ones? Or are all directives of all sections in
init.recovery.[platform].rc parsed before default init.rc? I'm asking this,
because the init.rc pulled from OEM recovery.img shows customization in this
file, not in init.recovery.[platform].rc (that doesn't exist).
Émeric
_______________________________________________
dev-fxos mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-fxos
