Turbo Quattro

отредактироавл. У меня на ноуте кнопки козьи, то по два три раза жмёшь, что бы букву написать , то сдваевает))) Я на крапал по аглицки- почти

[quote="FRUITCAT"]allmost )))[/quote] Котяра ты чего написал... Гугл не знает... А нашему брату из Азии докладываю - И смотреть парад и участвовать ... и если нужно всем пизды дадим... :bb: :az:

almost )))

Did everyone to watch the powerful Russian military parade？？？？

I use the command : file efs-persist.img

respond：“efs-persist.img: data ”

Looks like the data image files

Then used the command: mount -o loop efs-persist.img /fs

Looks like the command is incorrect

There are also exploring the solution of this problem alone，Maybe he and I were talking about the same thing
[url]http://reverseengineering.stackexchange.com/questions/8372/unpack-qnx-img-files[/url]
[quote]I am currently investigating firmware of an embedded system (car navigation) and have identified the OS as QNX.

The firmware has .ifs files which I was able to extract/unpack using QNX dumpifs tool and .img files. The .img files do not appear to be compressed, is there a file format or dump tool for QNX .img files?

/edit: some extra information file -sL file.img reports x86 boot sector Mount attempt in Ubuntu mount -t qnx6 ./file.img -o loop/dev/loop1,blocksize=512 /media/qnx fails with wrong fs type, bad option, bad superblock on /dev/loop1

dmesg reports qnx4: wrong fsid in superblock or qnx6: invalid mount operation

cat /proc/filesystems reports both qnx4 and qnx6[/quote]