by Stefan » Wed, 09 Feb 2011 22:34:03 GMT

Sponsored Links
 I'm not sure, maybe it's a dumb question, but anyway:

When I want to start Android, and I use the images from the
sdk I have to adjust the init.rc file. But what happens with the
init.goldfish.rc file which is in the same directory?

Shall I delete it and make my own init.<architecture>.rc file?

If yes, what shall I write into this file?




Re: init.<architecture>.rc

by Joerie de Gram » Thu, 10 Feb 2011 00:52:17 GMT


It's evaluated for the goldfish (emulator) board. It's not
architecture, but board specific. On bootup it attempts to run
init.<boardname>.rc, where boardname is the kernel supplied board
name, lowercase (and if it contains spaces, up to the first space).

Anything to be performed at init, specific to your board.



Sponsored Links

Re: init.<architecture>.rc

by Stefan » Fri, 11 Feb 2011 17:19:40 GMT

 > It's not architecture, but board specific.

So, I have to delete the goldfish-init and write my board specific

What do I have to write into e.g. init.myOwnBoard.rc if I "only"
want to start Android as I can see it running on the emulator?

Do I have to edit the normal init.rc too for this?

Would you be so kind and give me an example for a running init.XXX.rc-


Re: Re: init.<architecture>.rc

by David Turner » Fri, 11 Feb 2011 21:58:32 GMT


board-specific initialization.
It could defining new services, mounting partitions, defining system
properties, whatever.

Apart from that, consider it an extension of init.rc

It really depends on the customization you have done.


I.e. if you modify the platform in significant ways, you would modify
init.rc to reflect that.
You could then use the same platform to build various product configurations
(each corresponding to a different board), and put their own customizations
in init.<board1>.rc, init.<board2>.rc, etc...

Of course, if all you do is developing a single product/board, you can just
modifiy init.rc instead.

Would you be so kind and give me an example for a running init.XXX.rc-


Other Threads

1. using mknod() to create named pipes

Hi all,

I am having some difficulties using the mknod() function to create
named pipes. I am currently porting an OMX Resource Manager which
relies heavily on intra-process communication.

I was wondering if there are any differences in the mknod() used in
Android vs. the standard implementation?

Also, in this same component I have been appending the PID (obtained
from getpid()) to the named pipe's name. For example "/dev/
pipename_790" is created. I create one of these pipes for each other
registered component in the system. It appears that this is causing
some problems and I have noticed that the same PID is being used for
each component. Can someone describe how process are started and which
tasks will get different PID's in the Android environment?

Another interesting point is that I can create pipes using simple
names, i.e. only the pipes with the PID appended fail to be created...

Any info will be helpful!


2. Como descargarse proyectos free de Android Market

estoy interesada en descargarme o ver el codigo de alguna aplicacion
de Android Market (free),
alguien sabe si se puede hacer eso??

Un saludo y gracias

3. Which cpu?

4. How to add a new library to android source

5. running hello world application

6. ALSA Waiting for sevice media.audio_flinger

7. Getting driving directions from application