Again, I made a diagram for hive-base registry.
Key points of this diagram:
- Three kinds of HIVE in mobile system
- Filesys,dll will mount Boot.hv from ROM first
- Boot.hv used to pre-load root partition (storage driver, marked as bootable) and locate system hive position (HKLM\Init\SystemHive)
- Default.hv is the ROM portion of system hive
- System.hv stores the changes of default.hv
- Again, current users user.hv will be located by system hive
- User.hv in root file system stores the changes of user.hv in ROM image
- Whatever system hive or user hive, system will store ROM portion’s MD5 checksum as signature
- When filesys.dll load system hive and user hive from root file system, the signature will be checked. If signature not match, the system.hv and user.hv in file system will be delete
- The signature mechanism cannot be disabled
- There are OEM I/O controls can force system to delete system.hv and user.hv in root file system
突然想到，解釋這麼落落長，那不就代表這張圖沒有用…
沒有留言:
張貼留言