Quote:
|
Originally Posted by DHer
ok, there seems to be a script to flash the file system, check out /oldroot/linuxrc
|
Yes, if you check bin of oldroot you will see that bin/init is simply a link to linuxrc
Now the launching process (2.4) is not trivial. dmesg tels that
Kernel command line: root=/dev/tffsa1 rw console=ttyS2,115200 mem=64M
while oldroot is ttfsa2
Actually the partition of ttfs is
tffs: TrueFFS driver 632.70
tffs: Socket 0: type 7 0x9876 chips 4 floors 4 size 256M in addr 0xc8000 ebs 0x10000
tffs: Device 0x0: size 0xea00000 HW sector 0x200 (recommended 0x800)
tffs: Registered module at major 100
Partition check:
tffsa: tffsa1 tffsa2 tffsa3 < tffsa5 tffsa6 tffsa7 >
tffs: partition 0x1 size 0x305800 start offset 0x6800
tffs: partition 0x2 size 0x4884000 start offset 0x30c000
tffs: partition 0x3 size 0x400 start offset 0x4b90000
tffs: partition 0x5 size 0x1d39800 start offset 0x4b96800
tffs: partition 0x6 size 0x803f800 start offset 0x68d6800
tffs: partition 0x7 size 0xe3800 start offset 0xe91c800
According mount,
partition 2 is mounted as / (and /old-root, but this is somehow wrong),
partition 5 is mounted as /mnt/protected (it contains the images, when updating)
partition 6 as /mnt/free (and it is a vfat, to store content)
partition 7 as /mnt/settings
but the content of /old-root when I look at it seems to be equal to partition 1. I think that mount is a bit confused by the pivot_root procedures.