/ffx
or /ffxusr
respectively although there should be free memory left.pdflush
running on the system. This special daemon-process is responsible for handling the memory-writebacks and flash-handling. Thus when erasing large files it is presumable that it needs a couple of time until pdflush
has finished its work and you can use the whole flash-memory./ffx
has only 16MByte diskspace but I created a file with a total size larger then 16MByte. How is this possible./ffx
is using the so called JFFS2 which is capable of compressing data.jffs2_scan_eraseblock
message mean?~ $ dmesg ... jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00bbe0e8: 0xfd23 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00bbe0ec: 0xdf7f instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00bbe0f0: 0xd9ca instead ... ~ $
~ $ telnetd -l /bin/login -p 22
For an unprotected login at port 11 enter
~ $ telnetd -l /bin/ash -p 11
~ $ cat /proc/cpu/alignment User: 37 System: 0 Skipped: 0 Half: 0 Word: 0 Multi: 0 User faults: 0 (ignored)
For example a cast to unsigned short
of an odd character address leads to alignment faults.