cannot adb push init.rc

[pavan savoy]

Hi,

When I want to modify a service or add / remove something from init.rc, I do a adb pull init.rc, edit and modify it.
And expect upon reboot to work as expected because of the modification.

However almost all the time init.rc file is corrupted. I see a bunch of strange characters in the file.
Any reason why ?

--
--Pavan Savoy

[jairo martin]

How to do you push the init.rc back onto the root directory(/). The
root directory is read only.

Regards,
J

[David Turner]

init.rc is part of the ramdisk, you cannot modify it.

--
You received this message because you are subscribed to the Google Groups "android-platform" group.
To post to this group, send email to android-...@googlegroups.com.
To unsubscribe from this group, send email to android-platfo...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-platform?hl=en.

[David Turner]

On Fri, Mar 26, 2010 at 11:15 AM, David Turner <di...@android.com> wrote:

init.rc is part of the ramdisk, you cannot modify it.

To be more exact, what you should do is modify init.rc to include another script that will be located in a different location of the system partition, not the ramdisk.

You will then be able to modify the file at will with adb pull/push.

[pavan savoy]

On Fri, Mar 26, 2010 at 1:16 PM, David Turner <di...@android.com> wrote:

On Fri, Mar 26, 2010 at 11:15 AM, David Turner <di...@android.com> wrote:

init.rc is part of the ramdisk, you cannot modify it.

To be more exact, what you should do is modify init.rc to include another script that will be located in a different location of the system partition, not the ramdisk.

You will then be able to modify the file at will with adb pull/push.

Hnm, makes sense, although in my case there is no ramdisk, there is no system.img, since I am not using yaffs2.

So, is adb thinking it cannot push ? and is a part of ramdisk ?
or something un-usual happening on remounting it ?

Because I can still push other things to '/'
 

On Fri, Mar 26, 2010 at 10:03 AM, pavan savoy <pavan...@gmail.com> wrote:

Hi,

When I want to modify a service or add / remove something from init.rc, I do a adb pull init.rc, edit and modify it.
And expect upon reboot to work as expected because of the modification.

However almost all the time init.rc file is corrupted. I see a bunch of strange characters in the file.
Any reason why ?

--
--Pavan Savoy

--
You received this message because you are subscribed to the Google Groups "android-platform" group.
To post to this group, send email to android-...@googlegroups.com.
To unsubscribe from this group, send email to android-platfo...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-platform?hl=en.

--
You received this message because you are subscribed to the Google Groups "android-platform" group.
To post to this group, send email to android-...@googlegroups.com.
To unsubscribe from this group, send email to android-platfo...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-platform?hl=en.

--
--Pavan Savoy

[Tirtha Kanti Ghosh]

why dont u change your init.rc before building your images.

Normally, system/core/rootdir/init.rc for emulator.......

And every vendor provides their own init.rc...in general in vendor folder....

And as you said, you are not using system.img, are you using NFS or SD card for Android File System???

If, so then, u can just change init.rc there only.

regards,