This is unrelated to the sysvinit package. Migration of config files into /etc/writable is handled by a touch-specific overlay component.
However, I see no reason that we want to support making /etc/rc.local writable on a read-only touch image. This is a last-resort mechanism for modifying the system startup, not one that we want to endorse in the phone images; and the specific example you give, of disabling bluetooth, is one that will be handled by different means.
And any "usual instructions" that tell users to run 'service bluetooth stop' in /etc/rc.local are absolutely wrong.
This is unrelated to the sysvinit package. Migration of config files into /etc/writable is handled by a touch-specific overlay component.
However, I see no reason that we want to support making /etc/rc.local writable on a read-only touch image. This is a last-resort mechanism for modifying the system startup, not one that we want to endorse in the phone images; and the specific example you give, of disabling bluetooth, is one that will be handled by different means.
And any "usual instructions" that tell users to run 'service bluetooth stop' in /etc/rc.local are absolutely wrong.