Quote:
Originally Posted by del4
What is this time drift issue I'm seeing mentioned? The only time-related issue I have experienced is that when I boot back into Windows after having run Android, my clock in WM is ahead by 7 hrs, as if the GMT offset (I'm at -7 GMT) has been lost? Is there a fix or a setting in WM I need to change to eliminate this from happening?
|
If you turn on automatic network time updates (somewhere in the phone settings), it should work around that.
Quote:
|
BTW, a noob question, I'm sure, but could someone clarify the meaning/purpose/role of each of the files in the current distribution? This may clear up for me (and hopefully others) which files could/should be replaced with each update...
|
I posted up an explanation of this on another site -- I'll repost it here. Might not be exactly what you're looking for, but it gives a bit of an overview:
Here's the breakdown. In unix systems, the file system is all organized around root. That is:
/
So... at boot, HaRET loads the kernel (zImage) and the initial ramdisk (initrd.gz), which has a lightweight filesystem on it, into memory. This allows the booting of linux to proceed, without having to interact with the block devices (sd card, in this case), which are not yet initialized. After the kernel and initrd have booted the hardware, then it's time for the actual / (root) filesystem to be mounted. (If you were to mount rootfs.img, you would see a number of initialization scripts, as well as standard linux directories (proc, bin, lib, dev, etc), some with files in them, some empty.) The init script in the rootfs, in turn, loads data.img (the userdata) as a rewriteable partition under /data, and system.sqsh (the Android code) as a read-only partition under /system. Then it calls the Android initialization routine, and that cool nexus one boot animation starts. The end.