it still is re-created empty, unless you use the -cache <filepath> option (in this case, the file is re-used, and created if it doesn't exist yet).
On Thu, Jan 15, 2009 at 12:18 PM, Jean-Baptiste Queru <[email protected]>wrote: > > Is it still re-created empty? I thought we had made it persistent so > that I could test the download manager's ability to resume downloads > across reboots... > > JBQ > > On Wed, Jan 14, 2009 at 11:25 PM, David Turner <[email protected]> wrote: > > for the record, in the current emulator, the /cache partition is > re-created > > empty on each new emulator start, so it's normal you don't see anything > > here. > > for the record, a future release of the SDK will feature "virtual > machines", > > where each VM corresponds to a directory holding persistent disk images, > > including a cache.img disk image. > > > > On Wed, Jan 14, 2009 at 9:53 PM, twebb <[email protected]> wrote: > >> > >> In using the android emulator, I see that the /cache volume is 64MB > >> but I don't ever see any files in it. For products that don't have > >> extra flash memory to spare, that seems like a lot of memory to > >> allocate for apparently little or no use. Is /cache used for > >> anything, and if so, are there general guidelines for how much flash > >> memory (perhaps as a percent of total flash memory) should be > >> allocated to /cache? > >> > >> Thanks, > >> twebb > >> > >> > > > > > > > > > > > > > -- > Jean-Baptiste M. "JBQ" Queru > Android Engineer, Google. > > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
