Quote:
Originally Posted by Mono
EDIT:
As I do not understand Linux, there might be also possibility that physical partition where are user data is somehow "mounted" to OS ("firmware") file structure. And so it seems like being in one common partition. Linux geeks would have to say the final testament.  |
That is the case.
(I'm a 7 years Linux user)
The folder structure is meaningless in terms of partitioning. All the 0 bytes folders you see in the zip are populated at runtime. And every folder can be mounted to basically any physical partition(s) available in the system (actually, it's the viceversa). Each of the folders can be a physical partition or all the folders could belong to just one partition. It depends on the system, really.
The fact that you never see the entire root filesystem ("folder structure" as you call it) containing firmware files once you connect the Onyx to the PC tells (not an assumption at all) that they are on physical partition other than "internal storage" (aka user data). And that one is never touched by anything other than fw upgrade.
What Onyx call "Format Memory" corresponds to resetting the filesystem on the user data partition, as every device in the world that provides an "Erase Memory" function does.
When 1.7 carries over the partitions set-up by an 1.6 fw, everything's fine.
When 1.7 makes the partitioning itself, it just seems to provide the plain wrong size to the command parameter...
Given that the sizes of the partitions are respectively 3.2 (created on 1.6, correct) and 2.1 GB (on 1.7, wrong), that could be down to a simple typo in the fw update scripts...
