Greetings. Regarding ramdisk.img: I recently discovered that my mac has 21 copies of this ramdisk.img file averaging 150 kb each; is it safe to delete these? (esp since I have no active android projects going on right now)
Thanks On Friday, February 20, 2009 9:12:20 PM UTC-5, MBethDev wrote: > > Hi, > > I'm new to Android development and recently I've been playing with the > emulator and the applications, etc, and overall just getting to know > the internals of the code. My main goal though is understanding the > porting aspect of it on an actual embedded device. > > Anyway, on to my question. I noticed that when building android it > creates three img files: ramdisk.img, system.img, and userdata.img. > Can someone give an explanation what these images are? My > understanding is that these images are *emulator-specific* images to > the ram, system, userdata, respectively on the emulator, but not > necessarily "generic" images for any android-capable phones. In other > words, is it possible (at all) to upload these same images to, say, a > G1 phone and expect the same behavior I see in the emulator to be on > the G1 phone (assuming of course I use a cross-compiler for that > target phone to build the *.img files). Or are these img files solely > for emulator-purposes only? > > I apologize if this is too elementary for you guys as I'm learning > along the way here. Any input about those img files are greatly > appreciated. > > Thanks. > > MBeth -- -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting --- You received this message because you are subscribed to the Google Groups "android-porting" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-porting+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
